Blog

SOX-Ready Close Automation: How to Evidence Controls for External Audit

SOX-Ready Close Automation: How to Evidence Controls for External Audit

Written by

Naman Mathur

Published on

Key Takeaways

  • Under the Sarbanes-Oxley Act (SOX), auditors sample evidence. SOX-ready close automation creates it as work happens, with every approval and sign-off timestamped.

  • Run a six-step audit trail test in every demo, including a self-approval attempt and a ledger balance change after sign-off.

  • Reconciliation sign-off counts as evidence only when it records preparer, reviewer, support and match basis. Late intercompany breaks become top-side adjustments auditors must test.

  • Brief the audit committee at shortlisting. Under Provision 29, the board declares material controls effective, and the external auditor is not required to test them.

Auditors don't test features. They take a sample from a population and ask you to prove each item happened the way your control says it did. Choosing SOX-ready close automation software comes down to whether the platform produces that proof by default for your external audit.

The standard advice gets this backwards. Shortlists are built on feature checklists, which treat evidence as something collected later rather than created as the work happens.

We have written before about treating SOX as an evidence standard, and this guide applies that view to the auditor's request list. It answers what to look for, how to evidence controls, which software helps, and how to handle audit trails, reconciliations, intercompany and your audit committee.

What Should Finance Teams Look for in SOX-Ready Close Automation Software?

Look for software that produces the evidence an auditor samples as a by-product of doing the work. Enforced segregation of duties (SoD) and general ledger (GL) posting gates stop the wrong entry. A continuous audit trail, locked periods, read-only auditor access and vendor assurance prove what happened.

For groups with a US listing or a US-listed parent, Section 404 of the Sarbanes-Oxley Act (SOX 404) requires management to assess internal control over financial reporting (ICFR), and larger filers also need an auditor attestation under the Public Company Accounting Oversight Board's (PCAOB) Auditing Standard (AS) 2201. UK groups now face a parallel requirement: under Provision 29 of the UK Corporate Governance Code 2024, the board declares its material controls effective. Both rest on the same thing, evidence that each key control operated.

SoD has to be enforced by the system at task level, because a policy saying preparers cannot review their own work only describes the design. A GL posting gate means nothing reaches the ledger until the approval and its support exist. Every action should record who did it and when, and sign-off should lock the period.

Then check assurance over the vendor itself. Ask for a System and Organization Controls (SOC) 2 Type II report and an ISO 27001:2022 certificate.

If your auditor treats the platform as part of your financial reporting system, they may want a type 2 report on the vendor's controls. One option is SOC 1, a framework of the American Institute of Certified Public Accountants (AICPA). The AICPA SOC 1 overview describes it as an examination of a service organisation's controls likely to be relevant to user entities' ICFR.

International Standard on Auditing (UK) 402, or ISA (UK) 402, covers how auditors use these reports. The ISA (UK) 402 service organisations guidance notes that type 1 or 2 reports may be issued under International Standard on Assurance Engagements (ISAE) 3402. It also makes clear that a type 1 report gives no evidence of operating effectiveness.

No software makes a company SOX compliant, because the company owns the controls and the assessment. The platform is the execution layer that runs the work and keeps the record, so test it on exactly that.

What an Auditor Asks for in a Close: The Evidence List

Start your evaluation from the prepared by client (PBC) list, the requests your auditor sends before fieldwork. Each item is audit evidence and should come straight from a close artefact.

UK regulators look at the same areas. The Financial Reporting Council (FRC) inspects audits of UK public interest entities each year. The FRC Annual Review 2026 lists journals testing and group audit oversight among the six most frequently inspected areas.

PBC request

What the auditor checks

Close artefact that should produce it

Journal population with approvals

Completeness, approval before posting

Posting log with approver, timestamp and support

Reconciliations with preparer, reviewer and date

Timely, independent review

Signed reconciliation with support and exceptions

User access lists and changes

Who could approve or post, and when that changed

Role history and access change log

Period lock evidence

No unapproved entries after close

Lock record and reopen log

Exception logs

Unusual items investigated and cleared

Exception list with owner and ageing

Intercompany agreement

Both sides agree before elimination

Counterparty confirmation per entity pair

Change logs for rules and templates

Logic changed only under control

Versioned history of rules and checklists

Source: Stacks implementation practice, 2026.

Use the table as your evaluation script. Ask the vendor to show each artefact in a working environment, and note every row where the honest answer is a spreadsheet.

How Can Finance Teams Demonstrate SOX Compliance Using an Automated Close Platform?

