SOX Assessment: Scoping, Testing, and Section 404 Reporting

A SOX assessment is the annual review of internal controls over financial reporting that the Sarbanes-Oxley Act of 2002 requires every SEC-registered public company to perform. Management scopes the financial reporting environment, documents the controls that protect it, tests whether those controls are designed well and operating consistently, classifies any deficiencies, remediates what it can, and issues a formal conclusion in the annual 10-K. For larger filers, the external auditor performs a parallel attestation. The depth of the work varies with company size, but the obligation to assess does not.

Who Has to Perform One

Every public company that files periodic reports with the SEC must complete a management assessment of internal controls under Section 404(a) of the Act. Size does not change that. What size changes is Section 404(b), which requires an independent external auditor to separately attest to the effectiveness of those controls. The auditor attestation only applies to accelerated filers and large accelerated filers.1Office of the Law Revision Counsel. United States Code Title 15 – 7262 Management Assessment of Internal Controls

Filer classification runs on public float, the market value of shares held by non-affiliate investors:

  • Large accelerated filer: public float of $700 million or more
  • Accelerated filer: public float of $75 million to less than $700 million
  • Non-accelerated filer: public float below $75 million

Non-accelerated filers are permanently exempt from 404(b) auditor attestation, an exemption Congress made permanent through the Dodd-Frank Act in 2010.2U.S. Securities and Exchange Commission. Accelerated Filer and Large Accelerated Filer Definitions They still complete the management assessment, and their officers still face criminal exposure for false certifications. A smaller reporting company with public float between $75 million and $700 million can also stay outside 404(b) if annual revenues fall below $100 million.3U.S. Securities and Exchange Commission. Smaller Reporting Companies

As of mid-2026, the SEC has proposed raising the large accelerated filer threshold from $700 million to $2 billion in public float and eliminating the accelerated filer category entirely. If adopted, many companies would move out of the 404(b) attestation requirement. The proposal is not final.

The Annual Cycle

A SOX assessment runs on the fiscal year, not as a single event. The rhythm looks roughly like this:

  • First quarter: scoping and risk assessment. Management identifies the accounts, processes, locations, and IT systems in scope and builds the risk-control matrix.
  • Second quarter: walkthroughs and interim testing. Individual transactions are traced end-to-end to verify that documented controls match reality.
  • Third quarter: the main testing window. Samples pulled from throughout the year confirm whether controls operated consistently. Most deficiencies surface here.
  • Fourth quarter and year-end: remediation and reporting. Deficiencies get fixed, auditors perform roll-forward testing through the last day of the year, management issues its 404(a) report, and the external auditor issues its 404(b) attestation where required. Both go into the 10-K.

Companies that wait until the fourth quarter to begin serious testing routinely discover that there isn’t enough operating history to conclude a remediated control is effective, and the finding rolls into the annual filing.

Scoping the Assessment

Scoping sets the perimeter for everything that follows. Scope too narrowly, and a material control gap goes untested. Scope too broadly, and low-risk areas absorb resources the high-risk ones need.

Auditors and management use a top-down, risk-based approach that begins at the financial statement level and works down to significant accounts, disclosures, and their relevant assertions.4Public Company Accounting Oversight Board. AS 2201 An Audit of Internal Control Over Financial Reporting Materiality here means the threshold at which an omission or misstatement would influence a reasonable investor. Each account is evaluated on size, transaction complexity, and the likelihood that errors could go undetected.

Scope extends past journal entries and reconciliations. IT General Controls governing the systems that house financial data are a core part of any SOX assessment. They cover who can access financial applications, how software changes are authorized and tested, and whether backups and recovery procedures actually work. Any system that processes data affecting the financial statements, feeds another financial system, or could materially influence results belongs in scope.5Wolters Kluwer. ITGC SOX The Foundations and Key Steps for Compliance

Business Processes

Financial reporting risk concentrates in a familiar set of business processes: revenue recognition, payroll, inventory valuation, accounts receivable, accounts payable, and expense reporting.5Wolters Kluwer. ITGC SOX The Foundations and Key Steps for Compliance For each, the team identifies which assertions matter. Inventory typically carries valuation and existence risk. A payroll liability account leans toward completeness and accuracy.

Third-Party Service Providers

