Catch-Up Bookkeeping: Months of Bank Statements, Fast
By SheetStatement Team · · Updated · 11 min read
TL;DR: Catch-up bookkeeping goes fastest in a fixed order: collect every statement for every account, check the set for gaps, convert and verify each statement, import or combine, tag transfers, categorize the big recurring items first, then reconcile month by month. Don't start categorizing until you know the data is complete.
Almost every bookkeeper we talk to has a "catch-up" story. A new client arrives with eight months of nothing. A business owner realizes in March that last year's books were never done. Someone inherits a set of accounts after a partner leaves. The task is always the same: turn a pile of bank statements into clean, reconciled books, and do it before a deadline that's closer than anyone would like.
This is the process we've settled on. It isn't glamorous, but it's predictable, and predictability is what you want when the deadline is real.
Step 0: agree on the scope
Before touching a statement, write down:
- The period: for example, January 1 to December 31.
- The accounts: every bank account, savings account, credit card, loan and payment processor that touches the business.
- The deliverable: reconciled books in accounting software, a categorized spreadsheet for a tax preparer, or both.
- Who answers questions: the person who knows what the transactions were. Catch-up work always generates questions.
The accounts list matters most. The single most common source of trouble in catch-up work is an account nobody mentioned: a second card, a PayPal balance, an old savings account. Transfers to it look like expenses until you find it.
Step 1: collect every statement
For each account, get every monthly statement in the period, plus the statement before the period starts and the one after it ends. The month before gives you a verified opening balance; the month after helps with items that cross the period end (checks written in December that clear in January, for example).
Ask for PDFs downloaded from online banking where possible. They convert more accurately than scans or photos. If the client only has paper, ask for clear, flat, well-lit scans.
Name files consistently as they arrive:
bank-checking-1234-2026-01.pdf
bank-checking-1234-2026-02.pdf
card-amex-1007-2026-01.pdf
Step 2: check the set for gaps
Make a simple grid: accounts down the side, months across the top. Tick each statement as you receive it. Gaps jump out immediately.
Then, for each account, fill in the opening and closing balance of each statement. Each month's opening balance should equal the previous month's closing balance. If one doesn't, a statement is missing or you have the wrong account.
This takes twenty minutes and saves days. We've seen catch-up projects get to the end, fail to reconcile, and only then discover a missing month.
Step 3: convert and verify each statement
Now convert. With a statement converter like SheetStatement, upload the PDFs for one account at a time. For each statement:
- Check that the converted transactions balance: opening + all amounts = closing.
- Review any flagged rows against the PDF.
- Note the result in your grid (a tick or "balanced").
Don't move on from a statement that doesn't balance. A small unexplained difference in January turns into a messy reconciliation in June.
If you're working with scanned statements, budget extra time for review. Scans are where misread digits happen; the balance check finds them, but you still have to look.
Step 4: decide where the data goes
Two paths:
Path A: straight into accounting software. Export each account in the software's preferred format: a QBO file for QuickBooks (bank statement to QuickBooks), a Xero CSV (bank statement to Xero), or a CSV for others. Import month by month into the matching bank account.
Path B: a master spreadsheet first. Combine all accounts into one table with Account and Statement columns, categorize in Excel, then import or hand over. This is useful when the client doesn't have accounting software yet, when the tax preparer just wants a summary, or when you want to sort out transfers before importing.
We usually choose A for ongoing clients who already use software, and B when the job is a one-time cleanup for a tax filing.
Importing into software for a catch-up
A few things that help with path A:
- Set the opening balance first. The account's opening balance in the software should equal the statement's opening balance at the start of your period.
- Import in date order. One month at a time makes checking easier.
- Turn off or limit automatic matching rules until you've checked a couple of months, or at least review what they're doing. Rules created for current transactions can misfire on old ones.
- Watch for bank feed overlap. If the account is connected to a live bank feed, the feed may have already pulled some of the period. Importing statements over the same dates creates duplicates. Decide on a cutoff date: statements before it, feed after it.
Step 5: tag transfers first
Before categorizing anything else, find and tag transfers between the client's own accounts:
- Checking to savings and back.
- Checking to credit card payments.
- Payment processor payouts into checking.
- Owner contributions and draws between personal and business accounts.
In accounting software, these become transfers between accounts (or the appropriate equity entries for owner money). In a spreadsheet, give them a Transfer category and exclude them from income and expense totals.
Doing this first removes a large chunk of rows from the categorization work and prevents the classic double count, where a 5,000 transfer to savings shows up as a 5,000 expense.
Step 6: categorize the big and recurring items
Sort transactions by payee and count. A small number of payees usually covers most of the rows: payroll, rent, the main suppliers, software subscriptions, the payment processor, utilities. Categorize those with rules (in the software) or a lookup table (in Excel; see Excel formulas for categorizing transactions).
Then sort the rest by amount, largest first. Large items matter most for accuracy, and they're the ones you need to ask about if they're unclear.
What's left is the long tail of small, one-off transactions. Categorize them quickly, and use a "Review" category for anything you genuinely can't identify. Don't guess silently.
Step 7: ask questions in batches
You'll have questions. Collect them in a list with the date, amount, description and your best guess, and send them in one go rather than one email per transaction. A shared spreadsheet with a "Client answer" column works well. Clients answer a single organized list much faster than a stream of interruptions.
Typical questions:
- What was this large deposit? (Loan, owner money, customer payment, refund, sale of an asset?)
- Is this payee a contractor or an employee?
- Was this purchase business or personal?
- What's this account that money keeps going to?
Step 8: reconcile month by month
With everything categorized, reconcile each account for each month, oldest first. In accounting software, use the reconcile feature with the statement's closing balance. In Excel, follow the process in our bank reconciliation guide.
If a month won't reconcile, the usual causes are:
- A duplicate from a bank feed overlap.
- A transaction entered manually that also came in on import.
- A missing statement page.
- An opening balance that was wrong from the start.
Fix each month before moving to the next. Our guide to finding bank reconciliation discrepancies has a systematic approach.
Step 9: review and hand over
Final checks:
- Every account reconciled for every month.
- No transactions left in Review or Uncategorized, or a short list with explanations.
- A profit and loss for the period that makes sense: revenue roughly in line with expectations, no wild category spikes.
- Owner draws and contributions recorded consistently.
- A short note to the client or tax preparer explaining any assumptions.
Keep the converted files, the PDFs and your question list together. If anything is questioned later, you can show how each number was reached.
Handling payment processors and marketplaces
Processor payouts deserve their own mention, because they cause more confusion in catch-up work than almost anything else. A payout from a card processor or marketplace into the bank is usually net: customer payments minus fees, refunds and sometimes chargebacks or reserves. The bank statement only shows the net amount.
If you record each payout simply as revenue, your revenue is understated and your fees disappear. For a quick tax summary, some preparers accept that as a starting point. For proper books, most accountants want gross sales, fees and refunds recorded separately. That means pulling the processor's own payout or settlement reports for the same period and using them to split each deposit.
A practical approach: treat the processor as its own account in the books (a clearing account). Record gross sales, fees and refunds into it from the processor's reports, and record each bank payout as a transfer from the clearing account to checking. When the clearing account's balance matches what the processor says it's holding, you know it's right. It's a bit more work, but it turns a mystery into something you can reconcile like any other account.
Splitting the work between people
On bigger catch-ups, two people often share the work. What divides cleanly:
- One person per account for conversion and verification. Each statement is self-contained, so there's no overlap.
- One person for transfers and questions, since that needs a view across all accounts.
- Reconciliation by account, again because each account reconciles independently.
What doesn't divide well is categorization rules. If two people build rules separately, you'll get two names for the same thing. Agree on the category list and keep a single rules table that both use.
How long does it take?
It depends heavily on transaction volume, the number of accounts, the quality of the statements and how quickly questions get answered. Conversion itself is fast with a good tool; most of the time goes into categorization, questions and reconciliation. Our honest advice is to estimate by the number of transactions and accounts rather than months, and to build in time for questions. The client's response time is usually the biggest variable.
A worked example
Say a small design studio comes to us in February needing last year's books for their tax preparer. They have:
- One business checking account
- One business credit card
- A payment processor that pays out to checking
- A savings account that the owner "occasionally used"
We collect 13 statements for each of the three bank and card accounts (December of the prior year plus all twelve months) and ask for processor payout reports. The grid shows that the savings statements for May and June are missing. We ask for them before converting anything.
Conversion goes smoothly. Two card statements fail the balance check: one had a missed interest line, one had a foreign currency line read as an extra charge. Both are fixed in review.
Transfers are tagged: monthly card payments, processor payouts, and four transfers to and from savings. After that, about 40% of the rows are already handled.
Twenty payees cover most of what remains: the owner's two freelancers, software subscriptions, rent, a coworking space, a few suppliers. Rules handle them. We sort the rest by amount and send the client a list of 31 questions. They answer 28 within two days; the other three go into a clearly labeled "Owner to confirm" category.
Reconciliation finds one issue: a client payment that appears in both the bank feed (which was connected in November) and our imported statement for November. We delete the duplicate. Everything reconciles.
The tax preparer gets reconciled books, the PDFs and a one-page note. Nobody had to retype a single line.
Common mistakes in catch-up work
Starting to categorize before the data is complete. You'll redo work when the missing statement shows up.
Ignoring the accounts nobody mentioned. Ask directly: "Are there any other accounts, cards, or payment apps used for the business?"
Letting automatic rules run unchecked on historical data. Rules built for this year's vendors can misfire on last year's.
Overlapping feeds and imports. Pick a cutoff date and stick to it.
Guessing on big items. A large unexplained deposit categorized as revenue might be a loan. Ask.
Our take
Catch-up bookkeeping rewards order over speed. Complete data first, then transfers, then the big recurring items, then questions, then reconciliation. Converting statements automatically removes the most tedious part; the judgment calls still need a human, and that's where your time should go.
If you're facing a stack of statements, the pricing page shows how many pages each plan covers, so you can estimate the conversion side of the job.
Troubleshooting a catch-up job
The opening balance is wrong. If the books were last reconciled long ago, the last reconciled balance may not be reliable. Confirm it against the statement at that date before importing anything.
The client can't explain transactions. Batch questions, offer your best guess, and park unclear items in a suspense account. Don't let a handful of questions block the reconciliation.
Statements are missing in the middle. Get them before importing later months. Gaps make reconciliations impossible.
The bank feed covers part of the period. Decide on a clear cut-over date: statements before it, feed after it. Write it down.
The work keeps expanding. Agree scope at the start, and log anything extra you find as a separate item for discussion.
A mini checklist for the first day
- Account register with every account and its status.
- Statements gathered and checked for gaps.
- Opening balances confirmed.
- Cut-over date agreed for each bank feed.
- Plan for import order: banks, then cards, then processors.
- Question log started.
A second worked example
A bookkeeper picks up a café 11 months behind. She builds the account register (two bank accounts, one card, one card processor), gets all 44 statements, confirms the opening balances with the previous accountant, and works month by month. Processor payouts are matched to daily sales with fees recorded. The question log ends with 31 items, sent to the owner in two batches. The whole job takes four working days, and every month is reconciled.
FAQ
How do I catch up on bookkeeping from bank statements?
Collect every statement for every account, check for gaps, convert and verify each statement, tag transfers between accounts, categorize recurring and large items first, ask questions in batches, and reconcile each month in order.
Should I import statements into accounting software or use a spreadsheet?
Use accounting software if the client already has it and will keep using it. Use a master spreadsheet for one-time cleanups or when a tax preparer only needs categorized totals.
How do I avoid duplicates when a bank feed is also connected?
Choose a cutoff date. Import converted statements only for dates before the feed started, and let the feed handle transactions after that date.
What if a statement is missing?
Request it from the bank or the client before you continue. The continuity check, where each opening balance equals the prior closing balance, shows exactly where a statement is missing.
How should I handle transactions I can't identify?
Put them in a clearly labeled review category and ask the client. Don't silently guess, especially for large deposits that might be loans or owner contributions.
Skip the retyping
Upload a PDF or scanned statement and download a balance-checked Excel, CSV, QuickBooks or Xero file. Try the converter free.
Related articles
Convert your first statement free
3 pages a month on the free plan. No credit card.