You demonstrate SOX compliance by showing that each key control operated, every period, from records created when the work was done. The platform's job is to make those records complete and impossible to backfill.

Auditors look at controls in two stages, starting with design and implementation. Where they plan to rely on a control, the ISA (UK) 330 testing controls guidance requires a separate test of operating effectiveness.

That test samples from the population, which is where manual closes struggle. If approvals live in email and sign-offs in a spreadsheet, you cannot prove completeness. An auditor who doubts completeness widens the sample or stops relying on the control.

For UK groups with a US listing, SOX evidence also forms the base for Provision 29 of the UK Corporate Governance Code 2024. The FRC on material controls notes "the majority of companies are suggesting that they have identified somewhere between 30 and 50 material controls". The same guidance says SOX reporters are building on their existing approach, as Provision 29 goes beyond SOX financial controls.

Treat the 30 to 50 figure as a sense of scale, not a target. Map each key or material control to the artefact that proves it, then reuse the map for both regimes.

How Does Close Automation Software Support Internal Controls Testing?

Close automation supports internal controls testing by giving the auditor complete populations to sample and a stored artefact for every control instance. The table maps common close controls to both.

Control

Test the auditor runs

Artefact the platform should produce

Journal approval

Confirm approval preceded posting

Approval and posting timestamps

Reconciliation review

Confirm timely independent review

Preparer, reviewer, dates and support

Segregation of duties

Look for self-approval

SoD conflict report and blocked-attempt log

User access review

Confirm review and leaver removal

Dated access review with role changes

Automated matching

Test the rule, then change control

Rule version history and per-item match basis

Period lock

Look for entries after close

Lock record and reopen log

Source: Stacks implementation practice, 2026.

An automated control should behave the same way until someone changes it, so auditors often focus on IT general controls (ITGCs) over change management. Under ISA (UK) 315 automated controls guidance, weak ITGCs can affect whether the auditor relies on automated controls at all. That makes the matching rule's change log key evidence.

Artificial intelligence (AI) matching needs the same discipline. A deterministic rule gives the same result every run, so the auditor can re-perform it. An AI-suggested match is testable when the platform stores each item's basis and routes it through approval or a documented threshold.

Ask each vendor to show both records for one cleared item. Our approvals and audit trail checklist covers the approval side in more detail.

What Software Helps Companies Prepare for External Audits?

We group the software that helps companies prepare for external audits into four categories. They are close management and reconciliation platforms, enterprise resource planning (ERP) logs, PBC trackers or audit portals, and consolidation tools. They differ in where the evidence comes from.

An ERP log records who posted, but rarely why or against what support. A PBC tracker organises requests well, yet someone still finds and uploads each item. Consolidation tools hold group adjustments, but they only see the result of the close.

Our view is that the platform which runs the work prepares you best. Evidence created at preparation and review needs no collection exercise and cannot drift from its balance. Read-only auditor access then removes many PBC requests, because the auditor pulls samples with support in context.

We describe that model as being audit-ready by default. Test any vendor against your last PBC list: how many rows would their platform have answered without a person in the middle?

What Should Finance Teams Look for in a Platform's Audit Trail and Documentation Capabilities?

Look for an audit trail captured at the moment of work, held in an immutable log and linked to the balance and its support. It should also cover configuration changes and user access, and export as a whole.

The documentation standard comes from ISA (UK) 230, which governs the auditor's own file. Under the ISA (UK) 230 documentation requirement, documentation must enable an experienced auditor with no previous connection with the audit to understand the work.

That duty sits with the auditor, but it is a good test for management's records too. If an outsider cannot follow your trail without a guided tour, expect a longer walkthrough. Ask whether an administrator can edit a log entry, and remember that a changed threshold alters every control instance after it.

Which Financial Close Platforms Provide a Complete Audit Trail? A Test You Can Run in a Demo

Criteria travel better than rankings. A platform provides a complete audit trail if it passes all six steps below, run live in its own demo environment.

  1. Ask the presenter to approve a journal they prepared. A pass is a hard block, with the attempt logged.

  2. Try to post a journal to the GL before approval. A pass is a gate that holds until approval and support exist.

  3. Change an ERP balance after the reconciliation is signed off. A pass is an automatic reopen, with both balances recorded.

  4. Change a user's role mid-period. A pass is a dated entry showing who made the change and what access it granted.

  5. Edit a matching rule. A pass is a versioned record showing the editor, the time, the old rule and the new one.

  6. Export the full trail and give it to a colleague who didn't watch. A pass is a colleague who can explain what happened.

In our experience, step six is where most demos fall apart. Run it with someone from internal audit if you can.

