Start hereScope financial reporting risks
~144 days leftOpen step
Guide library
Audit report North America

SOX Section 404

Sarbanes–Oxley Act Section 404 · Internal control over financial reporting

Build management’s internal-control assessment and support an integrated external audit where required.

Who it applies to

SEC reporting issuers subject to Section 404. External auditor attestation depends on filer status and applicable exemptions.

What you’ll produce

Management’s ICFR report and, where required, external auditor’s opinion on ICFR.

Confirm filer status and management assessment versus auditor attestation duties. Consider service organization controls and complementary user controls.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which entities and reporting risks are in scope?
The CFO and Controller should confirm filer obligations, significant accounts, relevant assertions, locations and systems. Coordinate with the external auditor where attestation applies.
Who can conclude on a deficiency?
Define how Control Owners, Internal Audit, the Controller, Legal and the Audit Committee review and escalate findings. Give named owners access to evidence and time to remediate before year-end.
Where does the project need resources?
Estimate testing time by control frequency, evidence availability and tester independence. Reserve capacity for late remediation and retesting. Confirm external auditor scope and timing separately.

How to spend the first week

  1. Bring trial balance, consolidated financial statements, filer status, location information, prior findings and recent acquisitions or systems changes.
  2. Choose a material transaction cycle and run one walkthrough. Confirm where evidence lives and who can extract complete populations.
  3. Set the testing and reporting calendar around close cycles, remediation lead time, auditor coordination and the Audit Committee schedule.

What to review each week

Report key controls without design or operating evidence, deficiencies by status and potential severity, and remediation that cannot be retested before reporting.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

