Catch-up bookkeeping: how to reconcile a year of missing statements

Every bookkeeper gets this client eventually: twelve months (or three years) behind, a mix of PDFs, paper and missing months, and a deadline — a tax return, a loan application, a nervous accountant. Catch-up work feels overwhelming because it arrives as a pile. The fix is to stop treating it as a pile and run it as a pipeline: collect → convert → import → reconcile, month by month.

1. Take inventory before touching anything

Make a simple grid: one row per account, one column per month. Mark what you have — PDF, paper, or missing. This ten-minute step is the difference between a controlled job and endless "wait, which months am I missing?" interruptions later. Every account that touches the business belongs on the grid: current accounts, savings, credit cards, PayPal and Stripe if they settle to their own balances.

2. Chase the gaps first

Missing statements have the longest lead time, so request them on day one and let the bank work while you do. Online banking archives typically reach back 5–7 years, and banks can reproduce older statements on request — even for closed accounts. While you wait, start processing the months you already hold.

3. Convert the pile in batches

Drop each account's statements into NoRekey as a batch — paper scans and photos included — and download CSV for your working papers or OFX for direct import. Two things matter at this volume. First, per-page pricing: a year of statements for one client is typically 60–150 pages, which costs a few pounds rather than the per-document fees some tools charge. Second, verification: every conversion is checked against the statement's own opening and closing balances, so amount discrepancies can be investigated before import. Matching totals alone cannot prove every field or row is correct. Anything that can't be verified is flagged for review instead of being quietly delivered — on a catch-up job, that flag is your early-warning system.

4. Import and reconcile month by month, oldest first

Resist the urge to import the whole year and "sort it out after". Import one month, reconcile it — opening balance plus the month's transactions must land exactly on the closing balance — then move forward. Errors compound: a June mistake found in June costs five minutes; found at year-end, it costs an afternoon of unwinding. (Software-specific import steps: QuickBooks, Xero — Sage and Quicken work the same way.)

5. Watch for the classic catch-up traps

• Duplicate months — clients love sending the same statement twice with different filenames. Your inventory grid catches this.
• Mid-month statement periods — some accounts run the 15th to the 14th. Reconcile to the statement's period, not the calendar month.
• Overlap with the bank feed — if the client's software has a feed covering recent months, only import up to where the feed starts.
• Transfers between the client's own accounts — they appear twice (once per account) and must be matched to each other, not categorised as income and expense.

6. Close it out

When every month ties out, produce the summary the client actually needs: closing balances per account, and a note of anything flagged for review with your resolution. A year that reconciles month by month, against the bank's own documents, is a year an accountant — or an HMRC enquiry — can trust.

The whole job, timed honestly: inventory 15 minutes, conversion of a year's statements about ten, and the real work — import, reconcile, categorise — a focused afternoon instead of a lost week of typing.