Why does three-way matching miss some invoice errors?

It compares documents inside the P2P process. Wrong rates and missed credits can still satisfy PO and receipt checks when the PO envelope is wide enough.

Does three-way matching check rate cards?

Not in the usual ERP setup. Rate cards live in the contract. PO match looks at ordered amounts and tolerances, not every scheduled unit price.

What is four-way matching with the contract?

Teams use it to mean adding the contract or rate card as a fourth reference so commercial terms are tested in addition to PO and receipt checks.

Should we turn off three-way match?

No. Use both. Three-way match protects process. Contract validation protects price, scope, and entitlements.

Resources

Three-Way Match vs Contract Validation: Why PO Match Still Misses Overbilling

10 September 2026

Three-way match confirms PO, receipt, and invoice agree. It still misses rate card and contract drifts. Here is what each control catches.

Definition: Three-way matching compares purchase order, goods receipt, and invoice for consistency. Contract validation compares invoice lines to commercial terms in the signed agreement. Both matter. They are not the same control.

If the PO was cut at the wrong rate, three-way match can validate the error perfectly. That blind spot is the opening for contract-to-invoice checks.

Three-way match

PO, receipt, and invoice consistency
Quantity and amount tolerances
Strong on goods process control

Contract validation

Rate card and commercial schedules
Scope, credits, and amendments
Surfaces drift even when PO match is green

What three-way matching actually checks

Quantity and amount tolerances against the PO
Receipt confirmation when a GRN exists
Duplicate invoice numbers in many ERP setups
Supplier and currency consistency on the documents

Those checks protect process integrity inside P2P. They do not prove billing accuracy against negotiated terms trapped in a PDF.

What three-way matching does not check

Bill rates vs a contracted rate card
Out-of-scope lines that still fit under a lump-sum PO
Volume tiers or service credits that should change the amount due
Amendments signed after the PO was created
Title mapping that quietly upgrades a rate tier

Why services expose the gap

Many services have no goods receipt. POs are often not-to-exceed totals. Accessorials and change orders never enter the match. The invoice can be correct against the PO and still wrong against the contract.

Illustrative example, not client data: staffing PO for $250,000 NTE. Weekly invoices post under that PO. One role bills one tier high for six weeks. Document match stays green. Rate card validation fails.

Four-way match, carefully defined

Teams sometimes call “four-way match” the act of adding the contract as a fourth reference. Use the term when your audience already does. The job underneath is invoice validation against commercial terms, not a new Gartner category.

Side-by-side

Issue	3-way match	Contract validation
Wrong unit rate under NTE PO	Often passes	Surfaces vs rate card
Missing GRN on goods	Blocks or holds	Not the primary control
Missed volume tier or credit	Usually silent	Can surface when terms are structured
Duplicate invoice number	Often caught	Useful, not unique
Out-of-scope line inside PO total	Often passes	Surfaces vs scope schedule

What to do next

Keep three-way match
Retain it for goods and PO discipline.
Add contract validation
Prioritize services, facilities, and any category with rate cards or credits.
Set exception policy
Decide which findings block payment vs create a procurement review.
Prove with a sample
Run a historical category pass before redesigning the whole AP workflow.