How Do Reconciliation Automation Platforms Document Sign-Off for Audit Purposes?

Reconciliation automation platforms document sign-off by attaching a full record to each reconciliation. It holds preparer, reviewer, timestamps and support, plus the match basis for auto-cleared items, exceptions with owners and any reopen record.

The match basis is the piece most often missing. When a platform clears thousands of bank lines, the reviewer signs one reconciliation. The auditor still needs to see why each line cleared, or the sign-off covers work nobody can re-perform. The support usually sits outside the ERP, in Stripe or Adyen payouts, Pleo or Coupa spend, or a payroll file, so the sign-off record has to link to those source records, not just the GL balance.

A reconciliation can also balance for the wrong reason. Two offsetting errors, or a plug to suspense, produce a zero difference and a clean sign-off. Exception ageing and a recorded match basis let a reviewer catch it.

Record the risk rating and frequency for each account, so the auditor can test against your policy. Treat auto-certification thresholds as policy too, approved and versioned like any control. Our guide to reconciliations across entities covers this at group scale.

What's the Impact of Poor Intercompany Reconciliation on Audit Timelines?

Poor intercompany reconciliation pushes problems to consolidation, where late breaks become top-side adjustments. The group auditor must test them and component auditors must chase the entities behind them, which extends fieldwork.

The arithmetic explains it. Ten entities trading with each other create 45 possible pairs, and 40 entities create 780.

Offsetting errors make it worse. Two breaks in opposite directions can net to zero at matrix level, so consolidation balances while two entities hold wrong numbers.

Foreign exchange (FX) adds another layer for groups applying International Accounting Standard 21 (IAS 21). IAS 21 requires foreign currency monetary items to be translated at the closing rate. In our experience, intercompany breaks appear when two entities apply different rates or rate dates.

Group audit oversight is among the FRC's most frequently inspected areas, and its 2025/26 focus included ISA (UK) 600 (Revised), the group audit standard. In our experience, unexplained eliminations send questions to every component involved, and each answer takes days.

Track two measures before and after any change: unmatched intercompany value at day one of close, and breaks aged over 30 days. Our article on choosing intercompany accounting software covers what to automate first.

How Should Finance Teams Involve Their Audit Committee in Evaluating Close Automation Software?

Brief the audit committee at shortlisting and show them evidence from a parallel run before contract. Bring the external auditor's view on reliance, and report back after the first live close. No FRC rule requires this, but the evidence question lands on the committee anyway.

Provision 29 is why. For periods beginning on or after 1 January 2026, boards of UK Corporate Governance Code 2024 companies declare material controls effective, on a comply-or-explain basis. FRC guidance limits the auditor's Provision 29 responsibilities: "the auditor is not required to test the design, implementation and operating effectiveness of the material controls".

The auditor may still test overlapping controls for the financial statement audit. Its opinion does not cover the Provision 29 statement, so the board, usually through the audit committee, owns the evidence.

What to Show the Audit Committee: The Evidence Pack

The FRC audit committee minimum standard asks audit committees to review the management letter and "establish whether recommendations have been acted upon". It was written for FTSE 350 audit committees and is good practice for others. A close platform decision should arrive with this pack:

  • A control map linking each key or material control to its platform artefact

  • An exported audit trail covering one full close of the parallel run

  • An SoD conflict report from the pilot, showing blocked attempts

  • An exception ageing report from the same close

  • The vendor's SOC 2 Type II report and ISO 27001:2022 certificate

  • The external auditor's written view on relying on the platform's records

  • A list of open management letter points the platform would close

Questions Audit Committees Typically Ask About Controls and Evidence

Expect these questions, and answer them in the pack:

  • Who can override a control, and where is the override recorded?

  • What happens when a balance moves after sign-off?

  • How often is user access reviewed, and by whom?

  • What does the external auditor think of the platform's evidence?

  • If we leave the vendor, how do we export the full trail?

  • Who in finance reviews the vendor's SOC report each year?

  • How are AI outputs reviewed before they affect the ledger?

Why Standard Audit-Prep Advice Fails

The common playbook pairs a PBC tracker with a year-end clean-up sprint. The exported system log then goes to the auditor as the trail.

It deserves a fair hearing. For a two-entity group with a small journal population, a well-run tracker and a disciplined sprint work, and the auditor can follow them.

Our view is that it breaks as the group grows. Evidence created in a sprint is created after the fact, and auditors notice a sign-off dated weeks after the period closed. The exported log floats free of the balances, so someone still ties each entry to a reconciliation by hand.

