Three-way matching keeps invoice approval from becoming a payment guessing game.
Three-way matching process means comparing the purchase order, supplier invoice, and goods receipt before accounts payable releases payment. It is a finance control for confirming that the business ordered the goods, received them, and was billed at the agreed quantity and price.
Quick answer
A three-way matching process checks three records: the purchase order, the invoice, and the receiving record. If quantities, prices, supplier details, and terms agree within policy tolerance, the invoice can move to payment. If they do not match, the invoice becomes an exception that needs procurement, receiving, vendor, or finance review.
Why three-way matching matters
Accounts payable is often judged by how quickly invoices get paid. Speed matters, but speed without control creates duplicate payments, overpayments, unresolved receiving issues, and weak audit evidence. Three-way matching gives AP a simple operating test before cash leaves the business: did the invoice match what was approved and what arrived?
The control is especially useful for physical goods, inventory, equipment, supplies, project materials, and high-value vendor purchases. Services and subscriptions may use different evidence, but PO-backed goods benefit from a documented match.
The IRS guidance on business recordkeeping says records should support purchases, expenses, and entries in the books. Three-way matching does not replace accounting records, but it connects approval evidence, delivery evidence, invoice detail, and payment readiness in one review path.
How the three-way matching process works
The workflow starts before the invoice arrives. A buyer creates a purchase order that states the supplier, items, quantities, price, delivery terms, and approval. When the goods arrive, the receiving team records what was actually delivered and flags shortages, damage, substitutions, or partial shipments. When the supplier invoice arrives, AP compares the invoice against both records.
At minimum, the match should compare vendor identity, PO number, item description, quantity ordered, quantity received, unit price, tax or freight treatment, payment terms, and invoice total. Strong teams match at the line level instead of only comparing totals. Two offsetting errors can make a total look right while individual lines are wrong.
| Document | What it proves | Owner |
|---|---|---|
| Purchase order | The business approved the purchase, price, quantity, supplier, and terms. | Requester, procurement, or budget owner |
| Goods receipt | The goods or materials were received in the expected quantity and condition. | Receiving, warehouse, operations, or project owner |
| Supplier invoice | The vendor is requesting payment for specific goods, prices, taxes, and terms. | Supplier and accounts payable |
Three-way vs two-way vs four-way matching
Two-way matching compares the purchase order and invoice. It confirms that the vendor billed what was ordered, but it does not prove the goods arrived. That may be acceptable for certain services, recurring subscriptions, or low-risk purchases where receipt evidence is handled differently.
Three-way matching adds the receiving record. It is the standard control when payment should depend on delivery. Four-way matching adds another inspection or quality record, which is useful in regulated, manufacturing, construction, healthcare, or quality-sensitive environments where arrival alone is not enough.
| Match type | Documents compared | Best fit |
|---|---|---|
| Two-way | Purchase order and invoice | Services, subscriptions, low-risk vendor invoices |
| Three-way | Purchase order, invoice, and goods receipt | Goods, inventory, supplies, equipment, and materials |
| Four-way | Purchase order, invoice, goods receipt, and inspection | Quality-controlled or regulated purchases |
A practical matching workflow
- Create the purchase order before commitment. The PO should define supplier, item, quantity, price, terms, delivery location, budget owner, and approval.
- Record receipt when goods arrive. Receiving should capture quantity, condition, substitutions, backorders, and the person who accepted the delivery.
- Capture invoice data consistently. AP should extract vendor, PO number, invoice number, invoice date, lines, quantities, unit prices, taxes, freight, and payment terms.
- Match at the line level. Compare invoice lines against the PO and goods receipt, not just the total.
- Apply tolerance rules. Small price, freight, or quantity differences may pass if policy allows. Larger differences should stop payment.
- Route exceptions by cause. Price issues go to procurement. Quantity issues go to receiving or operations. Tax, duplicate, or vendor master issues go to AP or finance.
- Store the audit trail. Keep the documents, match result, exception reason, approver, resolution, and payment reference together.
Set tolerance rules before exceptions pile up
A matching policy should not turn every tiny variance into a manual investigation. Finance should define tolerances by amount, percentage, vendor, category, tax treatment, and risk. Microsoft’s documentation on three-way matching policies shows how invoice matching can use price totals, quantity matching, charges matching, and policy controls to decide when review is required.
A practical policy might auto-clear a low-value invoice with a small freight variance, but block a quantity mismatch, a changed bank account, a new vendor, a duplicate invoice number, or a price increase above the approved tolerance. The point is not to remove judgment. It is to reserve judgment for the exceptions that matter.
Common mistakes to avoid
- Matching only at the header total. Line-level errors can hide inside a correct-looking total.
- Letting invoices arrive without PO numbers. AP spends too much time finding the buyer, order, and receipt evidence.
- Using one tolerance for every vendor. High-risk categories need tighter controls than routine supplies.
- Routing every exception to finance. Procurement, receiving, legal, and operations often own the real answer.
- Paying before receipt is confirmed. This weakens leverage when goods are missing, damaged, or substituted.
- Keeping evidence in separate systems. A match is only audit-ready when the documents and decisions stay connected.
Where Workhint fits
Workhint helps teams turn matching policy into a live finance workflow. A business can structure purchase requests, vendor records, receiving tasks, invoice intake, approvals, exception ownership, payment readiness, and reporting in one connected path.
That is useful when three-way matching crosses departments: procurement owns the PO, operations confirms receipt, AP reviews the invoice, finance sets controls, and the vendor expects payment. Workhint is not the payment rail or accounting ledger. It coordinates the workflow around them, so the right person sees the right exception with the right evidence. Teams designing this control can connect it to broader workflow automation software for approvals, routing, and audit-ready operations.
FAQ
What is a three-way matching process?
It is the accounts payable process of comparing a purchase order, supplier invoice, and goods receipt before approving payment. The goal is to confirm that the business ordered, received, and was correctly billed for the purchase.
What documents are needed for three-way matching?
The core documents are the purchase order, the supplier invoice, and the goods receipt or receiving report. Supporting evidence may include contracts, delivery notes, packing slips, approvals, tax documents, or exception notes.
Is three-way matching required for every invoice?
No. It is most useful for PO-backed goods, inventory, equipment, supplies, and materials. Some service invoices, subscriptions, and low-risk purchases may use two-way matching or a different approval model.
What happens when the documents do not match?
The invoice should be held as an exception and routed to the owner who can resolve it. Common actions include correcting the invoice, updating the receipt, approving a variance, requesting a credit, or rejecting the charge.
Can three-way matching be automated?
Yes. Automation can capture invoice data, compare it to purchase orders and receiving records, apply tolerance rules, route exceptions, and preserve the audit trail. Human review is still needed for material exceptions and policy overrides.
Conclusion
The three-way matching process is a simple control with real operational value. It gives finance a documented way to confirm that a vendor invoice matches what was ordered and received before payment leaves the business. The best version is not a slow manual checklist. It is a structured workflow with clear owners, line-level matching, sensible tolerances, exception routing, and evidence that stays connected from purchase request to payment.
Leave a Reply