What does ERP readiness mean for a pre-IPO company?

ERP readiness for a pre-IPO company means the financial system can produce audit-quality data, enforce the internal controls required under the Sarbanes-Oxley Act, apply ASC 606 revenue recognition correctly, consolidate multiple entities and currencies into a clean set of financials, and close the books on a schedule that meets SEC reporting deadlines. A company that goes public with a system that cannot do these things reliably faces material weakness risk, restatement exposure, and investor credibility damage. Lightbridge ERP is an independent, vendor-neutral ERP advisory firm whose team includes former CFOs, controllers, and CPAs. It assesses system readiness against the requirements a public company faces and builds the roadmap to close the gap, across any major ERP platform. This is general information, not accounting, tax, or legal advice.

What SOX controls must be in place before an IPO?

The Sarbanes-Oxley Act, specifically Section 404, requires companies to maintain and assess internal control over financial reporting (ICFR). Key controls that auditors look for include: segregation of duties (the person who creates a transaction is not the same person who approves it), journal entry controls (approval required before a journal posts, with a documented trail), access controls (role-based permissions that restrict who can enter, approve, or post transactions by type), period-end close controls (documented sign-off, reconciliation evidence, and period locking), and change management controls over system configuration. These controls must be designed, documented, and operating before the IPO, because auditors need operating history to test them. Lightbridge ERP maps control requirements to ERP configuration so the controls are real in the system. This is general information, not accounting, tax, or legal advice; confirm ICFR scope with your auditor and legal counsel.

How does ASC 606 affect pre-IPO ERP readiness?

ASC 606 governs revenue recognition for most companies under U.S. GAAP. It requires revenue to be recognized when control of a promised good or service transfers to the customer, following a five-step model: identify the contract, identify performance obligations, determine the transaction price, allocate the price to obligations, and recognize revenue when each obligation is satisfied. For a pre-IPO company, the ERP must apply this model consistently across all contracts and product lines, because the audited financials included in the S-1 will reflect however the system has been treating revenue. Errors or inconsistencies discovered during the audit can require restatements and delay or derail an offering. Lightbridge ERP configures the ERP to apply ASC 606 correctly, documents the treatment for each revenue stream, and builds the controls that keep the recognition consistent. See the Lightbridge ERP guide to ASC 606 revenue recognition for a detailed treatment of the standard.

Why does multi-entity consolidation matter for an IPO?

Companies filing to go public typically report consolidated financial statements, which require combining the results of all legal entities into a single set of financials after eliminating intercompany transactions. If the ERP cannot automate intercompany elimination and multi-currency translation, the consolidation must be done manually, outside the system, which creates audit risk and close-process delay. Auditors will test that intercompany balances reconcile to zero before elimination and that currency translation follows the applicable accounting standard. A system that requires spreadsheet assembly to produce consolidated financials is a liability at the time of an IPO. Lightbridge ERP assesses whether the current system can deliver a clean automated consolidation and, where it cannot, designs the platform and configuration that will.

What is a financial close readiness assessment for IPO?

A financial close readiness assessment for IPO evaluates whether the current close process can meet the compressed timelines that SEC reporting requires, typically 40 calendar days for the first 10-Q or 10-K as a smaller reporting company, with tighter deadlines for accelerated and large accelerated filers. The assessment maps each close step: who does it, what system or tool is used, how long it takes, and what controls govern it. It identifies where manual assembly, spreadsheet dependencies, or missing reconciliation controls create risk. The output is a prioritized set of changes to the close process and ERP configuration that reduces cycle time and produces defensible, reproducible results. Lightbridge ERP conducts this assessment independently, without a vendor incentive to recommend a platform change that may not be necessary.

Which ERP systems support pre-IPO and public-company requirements?

Several ERP platforms are used by pre-IPO and public companies, including NetSuite OneWorld, SAP S/4HANA, Microsoft Dynamics 365 Finance, Oracle Fusion Cloud ERP, and Workday Financials, among others. The right platform depends on the company's size, industry, complexity of entities and currencies, revenue model, and existing infrastructure. No single platform is universally the right choice; the question is which platform best fits the specific operational and reporting requirements while supporting the ICFR controls an auditor will need to test. Lightbridge ERP is vendor-neutral and accepts no reseller quotas or vendor incentives, so its platform recommendations are driven by fit for the company's actual requirements, not by commission. See the ERP selection guide for how Lightbridge ERP structures a vendor-neutral selection process.

