Vendor statement reconciliation is the monthly line-by-line check of supplier statements against your AP subledger that reveals missing invoices and unprocessed credits so you can correct balances and close the month accurately. Done well, it leaves you with a short, actionable list of reconciling items rather than a vague sense that something does not add up. Start by running it for your top suppliers by spend this month.
TL;DR:
- Run the check monthly, reconcile the prior period’s closing balance before current transactions, and request missing supplier statements by a fixed monthly deadline.
- Match in both directions: compare ledger entries with statement lines, then check statement lines against the ledger to catch items missing from either record.
- Keep reconciliation separate from payment processing, verify bank details through contact information already on file, and log manual match overrides with reasons.
- Matching purchase orders, receipts, and invoices cannot catch supplier invoices absent from your system, so reconcile statements separately and apply credits only after confirmation.
- Set owners and deadlines for every discrepancy, retain statements and correspondence as evidence, and track whether timely payments meet the 95% or higher internal target.
Table of Contents
- What vendor statement reconciliation is and why it matters
- Common reconciliation problems and how to fix each one
- Step-by-step vendor statement reconciliation process to run each month
- Controls and best practices to reduce errors and fraud risk
- What busy AP teams get wrong about reconciliation
- Centralising supplier credits with BlankLedger
- FAQ
- Sources
What vendor statement reconciliation is and why it matters
Vendor statement reconciliation compares two datasets: the supplier's statement of account and your own AP subledger or aging report. One side shows what the supplier believes you owe; the other shows what your books say. Any gap between them is a reconciling item that needs an explanation.
Most finance teams run this check monthly, tying it to the close cycle so discrepancies get caught before they compound. The ACCA's guidance on supplier statement reconciliations treats this as standard practice precisely because small timing gaps become serious problems if they sit unresolved for several periods.
Skipping or rushing the check carries real risk: duplicate payments slip through, invoices go unrecorded until a supplier chases you, disputes drag on because nobody has evidence, and payments run late simply because nobody noticed an invoice was missing from the ledger in the first place.
Common reconciliation problems and how to fix each one
Most reconciliation headaches repeat month after month. The fix usually takes less time than the problem does once you know what you are looking at.
- Missing or incomplete supplier statements: build a standing request routine with a fixed due date each month, and escalate automatically when a statement does not arrive on time.
- Format inconsistency: create import rules or a standard template for the fields you need (invoice number, date, amount, reference) so statements from different suppliers normalise into one view.
- Opening balance mismatches: trace the prior period's closing balance forward and reconcile it before touching current-month transactions, since an unresolved opening gap distorts everything that follows.
- Duplicate or unrecorded invoices: apply duplicate-detection rules matched on vendor, invoice number and amount, and flag anything that appears on the statement but not in your subledger for immediate investigation.
- Timing differences: align cut-off dates with each supplier and tell them, in writing, what timing variance to expect so a payment in transit does not get logged as a discrepancy.
- Unallocated cash or credit notes: apply credits only after supplier confirmation, and keep a running log of anything still unapplied so it does not get lost between periods.
- Manual-process scaling limits: triage by value, putting high-value or unusual items in front of a reviewer and letting routine, rules-based matches clear automatically.
- Transposition and data-entry errors: verify key fields on entry and run two-way checks, since a single digit out of place is often the real cause behind an apparent missing invoice.
The ACCA sets out several of these causes directly, including timing differences and transposition errors, with worked examples showing how small entry mistakes create balance gaps that look larger than they are.
Pro Tip: Reserve manual review time for the handful of high-value or unusual items; let clear, rules-based matches (same invoice number, same amount) clear automatically so your attention goes where it is actually needed.
Step-by-step vendor statement reconciliation process to run each month
A repeatable sequence turns reconciliation from a dreaded task into a routine one.
- Prepare: collect every supplier statement, your AP subledger, remittance records and bank statements, and align the date ranges across all of them before you start matching.
- Match: run the check both ways. Match ledger entries against the statement, then match statement lines against the ledger, since checking only one direction misses items that exist on just one side.
- Record: log every reconciling item with a clear description, assign an owner, and set a resolution deadline rather than leaving it as a loose note.
- Resolve: apply confirmed credits, post any adjusting entries, and chase suppliers with documented evidence attached to each query.
- Close: update your records, mark the supplier account reconciled, and retain the supporting evidence in case of audit.
The two-way check in step two matters more than it sounds. The ICAEW's guidance on data extraction quality points out that checking only ledger to statement, or only statement to ledger, is a common pitfall that lets missing items go unnoticed on whichever side you did not check.
Before moving on, make sure each closed reconciliation includes:
- A dated copy of the supplier statement used
- The matched AP subledger extract for the same period
- A log of reconciling items with owners and resolution notes
- Evidence of any supplier correspondence tied to a dispute
Controls and best practices to reduce errors and fraud risk
Reconciliation only works as a control if the person doing it is independent from the person processing payments. The GAO Green Book's principle on control activities treats segregation of duties as a core design requirement, not an optional refinement, and that separation is what makes a reconciliation trustworthy rather than a formality.
A few preventive measures do most of the work:
- Verify supplier bank details independently, using contact information already on file rather than details printed on an invoice, as recommended in ICAEW's guidance on fake invoices.
- Apply three-way matching (purchase order, receipt, invoice) to validate invoices before payment, alongside duplicate-invoice checks.
- Limit who can override a manual match, and log every override with a reason.
- Retain evidence and correspondence for every reconciling item, with a clear escalation route for anything that looks like fraud.
Many AP teams set an internal target of on-time payment rates at 95% or higher as a performance measure under their control framework, which gives reconciliation owners a concrete benchmark to work towards rather than a vague aim of "fewer errors."
What busy AP teams get wrong about reconciliation
The biggest mistake we see is treating reconciliation as a once-a-quarter clean-up rather than a monthly habit. By the time a gap has sat for three months, nobody remembers which invoice went missing or why a credit was never applied, and the investigation takes ten times longer than the original match would have.
The second mistake is confusing three-way matching with reconciliation. Three-way matching checks invoices you already have against a purchase order and a receipt. It does nothing for an invoice the supplier raised that never reached your system at all, which is exactly the gap vendor statement reconciliation is built to catch.
— tylan
Centralising supplier credits with BlankLedger
Most of the fixes above come down to one thing: knowing, at a glance, what you are owed and who still owes it to you. We built BlankLedger around that problem faced by independent automotive repair shops, where returned parts, supplier credits and partial refunds can pile up across multiple suppliers and become hard to track by spreadsheet alone.
With BlankLedger, you can keep one record of expected credits from parts returns, payments received against those credits, and unresolved discrepancies still waiting on a supplier response.
| What you track | Where it typically lives without BlankLedger | Where it lives with BlankLedger |
|---|---|---|
| Expected supplier credits | Scattered emails and paper slips | One central record |
| Received refunds | Bank statements, manually matched | Logged against the original credit |
| Unresolved discrepancies | Sticky notes or memory | Tracked with follow-up status |
If reconciliation keeps surfacing supplier credits you cannot easily follow up on, visit the BlankLedger product page to see how we help repair shops recover money owed to them without adding administrative work.
FAQ
What is a vendor reconciliation statement?
A vendor reconciliation statement is the record produced when you compare a supplier's statement of account against your own AP subledger, showing matched items and any outstanding differences. It typically lists invoices, payments, credits and the specific items still unresolved between the two records, as described in ACCA's guidance.
What is an account reconciliation statement?
An account reconciliation statement is a document showing the comparison between two sets of records for the same account, such as a bank statement against a cash ledger, or a supplier statement against an AP subledger. It records the starting balances, matched transactions and any differences still needing explanation.
What is reconciliation of accounts payable?
Reconciliation of accounts payable is the process of checking your AP subledger against supplier statements, bank records and purchase documentation to confirm that recorded liabilities are accurate and complete. It identifies missing invoices, duplicate entries and unapplied credits, which is why most finance teams run it as part of the monthly close.
What is reconciliation in simple words?
Reconciliation, in simple words, means comparing two records that should agree and working out why they do not. In accounts payable, that usually means lining up what a supplier says you owe against what your own books say, then explaining or fixing every difference.
Sources
- Supplier statement reconciliations | ACCA
- Data extraction quality: getting it right every time | ICAEW
- GAO Green Book – principle on control activities