SOX 404(b): Requirements, Exemptions, and Audit Process

SOX 404(b) compliance means having your company’s independent external auditor examine your internal controls over financial reporting and issue a formal opinion on whether those controls are effective. It applies to accelerated filers and large accelerated filers, and the auditor’s work is independent testing, not a review of what management already did. The obligation sits alongside management’s own annual assessment under Section 404(a), but it is the auditor’s separate opinion that carries the greatest weight with investors and the SEC.

What Section 404(b) Requires

Section 404 of the Sarbanes-Oxley Act has two parts. Section 404(a) requires management to assess the effectiveness of internal controls over financial reporting (ICFR) each year and include that assessment in the annual Form 10-K. Section 404(b) requires the company’s registered public accounting firm to independently attest to and report on management’s assessment, following standards issued by the Public Company Accounting Oversight Board. The attestation cannot be treated as a separate engagement from the financial statement audit.

The practical distinction matters. Under 404(a), management designs, documents, and tests its own controls, then writes a report saying whether those controls work. Under 404(b), the external auditor runs independent tests on those same controls and issues a separate opinion. If the auditor disagrees with management or finds problems management missed, the auditor’s opinion is what investors see. The auditor is not rubber-stamping management’s work, which is where most of the compliance cost and organizational stress concentrates.

Which Companies Have to Comply

Whether 404(b) applies to your company depends on its SEC filer category, which is driven mainly by public float. Public float is measured on the last business day of your most recently completed second fiscal quarter (for a calendar-year company, typically the last business day in June) and reflects the aggregate worldwide market value of voting and non-voting common equity held by non-affiliates. Management should re-evaluate filer status at each fiscal year-end.

Large Accelerated Filers

A large accelerated filer has a public float of $700 million or more. These companies must include the auditor’s attestation report on ICFR in their annual filing and have the shortest 10-K filing deadline: 60 days after fiscal year-end.

Accelerated Filers

An accelerated filer has a public float of $75 million or more but less than $700 million, with a 75-day 10-K filing deadline. Accelerated filers must comply with 404(b) unless the 2020 revenue-based exemption removes them from that category.

The 2020 Revenue-Based Exemption

In March 2020, the SEC amended the accelerated filer definition to exclude companies that are eligible to be smaller reporting companies and had annual revenues of less than $100 million in their most recent fiscal year. A company meeting this exclusion is reclassified as a non-accelerated filer even if its public float sits in the $75 million to $700 million range. These lower-revenue companies are no longer required to obtain the 404(b) auditor attestation, though they still must complete the management assessment under 404(a). If your company falls in the accelerated filer range on public float but generates less than $100 million in revenue, this exemption likely applies.

Non-Accelerated Filers

Companies with a public float below $75 million are non-accelerated filers and are permanently exempt from 404(b). The Dodd-Frank Act codified this by adding subsection (c) to the statute, which explicitly states that the auditor attestation requirement does not apply to issuers that are neither large accelerated filers nor accelerated filers. Non-accelerated filers still complete the 404(a) management assessment and have 90 days after fiscal year-end to file their 10-K.

Emerging Growth Companies

The JOBS Act created a separate exemption for emerging growth companies. A company qualifies as an EGC if it had total annual gross revenues of less than $1.235 billion during its most recently completed fiscal year. EGC status generally lasts up to five years after the company’s IPO, unless the company crosses an exit threshold sooner (for example, becoming a large accelerated filer or exceeding the revenue limit). During this period, the company is exempt from 404(b) regardless of its public float.

Foreign Private Issuers

Foreign companies listed on U.S. exchanges follow the same filer-category thresholds as domestic issuers. A foreign private issuer classified as a large accelerated filer or accelerated filer must comply with 404(b); a non-accelerated foreign private issuer is exempt. The 2020 revenue-based exclusion applies equally. Foreign private issuers file on Form 20-F or 40-F rather than Form 10-K, but the ICFR attestation requirements are substantively the same.

Preparing for the 404(b) Audit

Preparation is a multi-phase internal project that typically runs across most of the fiscal year. Both management’s assessment and the auditor’s attestation evaluate controls against a recognized framework, and nearly every public company uses the COSO Internal Control — Integrated Framework (2013 version). SEC rules require management to identify the framework used. Every control you document and test should map back to a COSO component, because a gap in any one area (particularly the control environment) can undermine an otherwise strong set of transaction-level controls.

Scoping and Risk Assessment

The work starts with identifying which accounts, business units, and financial statement assertions carry the highest risk of material misstatement. A top-down, risk-based approach focuses resources on revenue recognition, complex estimates, and accounts with high transaction volume or significant judgment. Assertions such as existence, completeness, valuation, and rights and obligations guide which controls need testing for each significant account. The goal is not to test everything, but to test the right things.

Documentation

Every in-scope process needs detailed documentation: narrative descriptions, flowcharts, and identification of the specific controls embedded in each process. The documentation must be thorough enough for the external auditor to trace a transaction from initiation through recording and reporting. Most companies produce a Risk and Control Matrix mapping each key control to the financial statement assertion it addresses, the COSO component it falls under, and the risk it mitigates.

IT General Controls