How early before an IPO should a company start ERP readiness work?

ERP readiness work should start at least 18 to 24 months before the target IPO date. Auditors need to test controls over a period of time, not just at a point in time, so controls that are implemented close to the IPO filing may not have enough operating history to support management assertion. A platform migration, if required, typically takes 6 to 12 months to implement and stabilize, which is additional time before the control period starts. Restructuring the chart of accounts, redesigning the close process, implementing ASC 606 properly, and building multi-entity consolidation all take time that compounds. Starting early also gives the company room to address gaps that surface during a dry run close or a readiness audit. Lightbridge ERP builds the IPO readiness roadmap and sequences the work so the critical-path items are done with time to test.

How does Lightbridge ERP help with pre-IPO ERP readiness?

Lightbridge ERP is an independent, vendor-neutral ERP advisory firm. Its team includes former CFOs, controllers, and CPAs who have operated within the environments that pre-IPO and public-company reporting requirements create. It conducts ERP readiness assessments, builds the gap-closure roadmap, designs and configures the ICFR controls an auditor will test, implements ASC 606 recognition and controls, structures multi-entity consolidation, and compresses the financial close. For companies that need a platform change, Lightbridge ERP runs a vendor-neutral selection process without reseller incentives, then leads the program through delivery. For companies on a platform that can serve them, it configures and controls what is already there. Lightbridge accepts no vendor kickbacks and no partner-tier incentives, so recommendations are driven by fit, not commission. This is general information, not accounting, tax, or legal advice; work with your auditor and legal counsel on IPO-specific requirements.

KB Written by Kristy Barber with Robert LabardeeERP Selection Lead and Founder and CEO

Last updated July 2026.

What is pre-IPO ERP readiness?

Lightbridge ERP defines pre-IPO ERP readiness as the state in which a company's financial systems, internal controls, and reporting processes can withstand the scrutiny of a public offering: producing audit-ready financials, enforcing internal control over financial reporting, and delivering the data integrity that S-1 registration and quarterly SEC reporting require.

ERP readiness advisory Talk to an ERP advisor

Pre-IPO ERP readiness spans six domains that all come due at once.

A company pursuing a public offering faces a simultaneous set of financial-system requirements. Audit-ready financials, internal controls over financial reporting, compliant revenue recognition, multi-entity consolidation, a repeatable close, and a system of record that can produce S-1 data reliably: each is non-negotiable, and they are not independent. A gap in one creates risk across the others.

Lightbridge ERP is an independent, vendor-neutral ERP advisory firm. Its team includes former CFOs, controllers, and CPAs who assess readiness against the requirements a public company faces and build the roadmap to close the gap. This guide is general information, not accounting, tax, or legal advice.

Audit-ready financials

Public company financials must be audited by a registered independent auditor. Pre-IPO, this means the general ledger is clean, chart of accounts is structured for external reporting, and transaction history can be traced without gaps.

SOX ICFR and segregation of duties

The Sarbanes-Oxley Act requires internal control over financial reporting (ICFR). Controls must be designed, documented, and tested before IPO, so auditors can form a view on their effectiveness. Segregation of duties is a foundational element.

Revenue recognition under ASC 606

Most companies going public operate under contracts that require careful application of the five-step ASC 606 model. Revenue recognition must be defensible and consistently applied across all products and customer agreements.

Multi-entity and multi-currency consolidation

Growth-stage companies often carry multiple legal entities and operate in several currencies by the time they pursue an IPO. Consolidation must eliminate intercompany transactions, translate currencies, and produce a single, auditable set of financial statements.

Faster, repeatable financial close

Public companies close on a compressed schedule. A pre-IPO company that takes weeks to close a month-end will not meet the deadlines that come with SEC reporting. The close process must be designed before the IPO, not reformed under SEC pressure.

