Most reconciliation guides start at the same place: open your accounting software, connect your bank feed, match transactions. Good advice — when the bank feed works.
The problem is that feeds don't always work. International banks, smaller regional institutions, business accounts at banks without open banking support, clients who share PDFs because that's what their bank provides — all of these leave you with a statement and no feed. Most guides skip past this entirely.
This guide covers the full reconciliation process, starting with the step that usually gets glossed over: getting accurate, structured transaction data out of a PDF before the reconciliation begins.
What bank reconciliation actually checks (and why it matters)
Bank reconciliation compares two independent records of the same account activity: the transactions recorded in your books and the transactions recorded by the bank. When they match, you have confidence that your records are complete. When they don't, you have a discrepancy that needs to be traced and resolved.
The reconciliation check answers three questions:
- Are all transactions on the bank statement recorded in the books?
- Are any book entries for transactions that haven't yet cleared the bank?
- Do the ending balances agree once timing differences are accounted for?
Timing differences are expected and normal — cheques issued but not yet cleared, deposits in transit, fees posted at month end. The reconciliation accounts for these systematically. What it's looking for are unexplained gaps: transactions in the books with no bank record, or bank transactions with no corresponding entry.
The practical stakes are significant. Undetected errors compound. A misposted transaction from February affects every running balance for the rest of the year. Catching discrepancies monthly keeps them small and traceable; catching them at year-end after eleven months of accumulation is a different kind of problem.
Gathering source documents: statements vs. bank feeds vs. exported PDFs
The reconciliation process needs two data sources: the bank's record and your books. How you get the bank's record matters more than most guides acknowledge.
Bank feeds are the cleanest option when available. The accounting software pulls transactions directly from the bank's API, categorizes them automatically, and presents them for matching. For major retail banks in countries with open banking infrastructure — UK, Australia, much of Europe — feeds work reliably for most account types.
CSV or OFX exports from online banking are the next best option. The client downloads the file, you import it. The data is structured and complete, though it may need date format adjustments or column remapping depending on the bank's export format.
PDF statements are the reality for a significant portion of client work. Smaller banks, international accounts, older business accounts, and clients who download their monthly statement rather than the data export — all of these land as PDFs. The data is there; it just isn't in a form your accounting software can use directly.
Before reconciliation can begin, PDF transaction data needs to be extracted into a structured format. The options are manual entry (slow, error-prone), generic OCR tools (inconsistent, often drops the running balance column), or a bank-specific converter that understands statement structure and validates the output against the opening and closing period totals.
The reconciliation workflow: 6 steps from import to close
With source documents in hand, the reconciliation process follows a consistent sequence:
- Import the bank statement data. Whether from a feed, CSV, or converted PDF, get the transaction rows into your accounting software or working spreadsheet. Verify the opening balance matches the prior period's closing balance before proceeding.
- Match transactions to book entries. Work through each bank transaction and find the corresponding entry in your books. Most accounting software does this semi-automatically; manual reconciliation in a spreadsheet requires sorting both datasets by date and amount and working through them in parallel.
- Record outstanding items. Identify transactions in the books that haven't yet appeared on the bank statement — cheques issued but not cleared, payments initiated but not settled. These are timing differences, not errors.
- Identify bank-only items. Find transactions on the bank statement with no corresponding book entry. Bank fees, interest charges, and direct debits the client didn't mention are the most common examples. These need to be posted to the books before the reconciliation can close.
- Reconcile the ending balances. Calculate: bank closing balance + deposits in transit − outstanding cheques = adjusted bank balance. This should equal your book balance after posting any bank-only items. If it does, the reconciliation is complete.
- Document and close. Record the reconciliation date, the closing balance confirmed, and any items that required adjustment. In accounting software, mark the period as reconciled. In a spreadsheet workflow, save the working file with a clear naming convention.
Common discrepancies and how to trace them
When the balances don't agree at step 5, the discrepancy needs to be traced before you can close. The most efficient approach is to work backwards from the difference.
If the discrepancy is exactly divisible by 9, there's likely a transposition error — digits swapped when entering an amount (e.g., $1,234 entered as $1,324). Sort both datasets and scan for amounts that differ by a multiple of 9.
If the discrepancy equals a specific transaction amount, that transaction is either recorded twice in one source or missing from the other. Search both datasets for that exact amount.
If the discrepancy is a round number, look for a bank fee or interest charge that wasn't posted to the books, or a payment recorded in the books for a different amount than what cleared.
If the discrepancy appears to have been present in the prior period, the opening balance is wrong — which means the previous reconciliation wasn't fully resolved. Check the prior period reconciliation file.
One category of discrepancy that's increasingly common in PDF workflows: extraction errors. If bank statement data was converted using a tool that didn't validate against the period totals, a misread digit in one transaction can produce a reconciliation difference that looks like a book entry error. Before spending time chasing the books, verify that the bank statement data itself is accurate — the opening balance, closing balance, and sum of all transactions should form a consistent chain.
Bulk reconciliation: handling multi-bank clients efficiently
For accounting firms managing clients with multiple accounts — or practices with a high volume of monthly reconciliations — the bottleneck is usually upstream of the reconciliation itself. It's getting clean transaction data in the first place.
A client with five accounts across three banks might provide a mix of bank feeds (for the major retail accounts), a CSV export (for the business account at a mid-tier bank), and PDF statements (for the international account and the company credit card from an institution without open banking).
The feeds and CSV are handled quickly. The PDFs each require conversion before they can be worked on. If that conversion is manual, it represents the majority of time spent on the client's reconciliation — before any actual reconciliation has happened.
Batch processing — converting all PDF statements at the start of the month, immediately after client document delivery — creates a consistent upstream process. All accounts are in structured format before reconciliation begins, so the workflow is the same regardless of which banks the client uses.
Tools that accelerate each stage
The reconciliation process spans several distinct tasks, and different tools are optimized for different stages:
Getting transaction data from PDFs. Bank-specific converters that validate output against period totals. The alternative — manual entry or generic tools — carries higher error rates and takes considerably more time per statement.
Matching and reconciliation. Accounting software (QuickBooks, Xero, Sage) handles this for connected accounts. For accounts without feeds, CSV or OFX import gets the data in; the matching workflow is then the same as any feed-connected account.
Discrepancy tracing. A working spreadsheet alongside the reconciliation software. Sorting by amount and filtering for unmatched items is faster in a spreadsheet than in most accounting software's built-in reconciliation screens.
Documentation and audit trail. The accounting software's reconciliation history is the primary record. Firms with external audit requirements often supplement this with the original statement PDF and the working reconciliation file, named and filed by client and period.
The step where most firms lose the most time is the first one — and it's the step that existing reconciliation guides consistently skip.
Frequently asked questions
How often should bank reconciliation be done?
Monthly is the standard for most businesses. More frequent reconciliation — weekly or daily — is common for high-volume accounts, cash-intensive businesses, or during audit periods. The key principle is that the longer the gap between reconciliations, the harder it is to trace discrepancies when they arise.
What is an outstanding transaction in bank reconciliation?
An outstanding transaction is one that appears in the books but hasn't yet cleared the bank — typically a cheque written but not yet presented for payment, or a payment initiated but not settled. Outstanding transactions are timing differences, not errors. They appear in the reconciliation as adjustments to the bank balance and are expected to clear in the following period.
What causes a bank reconciliation to be out of balance?
The most common causes are: a transaction recorded in the books but not yet on the bank statement (or vice versa), a data entry error where an amount was transposed or entered incorrectly, a bank fee that wasn't posted to the books, or an error carried over from the prior period's closing balance. Extraction errors from PDF conversion are an increasingly common source that's often overlooked.
How do accountants reconcile statements from banks that don't offer feeds?
The standard approach is to export a CSV or OFX file from online banking and import it. When neither is available and only a PDF statement exists, the options are manual data entry, a generic PDF-to-spreadsheet tool with manual cleanup, or a bank-specific converter that produces validated structured output. The choice depends on volume and accuracy requirements.
Can I reconcile directly from a PDF bank statement?
Not directly — accounting software requires structured data (bank feed, CSV, or OFX). A PDF needs to be converted to a structured format first. The conversion quality matters: a tool that validates extracted data against the statement's opening and closing balances confirms the data is accurate before reconciliation begins, rather than discovering an extraction error mid-process.
What's the difference between bank reconciliation and bookkeeping?
Bookkeeping is the ongoing recording of transactions as they occur. Bank reconciliation is the periodic verification that those records match the bank's independent record of the same account. Bookkeeping creates the records; reconciliation checks them. In practice, reconciliation often catches bookkeeping errors that weren't visible until the bank statement arrived.