First-time compliers frequently underestimate the work required on IT controls. The PCAOB requires auditors to understand how information technology affects the flow of transactions and to evaluate IT general controls as part of the integrated audit. ITGCs cover logical access, change management, computer operations, and information security. If ITGCs are weak, the auditor cannot rely on any automated controls in the affected systems, which dramatically expands the scope of manual testing.

Management Testing

Management must test its controls to confirm they are properly designed and operating effectively. Design effectiveness asks whether the control, if it works as intended, will prevent or detect a material misstatement. Operating effectiveness asks whether the control actually worked consistently throughout the year. This internal testing feeds the 404(a) assessment and previews what the external auditor is likely to find.

Remediation Timing

When testing reveals control deficiencies, the company must fix them, and timing is critical. Management and the auditor evaluate ICFR effectiveness as of the fiscal year-end assessment date, so any deficiency that still exists at year-end will appear in the reports. Remediating a deficiency in October for a December 31 year-end gives the auditor time to test the new control before issuing an opinion. Waiting until December is risky; the replacement control may not have operated long enough for the auditor to conclude it works.

What the Auditor Does

The 404(b) attestation is governed by PCAOB Auditing Standard No. 2201, which requires an integrated audit covering both internal controls and financial statement balances in a coordinated engagement. The auditor uses the same top-down, risk-based approach as management but makes independent judgments about which controls are significant and which assertions carry the greatest risk. The auditor identifies significant accounts and disclosures, evaluates entity-level controls, and works down to the process and transaction level. A strong control environment allows the auditor to reduce the extent of detailed transaction testing on the financial statements; a weak one leads to more substantive procedures and higher audit fees.

The auditor also evaluates how IT affects the financial reporting process, including the extent of IT involvement in the period-end close. Automated application controls (system-enforced three-way matching in accounts payable, automated revenue calculations, and similar) are considered lower risk when the underlying ITGCs are effective. If ITGCs fail, the auditor treats every automated control in those systems as unreliable.

The Auditor’s Opinion

When the audit is complete, the auditor issues a formal opinion on whether the company maintained effective ICFR as of the assessment date. This opinion is separate from the opinion on the financial statements. SEC rules allow only three outcomes, with no qualified opinion available for ICFR:

  • Unqualified opinion. The company maintained effective ICFR in all material respects. This is the clean result every company wants.
  • Adverse opinion. The auditor identified one or more material weaknesses. This is mandatory whenever a material weakness exists; the auditor has no discretion to soften the conclusion.
  • Disclaimer of opinion. A scope restriction prevented the auditor from performing enough work to form a conclusion. This is rare and typically signals a serious breakdown in the company’s ability to cooperate with the audit.

Deficiency Levels

Not every control problem carries the same weight. The PCAOB defines three levels, and the distinctions drive disclosure requirements and market consequences:

  • Control deficiency. A weakness in the design or operation of a control that could allow a misstatement to occur. This is the baseline level and does not require public disclosure.
  • Significant deficiency. A deficiency, or combination of deficiencies, less severe than a material weakness but important enough to merit the attention of those overseeing financial reporting. Significant deficiencies must be communicated to the audit committee but are not individually disclosed in the auditor’s public report.
  • Material weakness. A deficiency, or combination of deficiencies, where there is a reasonable possibility that a material misstatement of annual or interim financial statements will not be prevented or detected on a timely basis. A single material weakness triggers an adverse opinion.

The line between a significant deficiency and a material weakness is where the most contentious auditor-management conversations occur. The auditor evaluates both the likelihood and magnitude of potential misstatement, and individually minor deficiencies can aggregate into a material weakness when they affect related accounts or processes.

What Happens After an Adverse Opinion

An adverse ICFR opinion has real consequences. Research on companies that disclosed internal control weaknesses found that management turnover was 15 to 26 percent more likely, auditor turnover was 6 to 9 percent more likely, and class-action lawsuits were 5 to 10 percent more likely compared to companies without such disclosures. Markets have shown negative reactions to first-time adverse ICFR opinions, though correcting a previously disclosed weakness produces a positive market response.

The disclosure itself invites increased SEC scrutiny. Management cannot conclude that ICFR is effective if any material weakness exists; the rules explicitly prohibit that conclusion. The company must disclose the material weakness in its annual report and describe remediation efforts, which usually turns into a multi-quarter project under heightened board and investor attention. Audit fees almost invariably rise the following year because the auditor expands testing scope to verify remediation.

There is also a personal dimension for senior officers. Section 302 requires the CEO and CFO to personally certify each annual and quarterly report, including statements that they are responsible for establishing and maintaining internal controls, have evaluated those controls within 90 days of the report, and have disclosed all significant deficiencies and material weaknesses to the auditors and the audit committee. They must also disclose any fraud involving employees with a significant role in internal controls, whether or not the fraud is material. Section 906 backs those certifications with criminal penalties: up to $1 million and 10 years in prison for a knowing certification of a non-compliant report, rising to $5 million and 20 years for a willful violation. If a material weakness surfaces that contradicts a certification the officers signed while aware of unreported deficiencies, that statutory framework comes into play. In practice, most officers manage this exposure by working closely with auditors to identify and disclose weaknesses before signing certifications.