Supplier statement reconciliation is the process of checking a supplier's statement of account — their list of the invoices, credit notes and payments that make up your balance — against your own purchase ledger, line by line, to confirm the two agree and to investigate anything that doesn't.
Every supplier keeps their own record of your account: the invoices they've raised, the credit notes they've issued, the payments they've received from you. Periodically — usually monthly — they send a summary of that record as a statement of account, ending with the balance they believe you owe.
Your purchase ledger holds your version of the same story. In a perfect world the two match. In practice they drift apart: an invoice never arrived, a credit note was promised but not posted, a payment is in flight, something was keyed against the wrong account. Statement reconciliation is the discipline of putting the two versions side by side and accounting for every line.
The output is simple: for each supplier, either "we agree" or a short list of explained differences — each one classified as a timing difference (self-resolving), a supplier-side error (to query) or a ledger-side error (to correct).
Statement reconciliation is one of the few checks that tests your purchase ledger against evidence from outside the business. Skip it, and three kinds of problem accumulate quietly:
An invoice posted twice, or paid against the wrong account, looks fine from inside the ledger. Against the supplier's statement it stands out immediately.
Promised credits are easy to lose — the supplier agrees one on the phone, and unless someone checks the statement, nobody notices it was never issued or never posted.
Unrecorded invoices mean understated liabilities and accruals guessed rather than known. The statement is the completeness check for what you owe.
However it's done — spreadsheet, ledger module or automation — the process has the same four stages.
Gather a statement from every supplier due one this period, and chase the suppliers who haven't sent theirs. A reconciliation you didn't do because the statement never arrived is a gap in the control, not a saving.
Work through the statement line by line — invoices, credit notes, payments — ticking each against the purchase ledger. Every line ends up matched, or on the differences list.
Classify each unmatched line: timing difference, supplier error or ledger error. Request copy invoices, query wrong charges, post what's genuinely missing, and log queries so they carry into next period instead of being re-discovered.
Document the reconciliation — matched totals, differences and their explanations, queries outstanding — then have it reviewed and approved. That file is the audit evidence.
Statements arrive as PDFs, spreadsheets, scans and phone photos, each laid out differently. Most of the labour in manual reconciliation is reading and rekeying before any actual checking happens — which is why it gets squeezed to month-end and why coverage quietly shrinks to "the big suppliers, when there's time".
An invoice dated the 28th that reached your ledger on the 2nd looks like a missing invoice. A payment in flight looks like an unallocated balance. Teams burn hours investigating differences that were only ever timing — or, worse, learn to wave differences through without looking, which defeats the control.
A difference gets queried, the month closes, the spreadsheet is filed — and next period someone re-discovers and re-investigates the same line. Without a way to carry queries forward, the same work is done twice and supplier disputes drag on for quarters.
Everything mechanical in the process — reading statements in any format, matching lines against the ledger, recognising timing differences, chasing suppliers who haven't sent statements, producing the workbook — can now be automated reliably. What's left for people is the part that was always the point: deciding what a genuine difference means and what to do about it.
That changes the economics of the control. Full coverage every period stops being a staffing question, and reconciliation shifts from a month-end scramble to an exception-review discipline.
Statements in by email, every line matched against your ledger, exceptions surfaced for review — with chasing, queries and the Excel workbook handled. Includes a 65-second walkthrough.
See the tool →How the 1779 Henley brewer and pub company reconciles supplier statements across its managed pubs and head office — "in minutes rather than hours".
Read the case study →A supplier statement (or statement of account) is a summary a supplier sends listing every transaction they believe is open or recent on your account — invoices raised, credit notes issued and payments received — usually ending with the balance they think you owe. It's not a request for payment like an invoice; it's the supplier's view of your account, which is exactly what makes it useful as a cross-check.
Best practice is every accounting period — monthly for most businesses — and at minimum for all significant suppliers at year end. Reconciling little and often keeps differences small and recent enough to resolve quickly; leaving it until year end means unpicking months of history.
Bank reconciliation checks your cash records against the bank's records. Supplier statement reconciliation checks your purchase ledger against each supplier's records. Both are completeness and accuracy controls that work the same way — comparing your version of events against an independent external version — but they cover different balances: cash on one hand, trade creditors on the other.
A mismatch caused purely by when each side recorded a transaction, not by an error — a payment you sent on the 30th that the supplier allocated on the 2nd, or an invoice raised on the 28th that reached your ledger next period. Timing differences are expected and self-resolving; the skill is recognising them quickly so effort goes into genuine discrepancies instead.
Auditors routinely use supplier statements as independent evidence for trade creditors, and a file of completed reconciliations with documented queries and approvals materially strengthens that testing. Regular statement reconciliation is widely regarded as a core accounts payable control, so gaps tend to attract audit attention even though the reconciliations themselves aren't a statutory requirement.
Orka's Supplier Statement Reconciliation tool runs everything in this guide — collection, matching, chasing, queries and the audit workbook — leaving your team the judgement calls. There's a 65-second walkthrough on the tool page.
See how the tool works