The deeper failure is recurrence. A sprint fixes this year's findings but builds nothing to stop them, so the same management letter points return. The alternative is evidence produced every period by the process itself, covered in our piece on staying audit-ready all period.

A Pre-Audit Readiness Checklist

Run this audit readiness check four to six weeks before fieldwork. Each item has a pass condition you can verify before the auditor does.

Checklist item

Pass condition

Journal population

Complete, with approver and support on every manual journal

Reconciliation sign-off

Every in-scope reconciliation signed by the target close day

SoD conflict report

Clean, or each conflict has a documented mitigating control

User access review

Completed and dated, leavers removed

Period locks

In place for every closed period

Reopen log

Reviewed, each reopen approved and explained

Intercompany balances

Agreed by both counterparties for every pair

Exception ageing

No unexplained items aged over 30 days

Auditor access

Read-only role set up and tested

Management letter points

Each prior-year point closed, with evidence

Source: Stacks implementation practice, 2026.

Any item that fails is a PBC request you will answer by hand. Fix it before the request arrives.

Why Choose Stacks for SOX-Ready Close Automation

Stacks enforces segregation of duties at task level, and nothing posts to the GL until it has cleared the approvals your policy requires. Every task, approval and supporting document is logged with preparer, reviewer and timestamp in an immutable activity log as the work happens, and sign-off locks the period and its evidence. Your auditors get the full trail in a single export, or review it directly in a read-only role. When an ERP balance changes after sign-off, Stacks reopens the reconciliation and records both balances. See how this works in our close management software.

Stacks holds SOC 2 Type II and ISO 27001:2022 certification and handles EU data in line with the General Data Protection Regulation (GDPR). The reports are available in our Trust Center.

Our AI matching reaches match rates above 95% out of the box, against 70–75% for rules-based matching. Every confirmed match is documented, and every exception carries its probable cause, owner and supporting evidence. See how account reconciliations work.

Epidemic Sound signed on 29 August 2025 and was fully live on 6 October 2025, with more than 700 tasks and account reconciliations running across 102 bank accounts and 13 entities. The team saves about five hours per close on approvals.

FAQs for SOX-Ready Close Automation

Does Close Automation Software Make You SOX Compliant?

No. The company owns its controls and the SOX 404 assessment, and software provides the execution layer and evidence.

Does Your Auditor Need a Service Organisation Report From the Close Software Vendor?

Only if they treat the platform as a service organisation and plan to rely on controls the vendor operates for you. Ask early whether they need a type 2 report under SOC 1 or ISAE 3402, or whether SOC 2 Type II plus your own controls is enough.

Should External Auditors Get Direct Access to the Close Platform?

Yes, through a read-only role. It lets them pull samples with support in context and removes many PBC requests.

How Long Should Audit Trail Records Be Kept?

Under the Companies Act 2006, UK public companies keep accounting records for six years and private companies for three. Groups reporting under SOX usually align to the seven years their auditors keep workpapers. Agree the retention period with the vendor in the contract.

Does Provision 29 Require External Assurance Over Material Controls?

No. The FRC states the auditor is not required to test those controls, and the audit opinion does not cover the Provision 29 statement.

Does Close Automation Reduce Audit Fees?

Don't build the business case on a fee reduction. In our experience, the gain is fewer evidence requests and faster answers.

See How Stacks Maps to Your Close Process

Book a 30-minute walkthrough. We'll discuss your close process, show you which tasks run automatically, and outline the next step from there.

GET STARTED

"Since using Stacks, we've reduced the time to financial close by three and a half days, which is material in our case."

Ruben A., CFO, Juni

Trusted by fast-growing companies including: Datavant, Future, Cleo, Motorway, Nivoda, Yoto and Epidemic Sound.

See how Stacks maps to your close process

Book a 30-minute walkthrough. We’ll discuss your close process, show you which tasks run automatically, and outline the next step from there.

"Stacks has transformed how our finance team operates... it's saved us time and reduced frustration."

Graham B.

SVP of Finance at Volt

Trusted by fast-growing companies including:

See how Stacks maps to your close process

Book a 30-minute walkthrough. We’ll discuss your close process, show you which tasks run automatically, and outline the next step from there.

"Stacks has transformed how our finance team operates... it's saved us time and reduced frustration."

Graham B.

SVP of Finance at Volt

Trusted by fast-growing companies including:

See how Stacks maps to your close process

Book a 30-minute walkthrough. We’ll discuss your close process, show you which tasks run automatically, and outline the next step from there.

"Stacks has transformed how our finance team operates... it's saved us time and reduced frustration."

Graham B.

SVP of Finance at Volt

Trusted by fast-growing companies including: