Invoice reconciliation is the process of matching supplier invoices against purchase orders, contracts, and goods receipts to verify pricing, quantity, and terms before payment authorization. In the Contract Performance Management stack invoice reconciliation is the payables-side expression of the Financial Truth Layer, so the AP team clears matched invoices against live matched-against-ERP contract data rather than a rebuilt spreadsheet.
How it works
Invoice reconciliation runs on three sources of truth: the supplier invoice as received, the purchase order or contract clause that authorised the spend, and the goods receipt or service confirmation that proves delivery. A reconciled invoice is one where the price on the invoice matches the contract price, the quantity matches the goods receipt, and the payment terms match the negotiated clause. Any variance beyond a tolerance threshold is flagged as an exception and routed for resolution before the invoice is released to payment.
A working system stores the contract clauses as machine-readable rules, pulls open payables and receipts from the ERP continuously, and executes the three-way match on every line item. Clean matches pass through automatically; exceptions surface with the underlying clause, PO line and receipt attached, so the accounts payable team resolves the variance against evidence rather than reconstruction. See the contract transaction gap page for the wider matching context.
Why it matters
Unreconciled invoices are the surface expression of the underlying contract-to-transaction gap. WorldCC records 19% average contract value leakage across mid-large enterprises, with a 3-7% best-in-class band; on a EUR 200 million annual payables book the gap between the two is somewhere between EUR 24 million and EUR 32 million a year, most of it moving through overpaid off-contract prices, unclaimed early-payment discounts and missed rebate credits. Aberdeen records a 65% reduction in admin time once reconciliation runs against structured contract data. See the paired rebate reconciliation page for the credit-side of the same discipline.
How Vendortell handles it
Vendortell handles invoice reconciliation as one output of its Contract Performance Management platform. Contract clauses are extracted during onboarding into machine-readable rules, open payables and receipts stream from the ERP continuously, and the three-way match fires on every line item against the contract as the single source of truth. See the Financial Contract Intelligence layer for the wider Financial Truth stack that sits underneath the reconciliation engine. Onboarding runs in 30 days.
FAQ
How is invoice reconciliation different from a two-way match?
A two-way match compares the invoice against the purchase order only. Invoice reconciliation adds the contract clause and the goods receipt, so the price test looks at the negotiated rate rather than the PO shorthand, and the quantity test looks at what was delivered rather than what was ordered.
Who owns invoice reconciliation inside finance?
Ownership is joint. Accounts payable runs the day-to-day match, procurement owns the contract clauses that feed the price test, and controllership owns the exception queue at month-end. A CPM engine keeps clauses, POs, receipts and exceptions in one line of sight.
What tolerance thresholds work in practice?
Price tolerance is usually set at a small fixed amount plus a percentage band on the line total; quantity tolerance is set as a unit band on the shipped volume. The specific band is a procurement decision; the CPM engine enforces whatever band the finance policy carries.
Does invoice reconciliation need dedicated software?
For a small payables book direct ERP three-way matching is sufficient. At portfolio scale the reconciliation becomes continuous and every unresolved exception blocks a real payment. A CPM engine turns the workflow into a priced, evidence-backed queue.
