Read summarized version with
What is Three-Way Matching?
Three-way matching is an accounts payable control. Before a vendor invoice gets paid, three documents have to agree: the purchase order (PO), the goods receipt (or receiving report), and the supplier invoice. The invoice clears for payment only once quantities, prices, and terms reconcile across all three.
Really, it answers three questions in order. Did we authorize this purchase? Did we actually receive the goods or services? Is the vendor billing us what we agreed to? Each document comes from a different party at a different point in the procure-to-pay cycle, so when they all line up, that’s strong evidence the payment is legitimate. It’s a foundational step in any well-run documented AP procedure, and it tends to show up as a requirement in finance controls and audits.
If something doesn’t line up, the invoice gets held as an exception and routed through a defined sign-off process for investigation instead of being paid automatically. Per Ardent Partners, the typical AP organization flags about 22% of invoices as exceptions; teams with documented three-way match tolerances and a defined exception path cut that rate to around 9%.
Key Characteristics of Three-Way Matching
- Three source documents: Purchase order, goods receipt, and invoice, each created independently.
- Tolerance thresholds: Small variances (often 1 - 5% or a fixed dollar amount) auto-clear; larger gaps become exceptions.
- Fraud and overpayment prevention: Catches duplicate invoices, inflated quantities, price padding, and billing for goods never received.
- Exception handling: Mismatched invoices are quarantined and escalated, not paid.
Three-Way Matching Examples
Example 1: Inventory purchase
Picture your warehouse manager cutting a PO for 100 units at $10. A few days later the receiving dock logs only 90 units off the truck, but the vendor’s invoice still bills you for all 100. This is exactly where the match earns its keep: the 10-unit gap between the PO, the receipt, and the invoice gets flagged, so your AP team pays for the 90 that actually showed up and disputes the rest instead of quietly handing over an extra $100.
Example 2: Duplicate invoice
Now imagine a supplier’s billing system hiccups and fires off the same invoice twice. The first one matched fine and got paid. The second one has nothing left to pair with, no open PO line, no unmatched receipt, so it never clears the match. The duplicate gets blocked before anyone in finance even notices, and you don’t end up chasing a refund for money that should never have left in the first place.
Three-Way Matching vs Two-Way Matching
Two-way matching compares only the PO and the invoice and skips the goods receipt. It’s faster, but it can’t confirm anything was actually received, so it’s mostly used for services or low-risk spend.
| Aspect | Three-Way Matching | Two-Way Matching |
|---|---|---|
| Documents | PO + receipt + invoice | PO + invoice |
| Confirms delivery | Yes | No |
| Best for | Physical goods, high-risk spend | Services, recurring low-risk spend |
How Glitter AI Helps with Three-Way Matching
Here’s the thing about three-way matching: it only protects you if your AP team runs the steps the same way every single time. And in most finance teams, the real rules, where the tolerance limits sit, which exceptions get escalated and to whom, live entirely in one experienced person’s head. When they’re out, or they leave, things slip. Glitter AI fixes that by letting you simply screen-record your matching process once. It turns that recording into a clean step-by-step guide automatically, so the procedure is written down and anyone can follow it exactly, not just the one person who’s always done it.
That’s why finance teams reach for Glitter AI to standardize their whole accounts payable workflow, from PO matching all the way through payment runs. It keeps their procedures audit-ready as part of a broader set of finance procedures and a documented procurement process covering purchasing. When an auditor asks how you handle exceptions, you have a real answer instead of a shrug.
Teach your co-workers or customers how to get stuff done – in seconds.
Frequently Asked Questions
What is three-way matching in accounts payable?
Three-way matching is an AP control that compares the purchase order, goods receipt, and supplier invoice, approving payment only when all three agree on quantity, price, and terms.
What are the three documents in a three-way match?
The purchase order (what you authorized), the goods receipt or receiving report (what you actually received), and the vendor invoice (what you're being billed).
Why is three-way matching important?
It prevents fraud, duplicate payments, and overpayment by confirming a purchase was authorized and goods were received before any money leaves the company.
What is the difference between two-way and three-way matching?
Two-way matching checks only the PO against the invoice, while three-way matching adds the goods receipt to confirm items were actually received.
What happens when a three-way match fails?
The invoice becomes an exception, is held from payment, and is routed through an approval workflow for investigation and resolution.
What is a matching tolerance?
A tolerance is a preset variance threshold (a percentage or dollar amount) within which small discrepancies auto-clear instead of being flagged as exceptions.
Can three-way matching be automated?
Yes. AP automation software matches POs, receipts, and invoices automatically and only escalates exceptions, replacing slow manual reconciliation.
When is two-way matching used instead of three-way?
Two-way matching is common for services and recurring low-risk spend where there is no physical goods receipt to verify.
How does three-way matching prevent fraud?
Because the three documents come from different sources, a fraudulent or inflated invoice rarely reconciles with an authorized PO and a verified receipt, exposing the discrepancy.
Who performs three-way matching?
The accounts payable team typically performs the match, following a documented procedure that defines tolerances, exception handling, and approval routing.