What is Three-Way Match? | xMatix Glossary

A three-way match is the control that compares three documents before a supplier invoice is approved for payment: the purchase order (what was ordered), the goods receipt (what actually arrived), and the invoice (what is being charged). Payment proceeds only where the three agree within tolerance.

Why the three-way match matters

It is the primary defence against paying for goods never received, paying twice for one delivery, and paying a price nobody agreed. These are not exotic risks — they arise routinely from ordinary error, and they are also the mechanics of most procurement fraud.

Its second value is quieter and often larger: it forces the receiving step to be recorded properly. A business that matches invoices to receipts has to know what arrived, which improves inventory accuracy as a side effect of a finance control.

How the match works

Each pair of documents is checked on quantity and price:

PO to receipt — did what arrived match what was ordered, in quantity and item? Partial deliveries are normal and must be handled without blocking.
Receipt to invoice — is the invoice charging for what was actually received, rather than what was ordered?
PO to invoice — is the unit price the agreed price?

Tolerances make it workable. An exact match on every line is unachievable at scale — rounding, freight, minor quantity variances on bulk goods — so most implementations allow a small variance, by percentage or absolute value, that passes automatically. Anything outside tolerance goes to a person.

Exception handling is where the real design effort goes, because the exceptions are the point of the control.

An example

A purchase order is raised for 100 units at 250 each, totalling 25,000. The supplier delivers 98, recorded on receipt. The invoice arrives for 100 units at 250. The match fails on quantity: the invoice claims two units that were never received, worth 500. Without the receipt in the comparison, the invoice reconciles perfectly against the purchase order and is paid in full.

Common variations

Two-way match. PO against invoice only, used for services and other non-stock purchases where there is nothing physical to receive.
Four-way match. Adds an inspection or quality-acceptance document, used where goods must pass a check before they count as received.
Evaluated receipt settlement. The invoice is dispensed with — payment is generated from the receipt against agreed prices, which removes the mismatch by removing a document.

Limitations worth stating

The match verifies documents against each other, not against reality. If receipts are recorded from the delivery note rather than from what was physically counted, the control validates one supplier claim against another. Tolerances set too loosely permit systematic small overcharges to pass indefinitely; set too tightly they generate an exception queue nobody can clear, and the usual outcome is that exceptions get approved in bulk — which is the control failing while appearing to operate.

How xMatix supports the three-way match

xMatix Procurement runs requisition-to-bill with the three-way match built into the path rather than added as a report: approvals on the requisition and order, quality-gated receipts, and the match against the supplier bill before payment. Because receipts post to the same append-only inventory ledger used everywhere else, the quantity the match relies on is the quantity that moved stock — there is no separate receiving record to reconcile.

Approval routing and tolerance behaviour are configured through the platform's business rules and approval engine, so thresholds and escalation paths are policy rather than code. Matched bills post through to Finance & Accounting on the same model, so the payable, the ledger entry and the stock movement all originate from one chain of documents.