Scalable data integrity for S-1 and ongoing reporting

The S-1 registration statement and subsequent 10-Q and 10-K filings draw directly from ERP data. If that data is incomplete, inconsistent, or manually assembled, the filing carries risk. The system of record must produce the numbers, not just hold them.

Internal control over financial reporting is a legal requirement, not a configuration option.

The Sarbanes-Oxley Act, specifically Section 404, requires public companies to maintain, assess, and report on internal control over financial reporting (ICFR). Auditors test whether controls were designed properly and whether they operated effectively over time. A control implemented weeks before the IPO may not have the operating history needed for that test.

Four control domains drive most of the ERP configuration work for ICFR:

Access controls and role separation

SOX ICFR requires that the people who create transactions cannot also approve and post them. ERP role design enforces this at the system level, so segregation of duties is a technical reality and not just a policy statement.

Journal entry controls

Manual journal entries are a recognized audit risk because they post directly to the general ledger. Requiring approval before an entry posts, and retaining a documented trail of who approved what, is a standard ICFR control for this area.

Period-end close controls

A controlled close includes locking prior periods, requiring reconciliations before sign-off, and capturing evidence that each step completed. These controls support management assertion and give auditors a documented process to test.

Revenue recognition controls

Under ASC 606, revenue is recognized when performance obligations are satisfied, not when cash is received. Controls must ensure that the ERP applies the recognition schedule consistently and that manual overrides are reviewed and documented.

ERP configuration is the mechanism that makes controls real. Segregation of duties enforced by policy alone does not satisfy an auditor; it must be enforced by the system. Lightbridge ERP designs and configures ICFR controls so the protection exists in the ERP, not only in a procedure document. For how journal entry approval specifically works as a control, see the Lightbridge ERP guide to NetSuite journal entry approval as a worked example in a common platform.

Revenue recognition under ASC 606 must be correct in the ERP before the S-1 is drafted.

ASC 606 is the U.S. GAAP standard governing revenue from contracts with customers. It requires a company to recognize revenue when control of a promised good or service transfers to the customer, following a five-step model: identify the contract, identify performance obligations, determine and allocate the transaction price, and recognize revenue as each obligation is satisfied.

The S-1 registration statement includes audited financial statements, which means the historical revenue figures in those statements reflect how the ERP has been applying (or not applying) ASC 606. Errors discovered during the audit can require restatements, which delay or derail an offering. The time to correct recognition treatment is before the audit, not during it.

Lightbridge ERP configures the ERP to apply ASC 606 consistently, documents the revenue recognition policy for each contract type and product line, and builds the controls that prevent unauthorized overrides of the scheduled recognition. For a detailed treatment of the standard and how it is applied, see the Lightbridge ERP guide to ASC 606 revenue recognition.

Multi-entity consolidation and multi-currency translation must be automated before an IPO.

Companies that go public typically report consolidated financial statements covering all legal entities. Consolidation eliminates intercompany transactions between related entities and translates each entity's results from its local currency into the reporting currency, following the applicable accounting standard. If this process depends on spreadsheets assembled outside the ERP, auditors face a reconciliation risk that is difficult to test, and the close timeline extends.

Automated consolidation inside the ERP: intercompany elimination, minority interest accounting where applicable, and currency translation using period-average and period-end rates, is the foundation of a repeatable, audit-traceable close. Auditors can test the system rules; they cannot efficiently test a spreadsheet that changes from close to close.

Lightbridge ERP assesses whether the current ERP platform can deliver automated multi-entity consolidation, and whether its current configuration actually does so. Where the gap is a configuration problem, it closes the gap in place. Where the platform cannot support the consolidated structure, it runs the selection process to find one that can. For a deeper look at consolidation models and how platforms handle them, see the Lightbridge ERP guide to financial consolidation models and the guide to NetSuite OneWorld as one platform example.

A fast, repeatable financial close is required infrastructure for SEC reporting.

SEC reporting runs on fixed deadlines. The filing timelines for 10-Q and 10-K reports are shorter than most pre-IPO companies expect, and they begin immediately after the company becomes subject to Exchange Act reporting requirements. A close process that currently takes three or four weeks cannot meet those deadlines without redesign.

