A SOX compliance checklist is the list of internal controls a public company has to operate and prove each year so that management can certify its financial reports. Here is the short version, in the order most programs work through it:
- Scope the program. Pick the significant accounts, the processes and systems behind them, and a materiality threshold.
- Choose a framework and build a risk and control matrix. COSO is the default.
- Document entity-level controls, starting with the code of conduct, the annual risk assessment, and audit committee oversight.
- Set access controls and segregation of duties for every in-scope system.
- Put approval controls on transactions in purchasing, payables, revenue, payroll, and journal entries.
- Run reconciliation and close controls with a named preparer and reviewer on each one.
- Cover IT general controls for access, change management, operations, and outside service providers.
- Test design and operating effectiveness, then fix deficiencies before year-end.
- Certify and retain. Section 302 every quarter, Section 404 every year, records kept to your retention policy.
Each section below turns one of those lines into checklist items and says what evidence the auditor will ask to see. The evidence is where checklists fail, so it gets as much space as the controls.
Which SOX sections your checklist has to cover
Five sections of the Sarbanes-Oxley Act put work on a finance team’s calendar.
| Section | What it requires | What goes on your checklist |
|---|---|---|
| 302 | The CEO and CFO certify each quarterly and annual report, including that disclosure controls work | A dated sign-off packet every quarter, sub-certifications from process owners, and a record of deficiencies reported to the auditor and audit committee |
| 404(a) | Management assesses internal control over financial reporting (ICFR) and reports on it in the annual report | Risk and control matrix, process narratives, test results, and management’s written conclusion |
| 404(b) | The external auditor attests to management’s assessment | Evidence packages ready for testing under PCAOB AS 2201 (accelerated and large accelerated filers) |
| 409 | Disclose material changes in financial condition or operations on a rapid and current basis | A list of events that trigger a current report, with a named owner and an escalation path to whoever files |
| 802 | Criminal penalties of up to 20 years for destroying or altering records to obstruct an investigation | A written retention policy that is enforced in the systems, including email and chat, plus a legal hold process |
| 906 | Criminal penalties for certifying a report the officer knows is false | Fold it into the 302 sign-off so certifiers see the evidence before they sign |
For retention, the audit firm itself must keep its audit records for seven years after the audit under SEC Rule 2-06. That window is a sensible reference point when you set your own policy for the records behind the financial statements.
Who has to comply. SOX applies to every company registered with the SEC. The auditor attestation in 404(b) is narrower. It does not apply to emerging growth companies or to issuers that are neither accelerated nor large accelerated filers (15 U.S.C. 7262). Since the SEC’s 2020 amendments, a company that qualifies as a smaller reporting company and has annual revenues under $100 million is not an accelerated filer. Those companies still owe the management assessment under 404(a) and the 302 certifications every quarter. Private companies on the way to an IPO or owned by a public parent build SOX-style controls early, because the requirement arrives faster than a control environment can be built.
Step 1: Scope the program before you list controls
A checklist built before scoping covers too much in some places and misses accounts in others. Scope first.
- List every legal entity and business process that feeds the consolidated financial statements.
- Set a materiality threshold using a documented benchmark, and record how you chose it.
- Identify the significant accounts and disclosures, and the assertions at risk for each (existence, completeness, valuation, and so on).
- Map each significant account to the process that produces it and the systems that process runs in. Include spreadsheets and reports that feed the numbers.
- List the outside service providers that process financial data for you, such as payroll processors and payment platforms.
- Choose your control framework. Most public companies use the COSO Internal Control Integrated Framework. The SEC accepts other suitable frameworks, but COSO is the one auditors work in most.
The output of scoping is a risk and control matrix (RCM). Each row is one control, and each control answers the same questions:
| Field | Example: AP bill approval |
|---|---|
| Risk | A bill is paid that was not authorized |
| Control | Bills over the approval threshold are approved by the budget owner before payment |
| Owner | AP manager |
| Frequency | Every transaction |
| Type | Preventive, automated routing with a manual approval |
| Evidence | Approver name, decision, and timestamp stored on the bill record |
A key control is one whose failure could let a material misstatement go through undetected. Those are the controls the auditor tests, so they are the ones whose evidence has to be clean. The control families below are the SOX controls list most programs end up with.
Entity-level controls
These set the tone for everything else. Auditors look at them first because a weakness here changes how they test the rest.
- A documented control environment with a code of conduct, an ethics policy, a whistleblower process, and audit committee oversight.
- Annual sign-off on the code of conduct by employees in finance and other key roles.
- An annual risk assessment refreshed against the current business, with a named owner for each risk.
- Change management for the chart of accounts and for process changes that affect reporting.
- Management review of key financial reports, with the reviewer’s name and date captured.
- An escalation path for control deficiencies, with remediation deadlines tracked.
Entity-level controls fail at audit when the policy exists but the proof that it operated does not. A code of conduct nobody signed and a risk assessment dated three years ago both count against you. Treat each one as a recurring activity that leaves a record, not as a document you wrote once.
Access controls and segregation of duties
This family catches teams off guard because several teams own the controls and the evidence sits in several systems.
- User access reviews for every in-scope financial system on a stated cadence (quarterly is the common bar), with the reviewer’s name and date recorded against each access list.
- Separation of initiation, approval, and posting in payables, revenue, and journal entries. No one user can both create and approve a transaction in an in-scope cycle.
- Logging of privileged access in the ERP and connected systems, with periodic review of admin activity.
- A joiner, mover, and leaver process for finance system access, with evidence that access changes within a stated window of the HR change.
- Documented exceptions where duties cannot be separated, each with a compensating control and a management review.
Here is the part most SOX guides leave out. Segregation of duties is the control a small finance team is least able to meet in full, because there are not enough people to split every duty. The defensible approach is to document the exception and describe the compensating control, such as a review by someone outside the transaction. Then keep the record of that review every period.
Approval controls on transactions
This is where the audit trail question gets concrete.
- Every approval captures the approver’s name and a timestamp, not just the final approval in a chain.
- Approval thresholds follow a written delegation of authority matrix that is reviewed on a set schedule.
- Transactions outside the standard rule route to an explicit review instead of being approved in bulk.
- For automated approvals (posting under a threshold, for example), the rule that fired and the inputs it checked are documented.
- The full approval history is retained, including rejections and comments, not only the approved record.
Compare two ways of running bill approvals. In the first, approvals happen in email threads, and someone rebuilds the trail from inboxes when the auditor asks. In the second, the approver’s name and the time of the decision are written onto the bill record in the accounting system the moment the approval happens. The first can pass an audit, but only after someone spends weeks rebuilding the trail. The second passes because the record already exists.
The second pattern is a workflow that sends the approval request to the approver in the channel they already use, waits for the answer, and writes the decision back to the system of record. FlowRunner’s QuickBooks Online and Slack approval workflow pauses bills over a threshold for a manager decision in Slack and records the named approver and timestamp. The same structure works on Acumatica, where the AP approval cycle captures approver identity against each bill. If you are still defining the upstream step, the PO approval workflow shapes most of what your approval evidence will look like, and the approval routing use case shows the routing options.
Reconciliation and financial close controls
The close is where reconciliation evidence either exists or has to be reassembled.
- Balance sheet reconciliations for every account on a stated cadence, with preparer and reviewer recorded per account and per period.
- Bank, payment processor, and intercompany reconciliations, with the decision on every reconciling item retained.
- Journal entry review before posting, with the support attached to the entry rather than stored somewhere else.
- Review of manual and top-side journal entries, and of entries posted by unusual users or at unusual times.
- A close checklist with dated sign-offs at each milestone, tied to a named person.
- A periodic look at accounts that keep rolling forward with unexplained items.
The common failure is a reconciliation spreadsheet with the right numbers and no preparer name, no review evidence, and no explanation for the items that did not match. A reconciliation that records the preparer, the reviewer, and the decision on each item as the close runs produces evidence in the form auditors expect. FlowRunner’s workflow for reconciling Stripe payments against QuickBooks invoices keeps the decision history for each step.
Procure-to-pay, revenue, and payroll controls
Purchasing and payables carry some of the highest fraud and error risk, so auditors look hard at the preventive controls there.
- Vendor master validation and duplicate detection before a bill is created, with the check’s result kept against the bill.
- Three-way match of purchase order, receipt, and invoice where it applies, with mismatches routed for review rather than waived.
- Outlier checks on payment amounts, new vendors, and round-dollar invoices, with each exception decision logged.
- Verification of every vendor bank account change through a documented callback or second channel.
- Separation between vendor master maintenance, invoice entry, and payment release.
Revenue and payroll need the same treatment in their own terms.
- Revenue: contract review against your recognition policy, approval of credit memos and price overrides, and cutoff testing at period end.
- Payroll: approval of new hires and pay rate changes, review of each payroll register before release, and reconciliation of payroll to the general ledger.
A preventive control that runs at the moment of the transaction and routes the exception to a person leaves a cleaner audit record than a detective control that catches the same issue weeks later in a reversal. FlowRunner’s workflow for vendor validation and duplicate checks before bill creation is an example of the preventive pattern.
SOX IT checklist: IT general controls
IT general controls (ITGCs) are tested because every automated control and every system report is only as reliable as the system that runs it. If the ITGCs fail, the auditor cannot rely on the application controls above them.
| ITGC area | What to have in place | Evidence auditors ask for |
|---|---|---|
| Access management | Approved provisioning, timely removal at termination, periodic access reviews, restricted and logged privileged access, MFA for financial systems | Access requests with approvals, termination tickets matched to HR dates, signed access reviews, admin activity logs |
| Change management | Changes approved and tested before release, developers separated from the production push, an emergency change process | Change tickets with approval and test sign-off, a list of who can deploy, emergency changes reviewed after the fact |
| Computer operations | Backups with periodic restore tests, monitored scheduled jobs and interfaces, incident response | Backup and restore logs, job failure records and their resolution, incident tickets |
| New systems and data migration | Approved implementation plans, tested data conversion, sign-off before go-live | Project approvals, conversion reconciliations, go-live sign-off |
| Service providers | SOC 1 reports collected for providers that process financial data, with the user controls they expect you to run | SOC 1 reports reviewed each year, a mapping of the complementary user entity controls to your own controls |
One scoping point gets missed. Automations and integrations that post to the ledger are in-scope systems. A flow that creates bills in your ERP or syncs payments into your accounting system is part of the financial reporting process. It needs the same access control and change management as the ERP. You should be able to show who can edit it and who approved the last change before it went live.
If those automations run in FlowRunner, the Change Log records who created, changed, started, or stopped each flow and when. It is the audit trail included on the Professional plan and higher, and role-based access control on Professional limits who can edit flows. SSO comes with the Business plan (pricing).
SOX audit checklist: getting ready for testing
Audit readiness is its own checklist. Work through it before the auditor’s interim testing, not during it.
- Set up one evidence repository, organized by control, before testing begins.
- Walk through each material process with its control owner, and confirm the documented control matches what people do.
- Test design effectiveness first: would the control, operating as written, catch the risk?
- Then test operating effectiveness on a sample from the period, at the frequency the control runs.
- Classify every failure using the AS 2201 definitions: control deficiency, significant deficiency, or material weakness.
- Keep a remediation tracker with an owner, a deadline, and a retest date for each deficiency.
- Confirm last year’s findings stayed fixed.
- Roll interim testing forward to year-end, and draft management’s ICFR conclusion before the annual report deadline.
- Agree the timeline and evidence format with the external auditor early in the year.
When each SOX activity happens
| Cadence | Activities |
|---|---|
| Every transaction | Approvals, three-way match, duplicate and vendor checks, journal entry review |
| Monthly | Account reconciliations, close checklist sign-offs, review of manual journal entries |
| Quarterly | Section 302 certification and sub-certifications, user access reviews, interim control testing, remediation status |
| Annually | Risk assessment and scoping, RCM update, Section 404 management assessment, 404(b) audit where required, SOC 1 report review, code of conduct sign-off |
| As they happen | Joiners, movers, and leavers, system changes, vendor bank account changes, events that trigger a current report |
Where SOX checklists break: the evidence
Most of the cost of a SOX audit is the cost of reconstruction. Audit fees and the controller’s late nights before fieldwork both grow when the evidence was not where it needed to be when the auditor asked.
Auditors ask the same questions every year:
- Who approved it, and when?
- What supporting documents were attached?
- Why was an exception allowed?
- Who had access to the system at the time?
When those answers are captured as the transaction happens, in the system that owns the record, answering an evidence request means running a report. When they are not, someone has to rebuild them from email and memory.
The fix is unglamorous. Record who approved and when, plus the reason for any exception, at the moment of the transaction. Store it against the record it belongs to. Route exceptions to a person for an explicit decision, and keep the decision history next to the data.
No single system can do this alone, because financial reporting runs across many systems and the chat and email channels finance works in. Each control lives inside one system. The handoffs between systems are where approvals travel and reconciling items get explained, and none of the systems of record watches those handoffs. That gap is the job of an orchestration layer. It sits above the systems of record, moves the work between them, and pauses for a person when a decision needs judgment. Then it writes the evidence back into the system that owns the record. FlowRunner is built for that layer, around agents that know when to stop and ask a person. Human-in-the-loop is an execution pattern where AI agents pause autonomously, assemble the relevant context and the decision choices available, route to a human via their preferred channel, and resume the moment the human responds. In a SOX approval, that channel is Slack, email, WhatsApp, or phone, and it is included on every FlowRunner plan.
No software is a SOX certification. SOX compliance is the issuing company’s responsibility, and no automation tool satisfies Section 404 by itself. What a workflow layer does is produce the evidence your controls are designed to produce, in the form auditors expect. For the reporting side of that, see automated compliance reporting. If you are weighing a GRC platform against a workflow layer, the Vanta comparison for SOX covers where each fits.
Putting the checklist into practice
For a first-year SOX program, or one that has gone stale, this order works:
- Map each control to the system that holds its evidence. If the evidence does not live somewhere you can query, that is the first gap to close.
- Start with approvals, access, and reconciliations. These families depend on people acting at the moment of work, so their evidence is the most likely to be missing when the auditor asks.
- Design for the exceptions. The control that holds up is the one that handles the unusual case on purpose.
- Talk to the external auditor about control design early in the year. A short conversation in the first quarter costs less than a finding at year-end.
- Prefer fewer controls that produce clean evidence over a long list of controls that run on trust.
A SOX checklist is finished when every line names a control, an owner, a cadence, and a place where the evidence already sits. If you would rather have the approval or reconciliation flows built than build them yourself, our implementation team can set them up in your FlowRunner workspace.
Frequently asked questions
What is a SOX compliance checklist?
It is the list of internal controls a public company has to run and prove each year so that management can certify its financial reports under Sections 302 and 404. A useful one names each control, its owner, how often it runs, and where the evidence lives.
What are the key controls for SOX?
SOX does not publish a fixed list. Each company picks its key controls from its own risk assessment, and they fall into a few families: entity-level controls, access and segregation of duties, transaction approvals, reconciliations and the financial close, and IT general controls. A key control is one whose failure could let a material misstatement go undetected.
What are IT general controls (ITGCs) in a SOX audit?
ITGCs are the controls over the systems that produce financial data: who can access them, how changes are approved and tested, how backups and scheduled jobs run, and how outside service providers are reviewed. Auditors test them because automated controls and system reports are only reliable if the systems behind them are controlled.
What is the difference between SOX 302 and SOX 404?
Section 302 requires the CEO and CFO to certify each quarterly and annual report, including that disclosure controls work. Section 404 requires management to assess internal control over financial reporting every year, and for larger filers the external auditor must attest to that assessment under PCAOB AS 2201.
Does SOX apply to private companies?
SOX applies to companies registered with the SEC. Private companies on the way to an IPO or owned by a public parent build SOX-style controls early so they are ready when the requirement arrives.
How often are SOX controls tested?
Management tests key controls every year to support the annual Section 404 assessment, and the CEO and CFO certify under Section 302 every quarter. Within the year, each control runs on its own cadence, from every transaction to monthly reconciliations to quarterly access reviews.
What are the penalties for SOX non-compliance?
Under Section 906, an officer who knowingly certifies a false report faces fines up to $1 million and up to 10 years in prison, rising to $5 million and 20 years when the false certification is willful. Section 802 makes destroying or altering records to obstruct an investigation punishable by up to 20 years.