SOX Internal Controls Compliance Checklist

Last updated: 2026-04-08 — ComplianceStack Editorial Team

20 items
Progress 0 of 20 reviewed

Section 404 of Sarbanes-Oxley requires management to assess the effectiveness of internal control over financial reporting (ICFR) every year — and your external auditor must attest to that assessment. The PCAOB and SEC have consistently found that inadequate internal controls are the root cause of most financial restatements. Material weaknesses in internal controls cost public companies an average of $1.2 billion in market capitalization when disclosed. This checklist covers the 20 internal controls requirements that define a defensible Section 404 program, based on COSO 2013 and PCAOB AS 2201.

Priority Legend:
● Critical ● High ● Medium ● Ongoing

SOX Compliance Checklist for Internal Controls

1

Adopt COSO 2013 Internal Control — Integrated Framework as your control framework

Critical 2-3 days

SEC management guidance and PCAOB AS 2201 both reference COSO 2013 as the baseline. Document your formal adoption, ensure all five components (Control Environment, Risk Assessment, Control Activities, Information & Communication, Monitoring) are addressed, and confirm COSO 2013 replaces any use of the legacy 1992 framework.

PCAOB AS 2201.03; SEC Release No. 33-8810; COSO Internal Control — Integrated Framework (2013)
2

Define and document your financial reporting scope: identify significant accounts, disclosures, and processes

Critical 3-5 days

Scope your Section 404 program by identifying accounts with a reasonable possibility of material misstatement. Use quantitative thresholds (typically 5% of pretax income) and qualitative factors (complexity, susceptibility to fraud). Document your scoping rationale — auditors will challenge any significant account excluded without documented justification.

PCAOB AS 2201.23-.28; SEC Management Guidance (June 2007)
3

Map financial reporting processes and identify key controls at the assertion level

Critical 1-3 weeks

For each significant process (Order-to-Cash, Procure-to-Pay, Close-to-Report, Payroll, etc.), document process narratives or flowcharts. Identify the key controls that address financial statement assertions — existence, completeness, accuracy, cutoff, and classification. This documentation is the foundation for your control testing plan.

PCAOB AS 2201.39-.43; COSO 2013 Principle 10
4

Evaluate Entity-Level Controls (ELCs) across all 17 COSO principles

Critical 3-5 days

ELCs — including tone at the top, code of conduct, whistleblower programs, and board oversight — can have a pervasive effect on other controls. Assess all 17 COSO principles within each of the five components. Deficiencies at the entity level are often classified as material weaknesses due to their broad impact.

PCAOB AS 2201.22; COSO 2013 Principles 1-17
5

Design and implement IT General Controls (ITGCs) for all in-scope systems

Critical 2-4 weeks

ITGCs cover access management (user provisioning/deprovisioning, segregation of duties), change management (program changes, patches, releases), and computer operations (job scheduling, backup and recovery). Automated application controls depend on reliable ITGCs — a ITGC deficiency can elevate the risk of every automated control that relies on the affected system.

PCAOB AS 2201.26; PCAOB Staff Practice Alert No. 11
6

Enforce segregation of duties (SOD) in financial systems and document SOD conflicts

Critical 1-3 weeks

No single individual should have the ability to authorize, execute, and record a transaction. Map user access rights in ERP systems (SAP, Oracle, Workday) to identify SOD conflicts. Where conflicts exist due to business necessity, implement and test compensating controls. Document all compensating controls and review them at least quarterly.

COSO 2013 Principle 10; PCAOB AS 2201.42; SOX Section 302
7

Develop a risk-based control testing plan with appropriate sample sizes

High 2-3 days

PCAOB AS 2315 governs sample sizes for substantive testing; apply the same rigor to control testing. Manual controls operating monthly typically require 2-5 samples; daily controls require 25+ samples. Document your testing approach, attribute tested, population size, sampling method, and deviation rate threshold before testing begins.

PCAOB AS 2315 (Audit Sampling); PCAOB AS 2201.44-.47
8

Test operating effectiveness of key controls and document results contemporaneously

High Ongoing throughout year