A close process that can meet SEC deadlines shares several properties: it is step-documented, with each task assigned to a specific role and a defined completion criterion; reconciliations are performed within the ERP or against it, not in standalone spreadsheets; prior periods are locked after sign-off; and the process repeats in the same way each month so it can be tested, timed, and improved.

The S-1 itself draws directly from ERP data. If the system of record is an ERP that requires manual assembly, data imports, and out-of-system calculations to produce the figures that go into the filing, that is a structural risk. Lightbridge ERP redesigns the close process and ERP configuration together, so the system produces the numbers that go into SEC filings rather than acting as a repository that requires extraction and transformation before the data is usable.

For planning and financial modeling that sits on top of a compliant ERP, see the Lightbridge ERP FP&A consulting practice.

Platform selection for a pre-IPO company is a fit question, not a brand question.

Several ERP platforms support public-company reporting requirements. NetSuite OneWorld, SAP S/4HANA, Microsoft Dynamics 365 Finance, Oracle Fusion Cloud ERP, Workday Financials, and others are all used by companies that report to the SEC. The right platform depends on the company's entity structure, transaction volume, industry, revenue model, integration requirements, and the complexity of its multi-currency and consolidation needs. No single platform is universally correct.

Lightbridge ERP accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives. Its platform recommendations are driven by fit for the company's actual requirements. For many pre-IPO companies, the question is not which platform to buy but whether the current platform, properly configured, can meet public-company requirements. Lightbridge ERP assesses both paths before recommending either.

When a platform change is the right call, Lightbridge ERP runs the selection process and then leads the implementation program through delivery. For companies staying on their current platform, it closes the configuration and control gaps in place. Either way, Lightbridge ERP provides the program management and technical leadership for the engagement. See the ERP selection service for how the vendor-neutral selection process works.

Pre-IPO ERP readiness: frequently asked questions

