Skip to content
StatementSmith

Catch-Up Bookkeeping: How to Clear a Backlog

Work forwards, not backwards. A backlog looks like one enormous task and is really a chain of small ones that have to be done in order, because every period starts from the closing balance of the one before it.

Published 10 August 2026 · 7 min read

The short answer

Gather every statement for the whole period first. Start at the oldest month, not the most recent. Enter and reconcile that month completely before touching the next one. Repeat until you reach the present. It is slow for the first two months and then much faster, because most of the work in month one is setting up decisions you reuse.

The instinct is to start with the most recent month, since it feels most urgent. It is the one month you cannot finish: reconciling it needs a proven opening balance, and that only exists once everything before it is done.

First, work out how far back you have to go

Further than the last set of accounts you filed, and no further than you have to. The usual answer is the start of the earliest open financial year, because that is the earliest point anything you produce can still change a return.

Find the last period that was genuinely closed and reconciled, and treat its closing balance as your starting point. If nothing was ever reconciled, the start is the day the account was opened, and that is worth knowing early rather than discovering in week three.

Get the records before you start entering anything

Gathering is the step with the longest lead time and the one most often left until it blocks everything. Statements from a bank you still use are instant. Statements from an account somebody closed eighteen months ago are a request measured in weeks.

  • Every bank and card account, including the ones nobody mentions: the card used twice, the account opened for a grant.
  • Whole periods, not the interesting months. Statements chain, and a gap stops the chain rather than leaving a hole in it.
  • Sales and purchase invoices for the same span, since the statements show that money moved and not what it was for.
  • Anything already entered, so you know what you are reconciling against rather than duplicating.

For accounts that have been closed, the bank still holds the records long after your access ends: getting old statements from a closed account covers how to ask and roughly what it takes. Start those requests on day one and do the reachable months while you wait.

Work oldest first, one period at a time

This is the whole method and it is worth being stubborn about. Each month's opening balance is the previous month's closing balance, so a month reconciled on top of an unreconciled one proves nothing: you have matched a total to a figure you have not verified.

  1. Take the oldest unreconciled month.
  2. Enter every transaction on the statement for that month.
  3. Reconcile it, and do not move on until it balances. Reconciling a bank statement covers what the size of a difference usually tells you.
  4. Note any decision you had to make: how a recurring payment gets categorised, which account an odd transfer belongs to.
  5. Move to the next month and reuse those decisions rather than making them again.

That last step is why a backlog gets faster rather than slower. The first month is genuinely hard because you are inventing the treatment of every recurring item. By month four you are applying decisions rather than making them.

What being caught up actually means

Entered is not caught up. A backlog of transactions typed into accounting software is a backlog in a different shape: it looks finished and is unverified.

Caught up means every period is reconciled against the bank's own record, every balance on the balance sheet is something you could explain, and the last period is closed and locked. Anything short of that is a set of books somebody will have to check later, which is the job you are currently doing.

Getting the data in when there is no feed

Bank feeds rarely reach backwards far enough to be useful here. Most pull ninety days, some a year, and none of them work for an account that has been closed, which is exactly the situation a backlog tends to involve.

So the statements themselves are usually the source, and the work is getting each one into a shape the software will accept. Where a bank offers a CSV or a spreadsheet alongside the PDF, take it. Where it does not, or where the account is closed and the PDF is all that survives, the file has to be converted.

Converting each statement here produces a dated transaction list and totals every row against that statement's own closing balance before you download it, which on a backlog matters more than usual, because a page missing from month three is not something you find out about until month nine otherwise. It does not categorise anything and it does not know your chart of accounts. That part is the job.

Turn a statement into a clean file

Categorising a backlog without doing it twice

Categorise as you go, monthly, rather than entering everything and sorting it at the end. Sorting at the end means holding a year of context in your head at once, and it is where the errors come from.

  • Keep a decisions list. One line per recurring payee and its treatment, written down where you can see it.
  • Use rules for anything that repeats, but check the first few they touch: a rule applied to a year of history is a year of the same mistake.
  • Park what you genuinely cannot identify in one holding account and query the lot at once, rather than stopping the run each time.
  • Do not guess to keep moving. A guessed category is indistinguishable from a known one a month later.

Gaps you cannot fill

Some backlogs have holes: a statement nobody kept, an account at a bank that no longer exists, a period before the current owner took over. Missing records are normal in this work and they do not have to stop it.

Reconstruct what you can from the other side: the supplier's copy invoices, the customer's remittances, the merchant statements. Where a figure genuinely cannot be established, record what you did establish, what you estimated, and on what basis. Documented estimates are ordinary practice. Silent ones are the problem.

How long it takes, and when to hand it over

As a rough shape: the first month of a backlog takes several hours, and later months settle to under an hour each once the recurring decisions exist. A year of a simple sole-trader account is a few days of real work. A year of a busy company with several accounts, staff and stock is not.

We do not offer catch-up as a service and this is not a pitch for one, so take the following as it is meant. Handing it to a bookkeeper is usually right when there is a filing deadline you would miss, when payroll or VAT periods are involved, when the records span a change of ownership or accounting system, or when you have started twice and stopped twice. The cost of a professional catch-up is almost always less than the cost of an amended return.

Staying caught up afterwards

Backlogs are a scheduling failure rather than a skills one, and they rebuild at the same rate whatever caused the first. The fix is frequency: an hour a week is less total work than a fortnight in March, because everything is still recent enough to recognise.

Once the books are current, a monthly close is what keeps them there: reconcile, review, lock, in that order. The lock is the part that matters most here, because a closed period cannot quietly drift back into being a backlog.

Frequently asked questions

How far back do I need to go? To the start of the earliest financial year that is still open, since that is the earliest point your work can still affect a filed return. Practically, start from the last period that was genuinely reconciled: if there has never been one, the start is when the account was opened.

Should I start with the most recent month or the oldest? Oldest. Every period's opening balance is the previous period's closing balance, so the most recent month is the one month you cannot actually finish until everything before it is done. Starting at the recent end feels faster and produces work that has to be redone.

Can I just import everything at once and sort it later? You can import in bulk, but reconcile period by period regardless. A year imported as one block cannot be checked against anything: reconciliation works because each statement has its own opening and closing figures, and merging them throws away the only evidence you had.

What if I cannot get statements for part of the period? Reconstruct from the other side where you can, using supplier invoices, customer remittances or card provider statements, and document what you estimated and why. Banks hold records for years after an account closes, so it is worth asking before concluding they are gone.

Do you offer catch-up bookkeeping as a service? No. This site converts statement files and checks that nothing was dropped on the way; the bookkeeping itself is not something we do. If you need somebody to take the work on, a bookkeeper who lists catch-up or clean-up work specifically is the thing to look for, since it is a different job from ongoing monthly work.

How do I stop the backlog coming back? Do it weekly rather than monthly, and close and lock each period once it is reconciled. Most backlogs rebuild because nothing was ever finished: an open period keeps accepting entries, so the work never actually stops accumulating.

Read next

Try it on the statement that’s annoying you right now.

No account, no card, no limit. If the layout isn’t recognised you will know immediately, rather than after a support ticket.

Convert a statement