SOX Section 404 kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Scope financial reporting risks · Controller + audit committee [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Bring trial balance, consolidated financial statements, filer status, location information, prior findings and recent acquisitions or systems changes.
2. Choose a material transaction cycle and run one walkthrough. Confirm where evidence lives and who can extract complete populations.
3. Set the testing and reporting calendar around close cycles, remediation lead time, auditor coordination and the Audit Committee schedule.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
The whole journeyabout 144 days across 4 steps
  1. 01Scope financial reporting risksController + audit committee · ~21 days
  2. 02Document key controls and ownershipProcess owners + IT controls lead · ~35 days
  3. 03Execute testing and evaluate deficienciesManagement testing team + external auditor where required · ~60 days
  4. 04Complete reporting and governance reviewManagement + audit committee + independent auditor if applicable · ~28 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 12 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Scope financial reporting risksController + audit committeeBefore annual testingSet a start dateScoping memo; Significant account map; Annual calendarOpen
Document key controls and ownershipProcess owners + IT controls leadBefore walkthroughsSet a start dateNarratives; Risk-control matrices; Evidence requirementsOpen
Execute testing and evaluate deficienciesManagement testing team + external auditor where requiredThroughout fiscal year and at year-endSet a start dateTest workpapers; Deficiency evaluation; Remediation evidenceOpen
Complete reporting and governance reviewManagement + audit committee + independent auditor if applicableAt annual filing milestonesSet a start dateManagement report; Auditor opinion if required; Audit committee materialsOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Scope financial reporting risks

    Who Controller + audit committee When Before annual testing

    Identify significant accounts, assertions, locations, processes, vendors and IT dependencies. Align criteria, scope and plan with leadership.

    How to do this step

    Before you start

    Trial balance, material accounts and disclosures, legal entity map, prior deficiencies and financial systems.

    1. Map significant accounts and disclosures to relevant assertions and the processes that can generate a material misstatement.
    2. Identify which locations, outsourced services and systems influence those risks. Combine quantitative and qualitative considerations and document exclusions.
    3. Reconcile the approved scope to the reporting calendar, tester capacity and engagement with the auditor.

    What a reviewer should see

    The account map connects revenue cut-off to order capture, invoicing, journals, report dependencies and the relevant locations.

    When to escalate

    Escalate a new acquisition, major system change or unresolved scope exclusion before testing plans are finalized.

    What to produce

    Scoping memoMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

    Significant account mapSpreadsheet

    Gather first

    • Asset exports or system discovery
    • Service owner interviews
    • Approved scope and architecture

    How to prepare it

    1. Export a dated baseline from the source system. Give each asset, service or record class a stable ID and remove duplicates without losing links to the source.
    2. Add ownership, purpose, sensitivity and any vendor or system it depends on. Mark unknowns explicitly and assign them to someone to resolve.
    3. Reconcile the register against an independent source such as cloud billing or the production deployment list. Set a refresh cadence and an owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    ID
    SYS-014
    Item
    Production billing database
    Owner
    Platform operations
    Location and purpose
    Production EU region, stores invoice and account data
    Impact and dependencies
    High. Identity provider and managed backups.
    Verified on
    2026-11-10, cloud inventory export

    Check before handing it over

    Each item has one accountable owner. The source and as-of date let a reviewer trace it back.

    Share the reviewed inventory with the people building the control, privacy or testing scope.

    Annual calendarSpreadsheet

    Gather first

    • Current obligations, expiry dates or audit window
    • Delivery dependencies and owner availability
    • Official rules or engagement confirmation

    How to prepare it

    1. Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
    2. Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
    3. Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Milestone
    Quarterly access review approved
    Date and kind
    2026-12-18, internal target
    Trigger or source
    Internal access control schedule v3
    Prerequisite
    Access export by 2026-12-09
    Owner and reminder
    IAM lead, remind one week before
    Status
    Scheduled

    Check before handing it over

    Every external deadline links to a real source. Planning targets are visibly marked.

    Add approved dates to the team calendar and share them with the people scheduled to deliver or review.

  2. 02

    Document key controls and ownership

    Who Process owners + IT controls lead When Before walkthroughs

    Trace end-to-end flows and risks. Identify key control activities, IT general controls, relevant reports and complementary user controls.

    How to do this step

    Before you start

    Process narratives, scoped assertions, system reports and evidence of a recent transaction.

    1. Walk a transaction from origin to financial statement and inspect the evidence for each control. Include manual overrides and processing that bypasses the main path.
    2. Define each key control’s trigger, owner, reviewer, evidence, error threshold and required follow-up. For reports or spreadsheets used in controls, document how the owner checks accuracy and completeness.
    3. Check that the control would detect or prevent the specific misstatement in time. Agree the design assessment and owner’s responsibilities.

    What a reviewer should see

    A revenue cut-off review records the reporting parameters, shipments near period end, reviewer’s criteria, exceptions and disposition.

    When to escalate

    Raise missing segregation of duties, review thresholds or report validation when they affect the control design.

    What to produce

    NarrativesMemo

    Gather first

    • Approved system boundary
    • Architecture, data flows, controls and service commitments
    • Current reporting instructions or system plan template

    How to prepare it

    1. Explain who uses the system, the commitments it supports and how people, processes, software, infrastructure and data fit together.
    2. Walk through actual transactions or requests and identify the relevant controls and shared responsibilities. Cover dependencies and any criteria or requirements in the agreed template.
    3. Validate each section with the technical owner against live architecture, procedures and evidence. Lock the approved version and reconcile it to diagrams and control records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Service and objective
    Hosted invoice service receives orders, calculates amounts and sends PDF receipts.
    Boundary and inputs
    Accepted production order events, account identifiers and billing records
    How it works
    Payment result updates invoice status. Release pipeline deploys code with approval.
    Shared roles
    Customer controls user configuration. Hosting vendor manages physical infrastructure.
    Evidence and review
    Architecture v3, deployment records and service-owner review

    Check before handing it over

    The written description, diagrams and control records agree. A reviewer can understand end-to-end operation.

    Send the approved draft to management and the independent evaluator. Transfer it to the prescribed system plan or report template when needed.

    Risk-control matricesSpreadsheet

    Gather first

    • Applicable criteria, requirements or risk decisions
    • Current procedures and configurations
    • Names of people operating or reviewing each control

    How to prepare it

    1. Give each requirement and implemented control an ID. Write a short control statement naming who does what, when and in which system.
    2. Record the evidence the control produces and how it could be tested. For a shared or inherited control, state who owns each part.
    3. Walk through one control with its operator. Check a real recent run, record gaps and obtain approval for exclusions or alternate controls.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement
    Production access is reviewed periodically.
    Control ID
    AC-04
    Control activity
    IAM team exports administrator roles every quarter. System owners approve or revoke each assignment.
    Owner and frequency
    IAM lead, quarterly
    Evidence
    Export with filters, annotated review and removal tickets
    Test and status
    Reconcile export to current roles. Inspect approvals. Operating.

    Check before handing it over

    A different person can operate the control or test it using the matrix and its evidence links.

    Give the baseline to control owners and the assessor before walkthroughs or sampling.

    Evidence requirementsSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

  3. 03

    Execute testing and evaluate deficiencies

    Who Management testing team + external auditor where required When Throughout fiscal year and at year-end

    Evaluate design and operating effectiveness. Document populations and samples, classify deficiencies and assess remediation and retesting.

    How to do this step

    Before you start

    Approved test plan, dated population extracts, evidence, earlier test results and remediation status.

    1. Capture population source, parameters and counts. Use the testing plan to select items and record why the coverage fits the frequency and risk.
    2. Document tests and results at item level. Preserve any late approval or missing evidence as an exception and test any compensating control relied upon.
    3. Have management assess likelihood, potential magnitude and aggregation. Preserve the basis for the deficiency’s evaluation, corrective action and retest.

    What a reviewer should see

    A reviewer can trace a result from the workpaper to the sampled transaction, supporting evidence and documented conclusion, with reviewer and date.

    When to escalate

    Promptly raise possible significant deficiencies or material weaknesses through the agreed governance route, including recurring or interacting deficiencies.

    What to produce

    Test workpapersMemo

    Gather first

    • Approved test scope and criteria
    • Population and sample records
    • Test approach, results and reviewer requirements

    How to prepare it

    1. State objective, dates, scope and the method before describing results. Record the tester, any independence requirements, and how samples were selected.
    2. For each item, compare what should have happened with what the evidence shows. Describe impact and link the evidence or recorded exception.
    3. Add limitations, obtain review and give each finding an owner and a date. Retain the underlying samples and calculations with the signed version.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Test objective
    Check that production role removals happen within the internal deadline.
    Method and population
    All September departures. Test each privileged account.
    Expected result
    Remove access within one business day.
    Observed result
    11 on time. One late by two days, ticket IAM-114.
    Finding and follow-up
    F-008. Retest the next departure and verify alerting.

    Check before handing it over

    Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.

    Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.

    Deficiency evaluationMemo

    Gather first

    • Agenda or decision request
    • Current performance measures and findings
    • Proposed actions and participants

    How to prepare it

    1. Write what decision is needed and list the reports or records the decision maker reviewed. Capture the date, people and decision authority.
    2. Record the decision, alternatives considered, any remaining risk and exactly who will do what by when.
    3. Send notes for factual review. File the approved record and add actions to the working tracker so progress reaches the next review.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Item
    Approve a fix for the missing access-removal retry.
    Inputs reviewed
    September test results and IAM incident root-cause notes.
    Decision
    Approve automatic retry plus daily reconciliation.
    Action and due date
    Platform lead to ship and test by 2026-11-28.
    Residual risk and follow-up
    Manual review remains until rollout. Check at December meeting.

    Check before handing it over

    The minutes identify the person who approved each action and the date the decision will be revisited.

    Give owners the actions and add the approved record to the relevant audit or governance file.

    Remediation evidenceSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

  4. 04

    Complete reporting and governance review

    Who Management + audit committee + independent auditor if applicable When At annual filing milestones

    Coordinate year-end roll-forward and evidence. Finalize management’s assessment and reporting, auditor attestation where required and governance communications.

    How to do this step

    Before you start

    Testing conclusions, deficiency evaluations, compensating control results, remediation retests and financial reporting timetable.

    1. Tie management’s conclusion to the evidence as of the reporting date, and reconcile it with disclosures and auditor communications where applicable.
    2. Prepare the Audit Committee pack with open deficiencies, severity rationale, remediation ownership and items affecting the conclusion.
    3. Keep the signed assessment and supporting workpapers. Move unresolved improvements into the next cycle with owners and dates.

    What a reviewer should see

    The reporting pack includes final management and governance approvals and traceable conclusions for issues that could affect internal control reporting.

    When to escalate

    Raise disagreements about severity, scope or disclosure with the Controller and Legal before reporting and arrange timely communication with the Audit Committee.

    What to produce

    Management reportMemo

    Gather first

    • Applicable form or requirements
    • Approved scope and supporting records
    • Named signatory and approval route

    How to prepare it

    1. Identify which person can sign and what they must confirm. Gather supporting evidence, dates, responsibility and any required issuer wording.
    2. Draft a signed-document checklist or brief in your organization’s approved format. Reconcile every factual claim against the source evidence and route the draft for review.
    3. Use the applicable official wording or format for the real signed document. File the executed copy with its date, applicable scope and supporting evidence.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document owner
    Accountable executive or authorized signatory
    Scope and date
    Agreed service scope, as of 2026-10-31
    Supporting documents
    Scope v3, final control testing and open issue review
    Review and approval
    Legal and responsibility owner review before signature
    Filed record
    Signed copy plus evidence references

    Check before handing it over

    The signer can explain the basis for each statement and the record reflects the required scope and period.

    Give the executed document to the relevant recipient under the engagement or regulation. Use the worksheet to organize review.

    Auditor opinion if requiredIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

    Audit committee materialsMemo

    Gather first

    • Agenda or decision request
    • Current performance measures and findings
    • Proposed actions and participants

    How to prepare it

    1. Write what decision is needed and list the reports or records the decision maker reviewed. Capture the date, people and decision authority.
    2. Record the decision, alternatives considered, any remaining risk and exactly who will do what by when.
    3. Send notes for factual review. File the approved record and add actions to the working tracker so progress reaches the next review.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Item
    Approve a fix for the missing access-removal retry.
    Inputs reviewed
    September test results and IAM incident root-cause notes.
    Decision
    Approve automatic retry plus daily reconciliation.
    Action and due date
    Platform lead to ship and test by 2026-11-28.
    Residual risk and follow-up
    Manual review remains until rollout. Check at December meeting.

    Check before handing it over

    The minutes identify the person who approved each action and the date the decision will be revisited.

    Give owners the actions and add the approved record to the relevant audit or governance file.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes