Finance Index
What is vendor statement reconciliation and how do I do it?
Reference guide to vendor statement reconciliation, including vendor records, onboarding requirements, compliance checks, fraud controls, and payment readiness.
Vendor statement reconciliation compares a vendor's statement of your account against your own AP records to surface gaps: invoices they billed that you never received, payments you made that they haven't applied, open credits, and disputed items. It's worth doing even with three-way matching because matching validates the invoices you *have* - reconciliation catches the ones you're *missing* and the unrecorded liabilities they imply.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Vendor statement reconciliation | Vendor statement reconciliation compares a vendor's statement of your account against your own AP records to surface gaps: invoices they billed that you never received, payments you made that they haven't applied, open credits, and disputed items. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Vendor impact | (1) Get the vendor's current statement and your open-items and payment history for that vendor. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| How often should I | Risk- and value-based, not universal. | Keeps vendor records and payment decisions reliable. |
| Reconcile statements if we already | Because three-way match only validates invoices you've received - it's silent on invoices you never got. | Helps finance decide what to do next. |
| Vendor statement shows invoices | Request copies of the unknown invoices, confirm they're genuinely yours (not another customer's or duplicates), record the real liabilities, then find where they vanished - usually a non-standard submission channel (sent to an employee, wrong inbox, lost attachment). | Reduces payment errors, timing issues, and reconciliation cleanup. |
How do I reconcile a vendor statement step by step?
(1) Get the vendor's current statement and your open-items and payment history for that vendor. (2) Tick off matches line by line. (3) Investigate the differences: invoices on their statement you have no record of (request copies - possible missing liability), payments you made they show as open (give them the payment details to apply), credits they owe you, and disputed items. (4) Resolve or document each exception. (5) Fix the upstream leak - if invoices are going missing, the intake process is the real problem.
How often should I reconcile, and for which vendors?
Risk- and value-based, not universal. Reconcile your top-spend and most-active vendors regularly (monthly or quarterly), any vendor on dispute or credit hold immediately, and the long tail opportunistically or at year-end. Reconciling all 4,000 vendors monthly is a waste; reconciling the 50 that represent most of your spend - plus anyone you're in conflict with - catches nearly all the exposure.
Why reconcile statements if we already do three-way match?
Because three-way match only validates invoices you've received - it's silent on invoices you never got. A vendor statement is the only routine view of what the vendor *thinks* you owe, which is how you catch missing invoices, unrecorded liabilities, and misapplied payments that matching can't see.
Vendor statement shows invoices we never received - how do I find them and stop the leak?
Request copies of the unknown invoices, confirm they're genuinely yours (not another customer's or duplicates), record the real liabilities, then find where they vanished - usually a non-standard submission channel (sent to an employee, wrong inbox, lost attachment). Fixing intake (one known submission address or a portal) stops the recurrence.
Vendor shows a balance but we show paid - how do I prove payment?
Pull the payment evidence (date, method, amount, and reference/clearing detail) and send it so the vendor can apply it on their side - most "you owe us" balances are unapplied-cash errors in their AR, not real debt. If they still can't locate it, trace the payment to clearing on your bank records.
Vendor put US on credit hold over disputed invoices - how do I get released?
Separate undisputed from disputed immediately: pay or confirm the undisputed items to show good faith and shrink the held balance, document the dispute basis in writing, and ask for release on the disputed portion while it's resolved. A clear paper trail and prompt payment of what's genuinely owed is the fastest lever.
How do I find unclaimed vendor credits before they expire?
Reconciliation is how you find them - credits sit on vendor statements as open items you've forgotten. Review statements for credit memos and overpayments, claim them as offsets against open invoices or request refunds, and act promptly: many vendors quietly expire unclaimed credits, so an unreconciled statement is money walking out the door.
Are there tools that automate statement reconciliation / can AI match statements to our ledger?
Yes - reconciliation tools and AI matching can parse a vendor statement and auto-match it against your AP ledger, flagging only the exceptions for human review. They handle the tedious line-by-line ticking well; the judgment (is this a real missing invoice or a duplicate? whose error is the unapplied payment?) still needs a person.
How do I use statements to catch unrecorded liabilities before year-end close?
Reconcile your major vendors just before close and treat any invoice on their statement that you haven't booked as a candidate accrual. It's one of the most reliable completeness checks for AP - vendor statements are an external source for liabilities your own system might be missing, exactly what auditors test for.
Stampli perspective
Stampli supports reconciliation-style questions inside the AP workspace - what was paid, when, and against which invoices - from the vendor record, with full invoice and payment history visible in one place rather than spread across the ERP, bank exports, and email. Because intake is centralized (email, upload, portal, and CSV all flow through the same path), the "missing invoice" leak that statement reconciliation exists to catch is narrower in the first place.