What is Three-Way Matching (3-Way Match)?
Three-way matching checks a supplier invoice against the purchase order and the goods receipt before payment, so you pay only for what you ordered and received.
Definition
Three-way matching is an accounts payable control that compares three documents, the purchase order, the goods or services receipt, and the supplier invoice, to confirm that a company is paying only for what it ordered and actually received, at the price it agreed. The quantities and amounts on all three must agree within a defined tolerance before the invoice is released for payment, which prevents overbilling, duplicate invoices, unauthorised price increases, and payment for goods that never arrived. A worked example makes the mechanics clear. Suppose a purchase order covers 100 units of a component at $12.50 each, a total of $1,250. The warehouse receives and records only 96 units, because four arrived damaged and were rejected. The supplier then invoices for 100 units at $12.75 each, a total of $1,275. The match produces two exceptions at once: a quantity variance of four units billed but never received, and a price variance of $0.25 per unit, which is 2 percent above the agreed purchase order price. If the configured tolerance is 1 percent on price and zero on quantity, the invoice fails the match and is blocked from payment. What the company actually owes is 96 units at $12.50, or $1,200, so paying the invoice as submitted would have overpaid the supplier by $75. Matching depth varies with risk. A two-way match compares only the invoice and the purchase order, so it confirms what was ordered and at what price but never confirms delivery, which makes it common for services, subscriptions, and low-value indirect spend. A three-way match adds the goods receipt and is the standard control for physical goods. A four-way match adds a fourth document, the inspection or quality acceptance record, and is used where incoming material must pass a quality check before it can be paid for, such as in regulated manufacturing, pharmaceuticals, and aerospace.
How Three-Way Matching Works in ERP
An ERP performs the match automatically by linking the supplier invoice to its purchase order and to the recorded goods receipt, then testing quantity and price against tolerances configured by company, vendor, or item. Invoices inside tolerance post and pay without human touch, while the rest become exceptions routed to a buyer, a receiver, or an AP approver. The mechanics differ meaningfully between systems. In SAP S/4HANA and ECC, the goods receipt debits inventory and credits the GR/IR clearing account, and invoice verification clears the other side of GR/IR, so a residual GR/IR balance is itself the signal that a receipt and an invoice have not yet paired up. That is why GR/IR reconciliation is a standard month-end task. Tolerance limits are configured per company code using tolerance keys, such as PP for price variance and DQ for quantity delivered variance, and a breach sets a payment block on the invoice. Blocked invoices are then worked through transaction MRBR, which lists them for release once the variance is resolved or accepted. In NetSuite, receiving against a purchase order creates an item receipt, and the vendor bill is generated from the purchase order so all three records stay linked. Bills that fall outside the configured variance surface as match exceptions and are held in the bill approval workflow until someone corrects or approves them. Dynamics 365 Finance and Operations makes the policy explicit: matching is set to not required, two-way, or three-way at the legal entity, vendor, or item level, and every vendor invoice line carries a matching status of passed, failed, or warning. Price and quantity tolerances are expressed as percentages, and failed lines can be configured either to warn or to block posting outright. Sage Intacct handles matching through the purchasing document workflow, converting a purchase order into a receiver and then into a vendor invoice, with tolerance limits on the transaction definition that warn or stop the conversion when a downstream document exceeds what was received or priced.
ERP Vendors with Strong Three-Way Matching
Oracle NetSuite
The original cloud ERP — built for fast-growing companies
SAP S/4HANA Public Cloud
Standardised cloud ERP with quarterly auto-upgrades and low TCO
Microsoft Dynamics 365
Modular ERP + CRM tightly integrated with Microsoft 365
Infor CloudSuite
Industry-specific cloud ERP suites on AWS
Frequently Asked Questions
What is the difference between two-way and three-way matching?
Two-way matching compares the supplier invoice to the purchase order, checking that the price and quantity billed match what was ordered. Three-way matching adds the goods receipt, confirming that the items were actually received before payment. Three-way matching is stronger because it prevents paying for goods that never arrived. Some organisations add inspection to make it a four-way match for quality-sensitive items.
What is a matching tolerance?
A matching tolerance is the allowable difference between the three documents that an ERP will accept without raising an exception. Tolerances are normally expressed as a percentage, an absolute amount, or both, and a common starting point is around 1 to 2 percent or $50 on price, whichever is lower, with a tighter tolerance on quantity. Set them too tight and AP drowns in exceptions caused by rounding and freight; set them too loose and genuine overbilling passes through unchallenged. Most finance teams review exception volumes each quarter and tune the thresholds until only a small share of invoices needs human review.
What happens when the documents do not match?
The ERP does not usually reject the invoice, it blocks it. The invoice is recorded but flagged with a payment block or an exception status, so it cannot be paid until the variance is cleared, and it appears on a blocked-invoice work list for the AP team to action. Resolution normally takes one of four forms: the receiver posts a missing or corrected goods receipt, the buyer amends the purchase order price, the supplier issues a credit note for the difference, or an authorised approver accepts the variance and releases the invoice. Every one of those steps is logged, which is what makes the control auditable after the fact.
Why do auditors care about three-way matching?
Three-way matching is one of the standard preventive controls auditors test in the purchase-to-pay cycle, because it stops payment for goods that were never received, a common route for both supplier overbilling and internal fraud. Auditors typically sample invoices to confirm the match actually ran, check who holds authority to release blocked invoices, and test whether one person can create a purchase order, post a goods receipt, and approve the invoice. That last point, segregation of duties, is what gives the control its strength; without it a single user can manufacture all three documents and the match proves nothing.
Can three-way matching be fully automated?
For most purchase-order-backed invoices, yes. Where suppliers send structured invoices by EDI or through a supplier portal, and the purchase order and goods receipt already exist in the ERP, the system can match, approve, and schedule payment with no human involvement, leaving the AP team to handle only exceptions. Full automation breaks down when invoices arrive as PDFs that need OCR, when invoice line descriptions do not map cleanly onto purchase order lines, or when the spend was never raised on a purchase order at all. Improving purchase order compliance usually lifts straight-through match rates more than any change to the matching engine itself.
When is a two-way match enough?
A two-way match is appropriate wherever there is no physical receipt to record: professional services, software subscriptions, utilities, rent, and most low-value indirect spend. In those cases approval of the service or the timesheet effectively replaces the goods receipt. Many organisations set the matching policy by category or by spend threshold, applying three-way matching to inventory and capital purchases above a defined value and two-way matching below it, so that control effort follows risk instead of being applied uniformly across every invoice.