Year end is recurring work too, and the most fragile kind
Tasks that run once a year are the easiest to forget and the hardest to cover. Build a year end close checklist while the work is still fresh.

Ask a finance team to list its recurring work and you will get the monthly close, the weekly payment run, the quarterly VAT return. You will rarely get the year end. It feels like a project: big, special, a once-a-year push. But it comes back on a date everyone knows, it follows much the same steps each time, and it is done by the same few people. That makes it recurring work, just with the longest gap between runs. This post argues that the long gap is exactly what makes year end tasks the most fragile on the list, and that the fix is a year end close checklist written while the work is still fresh, not reconstructed twelve months later.
Why once a year is the riskiest frequency
A task that runs every week is practised 52 times a year. Mistakes surface quickly, shortcuts get shared, and two or three people usually know how to do it. A task that runs once a year gets none of that.
Three things work against annual tasks.
Memory does not last twelve months
Whoever ran last year's fixed asset roll-forward knew exactly how the disposals were treated, which tab in the spreadsheet fed the note, and why one asset class is depreciated differently. A year later they remember the outline and have to re-learn the details. The re-learning is slow, and it is where errors creep in.
The people change
In a year, someone leaves, someone moves teams, someone goes on parental leave. Monthly tasks get handed over as part of the move, because they are due next month. Annual tasks get forgotten in the handover, because nobody is thinking about them in May. The gap only shows when the year end arrives and the one person who did the accruals review last time is no longer there to ask.
Nobody writes it down because it is "only once"
Documenting a weekly task pays back fast, so people do it. Documenting an annual task feels like effort for a job that will not come round for ages. So the method lives in an email thread, a folder of last year's working papers and someone's head. It is the classic shape of key person risk, the same pattern we described for single-owner tasks in the month end close, stretched over a longer cycle.
What sits on a typical year end list
Take a hypothetical in-house finance team at a 120 person company with a December year end. Its annual work, outside the normal monthly close, might include:
- the fixed asset register review and depreciation roll-forward
- the stock count, its cut-off and the reconciliation to the ledger
- the bad debt and doubtful debt review
- accruals and prepayments review across the full year
- the audit request list, and preparing the files the auditors ask for every year
- the statutory accounts working papers and disclosure notes
- intercompany balance agreement with group companies
- the annual insurance renewal and the asset values it relies on
- P11D or benefits reporting, and the year end payroll steps
- the annual budget upload into the accounting system
None of those is exotic. The question is how many of them have a written method, a named owner and a named backup today.
The year end close checklist, built as recurring work
The fix is to treat each annual task the same way as a monthly one. That means each gets its own entry on the recurring task list, with the same fields as any weekly task.
For each annual task, capture:
- The calendar rule. Not just "year end" but when the work actually starts. The stock count needs planning weeks before the count date. The audit request list arrives at a known point after the year end.
- The owner and a backup. If there is no backup, write that down. An annual task with one name against it is the highest risk item on the list.
- The inputs. Which reports, which system, which spreadsheet, which emails from which people.
- The steps, in order. Not a summary. The order the person actually works in, including the checks they make.
- The judgements. Where the person decides something, write down how. "Provide for debts over 90 days unless the client is on a payment plan" is a method. "Use your judgement on bad debts" is not.
- What went wrong last time. The late file, the adjustment the auditors raised, the step that took three times longer than planned. This is the most valuable line on the page and the one most often lost.
- Effort. Roughly how long it took, so next year's plan is based on something.
Write it while it is fresh
The timing matters more than the template. The best moment to document a year end task is during the work or in the two weeks after, not the week before it is due again.
A simple rule: nobody closes an annual task until its checklist is updated. When the fixed asset roll-forward is signed off, the person who did it spends half an hour updating the method with anything that changed or surprised them. When the auditors' points come in, each one that touches a year end task gets added to that task's notes, so next year starts from the corrected version.
If your year end is in December, this is a good month to prepare. Pull last year's working papers now and, for each annual task, ask the person who did it to spend twenty minutes writing down what they remember while they still can. Then add to it as the work runs in January.
This is the same discipline as keeping holiday handover notes: the moment the knowledge is freshest is the moment to capture it, because waiting means writing it from memory.
Why this matters beyond year end
Annual tasks are a good test of how a team holds its knowledge. They also matter for anything you later want help with. A year end task with a written method, clear inputs and a list of last year's problems can be shared across a team, given to a new joiner, or in time partly prepared by an AI agent that drafts the working papers for a person to review. A task that lives in one person's memory of last January cannot move anywhere. In Beaks, annual tasks sit on the same list as weekly ones, with the manual attached, so they get the same attention.
It is also kinder to the people doing the work. Re-learning a complex task under deadline pressure every year is stressful and slow. A good checklist turns the year end from a test of memory into a piece of work someone can plan.
One thing to do this week
List every task your team does only once a year. Put the owner and a backup next to each. Any task with no backup, or no written method, gets twenty minutes with its owner before the year end starts, to write down the steps and what went wrong last time.


