é É « » à è ù ç ô é

SOX compliance checklist 2026: a phase-by-phase guide

Alban Clot
November 15, 2026
| 13 min read
Audit Analytics Guide
Download Now

SOX fails as a year-end project. The work that produces a clean opinion runs across twelve months, and the teams that scramble in December are the ones who treated the other eleven months as downtime.

This checklist follows the order a controller actually works in: scope, design, test, remediate, prepare for the audit, then the two cycles that run alongside the annual arc, quarterly certification and year-round monitoring. Every line names an owner, a frequency, and the evidence an auditor will ask for. The regulatory explanation sits in the SOX compliance guide; this is the execution layer.

Phase
Activity
Owner
Frequency
Evidence expected
1. Scoping 
Set materiality, identify significant accounts and disclosures 
SOX lead with external audito 
Annual, Q1 
Scoping memo with quantitative and qualitative thresholds 
1. Scoping 
Map accounts to processes, systems, and locations 
SOX lead 
Annual, Q1 
Process and system inventory by account 
1. Scoping 
Rate risk and select key controls 
SOX lead, process owners 
Annual, Q1 
Risk and control matrix with rated risks 
2. Design 
Document process narratives and control descriptions 
Process owners 
Annual, refreshed on change 
Dated narratives and flowcharts 
2. Design 
Confirm each key control addresses a named assertion 
SOX lead 
Annual 
RACM mapping control to assertion 
2. Design 
Walk through each key control end to end 
Internal audit 
Annual, Q2 
Walkthrough documentation, one transaction traced 
3. Testing 
Test design effectiveness 
Internal audit 
Annual 
Test of design workpapers 
3. Testing 
Test operating effectiveness, interim phase 
Internal audit 
Q2 or Q3 
Sample selection, evidence per item, conclusion 
3. Testing 
Roll-forward testing to year end 
Internal audit 
Q4 
Roll-forward workpapers covering the remaining period 
4. Remediation 
Classify each exception by severity 
SOX lead, controller 
On identification 
Deficiency log with rating rationale 
4. Remediation 
Assign owner and remediation date 
Controller 
On identification 
Remediation plan with milestones 
4. Remediation 
Re-test remediated controls 
Internal audit 
After sufficient operating history 
Re-test workpapers 
5. Audit prep 
Agree scope and sample sizes with the external auditor 
SOX lead 
Q2 
Written scoping agreement 
5. Audit prep 
Assemble and index the evidence population 
SOX lead 
Q3 to Q4 
Indexed evidence repository 
5. Audit prep 
Run a dry run on key controls 
Internal audit 
~90 days before year end 
Dry run findings and open remediation window 
Quarterly 
Collect sub-certifications from process owners 
Controller 
Quarterly 
Signed sub-certification responses 
Quarterly 
Communicate deficiencies and fraud to auditor and audit committee 
CFO 
Quarterly 
Dated communication record 
Retention 
Preserve audit-related records under the retention policy 
Legal, IT 
Continuous 
Retention schedule and disposal log 
Monitoring 
Test controls across the full transaction population 
Finance systems, internal audit 
Each data extraction 
Exception report with disposition 
Monitoring 
Review user access to financial systems 
IT, reviewed by internal audit 
Quarterly 
Access review sign-off with exceptions cleared 

Phase 1: scoping and risk assessment

Scoping decides everything downstream. Get it wrong and the year is spent testing controls nobody needed while a material account sits uncovered.

Start from the financial statements and work down. Set materiality with the external auditor, identify the significant accounts and disclosures, then trace each to the processes, systems, and locations that feed it. Rate the risk of misstatement per assertion, and select the key controls that address the rated risks.

Filer status decides how the cycle ends. Accelerated and large accelerated filers face an auditor attestation on top of management's assessment; everyone else runs the same scoping work without it. The SOX 404 article covers the thresholds.

Two traps. Scoping by last year's matrix perpetuates controls that no longer address a risk. And scope creep tracks system count: KPMG's 2025 SOX Survey found the average number of in-scope systems rose from 17 in FY22 to 40 in FY24, the single clearest driver of rising program cost.

Phase 2: control design and documentation

Documentation here is the artifact the auditor reads first. Narratives and control descriptions that describe last year's process fail on contact.

For each key control, record what triggers it, who performs it, what evidence it produces, and which assertion it addresses. Management review controls need one extra element: the threshold applied and what happens to items that breach it. Reviews documented as a signature without a stated threshold are the most frequently cited financial close weakness in KPMG's 2025 material weakness study.

Walkthroughs close the phase. Trace one transaction end to end and confirm the control as described matches the control as performed. The ICFR framework article covers the assessment mechanics.

Phase 3: control testing

Testing splits in two. Design effectiveness asks whether the control, operating as described, would catch the misstatement it exists to catch. Operating effectiveness asks whether it actually ran, on identifiable items, across the period.

