Article
What Should an Invoice Matching Solution Actually Catch Before You Pay?
An invoice matching solution is software that checks an incoming invoice against other records - a purchase order, a receipt, sometimes an inspection report - before the invoice is approved for payment. The level of matching it runs, not just the fact that it "matches," determines what it actually catches and what slips through.
Most teams buying invoice matching solutions assume more automation means more protection. That is only true if the solution matches against the right documents. A tool that runs a fast 2-way match will clear an invoice a human would have stopped cold - and a padded rate or a rate-card violation will sail through just as easily whether the check is automated or manual.
What are the levels of invoice matching, and where does each one stop?
Every invoice matching solution on the market runs one of a handful of standard checks. The differences matter more than the marketing suggests.
| Matching level | What it checks | What it catches | What it misses |
|---|---|---|---|
| 2-way | Invoice vs. purchase order | Wrong item, wrong quantity billed vs. ordered | Goods never received, wrong price against the contract |
| 3-way | Invoice vs. PO vs. receipt/goods receipt | The above, plus billing for goods never delivered | Quality issues, rate-card and SOW terms |
| 4-way | Invoice vs. PO vs. receipt vs. inspection/quality report | The above, plus goods that arrived but failed inspection | Still nothing outside the PO - contract terms, rate cards, scope |
| Agreement-level | Invoice vs. the whole agreement - contract, SOW, rate card, plus the PO | Rate-card violations, scope creep, terms drift, ceiling breaches | Nothing that's actually written into the agreement |
We've covered how the mechanics of the 3-way match actually work, and where it falls short, and broken down the full 2/3/4-way ladder in detail elsewhere. The point worth repeating here: every rung on that ladder, including 4-way, still stops at the purchase order. For a services firm paying subcontractors on a master services agreement (MSA), statement of work (SOW), or rate card - often with no PO at all - that's the gap that matters most.
What does it cost you if your matching solution stops at the PO?
The cost shows up in two places: the labor to catch what the software doesn't, and the money that gets paid out anyway.
On labor: APQC's Open Standards Benchmarking data shows a wide gap between top and bottom performers in the fully-loaded cost to process a single AP invoice - the difference is mostly the manual review work that happens when the matching software can't finish the check on its own.
On the money leaking straight through: APQC's benchmark for duplicate and erroneous disbursements puts even top-performing AP teams at about 0.8% of annual disbursements going out as duplicate or erroneous payments, with the median organization closer to 1.5% and bottom performers around 2.0%. None of that requires a criminal actor - a rate-card violation on a T&M invoice, a duplicate submission from a subcontractor, or a stale price that never got updated in the PO will all clear a PO-level match without a flag.
Add deliberate fraud and the number gets worse. The Association of Certified Fraud Examiners estimates that a typical organization loses about 5% of annual revenue to occupational fraud each year, and billing and payment schemes are among the most common categories they track. A changed bank account, a payee mismatch, or an invoice citing a PO number that doesn't exist are all things a PO-only match was never built to see.
What should you actually look for when evaluating an invoice matching solution?
A short checklist, in the order it matters for a contract-governed services firm:
- Does it match against the agreement, or only the PO? If most of what you buy runs on an MSA, SOW, or rate card with no PO issued at all, a PO-matching tool has nothing to check against on those invoices.
- Does every flag explain itself? A useful match cites the exact line or clause behind a flag - a specific rate that doesn't match the rate card, a quantity that exceeds the SOW ceiling - not just a generic