Counting Twice Before Counting Once: The November Rehearsal for UK Year-End Reporting

Year-end reporting has a date, but it is not simply a date. For most UK finance, data and operations teams, the close is a sequence of handovers: data extraction, reconciliation, review, evidence collection, adjustment and sign-off. As of 9 November 2026, the 2026 close is close enough to rehearse and far enough away to fix what the rehearsal exposes. The case for a November dry run is straightforward: a controlled failure now is cheaper than an improvised failure in January.

A rehearsal, not a parallel audit

Some teams hear “dry run” and imagine a full parallel close, with duplicate ledgers and a second audit trail. That is rarely practical. The useful rehearsal is narrower: take a defined slice of the close, run it end to end under realistic conditions, and measure where the operating model strains. It is not about producing final numbers. It is about proving that the people, data, controls and escalation routes can produce them.

That distinction matters. A rehearsal should not become a shadow reporting cycle that exhausts the team before the real work begins. It should be a short, instrumented test with clear success criteria and a small enough scope to complete in one or two working days.

Why November earns its place

By early November, most UK organisations have a reasonable view of the year. The December change freeze may be approaching but has not yet closed every route to remediation. Subject-matter experts are still available, although leave calendars are beginning to fill. Audit and assurance teams are forming their year-end questions. This is the window in which findings can still be fixed without emergency change processes.

December is a poor month for a first rehearsal. Operational noise rises, key approvers disappear, and temporary fixes become permanent because there is no time to test alternatives. January is worse: every exception is now a live close issue. A failed rehearsal in November creates a remediation list. A failed close in January creates an incident.

Set the test scope and success criteria

A practical rehearsal needs a defined window, a representative scope and an agreed observer. Choose one or two entities, a sample of accounts or a reporting boundary that has caused difficulty before. Run the key steps in the order the close will run them. Record timings, handovers and waiting points.

Success criteria should be operational, not merely numerical. Did reconciliations complete within the agreed cut-off? Was evidence captured as part of the task rather than reconstructed afterwards? Were exceptions logged with owners? Did escalations receive an acknowledgement within the agreed service level? Could each owner explain the variance and the control around it? Agreement on these questions before the rehearsal prevents the exercise from becoming a general discussion about year-end stress.

Reconciliations: test the route, not only the result

Run the reconciliations that historically consume time: bank, intercompany, subledger to general ledger, VAT control, payroll control and revenue cut-off. Use a November snapshot or a prior-period dataset that is realistic enough to expose matching problems. Time each step. Note where the preparer waits for data, where the approver is unavailable, where matching rules fail and where manual workarounds appear.

A reconciliation that balances after three manual adjustments is not necessarily a success. It may be a control finding. The rehearsal should distinguish between a clean reconciliation and a reconciliation rescued by individual knowledge. The latter is a dependency risk that will be harder to manage in January.

Access checks belong in the rehearsal

Year-end often attracts temporary access: contractors, cover staff, central reporting teams and auditors. The rehearsal should test whether that access is controlled. Check who can post journals, run close reports, export ledgers and change master data. Test a leaver scenario and a temporary privilege grant. Confirm that emergency access is logged, time-bound and reviewed.

In the UK, access to financial and personal data also carries data protection obligations. The rehearsal is a sensible moment to confirm that reporting extracts are minimised, that sharing routes are approved and that retention expectations are understood. These checks are not separate from the close; they are part of whether the close can be trusted.

Evidence capture should be a by-product

Evidence is often reconstructed after the event, when memories have faded and screenshots are missing. A rehearsal should make evidence capture part of each task. Require ticket references, timestamps, system screenshots, sign-off records and query logs at the point of work. Store them in a single rehearsal evidence pack with a clear index.

That pack then becomes the template for January. It also gives audit and assurance teams a preview of how the organisation will demonstrate control. If the evidence pack is difficult to assemble in November, it will not become easier under January pressure.

Exception logging and escalation

Every rehearsal exception needs an owner, severity, root cause and due date. Separate data exceptions from process exceptions. A missing intercompany confirmation is different from an approver who is unavailable for two days. Both matter, but they require different remedies.

The rehearsal should also test escalation. Simulate a failed interface, a missing confirmation or an absent approver. Measure the time to acknowledgement and resolution. If the escalation path depends on one person, that is a finding. If the path is documented but nobody has used it, the rehearsal has proved only that the document exists.

Turn results into a remediation plan

Within a week of the rehearsal, triage the findings. Fix critical issues before the December freeze. Re-test only the critical items, not the whole exercise. Decide whether the organisation is ready for the close or whether specific controls need a fallback. Communicate the outcome to finance, data, operations and assurance leads in plain language.

A short readiness note is often enough: what was tested, what passed, what failed, who owns the fix and when it will be re-tested. That note is more useful than a broad assurance statement because it records known risk rather than hiding it.

The cost case

A rehearsal costs people time. A failed close costs more: audit adjustments, delayed board reporting, missed statutory deadlines, manual effort and reputational damage. In the UK reporting environment, timely and accurate reporting matters to boards, lenders, regulators and counterparties. A November rehearsal cannot eliminate risk, but it can convert unknown risk into known, owned and dated actions.

That is the practical argument for counting twice before counting once. The 2026 close will still have pressure. A November rehearsal simply decides where that pressure is felt: in a controlled test with time to repair, or in January when every exception is live.