← Back to Insights
Insight  •  SOX Compliance

What a First-Year SOX Program Actually Takes

Scoping, walkthroughs, testing and the decisions in between, in the order they really happen.

November 2026    5 min read
01

Most of the first year goes into understanding how the business really works, before testing starts.

02

Scoping decisions made in the first month shape the cost of every month after.

03

The aim for year one is a program the team can run again, not a perfect binder.

Most companies come to their first year of SOX expecting a testing project. What they get is closer to an education in how their own business works.

The testing does happen. Before anyone tests a control, though, someone has to agree which accounts matter, find out how transactions actually move through the systems, and write down controls that people may have been performing for years without ever calling them controls.

It helps to know the order things tend to happen in, and where the time usually goes.

A note on scope: every public company's management has to assess and report on internal control over financial reporting each year. Larger filers also need their external auditor to attest to those controls. Newly public companies generally get a transition period, so when a "first year" actually lands depends on the company.

The first year, and what tends to followThe stages of a first-year program, with what recent filings show about material weaknesses.
A first-year program
Fiscal 2025 filings
0
public companies disclosed a material weakness in internal control over financial reporting.
2021 to 2025
0%
of companies with a material weakness reported one in more than one year.
⚙
Most-cited systems issue: IT general controls, especially user access.
Source: KPMG, Trends in material weaknesses (2026), based on fiscal 2025 SEC filings sourced from Audit Analytics.
The program, step by step
01Scope

Scoping Comes First, and It Sets the Budget

Everything starts with deciding what is in scope: which accounts and disclosures are material, which locations and business units matter, and which systems feed them. There is always pressure to get through this quickly and on to the real work. That is usually where the overrun begins.

Scope too broadly and the team spends a year documenting and testing controls over balances that were never going to cause a misstatement. Scope too narrowly and the external auditor finds the gap later, when it costs more to close. Getting the external auditor's view before the plan is locked saves a surprising amount of rework.

02Walkthroughs

Walkthroughs Are Where You Learn the Business

A walkthrough follows one transaction from start to finish. An invoice from receipt to payment. An order from entry to cash. On paper it is simple. In practice it is where most first-year discoveries happen.

The procedure says three-way match. The walkthrough shows that one buyer can override the match for anything under a set amount, and nobody looks at the override report. The narrative says the controller reviews the reconciliations. The walkthrough shows the review does happen, on a printed copy that is never kept.

None of this is unusual. Finding it is what the first year is for.

An illustrative example

A newly public manufacturer assumed its revenue process was straightforward. The walkthrough found that about a third of its orders came through a distributor portal that fed the ERP overnight, with no reconciliation between the two. Nobody had flagged it, because the numbers had always tied at quarter end. Building a daily check took two weeks. Finding the gap took one walkthrough.

Hands unrolling architectural plans on a wooden desk
Worth remembering

Much of a first-year program is writing down what people already do, clearly enough that someone else could do it next year.

03Design

Design Before Testing

Once the processes are written down, each control needs a design review. If it operated exactly as described, would it actually catch the error it is meant to catch? Plenty of controls fail at this stage without ever being tested. A review with no defined threshold. An approval by the same person who entered the transaction. A reconciliation that compares a report to itself.

Fixing design problems before testing starts is far cheaper than finding them during testing. This is also the point where the program stops describing what exists and starts deciding what should.

04Testing

Testing, Remediation and the First Report

Year-one testing usually sorts controls into three groups: the ones that work, the ones that do not, and the ones that work but cannot be evidenced. The third group is often the largest. It is also the easiest to fix, as long as it is found early enough to remediate and retest before year end.

Systems deserve extra attention. In KPMG's review of fiscal 2025 filings, IT general controls, especially user access, were the most-cited systems issue behind material weaknesses. A user access review nobody can evidence is a small problem in October and a much bigger one in February.

The first year is also rarely the only year with problems. Of the companies KPMG tracked with a material weakness between 2021 and 2025, more than a third reported one in more than one year. Most of those repeats go back to things a first-year program could have settled: unclear ownership, thin evidence, and processes that were documented once and never revisited.

05

What a Good First Year Leaves Behind

A first-year program is not finished when the report is signed. It is finished when year two can run without starting over.

That means narratives someone new could actually follow. Control owners who know they are control owners. Evidence kept in one place, in a form the auditors accept. And a written scoping rationale, so next year's team is not rebuilding last year's decisions from memory.

The best first-year SOX programs feel a little routine by year two. That is the goal.

SourcesKPMG, Trends in material weaknesses (2026), based on fiscal 2025 SEC filings sourced from Audit Analytics.

Have a Specific Problem to Work Through?

An aging finding, control issue, documentation gap, or workstream short on capacity is enough of a starting point. Tell us what is happening and what you need to be true at the end.

Tell us what is stuck, what changed, or what deadline is driving the need. We can determine whether BPS Advisory Group is the right fit and what a sensible scope would look like.