Blog
Written by
Naman Mathur
Published on
Key Takeaways
The year-end scramble starts in month one, when an approval happens in email and its audit evidence never reaches the reconciliation it supports.
An audit-ready close runs on two checkpoints: sign-offs landed by working day 5, and a quarterly test of a reconciliation from three months back.
Seven artefacts need to exist at the moment of the work, including access history and a reopen log for any balance changed after sign-off.
Once evidence lives in the system, auditors sample it directly, prepared by client (PBC) requests fall and fieldwork turns to judgement areas.
An audit-ready close is a property of how each month runs, and no year-end project can create it. The January scramble is the cost of evidence that was never captured when the work was done. Months later, someone rebuilds it from an inbox.
The standard advice treats year-end audit preparation as a project. Run a pre-audit clean-up sprint and buy a better tracker for the prepared by client (PBC) list. Both fixes treat the symptom, and continuous audit readiness needs a change to the close itself.
This article covers how to stay audit-ready each period, why prep collapses at year-end, which artefacts must exist and how fieldwork changes.
How Can Finance Teams Keep the Close Audit-Ready Throughout the Period, Not Just at Year-End?
Create the evidence at the moment each task is done, so nobody has to rebuild it later. Every reconciliation and journal carries a named preparer and reviewer, with the support attached to the task. Exceptions keep an owner until they close, sign-off locks the period, and twelve closes run this way become the annual evidence file.
An audit-ready close is one where an outsider can open any balance, at any point in the year, and follow the audit trail. That trail runs from the number back to the support and the people who signed it. A binder assembled in January is the opposite.
When auditors plan to rely on controls, they look for that trail. Groups with a US listing face the same logic under the Sarbanes-Oxley Act (SOX), which we've argued is best read as an evidence standard: a control counts once the record shows it operated.
Why Does Audit Prep Collapse Into a Year-End Scramble?
Most controllers know the symptoms: late PBC items, missing sign-offs, unsupported journals and a reviewer who left in June. The causes sit upstream, in how evidence gets created.
Evidence Lives Outside the Work
Support for a reconciliation usually sits in an email thread or a shared drive folder, away from the balance it supports. For subledger balances it is often in another system entirely: a Stripe or Adyen payout report, a Coupa purchase order, Pleo receipts or the payroll provider's export. The review happens, but the approval has no link to the number. When the auditor samples it in February, it fails on documentation even though the control operated, and becomes another PBC request.
Ownership and Cadence Drift
Accounts with no clear owner get reconciled by whoever has time, and in month two of a quarter the low-priority ones get skipped. Permissions drift too. A cover role granted during parental leave outlives the leave, eroding segregation of duties.
Without an owner who knows the account, a reconciliation can balance for the wrong reason, such as an offsetting error or a plug nobody questioned. The fix is named owners and a risk-based reconciliation frequency, with the risk rating recorded so the auditor can see why.
Controls Are Tested on Whether They Operated
Under International Standard on Auditing (ISA) (UK) 330, where auditors rely on controls, they test whether those controls operated across the period. Boards of companies that report under the UK Corporate Governance Code face a related obligation under Provision 29: a declaration, as at the balance sheet date, that material controls are effective. Outside its scope, the declaration is still a useful test of what your board could stand behind.
Provision 29 sits in the UK Corporate Governance Code, set by the Financial Reporting Council (FRC). The FRC's Provision 29 Mythbuster confirms that it applies to periods beginning on or after 1 January 2026. The Code does not prescribe a definition of material controls, so each board defines the population itself.
That population is larger than many expect. The FRC's Provision 29 Mythbuster puts most companies at 30 to 50 material controls, with financial services groups higher; at an Institute of Chartered Accountants in England and Wales (ICAEW) session for financial services firms in April 2026, the FRC cited 30 to 70.
Much of that list lands on internal control over financial reporting (ICFR): reconciliations, journal approval, system access and period lock. Sign-offs rebuilt in January are weak ground for a board declaration.
What Does Continuous Audit Readiness Look Like, Period by Period?
Continuous audit readiness means each part of the month produces its own evidence on a fixed rhythm.
Timing | Activity | Evidence produced |
|---|---|---|
During the month | Reconcile on live data, assign exceptions | Exception log with owner and date |
Working days 1–5 | Review reconciliations, approve journals | Timestamped sign-offs, supported journals |
Period lock | Lock the period, reopen moved balances | Lock record and reopen log |
Quarterly | Sample a three-month-old reconciliation | Self-test result and fixes |
Source: Stacks implementation practice, 2026.
The quarterly self-test is the step we'd keep above all others. Pick a reconciliation from three months ago and ask an outsider to find its preparer, reviewer, support and later changes. If they can't, you've found next January's PBC request early.
Which Artefacts Should Exist Continuously Throughout the Period?
Seven artefacts carry most of the close's audit evidence. Rebuilt later, they prove only that someone tidied up.
Artefact | What it must show | When it is created |
|---|---|---|
Reconciliation sign-off | Preparer, reviewer and timestamp for each account | At review, inside the reconciliation |
Journal approval with support | Approver and support document, approved before posting | When the journal is staged |
Exception resolution evidence | Owner, cause, age and fix | When raised, updated until closed |
Account risk rating | Rating and the frequency it sets | At account set-up |
Procedure per task | The steps the preparer follows | Before the first close it applies to |
Access and role history | Who held which role, and when it changed | Each time a role is granted or removed |
Reopen log | What changed after sign-off, and who re-reviewed it | When a balance moves after sign-off |
Source: Stacks implementation practice, 2026.
When you evaluate close software, test each row in a demo. Our guide to approval gates and audit trails lists the questions to ask, such as whether a journal can post before its approval exists.
Why the Standard Advice Fails
The usual playbook is a clean-up sprint before the auditors arrive, backed by a quarter-end evidence pack. When fieldwork starts, someone exports the audit log from the enterprise resource planning (ERP) system.
It can work. A two-entity group with one controller who knows every balance can run a sprint, because the evidence and the memory sit in the same head.
It breaks as the group grows, because a sprint fixes this year's gaps and leaves the habits that caused them. A quarter-end pack is the same sprint run four times a year.
The exported log floats free of the balances. It shows a user clicked approve at 16:42, with no link to the number or its support.
Our view: move the control into the system and the evidence follows. If a journal cannot post without approval and support, you never have to prove afterwards that someone approved it.
How Does This Change the Year-End Audit Conversation?
When evidence lives in the close itself, fieldwork becomes sampling inside the system, at year-end and at interim. With read-only access, the auditor reads the trail directly, so the PBC list shrinks.
The discussion then moves to areas that need judgement, such as provisions and revenue cut-off. That is where your auditor's time should go, and where yours is better spent than chasing sign-offs.
Track four measures: reconciliations signed off by target day, exception ageing, reopened reconciliations and the PBC request count. If the first two hold and the last falls, the rhythm works.
Why Choose Stacks for an Audit-Ready Close
Stacks builds the audit trail as the close runs. In the close management workflow, every task, approval and supporting document is logged with preparer, reviewer and timestamp. Journals stage for review, posting stays blocked until approval and evidence are both present, and sign-off locks the period.
If an ERP balance changes after sign-off, the task reopens automatically. With reconciliation automation for enterprise, Stacks matches above 95% of transactions, and every exception becomes a tracked work item with an owner. Auditors get read-only access to sample inside Stacks, and the full trail leaves in a single export.
Stacks has a System and Organization Controls (SOC) 2 Type II report and ISO 27001:2022 certification; read more about our security and compliance posture. Stacks supplies the evidence, and your company still owns compliance and the Provision 29 declaration.
Epidemic Sound signed on 29 August 2025 and went live four weeks later across 102 bank accounts and 13 entities. Its first close on Stacks ran 713 tasks at 100% completion.
Ruben A., Head of Finance at Juni, reports a shorter close. "Since using Stacks, we've reduced the time to financial close by three and a half days, which is material in our case."
FAQs for an Audit-Ready Close
How Often Should Accounts Be Reconciled to Stay Audit-Ready?
Reconcile high-risk accounts monthly and low-risk accounts quarterly, and record the risk rating that sets each frequency. Your auditor then sees a documented basis for the schedule.
Which Accounts Should Get Audit-Ready Documentation First?
Start with accounts that carry judgement or high volume, such as accruals, provisions, intercompany and cash. In our experience, those are where auditors focus their samples.
What Are the Core Components of an Audit-Ready Close?
An audit-ready close needs named preparers and reviewers, support attached to each task, owned exceptions and a period that locks at sign-off.
Do Auditors Have to Test Provision 29 Material Controls?
No: the FRC says the auditor need not test the design, implementation or operating effectiveness of the controls the board identifies under Provision 29. It may still test overlapping controls as part of the financial statement audit (auditor's responsibilities under Provision 29).
Does a Faster Close Reduce Audit Fees?
Not automatically, since fees follow audit scope and risk. In our experience, fewer PBC chases give you a stronger case at the next fee discussion.
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: Datavant, Future, Cleo, Motorway, Nivoda, Yoto, Epidemic Sound