Run operating effectiveness in two phases. An interim round in Q2 or Q3, then a roll-forward covering the remaining period. Sixty-three percent of organizations tested this way in FY24, and the structure matters because it is what creates a window to fix what fails.

Sample size follows control frequency and assessed risk: one for annual controls, two for quarterly, two to five for monthly, five to fifteen for weekly, twenty to forty for daily. Agree the sizes with the external auditor before testing starts. Retesting a population the auditor declines to accept is the most expensive avoidable outcome in the cycle.

ICFR controls checklist

Three layers, tested in this order.

Entity-level controls. Control environment and tone at the top. Board and audit committee oversight, including how deficiencies reach them. Fraud risk assessment, refreshed annually. Period-end financial reporting controls covering consolidation, journal entries, and disclosure assembly. Monitoring activities and how exceptions escalate.

Process-level controls. For each significant cycle, the controls addressing completeness, accuracy, cutoff, existence, and valuation. Procure-to-pay: vendor master maintenance, three-way match, payment authorization, accrual completeness. Order-to-cash: credit approval, revenue recognition judgments, billing accuracy, receivable valuation. Record-to-report: account reconciliations with review evidence, journal entry approval, estimate methodology and review, consolidation and intercompany elimination.

Segregation of duties. Enforced in the system, evidenced by role definitions and conflict reports, and reviewed when roles change. A segregation rule documented in a procedure note and unenforced in the ERP is a design deficiency on its face.

ITGC controls checklist

Every automated control rests on IT general controls. A broken ITGC invalidates the application controls above it, which is why ITGC weaknesses cascade. The IT internal controls article covers scoping.

Domain
Control
Test procedure
Access management 
New user access approved before provisioning 
Sample joiners, inspect approval dated before the provisioning date 
 Access management 
Terminated user access revoked promptly 
Reconcile the HR leaver list to active accounts, test revocation timing 
Access management
Privileged access restricted and justified
Inspect the privileged account list against role requirements 
Access management
Periodic user access review completed 
Inspect review evidence and confirm flagged exceptions were resolved 
Change management 
Changes authorized before migration to production 
Sample changes, inspect approval predating deployment 
Change management 
Development and production environments segregated 
Inspect environment configuration and developer access to production 
Change management 
Testing evidence retained for each change 
Sample changes, inspect test results and sign-off 
 IT operations 
Batch job failures detected and resolved 
Sample failures, inspect resolution records and timing 
 IT operations 
Backups run and restoration tested 
Inspect backup logs and the most recent restoration test result 
 IT operations 
Interfaces between systems reconciled 
Inspect interface reconciliation for completeness and accuracy 

User access management is the leading systems-related material weakness theme: excessive privileges, leavers left active, and reviews performed late or superficially.

Phase 4: remediation

Remediation is where the calendar bites. A control that fails needs redesign, implementation, and enough operating history to be tested again before year end.

Classify first.

  • A control deficiency is a gap.
  • A significant deficiency merits the attention of those overseeing financial reporting.
  • A material weakness creates a reasonable possibility that a material misstatement goes undetected. One at year end produces an adverse ICFR opinion.

Then assign, date, and re-test. Track recurrence explicitly: across 2021 to 2025, 36% of companies reporting a material weakness reported one in more than a single year. A weakness that returns points at the process, not the control.

Phase 5: audit preparation

The external auditor's work is governed by PCAOB AS 2201, and the SOX audit article covers what they test and how. Preparation has four moving parts.

  • Scope alignment. Agree in writing which controls the auditor will test and at what sample size. Over half of organizations carry a larger in-scope control population than their auditor, so part of the internal burden is self-imposed.
  • Evidence indexing. Requests arrive by control reference. An indexed repository converts a request into a retrieval.
  • The dry run. Roughly 90 days before year end, test the key controls as the auditor will. The arithmetic is what matters here. A monthly control found broken in October can produce two or three clean occurrences by December, while the same control found broken in December cannot.
  • Reliance positioning. Auditor reliance on internal audit's work reduces auditor-performed testing. That reliance rests on the quality and reproducibility of the evidence behind it.

Quarterly checklist: Section 302 certification

Most checklists cover the annual cycle and stop. Section 302 runs four times a year with its own preparation sequence, and the Section 302 article covers what the certification commits the signers to.

The quarterly items:

  1. Issue sub-certification questionnaires to process owners and business unit leads.
  2. Open the quarter's deficiency log and carry forward anything unresolved.
  3. Collect signed sub-certifications and follow up on qualified responses.
  4. Convene the disclosure committee on open items, control changes, and anything flagged by legal.
  5. Conclude deficiency severity, including any fraud involving management regardless of materiality.
  6. Communicate deficiencies and fraud to the external auditor and the audit committee, and date the record.
  7. Reconcile the control change log to the Item 9A or Item 4 disclosure.
  8. Confirm the CEO and CFO read the document as filed before signing Exhibit 31 and Exhibit 32.

Item 8 is the one that gets skipped. The certification covers the version filed, not the draft reviewed.

