Catch-up work needs its own process
Every bookkeeper eventually gets this client: months, sometimes years, of unreconciled transactions, a QuickBooks file that hasn't been touched since a prior bookkeeper left, or a business owner who's been "meaning to get to it" since the spring. Catch-up bookkeeping is a different discipline from ongoing monthly work. You're not maintaining a system, you're rebuilding one from scratch, usually under time pressure from a tax deadline or a lender request.
Treating it as an ordinary bookkeeping engagement, just with more months, is how these projects sprawl. A defined process keeps a six-month cleanup from turning into a six-week ordeal.
Step 1: Define the scope before you touch anything
Nail down three things with the client before starting: how far back you're going, what the end goal is (tax filing, loan application, general accuracy, sale of the business), and what accounts are in play. A catch-up for tax purposes might only need P&L-level accuracy; a catch-up to support a loan application needs a defensible, audit-ready set of books. These require meaningfully different levels of rigor, and pricing the engagement without knowing which one you're doing is how catch-up projects lose money.
This is also the point to ask what accounting method the client wants going forward and whether their chart of accounts needs rebuilding, since a messy or inconsistent chart of accounts is often part of why the books fell behind in the first place.
Step 2: Gather every statement for the full period
Before doing any actual bookkeeping, collect every bank statement, credit card statement, and loan statement for the entire catch-up window. Don't start reconstructing January until you have August too — discovering a missing month halfway through is one of the most common ways these projects stall.
For a shoebox client who hands you a mix of paper receipts, forwarded emails, and downloaded PDFs, this step alone can take real effort. Most banks let customers download statement history directly from online banking going back a couple of years, which is usually faster than waiting on the client to dig through email. If the client genuinely can't access old statements, most banks can reissue them, though that can take a week or more — worth requesting immediately since it's often the long pole in the project.
Step 3: Convert statements to spreadsheets before reconstructing transactions
This is the step where catch-up projects are won or lost on time. Reconstructing a year of transactions by reading PDFs and typing each line into your accounting software is slow and error-prone at any volume, and catch-up work often means a dozen or more statements across multiple accounts.
Convert each statement into a clean spreadsheet first, rather than working transaction-by-transaction inside the PDF. A converter that verifies the running balance against the statement's own totals will flag a misread line immediately, which matters enormously in catch-up work — an undetected transcription error in month three doesn't surface until you're reconciling month three weeks later, by which point you've built five more months on top of it. A tool built for statement conversion, covering formats like Chase, Bank of America, Wells Fargo, and PNC, turns what would be days of retyping into a much shorter review-and-import task. See reconstructing a full year of transactions from statements for a deeper walkthrough of this specific step.
Step 4: Work month by month, oldest first
Once you have clean data for every account, reconstruct and reconcile one month at a time, starting with the oldest. This matters more than it might seem. Categorization decisions and vendor mappings you establish in month one carry forward and keep month two faster. Working in chronological order also means you can catch a beginning-balance mismatch early, before it's been silently carried through half a year of entries.
Resist the temptation to categorize everything across all months first and reconcile later. It feels faster but it isn't — you end up re-touching the same transactions multiple times instead of closing each month as you go.
Step 5: Reconcile each month before moving to the next
Confirm each month's ending balance ties to the statement before starting the next one. This is the same discipline as a normal month-end close, just applied retroactively and repeatedly. It's tempting to skip this and reconcile everything at the end, but a single error early in the sequence compounds across every subsequent month if it isn't caught immediately.
Step 6: Handle the judgment calls as a batch
Every catch-up project surfaces transactions that need a decision the bookkeeper can't make alone: a large deposit that might be a loan or might be revenue, an expense that might be personal, a transfer between accounts that isn't obvious from the statement alone. Rather than pausing the whole project every time one comes up, keep a running list and take it to the client as a single batch of questions. This keeps momentum and respects the client's time as much as your own.
Step 7: Deliver with a clear summary, not just clean books
When the catch-up is done, give the client a short summary of what was reconstructed, any assumptions you made on ambiguous transactions, and what's needed to keep the books current going forward — usually a monthly bookkeeping engagement and, if it isn't already in place, a live bank feed instead of PDF statements going forward. Catch-up projects are also the best moment to sell ongoing service, since the client has just seen firsthand what falling behind costs them.