SOX Readiness for Pre-IPO and Newly Public Companies

Companies going public must establish internal control over financial reporting (ICFR). Management's Section 404(a) assessment is generally first required in the second annual report after an IPO, and auditor attestation under Section 404(b) applies to accelerated and large accelerated filers that are not emerging growth companies. A readiness phase plus a dry-run testing cycle is the most reliable path.

An IPO changes a company's relationship with internal control overnight. Investors expect reliable financial reporting, auditors scrutinize controls during the offering process, and the Sarbanes-Oxley Act imposes ongoing requirements on management. The companies that navigate this well start early and scope smart.

What SOX requires — and when

Section 302 requires the CEO and CFO to certify each quarterly and annual report, including statements about disclosure controls and procedures. Certifications begin with the first periodic report after the IPO.

Section 404(a) requires management to assess and report on the effectiveness of internal control over financial reporting (ICFR). Newly public companies generally aren't required to include management's assessment until their second annual report after going public.

Section 404(b) requires the company's external auditor to attest to the effectiveness of ICFR. It applies to accelerated and large accelerated filers. Emerging growth companies (EGCs) are exempt for up to five years, and companies that qualify as smaller reporting companies with less than $100 million in annual revenue are generally not accelerated filers.

Timing exemptions don't mean controls can wait. Material weaknesses identified during the IPO audit may need to be disclosed, and investors pay attention.

A practical readiness roadmap

Phase 1: Assess and plan

  • Evaluate the financial close and reporting process — the most common source of material weaknesses for new public companies
  • Identify technical accounting and SEC reporting capabilities needed
  • Assess IT systems, especially ERP, billing and revenue systems
  • Build a roadmap and budget for the program

Phase 2: Scope top-down

Use a top-down, risk-based approach:

  1. Identify significant accounts and disclosures based on materiality and risk
  2. Map them to significant processes and the systems that support them
  3. Identify what could go wrong in each process
  4. Select the key controls that address those risks

Resist the urge to document every control. A focused set of key controls is easier to operate, test and sustain.

Phase 3: Document and design

Develop process narratives or flowcharts and a risk and control matrix (RCM). Close design gaps — common ones include formal account reconciliation review, journal entry controls, segregation of duties and review controls with sufficient precision.

Phase 4: Fix the ITGCs

IT general controls over access, change management and operations support every automated control and system report. First-year programs frequently struggle with user access reviews, privileged access and service organization SOC reports. Address them early.

Phase 5: Dry-run testing

Perform a full cycle of design and operating effectiveness testing before the first required assessment. A dry run reveals controls that don't operate as designed, evidence that isn't retained and owners who don't understand their responsibilities — while there's still time to fix them.

Phase 6: Sustain

Transition the program to owners with clear accountability, a testing calendar, deficiency tracking and periodic reporting to the audit committee. Look for opportunities to automate controls and evidence over time.

Working with your external auditor

Coordinate early. Share your scoping, RCM format and testing approach so the auditor can plan efficiently and, where appropriate, consider the work of others. Your auditor can't design your controls, but alignment on approach avoids surprises.

The bottom line

SOX readiness is a project with a long tail. Start with the close and the ITGCs, scope top-down to the controls that matter, test before it counts and build a program your team can sustain long after the IPO.

Frequently asked questions

When does SOX 302 certification start?

CEO and CFO certifications under Section 302 begin with the first periodic report after the IPO, which means disclosure controls and procedures need to be in place at the time of listing.

What framework should our SOX program use?

Most U.S. public companies evaluate ICFR using COSO's Internal Control — Integrated Framework (2013).

Can we wait until after the IPO to start SOX work?

You can, but it's risky. Material weaknesses identified during the IPO process may need to be disclosed in the registration statement, and remediation takes time.

This article is for general information only and does not constitute legal, accounting or other professional advice. Requirements change; consult the cited sources and a qualified advisor about your specific situation.

Formos Consulting Risk, compliance, cybersecurity and transformation advisors

Keep reading

Related insights

All insights

Let’s talk about what you need.

Tell us where you are and where you need to be. A senior member of our team will follow up to talk through options.