Statutory accounts rarely take as long as planned.

Even in well-run firms, files have a tendency to bounce back and forth. Late changes creep in, review queues stack up. During the busiest months, usually January through March, teams often experience the fire-fighting cycle: chasing inputs, unpicking errors, reworking documents and trying to hit deadlines without compromising quality.

It’s not that statutory account production is technically hard; the problem is usually a chaotic workflow.

Fragmented processes, disconnected systems and manual workarounds create rework and delay. The result is the same every year: too much time spent on admin, too little time spent on judgement.

What the statutory accounts production process actually looks like

Before you can fix delays, you need a clear baseline. A typical statutory accounts production process follows a predictable set of stages, although it probably doesn’t feel that way in practice.

These are the common statutory accounts preparation steps from start to finish:

• Data collection
  Gather the bookkeeping file, supporting schedules, prior-year accounts, lead schedules and any client notes or changes.
• Trial balance import
  Import or map the trial balance into your accounts production workflow, often via CSVs, exports or integrations.
• Working papers
  Build the working paper file: reconciliations, lead schedules, analysis, supporting documentation and sign-off points.
• Adjustments
  Post journals and adjustments, including accruals, prepayments, depreciation, tax, corrections, reclassifications.
• Review
  The file moves through review: first-pass checks, queries back to preparers, and final technical sign-off.
• Final accounts
  Produce the statutory accounts pack, ensuring disclosure completeness and consistency.
• iXBRL tagging
  Apply iXBRL tagging for submission requirements and resolve tagging errors or validation issues.
• Submission
  Submit to Companies House and HMRC with evidence captured for audit trail and compliance.

On paper, it’s linear, but in real life, it’s a loop. The same file can pass through these steps multiple times due to upstream instability.

For example: 

Bottleneck #1 — Manual data handling & re-keying

The first major delay often starts quietly: manual data handling.

When teams rely on exports, spreadsheets, CSV uploads and copy-paste workflows, the risk isn’t just wasted time. It’s that manual handling creates errors and uncertainty that ripple through the rest of the job.

Common symptoms include:

• numbers being re-keyed between systems
• mapping issues during trial balance import
• multiple spreadsheet versions with unclear ownership
• adjustments being tracked separately from the “final” file
• reviewers spending time validating the basics instead of reviewing the substance

Manual steps also create review friction. If the reviewer can’t trust the data flow, they will double-check everything, slowing down sign-off. Small data errors early on create bigger rework later, especially once iXBRL tagging and final accounts formatting are involved.

Bottleneck #2 — Non-standard working papers

The second bottleneck is less visible, but can drain hours of productivity: lack of standardisation.

When every preparer uses a different working paper layout, naming convention or structure, the review process becomes slower and riskier. Reviewers spend far too much time orienting themselves.

Typical causes include:

• different templates across teams or offices
• inconsistent file structures 
• unclear and inconsistent naming 
• key reconciliations missing or hard to locate
• no consistent sign-off or review checkpoints

The lack of standardisation also makes it difficult to assimilate new team members. New members will have to ‘feel’ their way along instead of following clear guidance. 

Bottleneck #3 — Late adjustments & change ripple effects

Late adjustments are a fact of life. The problem is how fragile the workflow becomes when changes arrive at the wrong time.

A single adjustment can:

• break reconciliations
• invalidate review notes
• change disclosures
• require rework in iXBRL tagging
• trigger resubmissions or re-approvals

Because statutory accounts production is often stitched together across multiple files and tools, even a small change can create a disproportionate ripple effect. For this reason, teams often feel stuck in “nearly done” mode: the accounts are close to complete, but every late change resets progress.

The real issue isn’t the adjustment but the lack of control in absorbing change.

Bottleneck #4 — Review & sign-off queues

Even when preparation is solid, review can become the biggest operational constraint.

That’s because review time isn’t only about reviewer capacity. It’s also about whether the file is genuinely review-ready.

Review queues build up when:

• the file isn’t complete when it hits review
• review notes are unclear or scattered across emails
• changes aren’t tracked, so reviewers re-check the same areas
• there’s no visibility into status or ownership
• the team can’t see what’s blocking sign-off

In busy periods, this becomes self-reinforcing: delays create pressure, pressure reduces quality, and reduced quality creates more review notes. A review becomes a bottleneck, not a safeguard.

Why mistakes are continuously repeated 

Many firms have moved to cloud tools but these cloud tools alone cannot fix statutory accounts delays. The real issues are structural:

• Disconnected systems (bookkeeping, working papers, accounts production, review notes)
• Unstandardised data and inconsistent mapping
• Manual checks used as a safety net
• Fragile workflows where small changes cause large rework

Proactive firms can have the most up-to-date software but still run old processes. That’s why the pain persists.

How to cut turnaround time

To reduce turnaround time, remove the friction that is creating unnecessary work.

1) Standardise working paper structures

Start with a consistent structure:

• what every file must contain
• where key reconciliations live
• how sign-off works
• what “review-ready” means

Standardisation speeds up review, reduces training time and makes quality more consistent.

2) Use connected, live data where possible

The less you move data manually, the less potential there is to introduce errors.

Live connections reduce:

• re-keying
• mapping confusion
• spreadsheet version drift
• the need to check or search for the latest version

3) Automate checks and validations

Automated checks catch problems earlier, when they’re cheaper to fix.

For example:

• balance checks
• variance flags
• missing schedules
• incomplete reconciliations
• unusual movements needing explanation

This reduces the dependence on the final review to pick up every error.

4) Make review workflows structured

Clear review workflows reduce back-and-forth:

• assign ownership for each query
• track status centrally
• capture what changed and why
• create a consistent review trail

Review becomes faster when it’s organised.

5) Create a single source of truth

The fastest teams don’t rely on multiple “almost final” versions.

They work from one controlled set of working papers and outputs, so changes don’t get lost, duplicated or contradicted.

Where Silverfin fits

Silverfin doesn’t eliminate professional judgement or the compliance work involved in statutory accounts. Our software helps to reduce the operational friction that causes delays, particularly manual handling, rework and review bottlenecks.

In practice, that means supporting firms with:

• live data connections
• standardised working papers across teams
• automated checks to catch issues earlier
• faster review cycles through clearer workflows and less duplication

The end objective is not to present teams with a set of completed accounts, but to create capacity by making the process more stable, repeatable and review-friendly.

Practical next steps for firms

If statutory accounts production feels slower than it should, start small. A few targeted changes can make a measurable difference.

Use this checklist:

• Map your current statutory accounts workflow (from data collection to submission)
• Identify where manual re-keying happens (and why)
• Standardise one working paper template (then roll it out gradually)
• Automate one high-impact check (eg balance checks or variance flags)
• Track review delays for one month (what’s waiting, and why)

The aim is simple: fewer handovers, fewer versions, fewer surprises.

Frequently Asked Questions

Want to see how firms are reducing rework and review friction in statutory accounts production?