Three-way match

Accounts payable uses three-way match to confirm you are paying for goods or services you ordered and actually received. The three documents are the purchase order (what you agreed to buy and at what price), the goods receipt or service entry (what arrived or was accepted), and the supplier invoice (what the vendor is billing). Each line on the invoice should trace to a PO line with quantities and prices that still hold after receipt.

Finance teams treat three-way match as the default control for indirect and direct materials spend because it catches billing before cash leaves the bank. A clean match means quantity received is at least the quantity invoiced (or within your partial-receipt rules), unit price matches the PO or an approved contract rate, and the supplier and remit-to details align with master data. When any leg is missing or out of tolerance, the invoice routes to an exception queue instead of payment.

Real programs rarely demand perfect equality on every field. Organizations publish tolerance bands: for example, unit price variance up to 1% or $50, quantity overbill up to zero, and tax rounding within a few cents. Receipt timing matters too—an invoice may arrive before the warehouse posts the GRN, so AP either waits for receipt or uses a two-way match interim rule with a later true-up.

Common exceptions include freight added on the invoice but not on the PO, price changes after PO issuance without a change order, consolidated invoices spanning multiple POs, and credit memos that reference original invoices. Each exception type should have a named resolver (buyer, receiver, or contract owner) so invoices do not sit in a generic queue.

Suppose PO-1042 orders five storage blocks at $9,200 each. The warehouse receives all five and posts GRN-5502. The supplier invoices five units at $9,480 each, citing a list-price adjustment. Total invoice is $47,400 versus an expected $46,000 on the PO—a $1,400 gap.

A three-way match engine compares line by line. Quantity matches (5 invoiced, 5 received, 5 ordered). Unit price fails if tolerance is 1% ($92 max on $9,200). AP holds the invoice, attaches the PO and receipt lines, and routes to the buyer to either accept the overrun with a change order or request a credit note for $1,400.

Two-way match compares only PO and invoice. It is faster and suits low-risk categories, subscription services with no formal receipt, or environments where receipt data is unreliable. Three-way match adds the receipt leg and is standard for physical goods and stocked items.

Mature procure-to-pay teams use a policy matrix: category, amount, and supplier risk determine which match type runs automatically and which requires human approval. The goal is not maximum matching on every invoice—it is consistent risk-based controls with an audit trail.

Document your tolerance matrix by category and currency, including whether tax and freight are in or out of price checks. Train AP to distinguish receipt-not-posted from true price variance so buyers are not pinged for warehouse delays.

Run monthly match-fail reports by supplier to spot repeat billing patterns before renewals. During ERP cutover, reconcile a sample of paid invoices with three documents to validate match configuration.

Review metrics quarterly with procurement, finance, and business owners who feel process pain—adjust rules when data shows a control is cosmetic or a bottleneck is upstream.

Internal audit samples three-way match by tracing transactions from requisition or contract through payment, looking for missing evidence and override patterns. Findings are usually systemic—stale catalogs, receivers not trained, or tolerances set too wide—rather than one rogue approver. Remediation plans should name a process owner outside AP when the root cause is upstream.

Leading indicators for three-way match include open exceptions, unposted receipts, contracts past notice windows, and classification backlog; lagging indicators include paid-after-due volume, duplicate hits, and price variance dollars. Review the same dashboard weekly with procurement during a transformation, not only at quarter close, so fixes land before suppliers escalate.

Pilot changes to three-way match on one company code or region with documented before-and-after samples on the same supplier mix. Parallel-run old and new rules until match or classification variances fall below an agreed threshold, then cut over with a rollback plan. Executive sponsors should see cycle time and touch-per-document, not only license go-live dates.

Technology helps three-way match only when master data, contracts, and receiving discipline keep pace. Budget for content stewardship—catalog updates, clause playbooks, screening lists—alongside software. Tie savings claims to redirected spend, captured discounts, and avoided overbill with line-level examples auditors can reproduce.

Stakeholder alignment matters: publish a one-page RACI for three-way match that names who sets policy, who operates the process, and who approves exceptions. Exception approvals should expire automatically after 90 days unless renewed with business justification, preventing "temporary" tolerances from becoming permanent holes in control.

Training should use live examples from your ERP, not generic slides—walk receivers and buyers through one held document and show which fields they can change to clear three-way match issues. Reinforce that fixing upstream data beats overriding match or approval rules downstream, because overrides rarely scale across thousands of transactions per month.