Evidence must be obtained during the period covered by the assessment — you cannot recreate or backdate testing. For each control tested, document: the control owner, test date, sample selected, evidence reviewed, exception noted (if any), and tester conclusion. Retain testing workpapers for at least seven years under SOX Section 802.

SOX Section 802; PCAOB AS 2201.44-.57; SEC Rule 13a-15
9

Evaluate and document control deficiencies using the correct severity classification

High 1-2 days per deficiency

Deficiencies are classified as: Control Deficiency (a gap exists), Significant Deficiency (more than remote chance of more than inconsequential misstatement), or Material Weakness (reasonable possibility of material misstatement). Misclassifying a material weakness as a significant deficiency triggers SEC enforcement. Document the basis for each classification with reference to quantitative and qualitative factors.

PCAOB AS 2201.62-.70; SEC Staff Guidance (Oct 2009); ASC 450
10

Establish a formal remediation tracking process for control deficiencies

High Ongoing

Every identified deficiency must have an owner, a root cause analysis, a remediation plan with milestone dates, and a validation test confirming the control is operating effectively after remediation. Track all open deficiencies in a centralized log reviewed by the Audit Committee at least quarterly. Unresolved significant deficiencies should be escalated before year-end assessment.

PCAOB AS 2201.79-.82; COSO 2013 Principle 17 (Monitoring)
11

Implement a formal management review control (MRC) for all significant manual journal entries

High 2-3 days to design, ongoing

Manual journal entries are a primary vehicle for financial fraud. Require supporting documentation for all manual entries, dual authorization for entries above a defined threshold, and automated routing to a reviewer who did not prepare the entry. Review 100% of manual entries to restricted accounts (revenue, top-side entries) regardless of amount.

PCAOB AS 2110.69; SOX Section 404; COSO 2013 Principle 10
12

Conduct quarterly sub-certifications from business unit controllers and process owners

High 1-2 days per quarter

CEOs and CFOs certify the accuracy of financial statements under Section 302. Protect that certification by requiring sub-certifications from the individuals who actually control the numbers. Sub-certifications should confirm that internal controls are operating effectively in their area and that no material weaknesses or fraud has occurred.

SOX Section 302; SEC Rule 13a-14(a)
13

Assess completeness and accuracy of data used in financial reporting controls

Medium 1-2 days per report

If a key control relies on a report or data extract from a system, you must validate that the report is complete and accurate. This is the "CAVR" requirement (Completeness, Accuracy, Validity, Restricted access). Many SOX deficiencies trace to unvalidated report outputs being used in management review controls.

PCAOB AS 2201.26; PCAOB Staff Practice Alert No. 11
14

Review and update your controls inventory for acquisitions, divestitures, and system changes

Medium Per change event

Any significant business change — a new ERP module, a major acquisition, an outsourced process — can create new risks not covered by existing controls. Perform a risk assessment for every material change and update your controls inventory within 30 days. New controls must be tested before year-end.

PCAOB AS 2201.9-.14; COSO 2013 Principle 9
15

Coordinate walkthroughs with external auditors at least annually

Medium 1 day per process

Walkthrough procedures confirm that process documentation reflects what actually happens in practice. PCAOB standards require auditors to perform walkthroughs for all significant processes. Engaging early (before year-end) allows you to identify gaps the auditor will test and remediate before the assessment deadline.

PCAOB AS 2201.34-.38; PCAOB AS 2110.43
16

Document the period-end financial reporting (PEFR) process including close calendar and review controls

Medium 3-5 days

The PEFR process covers financial close activities: consolidation, elimination entries, account reconciliations, financial statement preparation, and management review before filing. SOX auditors give this process heightened scrutiny. Document every step, every review control, the reviewer qualifications, and what evidence is retained.

PCAOB AS 2201.25; PCAOB AS 2110.68
17

Test controls over financial statement disclosures and footnotes

Medium 2-3 days

Disclosures are part of ICFR. Controls over debt covenants, lease obligations, commitments and contingencies, and related-party transactions are frequently under-scoped. Map each significant footnote to a disclosure control and include it in your testing plan.

PCAOB AS 2201.25; SEC Release No. 33-8810
18

