Invoice matching checks a single invoice against a purchase order and a goods receipt before it's paid. Statement reconciliation checks a supplier's whole statement against your ledger after the fact. One's a transaction-level control that runs before payment. The other is an account-level check that runs after it.
It's tempting to assume one makes the other redundant, but it doesn't. For a wider view of where this fits in a finance team's controls, take a look at our guide to supplier statement reconciliation.
Three-way matching catches a bad invoice before it's paid. Statement reconciliation catches what invoice matching misses, plus what happens afterwards.
Ask five people in finance to define "invoice matching" and "statement reconciliation" and you'll likely get five overlapping answers. Both compare numbers to catch errors. Both sit inside accounts payable. And in plenty of finance teams, the same person runs both.
They're not the same control, though, and treating them as interchangeable leaves blind spots neither one is designed to close on its own.
What invoice matching checks
Invoice matching, usually run as two-way or three-way matching, is a pre-payment control applied to a single invoice. Microsoft's own documentation on the process describes it as checking that the price and quantity on an invoice stay within tolerance of the purchase order and, for three-way matching, the goods receipt too.
Three documents go into the check:
- The purchase order, which sets the agreed price and quantity.
- The goods receipt, confirming what actually arrived.
- The invoice itself, the bill being paid.
If all three line up, the invoice clears for payment. If they don't, it's held for review before any money moves. That's the point of the control: it's a gate, not an audit. It runs once per invoice, before payment.
What statement reconciliation checks
Statement reconciliation works on a different unit entirely: the supplier account, not the invoice. It compares the supplier's own statement, everything they say you owe, against your purchase ledger for that supplier, over a period rather than a single transaction.
It's a detective control, not a preventive one; preventive controls are designed to stop errors before they happen, detective controls to find them afterwards. It doesn't stop a bad invoice from being paid. It finds what happened afterwards: an invoice that never made it into your ledger, a credit note sitting unclaimed, or a duplicate payment that slipped past invoice matching entirely.
NG Bailey’s accounts payable team saw this firsthand. Payments over £5,000 triggered a manual, line-by-line check against more than 500 supplier statements a month, exactly the kind of discrepancy reconciliation exists to catch. “Our goal was to implement a solution that gives us confidence in the alignment between our ledger and our supplier ledger, and where discrepancies exist, we want a clear audit trail of actions and communications to reduce missing or duplicate invoices,” says Michelle Baxendale, Head of Finance Shared Services at NG Bailey. Read the full NG Bailey case study for how that reconciliation process now runs.
Where the overlap stops
Invoice matching only works if an invoice reaches it. If a supplier's invoice never gets entered into the AP system (lost in an inbox, say, or sent to the wrong person), there isn't an invoice for three-way matching to check. Statement reconciliation is what catches it, because the invoice still turns up on the supplier's statement even though it never reached your ledger.
Duplicates are a second blind spot. An invoice that's identical to one already paid can pass three-way matching cleanly. That's because the PO and goods receipt still match. Reconciliation is usually what highlights this, when the supplier's statement shows one invoice and the ledger shows two payments against it. We cover duplicates in more detail in our breakdown of common statement reconciliation problems.
Gwent Police saw the problem at scale after moving to a new finance system. The system only checked invoice numbers for duplicates, so inconsistent numbering let 142 duplicate payments, worth over £1 million, go out. Finance only found out when suppliers started sending the money back. Part of the fix was full reconciliation of its high-volume suppliers. (Source: Gwent Police and Crime Commissioner)
Why you need both
Run only invoice matching, and a business stays blind to what happens outside the invoice-to-payment flow: unclaimed credits, invoices that were never entered, payments a supplier disputes months later. Run only statement reconciliation, and bad invoices can still get paid before anyone catches them, since reconciliation happens after the fact.
Used together, the two controls cover both ends of the process. Matching stops errors before they cost money. Reconciliation catches what gets through and what happens after payment.
Invoice matching vs statement reconciliation, side by side
Both controls do their best work together. To see how the matching process itself runs end to end, read our guide to how supplier statement matching works.
