Three-way matching explained: what it is and whether you actually need it

Quick summary

Three-way matching compares a purchase order (PO), receiving report or goods receipt, and supplier invoice before payment approval. The PO records what was ordered; the receipt records what arrived; the invoice records what is billed. A partial delivery may justify paying for the received portion while leaving the rest of the PO open, subject to the contract and approval policy.

Matching needs reliable receipt records. It does not establish that goods passed inspection, detect every duplicate invoice, or authorize payment by itself.

What gets matched

The purchase order records the authorized items, quantity, and price. The goods receipt identifies the PO lines and quantities delivered. The invoice states what the supplier wants paid. Compare the records at line level so that a correct order total does not hide a discrepancy in one item.

Microsoft’s invoice-matching documentation describes a price comparison against the PO and a quantity comparison against selected product receipts. Its exact wording is: “the quantity on the invoice matches the quantity on the corresponding product receipts.”

Tolerances are policy settings, not a universal percentage. Document the permitted price and quantity differences, the treatment of charges and discounts, and who can approve an exception. Microsoft allows configurable tolerances; its examples do not establish a recommended threshold for every company. A successful document match and authorization to release payment are separate decisions.

What it actually catches

The following are types of discrepancy to investigate, not a ranking by frequency. This page does not provide a verified industry-wide first-month match rate.

Quantity billed exceeds quantity received. A vendor ships 80 units against a PO for 100, but bills for 100 anyway. A PO-to-invoice comparison alone cannot establish that all 100 units arrived. Investigate whether another receipt is missing, the delivery is incomplete, or the invoice needs correction; the mismatch does not prove fraud.

Unauthorized price changes. The invoice price is higher than the PO price, sometimes because of a supplier price increase that was never communicated, sometimes because the wrong price list was used internally.

Duplicate invoices. The same invoice, or a near-duplicate with a slightly different invoice number, gets submitted twice. This is a separate problem from matching, and a separate duplicate-detection check can flag a suspected repeat for review.

Invoices for goods that were never received. A missing receiving confirmation can leave AP unable to distinguish an unrecorded delivery from goods that never arrived.

Where the friction comes from

Three-way matching only works if receiving is a real, tracked process. Someone has to log what arrived, in what quantity, against which PO, at the time it arrives. If your receiving process today is “the invoice shows up and someone pays it,” you don’t have the input data three-way matching needs, and turning it on will mean building a receiving workflow from scratch.

The workflow needs a named owner for each exception. Receiving should investigate missing delivery records, the buyer should verify an authorized price change, and AP should check invoice and payment history. Keep the original record and the reason for any correction.

For services, define what the receipt confirms. There is no physical shipment to count. Some companies substitute a project milestone sign-off or a manager’s confirmation that the work was completed as scoped. Record who accepted the deliverable and what evidence supports that acceptance.

When to use two-way matching instead

Two-way matching compares the PO to the invoice without requiring a receipt as the third document. Whether that gap is acceptable depends on the purchase and other controls, not a universal annual-spend cutoff.

It can flag prices that differ from the PO. A separate policy must establish how invoices without a PO are handled. What it misses is quantity discrepancies: if the invoice says 100 units at the agreed price and the PO says 100 units at the agreed price, it matches, whether or not 100 units actually showed up.

Evaluate the risk of paying for an incomplete delivery alongside the cost of recording receipts. Familiar suppliers still make errors. Where short shipments would cause a material loss, a receipt check provides evidence that the PO and invoice cannot supply.

Partial receipts: which amount can proceed?

These figures are an illustrative calculation, not a product test or survey. A PO authorizes 100 units at $10 each. The first delivery contains 60 units and 40 are outstanding. Assume no tax, freight, discount, or approved variance.

Document or calculation	Quantity	Unit price	Amount
Purchase order	100	$10	$1,000
First goods receipt	60	$10 assumed from PO	$600 value at PO price
Invoice A: delivered portion	60	$10	$600
Invoice B: entire order	100	$10	$1,000
Invoice B above this receipt	40	$10	$400

Invoice A agrees with the first receipt and unit price. It can proceed through the remaining company controls; the PO still has 40 units outstanding. Invoice B bills 40 units beyond this receipt. Check for an unrecorded delivery or ask the supplier to correct the invoice. Do not create a fictitious receipt to make it pass.

When the remaining 40 units arrive, review previous invoices before approving another bill. The $600 already billed belongs in that history. Also check units of measure: a case of 12 items and 12 individual items are not interchangeable quantities.

An r/Accounting discussion reports delays when procurement leaves discrepancies for accounting to resolve. One commenter describes procurement owning POs, receiving recording deliveries, and AP comparing invoices. These are individual workplace reports, not a measured failure rate.

Maintain an exception register with invoice number, PO line, disputed quantity or price, supporting evidence, responsible person, and due date. The invoice approval workflow guide addresses approval routing; duplicate-payment detection is a separate control from matching.

Software that supports it

Verify the required workflow in current product and plan documentation. A PO feature alone does not demonstrate receipt matching or inspection approval. ERP integrations may determine which system owns each record.

Ask a vendor to demonstrate the 100-unit PO and 60-unit delivery above, then add a second receipt and an earlier invoice. Check line-level differences, exception ownership, and the audit trail for overrides. These are evaluation questions, not claims that CashFlowPick tested the products. The purchase order software guide covers the PO side; confirm receiving and matching capabilities separately.

Frequently asked questions

What documents are needed for a 3-way match?

A purchase order, goods receipt or receiving report, and invoice. Compare the relevant lines and delivery records. A PO total alone does not identify which delivery an invoice covers. See Microsoft’s matching overview.

Is goods receipt matching the same as checking quality?

A goods receipt records receipt; it does not necessarily prove inspection acceptance. Oracle’s match-approval documentation distinguishes received quantities from accepted quantities. Decide whether the payment control needs both.

What is 2 3 4 way matching?

Two-way uses the PO and invoice. Three-way adds the receipt. Four-way adds accepted quantities from inspection. These are the levels in Oracle’s documentation; configuration determines exact checks and tolerances. A supplier’s packing slip is not inspection acceptance.

Does a clean match automatically approve payment?

That depends on the configured workflow. Document matching and payment-release authority are separate controls. Microsoft’s overview describes review and approval of discrepancies. Name the authorized exception approver and preserve the justification. Do not change the records simply to remove a warning.