Guide
How to reconcile invoices with bank statements
The purpose of reconciliation is simple: prove that every invoice corresponds to real money that moved, and that every bank movement is explained. Here is the process step by step — and where it stops scaling by hand.
Why reconcile at all
Unreconciled books drift. Receivables you believe were paid weren’t; invoices get paid twice; fees quietly eat margins; and fraud — which almost always leaves a trace in the bank activity — goes unnoticed because nobody compares the two sides. Reconciliation is the control that catches all of it, which is why auditors ask for it first.
The six steps of invoice-to-bank reconciliation
-
1. Gather every open invoice — both directions
Collect what you owe (payables) and what you are owed (receivables) for the period. Most reconciliation errors start here: an invoice that never made it into the list can’t be matched, so the payment for it looks like a mystery transaction.
-
2. Export the bank statement for the same period
Download CSV or PDF statements covering the full date range, with no gaps between the last statement’s closing date and this one’s opening date. A missing week is a blind spot where a duplicate payment or missed receipt hides.
-
3. Match line by line: amount first, then date, then reference
For each bank transaction, find the invoice it settles. Exact amount and a nearby date is the common case. Watch for the hard ones: one payment covering several invoices, partial payments, bank fees deducted from the transferred amount, and currency differences.
-
4. Classify what doesn’t match
Every unmatched line needs an explicit decision: is it an invoice you never recorded, a payment for a future invoice, a bank fee or internal transfer to ignore, or something that shouldn’t be there at all? “I’ll figure it out later” is how discrepancies age into write-offs.
-
5. Record the state of every line
Matched, pending a question, or deliberately ignored — write it down where the next person can see it. If your record is cell colors in a spreadsheet, the knowledge leaves when the person who colored them does.
-
6. Investigate the exceptions before closing
Duplicates, overpayments, amounts that differ from the invoice, payments to vendors you don’t recognize — these are the lines worth your senior person’s time. Everything routine should already be matched by now.
Where the manual process breaks down
Volume
Fifty invoices a month is an afternoon. Five hundred is a part-time job doing lookups a machine does in seconds.
Formats
Invoices arrive as PDFs, photos, and XML; statements as CSV and PDF exports that differ by bank. Most reconciliation time is spent re-keying, not deciding.
Partial and combined payments
One-to-one matches are easy. One payment across three invoices, or 60% now and 40% later, breaks naive matching — and most spreadsheets.
No memory between months
A spreadsheet doesn’t remember that a similar-looking invoice was already paid three weeks ago. Duplicate payments are caught by luck.
What to automate (and what to keep human)
The steps above split cleanly into lookup work and judgment work. Software should do the lookups:
- Data entry — AI extraction reads invoice PDFs, images, and XML so amounts, dates, and parties arrive as structured data.
- Statement parsing — CSV, PDF, and MT940 files become line-level transactions, with duplicate lines across overlapping uploads detected automatically.
- The first pass of matching — candidate pairs proposed by amount, date, reference, and party, each with a confidence score. Confident ones match automatically; the rest queue for review.
- Exception spotting — detectors flag duplicates, partial payments, overpayments, statement gaps, and unusual vendor activity with severity levels, instead of relying on someone noticing.
The judgment stays with you: confirming uncertain matches, deciding what to ignore, and acting on flagged anomalies. That is exactly how InvoiceHive’s reconciliation workflow divides the work.
Habits that keep reconciliation painless
- Reconcile weekly, not monthly — exceptions are cheap to fix while the context is fresh.
- Never leave a line without a state. “Unmatched and known” is fine; “unknown” is not.
- Keep both directions in one place — payables-only reconciliation misses half the risk.
- Treat statement gaps as findings, not inconveniences: request the missing period before closing.
- If a team handles it, use explicit roles — who matches, who confirms, who investigates flags.
Do the next reconciliation with the manual steps automated
InvoiceHive extracts your invoices, parses your statements, and proposes the matches — you keep the judgment calls.
Setup in 2 minutes — or talk to us first