The working papers standard that makes review fast

• Review is slow because the reviewer is quietly re-doing the job. A proper file lets them check the reasoning instead of rebuilding it.
• Seven things make a file reviewable: an index, lead schedules, a source for every number, cross-references, a query log, a completion checklist and a points-forward note.
• Cross-referencing is the single habit that cuts review time most. Every figure in the accounts should be one click from its evidence.
• Write the standard down as one page. A standard that lives in a partner's head cannot be handed to anybody — not to an outsourced team, and not to the person at the next desk.
• The file is also your defence. Company records run six years, anti-money-laundering records five, and ownership belongs in the engagement letter.

Why review takes two hours

Ask a practice owner where their week goes and a surprising amount of it is reviewing accounts. Not preparing them — reviewing them. And when you watch what actually happens in that review, most of it is reconstruction rather than review. The reviewer is opening the bank statement to see where the cash figure came from, hunting for the stock spreadsheet, recalculating depreciation because the schedule does not show the working, and trying to remember whether the director's loan was cleared by dividend or by salary.

None of that is judgement. It is archaeology. A reviewer who has to find the evidence before they can assess it is doing the preparer's job a second time, more slowly, at the most expensive rate in the building.

The fix is not a better reviewer or a smarter preparer. It is a file standard: a written description of what a finished working paper file looks like in your firm, applied on every job by everybody. It is dull, it takes an afternoon to write, and it is the highest-return afternoon in a production practice — because it converts review from reconstruction into checking.

What the file is actually for

A working paper file has three jobs, and confusion between them is why so many files are bloated and still unhelpful.

• It shows how each figure in the accounts was arrived at. That is the review job.
• It records the judgements somebody made and why. That is the memory job — the one that saves next year.
• It evidences that the work was done to a standard. That is the defence job, for your professional body, your insurer and any later dispute.

Every document in the file should serve one of those three. A file stuffed with 90 pages of downloaded bank PDFs and no schedules serves none of them. So does a beautiful set of schedules with nothing behind them.

The seven parts of a reviewable file

1. An index

One page, at the front, listing every section with its reference. If your document store gives you folders, the folder names are the index. Sections in a fixed order, the same order every job, so a reviewer can find the fixed asset schedule without thinking about it.

2. A lead schedule for every balance

One schedule per balance sheet caption and per material profit and loss line, showing this year, last year, the movement, and a one-line explanation of the movement. The explanation is the part people skip and the part reviewers read first. “Stock up £41,000” is data. “Stock up £41,000 — client bought ahead of the March supplier price rise, count sheets at B7” is a file that has already answered the reviewer's question.

3. A source behind every number

Not a screenshot of the ledger the number came from. The independent evidence: the bank statement, the supplier statement, the loan agreement, the RTI submission, the filed VAT returns. If the only evidence for a figure is the ledger that produced it, the figure has not been verified, it has been copied.

4. Cross-references, both ways

Every figure in the draft accounts references the lead schedule. Every lead schedule references the supporting paper. Every supporting paper references back up. Two-way referencing is what turns a file into something you can navigate rather than something you have to search, and it is the difference between a 25-minute review and a two-hour one.

5. A query log

One list per job. Query, date raised, who owns it, date answered, answer. Open queries visible at the front of the file. A job with three open queries is not a job that is nearly finished — it is a job that is blocked, and the file should say so plainly rather than burying it in an email thread.

6. A completion checklist, signed

The things that must be true before the file leaves the preparer: bank reconciled to statement, VAT control agreed to the submitted returns, PAYE control agreed to the RTI position, comparatives agreed to the filed accounts, depreciation recalculated rather than rolled forward, disclosure checklist run. A preparer who signs this knows where the finish line is. A preparer without one is guessing.

7. A points-forward note

Half a page written at the end of the job, not the start of the next: what was awkward, what the client was slow with, what you would do differently, what to watch next year. This is the cheapest piece of paper in the file and the one that compounds. It is also the document that makes the second year with any new preparer better than the first — as we set out in handing over year-end accounts without losing quality.

A worked example: the same client, two files

Illustrative, using our own published rates. One small limited company, one preparer, one reviewing partner. File A is prepared to no particular standard. File B is prepared to the seven-part standard above. An Accounts seat is £2,650 a month for 160 productive hours, which is £16.56 an hour (pricing).

Two hours of partner time, on one set of accounts. The standard cost half an hour more in preparation and gave back two hours of the most constrained resource in the practice — and it was cheaper in seat time as well, because rework is production hours you pay for twice.

