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 is a transaction-level control that runs before payment. The other is an account-level check that runs after it.
Finance teams often assume one makes the other redundant. It doesn't. For a wider view of where this fits in a finance team's controls, see our guide to supplier statement reconciliation.
Three-way matching catches a bad invoice before it's paid. Statement reconciliation catches everything that invoice matching missed, plus everything that happened afterwards.
Ask five people in finance to define "invoice matching" and "statement reconciliation" and you'll often 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 gaps neither one is built 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. 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.
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's no invoice for three-way matching to check. Statement reconciliation is what catches that gap, because the invoice still turns up on the supplier's statement even though it never reached your ledger.
The reverse happens too. A duplicate invoice, identical to one already paid, can pass three-way matching cleanly, because the PO and goods receipt still match. Reconciliation is usually what surfaces it, when the supplier's statement shows one invoice and the ledger shows two payments against it. For more on that specific failure mode, see our breakdown of common statement reconciliation problems.
Why you need both
Run only invoice matching, and a business stays blind to anything outside the invoice-to-payment flow: unclaimed credits, statements that never got entered, payments a supplier disputes months later. Run only statement reconciliation, and bad invoices still get paid before anyone catches them, since reconciliation happens afterwards, often weeks later.
Used together, the two controls cover both ends of the process. Matching stops errors before they cost money. Reconciliation catches whatever gets through, or happens after.
Invoice matching vs statement reconciliation, side by side
| Invoice matching | Statement reconciliation |
|---|---|
| Checks one invoice | Checks the whole account |
| Runs before payment | Runs after postings, usually monthly |
| Compares PO, goods receipt and invoice | Compares the supplier's statement to your ledger |
| Preventive control | Detective control |
| Misses invoices that never get entered | Catches them, because they still show on the statement |
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.