Outsourcing part of the financial operation, whether to a cloud payroll processor, a benefits administrator, or a hosted ERP provider, does not outsource SOX responsibility. If a service organization handles transactions that feed the financial statements, the company relying on that provider has to evaluate whether the provider’s controls are adequate.

The standard mechanism is a SOC 1 Type II report, covering both the design and operating effectiveness of the provider’s controls across a specified period. A Type I report, which only evaluates design at a single point in time, is not sufficient for SOX reliance. When reading the SOC 1, verify that its scope covers the services actually used, that its reporting period aligns with the company’s fiscal year, and that noted control deficiencies don’t undermine reliance. The report also lists complementary user entity controls, the controls the service organization expects the customer to maintain. If those aren’t in place, the company has its own gap to close before it can rely on the report.

Documenting the Control Environment

Before testing anything, the control environment has to be documented well enough that someone with no prior knowledge of the company could follow how each financial safeguard works. First-year SOX programs almost always underestimate this step.

The central artifact is the risk-control matrix, mapping every identified financial reporting risk to the specific control designed to mitigate it. Each row captures the risk, the control activity, the person who performs it, its frequency, and the evidence it produces. A single significant account may carry a dozen mapped controls across different assertions.

Supporting the matrix, process narratives and flowcharts trace the lifecycle of a transaction from origination through recording. A revenue-cycle narrative walks through how a customer order is received, fulfilled, invoiced, and recognized, naming who performs each step, what system carries the data, and what evidence gets generated. A bank reconciliation control might require a manager to review and sign a report, and that signed report becomes the artifact proving the control operated.

Governance, risk, and compliance platforms can automate much of the documentation and evidence collection, particularly for IT controls where access reviews and change logs can be pulled straight from the systems. A gap tends to persist between what those platforms orchestrate and what underlying IT systems actually produce, and that gap is where manual work accumulates as new applications outpace integration.

Testing the Controls

Testing happens in two phases: evaluating whether controls are designed properly, then testing whether they actually operated as intended across the year.

Walkthroughs

A walkthrough follows a single transaction end-to-end through a business process, confirming that documented controls exist and would catch an error or fraud if one occurred. It is not sampling. It is a one-transaction deep dive that verifies narratives and flowcharts against reality. If a walkthrough reveals that a documented approval step doesn’t actually happen, or that an exception-flagging system was retired months ago, the control fails on design before operating effectiveness testing even begins.

Operating Effectiveness

Once design is confirmed, assessors pull samples from across the fiscal year to test whether the control worked consistently. Sample sizes scale with frequency. A daily control typically requires 25 or more samples. A weekly control might need 10 to 15. Quarterly controls usually need two or three. These numbers reflect common practice rather than statute, and the external auditor may adjust them based on assessed risk.

Each sample is checked against specific criteria. For a manual journal entry approval, the assessor verifies that the entry was reviewed by someone with appropriate authority, that the review happened before the entry posted, and that evidence of the review exists. A single failed sample out of 25 triggers a conversation about whether the exception is a one-off mistake or a systemic breakdown.

Continuous Monitoring

Many organizations supplement point-in-time sampling with continuous monitoring tools that run automated checks throughout the year. These tools can flag access violations, unusual transaction patterns, or control deviations close to real time, giving teams a chance to investigate before problems harden into year-end findings. The tradeoff is data quality. Continuous monitoring depends on solid data governance to avoid producing more false positives than the team can work through.

Classifying Deficiencies

Not every failed test is a crisis. Severity drives who has to know and what has to be disclosed publicly.

  • Control deficiency. A control is designed or operating in a way that doesn’t fully allow management or staff to prevent or detect misstatements in the normal course of their work. The mildest tier. It should be communicated to management for correction but doesn’t require public disclosure.
  • Significant deficiency. A deficiency, or combination of deficiencies, less severe than a material weakness but important enough to merit attention from those overseeing financial reporting. It must be disclosed to the external auditors and audit committee, not publicly.6U.S. Securities and Exchange Commission. Final Rule Definition of the Term Significant Deficiency
  • Material weakness. A deficiency, or combination, where there is a reasonable possibility that a material misstatement of the annual or interim financial statements will not be prevented or detected on a timely basis. It must be disclosed publicly. A company cannot conclude that its internal controls are effective if even one material weakness exists.4Public Company Accounting Oversight Board. AS 2201 An Audit of Internal Control Over Financial Reporting