Run that across a book of 140 year-ends and the arithmetic stops being a rounding error: 280 partner hours, or roughly seven working weeks, currently spent reconstructing files that could have arrived finished. That is the number worth writing on a whiteboard, because it is not a saving on a fee — it is seven weeks of the owner's year, and what happens in those weeks is entirely the owner's choice. Put your own client numbers into the capacity calculator to see the shape of it for your practice.

Where practices lose the standard

Three failure patterns, all common.

• The standard exists but only in one head. The senior who trained everybody knows what good looks like and has never written it down. The firm discovers this the week that person is on holiday, or the month it tries to add capacity.
• Two standards, both unwritten. Ask two people in the same firm to describe a finished file and you get two answers. Neither is wrong; the firm just never chose. Reviewers then apply whichever one they personally use, and preparers experience that as arbitrary.
• Software mistaken for a standard. Accounts production software enforces disclosure. It does not enforce evidence, explanation or cross-referencing. A file can be fully compliant in the software and completely unreviewable.

Write the standard down as one page and none of the three survives. One page is the right length: long enough to settle the arguments, short enough that people read it. Keep it with the job, not in a policy folder nobody opens.

The file as your defence

Two retention periods sit underneath all of this. A company must keep its accounting records for six years from the end of the last financial year they relate to (gov.uk, company and accounting records). Your own anti-money-laundering records — client due diligence and supporting transaction records — must be kept for five years from the end of the business relationship or the completion of the transaction, and no longer than ten (regulation 40, Money Laundering Regulations 2017). Build both into where the file lives, not into a reminder somebody has to remember.

Ownership is separate and is settled by your engagement letter. ICAEW's guidance on documents and records: ownership, lien and rights of access is that ownership depends on the contract and the capacity in which you act, and recommends the engagement letter deals with it expressly. If production is subcontracted, that is another reason the letter deserves a look before the first job moves — the confidentiality side of it we covered in data security and confidentiality when outsourcing accounts.

The 2026 change to build into the standard now

The FRC's second periodic review, published in March 2024, changes FRS 102 for accounting periods beginning on or after 1 January 2026, with the substantial changes in lease accounting and revenue recognition: most leases come onto the lessee's balance sheet as a right-of-use asset and a lease liability, and revenue moves to a five-step model (FRC, revisions to UK and Ireland accounting standards).

For a file standard this is practical, not theoretical. Every client with a property lease, a vehicle lease or equipment on hire now needs a lease schedule in the file: term, payments, options, discount rate, and the transition adjustment. If you add that section to your standard this month, every file prepared from now on carries the information before you need it. If you do not, somebody re-reads every lease next spring under deadline pressure.

How to introduce it without a project

1. Afternoon one. Write the one page. Sections, order, what a lead schedule must show, the cross-referencing convention, the completion checklist.
2. Afternoon two. Take two files you are proud of and two you are not, and mark them against the page. That is where you find out whether the standard is real or aspirational.
3. Week one. Apply it to new jobs only. Never retro-fit finished files; the cost is real and the benefit is zero.
4. Week four. Count review points per set and reviewer minutes per set. Both should be falling. If they are not, the standard is describing a file nobody can actually produce, and it needs cutting rather than enforcing.
5. Quarter two. Only now consider moving preparation to anybody new — internal or outsourced. A standard tested on your own team transfers. One written specifically for an outsourced team never gets tested at all.

That last point is the one worth sitting with. Firms often write a file standard because they are about to outsource. The order should be the other way round: the standard is what makes the work movable in the first place, and it improves your in-house files whether anything moves or not. When work does move, the standard travels with it — our team works to the practice's own file standard inside the practice's own software, which is what makes the output white-label rather than merely relabelled (white-label accounts production, and accounts production for how the split works in practice).

What good looks like, in numbers

Count them for a quarter, then stop. They exist to tell you whether the standard is working, not to police anyone. Practices that keep counting forever end up measuring instead of managing, which is its own kind of production trap — the one year-end season capacity planning is about escaping.

Where to start

Write the one page this week and apply it to the next five jobs. Then work out what your production actually needs in hours with the capacity calculator, and read how it works for the sequence we use when a practice moves preparation to a permanent seat. When you want a hand with the standard itself, get in touch — we will build it with you against your own files, because most firms have the content and not the document. We muck in on the boring part; you keep the review and the signature.

Published 8 September 2026. Tax rules and rates change — check current figures on gov.uk before relying on anything here. This is general information for practice owners, not advice.