Catch up bookkeeping is the work of bringing a client's books current when months of transactions were never recorded. The fastest route starts from the bank statements: collect every missing one, convert them in a single batch, prove each month balances, then categorize and post. Do the paper chase first and the typing last.
How far behind is a catch up bookkeeping client?
A catch up client is as far behind as the oldest month with no posted transactions in their books, and you measure that from the statements, not from what the client tells you. Settle the real number before you quote a price or a deadline.
Find the true starting point
Open the client's ledger and find the last month with a reconciled bank balance. Everything after that month is backlog. If the ledger has no reconciliations at all, take the last month where the books agree with a bank statement closing balance, even if nobody ever marked it reconciled.
Then list every account that touched money in the backlog period. Clients forget accounts. A card the owner opened for one project, a savings account used as a tax reserve and a payment processor balance all produce transactions that belong in the books. Ask for a list of every bank and card account, open or closed, and check it against the opening balances in the ledger. An account with a balance in the ledger but no statements in the folder is the first gap to chase.
Count the work in statements
Express the backlog as a number of statements, because that is the unit the rest of the project follows. Months behind multiplied by accounts gives the count. A client who is fourteen months behind with three accounts owes you 42 statements. Two accounts that closed halfway through the period will lower that, and an account opened mid-period will too.
Pages come next, because they predict effort better than months do. First, write down three numbers: months behind, accounts, statements. Those three numbers drive every decision that follows.
Ordering catch up months: oldest first or newest first?
Work the months oldest first. Each month opens with the previous month's closing balance, so a mistake in an early month carries into every later one. Working in date order means every balance check has a trustworthy starting point, and any error shows up in the month where it was made.
Newest first has one real appeal: the client usually needs the current period, perhaps for a loan application or a tax deadline. If that pressure is real, do a split. Convert everything in one batch, but post the most recent quarter first using the balances printed on those statements, then go back and fill the older months in order.
When newest first is acceptable
Use newest first only when both of these hold:
- The client needs a report for a recent period by a fixed date.
- You have the statement that opens that period, so the opening balance is printed on paper and not guessed.
Mark the results as provisional until the older months are posted. If the older months turn up a missing account or a duplicate, the recent quarter may change.
Why oldest first catches errors sooner
Suppose a statement for month three is missing a deposit because one page of the PDF was lost in upload. The month-three balance check fails. If you are working in order, you stop at month three and fix it. If you worked newest first, the failed check at month three appears after you already categorized ten months on top of it. In order, a failure costs one month. Out of order, it can cost all of them.
Scoping a catch up project by statement pages
Scope a catch up project by counting pages, not months. Pages predict effort, because page count tracks transaction count, and transactions are what you categorize and check. Two clients who are each fourteen months behind can differ by a factor of five in pages.
How to count and estimate
Open a handful of statements from different months and note the page count of each. A quiet account may print a single page a month, while a busy card or operating account can print six or more. Take the average per account and multiply by the number of statements for that account. The figures below are an example for the client described later in this post:
- Operating checking: 14 statements at about 5 pages, so 70 pages.
- Business credit card: 14 statements at about 4 pages, so 56 pages.
- Savings: 14 statements at about 2 pages, so 28 pages.
That sums to 154 pages for 42 statements. Treat the page average as a guess, then correct it once the files are in your hands.
Fit the backlog to your tool's limits
If you convert with AutoBankConvert, check the page allowance of your plan before you upload a backlog. The Solo plan lists 500 pages a month and the Practice plan lists 2,000, per the homepage, so a 154-page backlog fits inside a single month on either one, alongside that month's regular client work. A much larger backlog may need to be spread over two billing months. Pricing during early access may change, so check the current figures when you plan.
Quote the project on the estimate and state the assumption. A line such as "Quote assumes about 150 pages and three accounts; an additional account or statement set is quoted separately" keeps the scope honest when a fourth account appears.
Catch up gaps from missing statements and closed accounts
A gap is any month and account without a statement in your folder. Gaps are the main cause of catch up projects running late, because the client has to act and you cannot. Find all of them in one pass at the start, then send a single request, not a trickle of reminders.
Build a statement grid
Make a grid with the months down the side and the accounts across the top. Mark each cell as received or missing. The grid doubles as your progress tracker and the document you send to the client. When you request statements, send the grid with the missing cells highlighted. A client can answer "here are the 6 cells I still need" far faster than "please send everything you have."
Statements are also a record you can check against: each one prints an opening and closing balance, and the closing balance of one month should equal the opening balance of the next. When the two do not match, the grid is missing a statement or the file contains the wrong month.
Where to get a missing statement
Most banks keep statements available online for a limited number of years. If the client can still log in, they can download the PDFs in a few minutes. If they cannot, the bank can usually issue copies on request, sometimes for a fee. For the client's side of this process, see the onboarding checklist's guidance on how many past statements to request.
Closed accounts and short years
A closed account still needs statements through its closing month. The last statement often shows a zero balance or a transfer of the remaining funds. That final transfer lands in another account, and if you skip the closed account, the matching entry in the other account has nothing to match to. Ask for the final statement explicitly.
When a statement truly cannot be obtained, do not guess. Post the month from whatever evidence exists, such as the next statement's opening balance, a transaction history export from online banking, or the client's payment records. Label the gap in your working notes, and tell the client which figures rest on weaker evidence. A hole you describe is better than a number you invented.
Posting caught up months without reopening closed periods
Post caught up months into the periods that are still open in the client's accounting file, and avoid touching any period the client or a tax preparer has already closed. If a closed period needs a correction, record it in the current period with a clear note, or ask for the period to be unlocked in writing.
Check what is locked
Before posting, find the lock date in the accounting software. Many files carry a closing date that blocks changes to earlier periods, and some clients have a tax preparer who relies on prior-year figures staying put. Ask the client whether any prior-year return was filed from the existing books. If it was, changing those months changes numbers a third party has already used.
Post in month order
Import one month at a time and balance it before moving on. After each import, compare the ending balance in the books against the statement's closing balance. Only when the two agree should you start on the next month. This is slower than importing everything at once, but it is the only way to know where a difference started.
A faster path exists for the conversion step. Converting the whole backlog in one run sorts a mixed folder by client, account and month. You get all 42 statements converted together, and you still post the resulting files in date order.
A worked example: fourteen months, three accounts, 42 statements
The example below uses made-up figures for a fictional client. It shows the order of work and a realistic two-week timeline.
The client is a small design studio. The last reconciled month was fourteen months ago. The books have no entries since. There are three accounts: operating checking, a business credit card and savings. That makes 42 statements and roughly 154 pages.
The steps
- Build the statement grid and send the missing cells to the client on day one.
- As files arrive, rename them by account and month, and fill in the grid.
- Convert all received statements in one batch. Each statement must pass its balance check before you treat it as done.
- Fix any statement that failed. A failure usually means a missing page, a duplicated page or a scan that read badly.
- Set the client's categorization rules from the first three months, and review what the rules could not place.
- Post month by month, oldest first, and compare each month's ending balance with the statement.
- Clear the remaining uncategorized lines and hand the client a short list of questions about items you could not identify.
- Run the final checks: every month balanced, every account tied to its last statement, no open gaps in the grid.
Two-week timeline
| Days | Work | Done when |
|---|---|---|
| 1 to 2 | Build the grid, request missing statements, confirm the lock date | Request sent, 42 cells tracked |
| 3 to 5 | Receive and rename files, convert in one batch | Every received statement passes its balance check |
| 6 to 7 | Chase the last missing statements, rerun any failures | Grid has no missing cells, or each remaining gap is documented |
| 8 to 9 | Write rules from the first quarter, categorize all 14 months | Review queue holds only unknown items |
| 10 to 12 | Post months oldest first, balance each one | Ledger ending balance equals statement closing balance for all 14 months |
| 13 to 14 | Send the client questions, final review, report | Client has answered, books are current |
Allow slack for the days waiting on the client. In practice, days 3 to 7 stretch most often, because the last few missing statements are the ones the client finds hardest to get.
How the tool fits
A batch converter takes the longest manual step, retyping or reformatting 154 pages, down to a single upload and a review of whichever statements fail the balance check. AutoBankConvert categorizes with rules you write once plus the client's past coding, and sends uncertain lines to a review queue. For a backlog, the rules you set on the first quarter then apply to the other eleven months.
What to do after the catch up is finished
A client who fell behind once will fall behind again unless the routine changes. When the last month is posted, move them onto a monthly schedule so the backlog never re-forms. That means asking for statements on a fixed day and automating the steps that do not need judgment, which how to automate bookkeeping step by step lays out in order.
Also look at how the hours were spent. A catch up project usually shows how much of your time went to typing and reformatting. Where bookkeeping data entry hours actually go breaks that down, so you can decide which parts to remove first.
To set up a first batch for a backlog client, request early access.