Certain findings are strong indicators of a material weakness on their own: fraud involving senior management, restatement of previously issued financial statements, the auditor’s identification of a material misstatement the company’s own controls missed, and ineffective oversight by the audit committee.4Public Company Accounting Oversight Board. AS 2201 An Audit of Internal Control Over Financial Reporting When one of these appears, the presumption of a material weakness is hard to overcome.

Remediating What You Find

Identifying a deficiency is half the job. The harder half is fixing it before year-end while proving to auditors that the fix actually holds.

Design deficiencies mean the control itself is flawed or missing, and remediation requires building or restructuring it. Operational deficiencies mean the control exists and is designed properly but isn’t being performed correctly. The fix there can range from retraining staff and tightening supervision to replacing personnel or automating the control entirely.

Timing decides whether remediation counts for the current year. A control fixed in October has to operate effectively through year-end, and the auditor needs enough evidence of it working under normal conditions to call it sustainable rather than a patch applied for the test. Companies that begin remediation in the fourth quarter regularly find there isn’t enough operating history to support an “effective” conclusion, and the material weakness carries into the annual filing.

SEC enforcement actions have made clear that identifying a material weakness and sitting on it for years is not acceptable. Penalties in recent enforcement cases for failure to timely remediate have ranged from $35,000 to $200,000, and the SEC expects clear disclosure paired with measurable remediation efforts.

The Report and the Officer Certifications

The assessment ends in two overlapping outputs: the Section 404 internal control report and the Section 302 and 906 officer certifications.

Section 404 Reports

Section 404(a) requires every public company’s annual report to contain an internal control report stating management’s responsibility for establishing and maintaining adequate controls and giving management’s own conclusion on whether those controls were effective as of fiscal year-end.1Office of the Law Revision Counsel. United States Code Title 15 – 7262 Management Assessment of Internal Controls If a material weakness existed at year-end, management cannot conclude that controls were effective, and the weakness has to be disclosed.

For accelerated and large accelerated filers, Section 404(b) adds a second layer. The company’s external auditor must independently attest to management’s assessment, and the auditor’s opinion appears alongside management’s report in the 10-K. A disagreement between the two virtually guarantees regulatory scrutiny.1Office of the Law Revision Counsel. United States Code Title 15 – 7262 Management Assessment of Internal Controls

CEO and CFO Certifications

Separate from the 404 report, Sections 302 and 906 impose personal certification requirements on the principal executive and financial officers. Under Section 302, the CEO and CFO must certify in every quarterly and annual report that they have reviewed it, that it contains no material misstatements, that the financial statements fairly present the company’s financial condition, and that they are responsible for the company’s internal controls.7Office of the Law Revision Counsel. United States Code Title 15 – 7241 Corporate Responsibility for Financial Reports They also certify that they have disclosed all significant deficiencies and any fraud involving management to the external auditors and audit committee.8Securities and Exchange Commission. Certification of Disclosure in Companies Quarterly and Annual Reports

Section 906 adds criminal exposure. Officers who knowingly certify a report that doesn’t comply face fines up to $1 million and up to 10 years in prison. If the false certification is willful, penalties rise to fines up to $5 million and up to 20 years in prison.9Office of the Law Revision Counsel. United States Code Title 18 – 1350 Failure of Corporate Officers To Certify Financial Reports These are the provisions that keep the assessment from becoming a box-checking exercise. Someone’s name and freedom sit under every 10-K.

If a Material Weakness Gets Disclosed

A material weakness disclosed in a public filing is one of the worst outcomes a compliance team can face, and the consequences run past the filing itself. The disclosure sits in the 10-K, which is publicly available and closely watched by analysts, institutional investors, and short sellers. Stock declines following material weakness disclosures are common, though severity depends on the nature of the weakness and whether the company has a credible remediation plan.

The SEC monitors material weakness disclosures and has pursued enforcement against companies that fail to remediate promptly. Beyond SEC scrutiny, a material weakness can trigger higher audit fees as the external auditor expands testing, filing delays as remediation competes with reporting deadlines, and reputational damage that reaches customers and board recruiting.

For companies subject to 404(b), a material weakness also means the external auditor will issue an adverse opinion on internal controls, a public statement that the company’s controls are not effective. That adverse opinion sits in the 10-K alongside the financial statements and stays part of the public record until the weakness is remediated and the auditor issues a clean opinion in a later year.