Year-End Statutory Accounts Timetable: Planning Template

Most year-ends run late for the same reason: the timetable is built forwards from the year-end date rather than backwards from the filing deadline, so the slack sits at the front where it is comfortable rather than at the back where it is needed. This page is a working template rather than an explainer. It plans the statutory cycle backwards from the filing deadline, names the owner and the dependency at each stage, and flags the four milestones that slip most often. The applicable framework — FRS 102 or IFRS — is maintained by the Financial Reporting Council. For the technical content of the accounts themselves, see our guide to preparing statutory accounts; for the audit specifically, FC audit preparation.

The fixed points

Two dates are immovable and everything else is planned against them. UK private companies must file accounts at Companies House within nine months of the period end, and the corporation tax return follows at twelve months, per HMRC’s company tax return guidance, with payment at nine months and one day. Where a shareholder agreement, lender covenant or investor reporting obligation requires accounts earlier — frequently four to six months — that becomes your real deadline and the whole timetable compresses accordingly.

Work out which date genuinely binds you before you plan anything. A great many finance functions plan to the statutory deadline and then discover the covenant certificate is due two months earlier.

The backwards timetable

The template below assumes a nine-month filing deadline and an audited entity. Adjust the compression for unaudited accounts or an earlier covenant date; the sequence does not change.

For a December year-end filing in September, that puts kick-off in late March — roughly three months after the period end, which surprises most people the first time they plan it properly.

The four milestones that slip

Across the year-ends we see, delay concentrates in four places rather than spreading evenly.

The balance sheet reconciliation at −18 weeks. By far the largest cause. A function that reconciles monthly reaches this point already complete; one that reconciles at year-end starts an excavation and everything downstream moves. This milestone is really a statement about the previous twelve months, not about the year-end — our guide to optimising the month-end close covers the discipline that prevents it.

The technical judgements at −14 weeks. Revenue recognition, provisions, impairment and deferred tax are frequently left until the auditor asks, at which point they are being formed under time pressure and argued rather than documented. Writing the memo before fieldwork changes the conversation entirely — see writing technical accounting memos.

Information from outside finance. Stock counts, work in progress, legal confirmations, contract data. Finance cannot control these and therefore must chase them early; the timetable should name the person outside finance who owns each, not just the finance-side recipient.

And auditor availability. Firms book fieldwork months ahead and December year-ends compete with every other December year-end. A slipped internal milestone can cost far more than the delay itself if it means losing the booked slot — which is the strongest practical argument for building slack at the front rather than the back.

Using the template

Four things that make the difference between a timetable and a document.

Name a person against every row, including the rows outside finance. “Operations” is not an owner.

Circulate it beyond finance at kick-off. Most of the dependencies sit elsewhere in the business, and people meet deadlines they knew about.

Review it fortnightly against actual, not at the end. A milestone missed at −18 weeks is recoverable; the same slippage discovered at −8 is not.

And keep the slack at the front. The instinct is to plan generously at the end because that is where the pressure feels greatest — but the end is where the auditor and the board control the timetable rather than you. Contingency is only useful where you can still spend it.

Where the timetable meets capacity

A timetable does not create capacity, and the common failure is a well-planned year-end running alongside a monthly close that has not stopped. Three honest options where the two collide.

Reassign the monthly cycle temporarily so the person preparing the audit file is not also producing the pack.

Bring in interim support for the peak. Year-end is a bounded, dated requirement — the clearest case for interim there is — and a financial accountant on assignment for eight weeks costs materially less than a late filing or a rushed audit. For groups, the same applies with more force: consolidation capacity is scarcest exactly when everyone needs it, as our guide to interim Group FC reporting-season cover sets out.

Or accept the compression consciously and tell the board the pack will be late in the relevant month, rather than discovering it. That is a legitimate choice; discovering it is not.