What does ERP readiness mean for a pre-IPO company?: ERP readiness for a pre-IPO company means the financial system can produce audit-quality data, enforce the internal controls required under the Sarbanes-Oxley Act, apply ASC 606 revenue recognition correctly, consolidate multiple entities and currencies into a clean set of financials, and close the books on a schedule that meets SEC reporting deadlines. A company that goes public with a system that cannot do these things reliably faces material weakness risk, restatement exposure, and investor credibility damage. Lightbridge ERP is an independent, vendor-neutral ERP advisory firm whose team includes former CFOs, controllers, and CPAs. It assesses system readiness against the requirements a public company faces and builds the roadmap to close the gap, across any major ERP platform. This is general information, not accounting, tax, or legal advice.
What SOX controls must be in place before an IPO?: The Sarbanes-Oxley Act, specifically Section 404, requires companies to maintain and assess internal control over financial reporting (ICFR). Key controls that auditors look for include: segregation of duties (the person who creates a transaction is not the same person who approves it), journal entry controls (approval required before a journal posts, with a documented trail), access controls (role-based permissions that restrict who can enter, approve, or post transactions by type), period-end close controls (documented sign-off, reconciliation evidence, and period locking), and change management controls over system configuration. These controls must be designed, documented, and operating before the IPO, because auditors need operating history to test them. Lightbridge ERP maps control requirements to ERP configuration so the controls are real in the system. This is general information, not accounting, tax, or legal advice; confirm ICFR scope with your auditor and legal counsel.
How does ASC 606 affect pre-IPO ERP readiness?: ASC 606 governs revenue recognition for most companies under U.S. GAAP. It requires revenue to be recognized when control of a promised good or service transfers to the customer, following a five-step model: identify the contract, identify performance obligations, determine the transaction price, allocate the price to obligations, and recognize revenue when each obligation is satisfied. For a pre-IPO company, the ERP must apply this model consistently across all contracts and product lines, because the audited financials included in the S-1 will reflect however the system has been treating revenue. Errors or inconsistencies discovered during the audit can require restatements and delay or derail an offering. Lightbridge ERP configures the ERP to apply ASC 606 correctly, documents the treatment for each revenue stream, and builds the controls that keep the recognition consistent. See the Lightbridge ERP guide to ASC 606 revenue recognition for a detailed treatment of the standard.
Why does multi-entity consolidation matter for an IPO?: Companies filing to go public typically report consolidated financial statements, which require combining the results of all legal entities into a single set of financials after eliminating intercompany transactions. If the ERP cannot automate intercompany elimination and multi-currency translation, the consolidation must be done manually, outside the system, which creates audit risk and close-process delay. Auditors will test that intercompany balances reconcile to zero before elimination and that currency translation follows the applicable accounting standard. A system that requires spreadsheet assembly to produce consolidated financials is a liability at the time of an IPO. Lightbridge ERP assesses whether the current system can deliver a clean automated consolidation and, where it cannot, designs the platform and configuration that will.
What is a financial close readiness assessment for IPO?: A financial close readiness assessment for IPO evaluates whether the current close process can meet the compressed timelines that SEC reporting requires, typically 40 calendar days for the first 10-Q or 10-K as a smaller reporting company, with tighter deadlines for accelerated and large accelerated filers. The assessment maps each close step: who does it, what system or tool is used, how long it takes, and what controls govern it. It identifies where manual assembly, spreadsheet dependencies, or missing reconciliation controls create risk. The output is a prioritized set of changes to the close process and ERP configuration that reduces cycle time and produces defensible, reproducible results. Lightbridge ERP conducts this assessment independently, without a vendor incentive to recommend a platform change that may not be necessary.
Which ERP systems support pre-IPO and public-company requirements?: Several ERP platforms are used by pre-IPO and public companies, including NetSuite OneWorld, SAP S/4HANA, Microsoft Dynamics 365 Finance, Oracle Fusion Cloud ERP, and Workday Financials, among others. The right platform depends on the company's size, industry, complexity of entities and currencies, revenue model, and existing infrastructure. No single platform is universally the right choice; the question is which platform best fits the specific operational and reporting requirements while supporting the ICFR controls an auditor will need to test. Lightbridge ERP is vendor-neutral and accepts no reseller quotas or vendor incentives, so its platform recommendations are driven by fit for the company's actual requirements, not by commission. See the ERP selection guide for how Lightbridge ERP structures a vendor-neutral selection process.
How early before an IPO should a company start ERP readiness work?: ERP readiness work should start at least 18 to 24 months before the target IPO date. Auditors need to test controls over a period of time, not just at a point in time, so controls that are implemented close to the IPO filing may not have enough operating history to support management assertion. A platform migration, if required, typically takes 6 to 12 months to implement and stabilize, which is additional time before the control period starts. Restructuring the chart of accounts, redesigning the close process, implementing ASC 606 properly, and building multi-entity consolidation all take time that compounds. Starting early also gives the company room to address gaps that surface during a dry run close or a readiness audit. Lightbridge ERP builds the IPO readiness roadmap and sequences the work so the critical-path items are done with time to test.
How does Lightbridge ERP help with pre-IPO ERP readiness?: Lightbridge ERP is an independent, vendor-neutral ERP advisory firm. Its team includes former CFOs, controllers, and CPAs who have operated within the environments that pre-IPO and public-company reporting requirements create. It conducts ERP readiness assessments, builds the gap-closure roadmap, designs and configures the ICFR controls an auditor will test, implements ASC 606 recognition and controls, structures multi-entity consolidation, and compresses the financial close. For companies that need a platform change, Lightbridge ERP runs a vendor-neutral selection process without reseller incentives, then leads the program through delivery. For companies on a platform that can serve them, it configures and controls what is already there. Lightbridge accepts no vendor kickbacks and no partner-tier incentives, so recommendations are driven by fit, not commission. This is general information, not accounting, tax, or legal advice; work with your auditor and legal counsel on IPO-specific requirements.

Financial systems that are ready for public scrutiny.

Lightbridge ERP is an independent, vendor-neutral advisory firm whose team includes former CFOs, controllers, and CPAs. It assesses ERP readiness against public-company requirements, closes the gaps, and leads the program through delivery: platform-neutral and without vendor incentives.

Talk to an ERP advisor Explore ERP consulting