Ensure access to financial systems is reviewed quarterly and terminated promptly on separation

Medium Quarterly, 1-2 days

Privileged access to ERP, financial close, and reporting systems must be reviewed at least quarterly against current employee roles. Departed employees must have access revoked within 24 hours of separation. Maintain logs of provisioning, access reviews, and terminations for audit evidence.

COSO 2013 Principle 11; PCAOB AS 2201.26; SOX Section 302
19

Maintain documentation of management's assessment conclusions and supporting evidence

Medium 2-3 days at year-end

Management must document the framework adopted, the scope of the assessment, testing performed, deficiencies identified, and the overall conclusion about ICFR effectiveness. This documentation must be available for auditor review and retained for at least seven years. Inadequate documentation itself constitutes a control deficiency.

SOX Section 802; SEC Rule 13a-15(d); PCAOB AS 2201.04
20

Disclose all material weaknesses and significant deficiencies in required filings

Critical As needed

Material weaknesses must be disclosed in the annual report (10-K) in Item 9A. Significant deficiencies must be communicated to the Audit Committee in writing. Do not delay disclosure in hopes of remediation — late disclosure after a material weakness has existed triggers additional SEC scrutiny and potential enforcement action.

SOX Section 404; SEC Rule 13a-15; PCAOB AS 2201.68-.70

See How Your Internal Control Scores on SOX

Run a free gap analysis to find out which items you have covered and where the risks are.

Gap Analyzer →   Training Tracker →

Common Mistakes That Trigger Enforcement

Scoping out significant accounts without documented qualitative justification
PCAOB inspections have cited inadequate scoping as a deficiency. If a significant account is omitted from testing and a misstatement later occurs, it escalates to a material weakness disclosure.
Relying on automated controls without validating IT General Controls
Automated controls inherit the risk of the IT environment. An ITGC deficiency (e.g., inadequate change management) can undermine the reliability of every automated control that runs on the affected system.
Treating all control deficiencies as "control deficiencies" to avoid disclosure
Misclassifying a material weakness as a significant deficiency is a disclosure violation under SOX Section 404. The SEC has brought enforcement actions specifically for deficiency misclassification.
Testing controls in a sprint at year-end rather than throughout the period
Controls tested only in Q4 provide evidence of effectiveness for only part of the year. PCAOB standards require evidence that controls operated effectively throughout the entire assessment period.
Not updating the controls inventory after a major ERP upgrade or acquisition
New systems and processes create new risks. Controls designed for the old environment may not address risks introduced by the new one, leaving gaps that auditors and regulators will find.

Frequently Asked Questions

What is the COSO 2013 framework and why does it matter for SOX?

COSO 2013 (Committee of Sponsoring Organizations of the Treadway Commission) is the Internal Control — Integrated Framework that the SEC and PCAOB recognize as the standard for evaluating ICFR effectiveness under SOX Section 404. It defines five components (Control Environment, Risk Assessment, Control Activities, Information & Communication, Monitoring) and 17 principles. Management must confirm that all five components are present and functioning and that all 17 principles are addressed to conclude ICFR is effective.

What is the difference between a material weakness and a significant deficiency?

A significant deficiency is a deficiency or combination of deficiencies in internal control over financial reporting that is less severe than a material weakness yet important enough to merit attention by those responsible for oversight. A material weakness is a deficiency where there is a reasonable possibility that a material misstatement will not be prevented or detected on a timely basis. The practical difference: material weaknesses must be disclosed publicly in the 10-K; significant deficiencies must be communicated to the Audit Committee but are not required to be publicly disclosed.

How long must we retain SOX internal controls documentation?

SOX Section 802 requires records relevant to an audit or review to be retained for at least five years. SEC rules extend this to seven years for work papers and records that form the basis of the audit. Most companies retain ICFR documentation for seven years to align with the longer requirement. This includes process documentation, testing workpapers, deficiency logs, and management assessment conclusions.

✉ Save This Checklist

Enter your email and we'll send you a clean copy — plus updates when requirements change.

We also offer a free personalized gap analysis for your specific situation.

Related Resources