A tight month-end bank reconciliation workflow

For bookkeepers running many clients, the close doesn't fail on judgment — it fails on volume. Here's a workflow that stays repeatable when the account count climbs.

Reconciling one bank account is a solved problem. Reconciling forty of them every month, across banks that each format statements differently, with feeds that quietly break, is a logistics problem wearing an accounting hat. The bookkeepers who close fast aren't smarter about debits and credits — they've turned the close into an assembly line where every step is predictable and the clerical work is compressed.

Below is that assembly line: five steps, in order, with an honest look at where the time actually goes.

The workflow, step by step

1. 1 — Gather every statement first

   Before you open the ledger, collect the period's statements for every account: operating, savings, each credit card, and merchant processors (Stripe, Square, PayPal). Get them as PDFs into one place per client. Chasing a missing statement halfway through the close is what turns a two-hour job into a two-day one.

   Standardize the intake: a shared folder per client, a naming convention (ClientName_Account_YYYY-MM.pdf), and a checklist of expected accounts so a missing statement is obvious at a glance, not a surprise at sign-off.

2. 2 — Get the transactions into the ledger

   This is the step that quietly eats your week. Every transaction on every statement has to land in the books, accurately, before anything can be matched. You have three realistic paths, and most clients force a mix:

   • Bank feed — great when it works, but feeds drop transactions, duplicate them, re-date them, and go dark without warning. They also carry no printed closing balance, so a feed can be silently incomplete and you'd never know from the feed alone.
   • Bank's own CSV/QBO export — clean when the bank offers it, but many banks (and most credit unions) only give you a PDF.
   • Convert the PDF statement — for everything else, you turn the PDF into a CSV or QBO file and import that. This is where the hours pile up if you're doing it by hand.
   Why this step is the time sink: it's the one part of the close that scales linearly with client count and can't be batch-approved with judgment. Ten clients is ten sets of statements to load; every broken feed and every un-importable PDF is manual, clerical minutes that repeat every single month. Speed here, more than anywhere else, is what lets you take on more clients without adding hours.

   This is also exactly where BankTidy fits: you drop the PDF statement in, and it converts it to CSV, Excel, QBO, or a Xero-ready file — and reconciles the statement before it ever hits your books. It adds the opening balance to the sum of every transaction it extracted and checks that it equals the printed closing balance. If it ties, you're importing a file you already know is complete. If it doesn't, it's flagged before a wrong number is sitting in the ledger. (See the accuracy benchmark: 14 real statements from 7 institutions across 3 countries, all reconciled to the penny.)

3. 3 — Match and clear

   With transactions in the ledger, match them against the statement and mark each as cleared. Modern software auto-matches most lines; your attention goes to the exceptions — anything uncategorized, any transfer between the client's own accounts (book both sides, don't double-count), and anything that looks personal on a business account. Code as you clear so the P&L is right when the reconciliation finishes, not later.

4. 4 — Investigate discrepancies

   If the cleared balance doesn't equal the statement's closing balance, the difference is a lead, not a nuisance. Common culprits, roughly in order of frequency:

   • Timing: outstanding deposits or checks that cleared the bank in a different period than they were booked.
   • Missing or duplicated feed lines: the single best argument for tying to the statement rather than trusting the feed.
   • Bank fees and interest booked by the bank but not yet in the ledger.
   • Sign or transposition errors from anything keyed by hand.

   A quick trick: if the difference is evenly divisible by 9, suspect a transposition; if it equals a specific transaction, you've probably missed or duplicated exactly that line. Note that starting from a source file that already reconciled removes an entire class of these — a difference at this stage is then almost always a genuine timing or coding item, not a botched import.

5. 5 — Lock the period

   Once the account ties to zero, finish it: attach the statement PDF to the reconciliation, record who signed off and when, and close the period in the software so it can't be silently edited after the fact. A locked period with the source statement attached is what makes next month's opening balance trustworthy and what an auditor or an incoming bookkeeper will actually thank you for.

Tips to compress the close

FAQ

Related reading: How to convert a PDF bank statement to CSV (every method, honestly).