Three-way match is the buyer-side accounts payable control that verifies a supplier invoice against the original purchase order and the goods receipt before approving payment, ensuring the goods or services were ordered, received, and billed consistently.
Three-way match is the standard internal control that corporate accounts payable teams use to authorise a supplier invoice for payment. The process compares three source documents and confirms they tell a consistent story before any money moves. If the three documents agree within tolerance, the invoice is approved and queued for payment. If they disagree, the invoice is held as an exception until the discrepancy is resolved.
The three documents are:
The match validates three things in sequence: the goods or services were ordered (PO exists), they were received (GR posted), and the supplier is billing for what was actually ordered and received (invoice agrees with PO and GR).
Matching happens at the line-item level, not the invoice header. AP systems compare each invoice line to its corresponding PO line and GR line across several criteria:
Most AP platforms allow tolerances so that small variances do not halt the workflow. A typical configuration permits price variance of 5-10% and quantity variance of similar magnitude. Invoices inside tolerance pass straight through to payment authorisation. Invoices outside tolerance route to an exception queue for human review, which is where delays start to accumulate.
Not every purchase warrants the full three-way control. Buyers calibrate match level based on risk and category:
The match level chosen by the buyer dictates what supporting documentation suppliers need to provide and how quickly invoices move through the AP cycle.
From the supplier's perspective, match failures are often invisible. The invoice was sent, the customer's AP system received it, and then nothing happens for weeks. The most frequent failure causes are:
Each of these failures parks an invoice in an exception queue. From the AR side, this shows up as inflated DSO and rising past-due balances that look like collection problems but are actually data-quality problems. When a collector calls, the customer's AP team often says the issue is with their system, when in reality the supplier's invoice triggered the exception.
Suppliers that consistently get paid on time treat three-way match as a problem to solve before the invoice goes out, not after it gets stuck. The defensive playbook includes:
Modern AP automation already does OCR-based extraction, auto-matching, and touchless approval for in-tolerance invoices. AI-native O2C platforms extend that intelligence to the supplier side of the transaction, where match failures originate.
An agentic O2C system can pre-validate every outgoing invoice against the customer's PO data and known receipt status before transmission, catching missing PO numbers, price drift, and entity mismatches at source. It tracks per-customer match success rates so AR teams know which buyers are most likely to reject invoices and why. Predictive models flag invoices that are likely to fail match based on historical patterns, and route those exceptions back to sales or operations to fix before the customer's AP ever sees them. The result is fewer disputes, faster payment, and a collections function that spends less time chasing problems that should never have left the building.
Two-way match compares only the Purchase Order and the supplier Invoice, and is typically used for services or low-value items where a goods receipt is not practical. Three-way match adds the Goods Receipt as a third document, confirming that the goods or services actually arrived before payment is authorised. Three-way match is the standard control for physical goods.
The most common reasons are a missing or invalid PO number on the invoice, a goods receipt that has not yet been posted by the buyer's receiving team, a quantity mismatch from a partial shipment, or a unit price on the invoice that differs from the PO outside the buyer's tolerance. Wrong vendor entity and wrong currency are also frequent causes.
Tolerances vary by buyer and category, but typical configurations allow 5-10% variance on unit price and a similar range on quantity. Invoices inside tolerance auto-approve and pay on schedule. Invoices outside tolerance route to an AP exception queue for manual review, which is where delays accumulate.
Every invoice held in a three-way match exception sits in the customer's AP system without ageing into a payable. From the supplier's AR view, the invoice is past due and DSO inflates. The root cause is rarely a credit or collections issue; it is a data-quality issue at billing. Resolving match failures upstream is one of the highest-leverage ways to reduce DSO.
Four-way matching adds a quality inspection or acceptance document to the standard three-way match. It is used in regulated industries such as pharmaceuticals, aerospace, defence, and food manufacturing, as well as on large capital expenditure projects where receipt alone is not sufficient proof that the goods meet specification.
The defensive playbook is to capture the PO number at order entry, validate its format before invoicing, confirm the correct legal entity and currency, send Proof of Delivery proactively to speed up goods receipt posting, and track invoice match status through the customer's AP portal. AI-native O2C platforms automate this pre-validation so failures are caught before the invoice is ever sent.
