Procure to pay
Three-Way Matching Explained: PO, Receipt, and Invoice Controls
Understand how three-way matching works, which fields to compare, how tolerances should be governed, and why exceptions still require human review.
Key takeaways
- Match identity, quantity, price, currency, tax, and terms—not only totals.
- Define tolerances by risk and document who can approve exceptions.
- Service invoices need evidence that differs from goods receipts.
- Keep unmatched items visible until they are resolved or formally accepted.
01
What the three documents prove
A purchase order shows what the organization authorized. A goods receipt or service confirmation shows what it says it received. The supplier invoice shows what the supplier wants to be paid. Three-way matching connects those claims before payment.
The control is strongest when each document is created by an appropriate role and linked by stable identifiers. If the same person can raise the order, confirm receipt, and approve the invoice, a technical match does not provide meaningful independence.
02
Fields that should be compared
Matching only the grand total can hide quantity and price errors that offset one another. Compare at the most useful level available, usually the line level for ordered goods and the milestone or deliverable level for services.
- Supplier and purchasing entity.
- Purchase-order number and line reference.
- Item or service description.
- Ordered, received, and invoiced quantity.
- Unit price, discounts, freight, tax, and currency.
- Payment terms and invoice date.
03
Set tolerances deliberately
Not every difference should stop a payment. Rounding, measured quantities, freight, and price-index changes can create legitimate variance. But an undocumented tolerance is simply an uncontrolled override.
Define tolerances by category, value, and risk. A small consumable may allow a narrow percentage variance, while professional services or capital purchases may require exact approval. Report both the absolute and percentage difference so large-value exceptions are not hidden by a percentage rule.
04
Handle common exceptions consistently
Partial deliveries, back orders, consolidated invoices, substitutions, and service milestones require context. Create named exception reasons and evidence requirements instead of relying on free-text approval. A consistent taxonomy also reveals which suppliers or internal processes create the most rework.
- 1
Identify
Show the precise fields and documents that do not agree.
- 2
Route
Send the exception to the buyer, receiver, budget owner, or vendor specialist who can resolve it.
- 3
Evidence
Attach the receipt, amendment, approval, or correspondence that supports the decision.
- 4
Resolve
Correct the source, obtain a credit, or approve a documented exception before payment release.
05
Use spreadsheet review as an independent layer
Even when an ERP performs matching, exported data can reveal missing receipt references, unusual overrides, repeated invoice numbers, or values outside the expected range. A browser-local review is useful when teams need to examine an export without creating another copy in cloud storage.
Treat the result as an exception queue. The final decision still belongs to the authorized process owner, supported by the source documents and the organization's policy.
This article provides general operational guidance, not accounting, audit, tax, or legal advice. Apply your organization's policies and professional judgment.