Blog
Written by

Naman Mathur
Published on

Key Takeaways
No software is compliant with the Sarbanes-Oxley Act (SOX). A vendor claiming otherwise has misread SOX.
Genuine SOX readiness shows in three controls: enforced segregation of duties, general ledger (GL) posting gates and an audit trail nobody can edit.
System and Organization Controls (SOC) 2 covers trust services criteria such as security. Your auditor relies on SOC 1 Type II for financial reporting.
Make the vendor break its own rules live on your data.
Introduction
In our view, no close automation software is SOX compliant, so the vendor has to prove its controls on your data. SOX compliance is something your company achieves control by control.
This guide covers how to test a vendor's SOX understanding, what genuine SOX readiness looks like, which assurance reports to ask for and why standard vendor evaluation misses SOX failures.
How Do You Assess Whether a Close Automation Vendor Understands SOX Compliance Requirements?
You assess whether a close automation vendor understands SOX compliance requirements by making it prove its controls live on your data, reading its independent assurance reports, and checking it can name the controls that stay your responsibility.
SOX binds issuers registered with the US Securities and Exchange Commission (SEC). That reaches European groups with a US listing and subsidiaries of US-listed parents, and the Financial Reporting Council (FRC) notes that SOX reporters are building on their SOX work to meet Provision 29. Under section 404(a), management assesses and reports on internal control over financial reporting (ICFR), as the SEC's 2009 study of Section 404 sets out.
Section 404(b) adds independent auditor attestation for larger filers. Once journals are prepared and approved in a close platform before they reach the enterprise resource planning (ERP) system, that platform is part of ICFR and your auditor will test it.
Six tests show whether a vendor understands SOX compliance requirements:
Ask the vendor to self-approve a task in a demo loaded with your data.
Try to post a journal to the GL without approval.
Ask an administrator to edit a past audit log entry.
Request a SOC 1 Type II report or an International Standard on Assurance Engagements (ISAE) 3402 report.
Map each complementary user entity control (CUEC) to an owner on your team.
Ask a customer's controller what their auditors said at the first year end.
A vendor that understands SOX separates ICFR from IT general controls (ITGCs), and distinguishes Type I from Type II reports and preventive from detective controls. It names its CUECs and bridge-letter process without prompting. It never offers a "SOX certification".
Why Isn't a "SOX-Ready" Badge Evidence?
A "SOX-ready" badge proves nothing on its own, because SOX compliance is a company-level outcome. No SOX certification exists for software. Management runs the controls and auditors test them.
When a vendor says "SOX-ready", "audit-ready", "compliance built in" or "continuous monitoring", ask which control each phrase means and what evidence it leaves.
UK boards face the same test. Provision 29 of the UK Corporate Governance Code 2024 requires a board declaration on the effectiveness of material controls. The FRC confirms Provision 29 applies to accounting periods beginning on or after 1 January 2026.
The FRC's Provision 29 mythbuster says the FRC understands most companies identify 30–50 material controls, and it sets no target. In our experience, several of those controls sit in the close, and a vendor badge is no evidence of their effectiveness.
What Does Genuine SOX-Readiness Require in a Close Platform?
Genuine SOX-readiness means the close controls auditors test hardest hold when someone tries to break them. The table separates real controls from cosmetic ones.
Vendor claim | What real evidence looks like | Demo test |
|---|---|---|
"Segregation of duties built in" | The system blocks self-approval | Assign yourself both roles and sign off |
"Approval workflows" | No journal posts without approval and evidence | Push an unapproved journal through |
"Full audit trail" | Named user and timestamp, with no edit rights | Ask an administrator to change a past entry |
"Period lock" | Sign-off locks the period against later edits | Post a late journal after sign-off and ask what happens |
Source: Stacks implementation practice, 2026.
What Does Enforced Segregation of Duties (SoD) Look Like?
Enforced segregation of duties (SoD) means the close system refuses to let one person prepare and review the same task.
In our experience, control drift often starts with parental-leave cover. A colleague picks up a task but nobody updates the assignment, so the audit trail shows a name that doesn't match who did the work.
Ask how the platform flags mismatched assignments, and whether leavers lose access through single sign-on (SSO) and System for Cross-domain Identity Management (SCIM).
What Should You Check in General Ledger (GL) Posting Gates?
A GL posting gate should block any journal from posting until approval and evidence are in place. The gate makes the control preventive, while a detective control only finds the bad journal afterwards.
Under International Standard on Auditing (ISA) (UK) 240, auditors test period-end and post-closing journal entries. The Institute of Chartered Accountants in England and Wales (ICAEW) explains the requirement in ICAEW's guide to journals testing.
Ask whether a user can bypass the gate by posting directly in the ERP, and who keeps those rights. The usual gap is the subledgers: journals from Stripe, Adyen, Pleo or payroll that post straight into NetSuite, Dynamics 365, Sage or Visma never pass through the close platform's gate.
What Makes an Audit Trail Complete and Immutable?
A complete, immutable audit trail is captured by the system as work happens, and nobody, including an administrator, can edit it. Every action carries a named user and timestamp, with evidence attached to the balance it supports.
Ask for the demo steps in writing. Then ask for read-only auditor access and a single evidence export; both cut the prepared by client (PBC) requests your team chases each year end.
Which Independent Reports Should a Vendor Provide?
A close automation vendor should provide an ISAE 3402 Type II report, the international standard, or a SOC 1 Type II report, its US equivalent, which covers controls relevant to your financial reporting.
The International Auditing and Assurance Standards Board (IAASB) sets out the standard in the IAASB's ISAE 3402 release. ISAE 3402 is the international standard for reporting on service organisation controls.
AICPA & CIMA (the American Institute of Certified Public Accountants and Chartered Institute of Management Accountants) issues the SOC reporting framework. Its introduction to SOC reporting places SOC 1 on ICFR, and SOC 2 on trust services criteria such as security and privacy.
ISO/IEC 27001, from the International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC), sets requirements for an information security management system. It covers information security, not financial reporting controls, so it doesn't replace either report.
Insist on Type II. A Type I report checks control design at a single date, while a Type II report tests whether controls operated across a period.
If a vendor holds SOC 2 Type II rather than SOC 1, ask which IT general controls it covers, such as logical access and change management, and agree with your auditor how they will get comfort over the rest.
Then read the CUECs, which are the controls the vendor relies on you to run, such as user access and approvals. Make the vendor explain each one. A vendor that blurs SOC 1 and SOC 2 has told you how well it knows your audit.
What Should Finance Teams Ask a Close Automation Vendor Before Signing?
Finance teams should put written questions to a close automation vendor before signing, and keep the answers.
On approvals and access, ask:
Can a user who prepared a task approve it under any role configuration?
How do you flag work done by someone other than the assigned user?
On audit evidence, ask:
Which journal types can post to the GL without approval?
What does the audit log record when an ERP balance changes after sign-off?
On assurance and references, ask:
Which CUECs does your SOC 1 Type II or ISAE 3402 report list?
Does a bridge letter cover the gap to our year end?
How do you notify customers before a release changes a control?
Whose auditors have relied on your platform, and may we speak to them?
How Do You Validate a Vendor's SOX Claims?
You validate a close automation vendor's SOX claims by testing what a scripted demo skips, then checking the paperwork behind it. Log in as a user you have just removed, and request the role matrix alongside the SOC 1 report.
If you are replacing a tool your auditor already relies on, run one close in parallel and measure the same things on both: self-approval exceptions, journals posted after sign-off, evidence not linked to a balance, and PBC requests at year end. Report the results to the audit committee in writing.
Why Does Standard Vendor Evaluation Fail for SOX?
Standard vendor evaluation fails for SOX because security questionnaires and feature checklists never test whether a control still holds a year after go-live. A reference call with the person who championed the purchase rarely fills that gap.
Evidence escapes into email when attaching it to the task is awkward, so the reviewer approves from an inbox your auditor will never see. Logs float free of the numbers when an ERP balance changes after sign-off and nothing flags it.
There is a fair case for the incumbent. A platform your auditors know from other clients shortens their learning curve, which has real value in a first audit year. That familiarity says nothing about whether your configuration blocks a self-approval, so run the same tests on every vendor.
Why Choose Stacks for Enforced Close Controls?
Stacks gives finance teams close controls that the system enforces, and that you can test before signing. Segregation of duties applies at task level, and GL posting gates hold journals until approval and evidence are present.
For manual journals, our journal entry posting controls include an Excel add-in that checks for missing data and formatting before the journal syncs.
Our close management with enforced approvals logs who prepared and reviewed every task, with a timestamp and supporting documents, as the work happens. Sign-off locks the period, and access runs through Security Assertion Markup Language (SAML) SSO.
We hold our SOC 2 Type II and ISO 27001:2022 certifications and comply with the General Data Protection Regulation (GDPR).
We don't claim Stacks makes you SOX compliant, and we don't ask you to take our word for the controls. Test us the same way.
Epidemic Sound's first close on Stacks ran on 6 October 2025. It covered 102 bank accounts and 13 entities, with 713 tasks at 100% completion. Epidemic Sound's VP of Accounting says having every task and reconciliation in one place across all 13 entities gives the team an auditable trail that simplifies the audit.
Most teams are live before their next close.
FAQs on Close Automation Vendor SOX Compliance
Can Close Automation Software Make a Company SOX Compliant?
No. Close automation software can enforce and evidence controls, but SOX compliance is a company-level outcome that management asserts and the auditor tests.
Is a SOC 2 Report Enough for SOX Purposes?
On its own, rarely. A SOC 2 Type II report gives your auditor evidence over IT general controls such as access and change management, but SOC 1 and ISAE 3402 reports are built for ICFR, so ask the vendor how your auditor will cover the gap.
Does Provision 29 Apply to Groups Already Reporting Under SOX?
Yes, Provision 29 applies to any company under the UK Corporate Governance Code 2024, whatever its SOX status. Existing SOX controls work is the starting point.
What Should a SOX Vendor Assessment Checklist Include?
A SOX vendor assessment checklist should include live attempts to break approvals and edit the audit log. Add the SOC 1 Type II report and an owner for every CUEC.
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.
Ruben A., Head of Finance at Juni, saw the difference. "Since using Stacks, we've reduced the time to financial close by three and a half days, which is material in our case."
Trusted by fast-growing companies including: Epidemic Sound, Nivoda, Motorway, Cleo, Yoto