Record retention checklist: Section 802

This is the most commonly misstated item on published SOX checklists. Section 802 added two provisions to the criminal code, and they do different things.

18 U.S.C. § 1519 prohibits altering, destroying, concealing, or falsifying records with intent to obstruct a federal investigation. It carries up to 20 years, applies to anyone, and sets no retention period.

18 U.S.C. § 1520 requires accountants auditing an issuer to maintain all audit or review workpapers for five years from the end of the fiscal period in which the audit or review concluded. A knowing violation carries up to 10 years.

SEC Rule 2-06 of Regulation S-X, adopted in January 2003 to implement Section 802, extends that to seven years after the auditor concludes the audit or review, covering workpapers plus the memoranda, correspondence, and electronic records containing conclusions or analyses related to the audit.

Both retention periods bind the audit firm. Neither imposes a seven-year retention obligation on the issuer, which is what most checklists imply. A company's own obligations come from elsewhere: the Exchange Act books-and-records provisions, litigation holds, tax rules, and state law. Most companies adopt seven years by policy to cover the overlap, and that is a sound default. It is a policy choice, not a Section 802 requirement.

The checklist items: a documented retention schedule by record class, enforcement in the systems holding the records including email, a legal hold process that suspends disposal on notice, and a disposal log showing what was destroyed and under what authority.

Year-round monitoring checklist

The teams that avoid the year-end scramble run controls testing continuously. The workload distribution matters as much as the total.

The monitoring items:

  • Continuous controls testing. Run control tests on each data extraction across the full transaction population. Exceptions surface within days, inside the period they belong to.
  • Exception disposition. Every exception gets a resolution and a date. An exception report nobody closes is evidence of a monitoring failure.
  • Quarterly access reviews. The leading ITGC weakness theme, and the one most amenable to systematic review.
  • Control change tracking. A running log, reconciled quarterly to the disclosure.
  • Scope maintenance. New systems, acquisitions, and process changes enter scope when they happen, not at next year's scoping.

Automation is the gap. The automated share of controls fell from 21% in FY22 to 17% in FY24 while in-scope systems more than doubled, which means the testing burden per control is rising. Continuous controls monitoring addresses that from the testing side instead of the control side. Rather than automating each control one system at a time, it tests the full population and accumulates the evidence as a byproduct. Supervizor's compliance solution runs that across procure-to-pay, order-to-cash, and record-to-report.

Conclusion

A SOX checklist earns its place by naming who does what, when, and what evidence results. The columns matter more than the items, because an auditor's question is never whether a control exists. One figure sets the direction of travel for 2026. In-scope systems doubled from 17 to 40 between FY22 and FY24 while the automated share of controls fell from 21% to 17%.

FAQ

Frequently Asked Questions

Seven blocks: scoping and risk assessment, control design and documentation, testing of design and operating effectiveness, remediation, audit preparation, the quarterly Section 302 certification sequence, and record retention. A usable checklist names an owner, a frequency, and the expected evidence for each line, because those three columns are what an auditor asks about. 

Entity-level controls covering the control environment, board oversight, fraud risk, and period-end reporting. Process-level controls addressing the assertions in each significant cycle. IT general controls over access, change management, and operations. Segregation of duties enforced in the system. No fixed list exists, since selection follows from risk-based scoping.

Agree scope and sample sizes with the external auditor in writing, index evidence by control reference so requests become retrievals, run a dry run on key controls around 90 days before year end, and keep the deficiency log current. Preparation that starts at year end has already failed, because the assessment covers the whole fiscal year. 

Three domains. Access management: provisioning approvals, timely revocation for leavers, privileged access restriction, and periodic access reviews. Change management: authorization before production migration, environment segregation, and retained testing evidence. IT operations: batch job monitoring, backup and restoration testing, and interface reconciliation.

The CEO and CFO certify personally on every 10-Q and 10-K. Supporting that signature takes sub-certifications from process owners, a current deficiency log, severity conclusions, documented communication of deficiencies and any fraud to the auditor and audit committee, a control change log reconciled to the disclosure, and confirmation that the officers read the version being filed.

Annual controls once, quarterly controls twice, monthly controls two to five times, weekly five to fifteen, daily twenty to forty. Testing runs in two phases, an interim round and a year-end roll-forward. Continuous controls monitoring replaces the sample entirely for high-volume controls by testing the full population on each extraction.

Section 802 requires accountants to retain audit and review workpapers for five years under 18 U.S.C. § 1520, extended to seven years for audit-related records by SEC Rule 2-06. Both bind the audit firm. Companies commonly adopt a seven-year policy to cover overlapping Exchange Act, tax, and state obligations, and to support litigation holds.

 

Alban Clot
Alban Clot began his career in consulting, where he spent several years as a Partner specializing in improving the quality of financial processes for large corporations. He then founded Supervizor in 2016, where he currently serves as Co-CEO in charge of product strategy. Alban is a graduate of ESCP Business School.
See more