What is Three-Way Matching? Definition, Process & Automation
Three-way matching compares a purchase order, goods receipt, and vendor invoice before approving payment. Learn how it works, why most invoices fail on first attempt, and how automation handles exceptions.
Ken
AI Finance Assistant
What is Three-Way Matching?
Three-way matching is an accounts payable control that compares three documents—a purchase order (PO), a goods receipt (GRN), and a vendor invoice—before approving payment. If all three agree on quantities, prices, and terms, the invoice is approved. If they don't, the invoice routes to an exception queue for human review.
The concept is simple. The execution is not. In practice, only 50-65% of invoices match cleanly on the first attempt. The rest—partial shipments, price adjustments, blanket POs, service invoices—require exception handling. That exception process is where AP teams actually spend their time.
How Three-Way Matching Works
The process reconciles data across three source documents:
Document 1: Purchase Order (PO)
The buyer creates a PO specifying what they're ordering: item descriptions, quantities, unit prices, and agreed terms. This is the "contract" with the vendor—what was promised and at what cost.
Document 2: Goods Receipt Note (GRN)
When goods arrive, the receiving team logs what was actually delivered: quantities received, condition, and delivery date. This confirms the vendor fulfilled their obligation. For services, a service completion report or timesheet serves the same function.
Document 3: Vendor Invoice
The supplier sends an invoice requesting payment for what they delivered. This states the quantities billed, unit prices charged, and total amount due.
The Match
AP compares all three:
| Check | What It Catches |
|---|---|
| PO vs Invoice | Overbilling, price increases above contracted rates |
| PO vs GRN | Short shipments, undelivered items still being billed |
| GRN vs Invoice | Charges for items not received, quantity padding |
When all three align within defined tolerance thresholds (typically ±2% on price, ±5% on quantity), the invoice auto-approves. When they don't, the invoice flags for review.
Three-Way Matching Example
A mid-market manufacturer orders 500 units of steel fasteners at $2.40 each:
PO: 500 units × $2.40 = $1,200 GRN: 480 units received (20 on backorder) Invoice: 500 units × $2.55 = $1,275
This invoice fails on two points. First, only 480 units were received, but 500 were billed—a quantity mismatch of 20 units ($51 overcharge). Second, the unit price jumped from $2.40 to $2.55—a 6.25% price variance above the PO rate.
Without three-way matching, this invoice gets paid as submitted. The company overpays $75 on a single order. Multiply that across thousands of invoices per year, and the losses compound to 2-5% of total AP spend.
Two-Way vs Three-Way Matching
| Aspect | Two-Way Matching | Three-Way Matching |
|---|---|---|
| Documents | PO + Invoice | PO + GRN + Invoice |
| Verifies delivery | No | Yes |
| Best for | Services, subscriptions, recurring charges | Physical goods, equipment, materials |
| Risk level | Higher (can pay for undelivered goods) | Lower (confirms receipt before payment) |
| Complexity | Lower | Higher (requires receiving process) |
Two-way matching skips the goods receipt check and compares only the PO against the invoice. It's appropriate for service invoices, software licenses, and recurring charges where there's no physical delivery to confirm. Three-way matching is essential when goods change hands—the GRN proves you actually received what you're paying for.
When Three-Way Matching Fails
The textbook process assumes clean data and straightforward transactions. Reality is messier:
- Partial shipments: Vendor delivers 3 of 5 line items. The GRN shows partial receipt, but the invoice bills the full order. The match fails, requiring manual split and rebill.
- Blanket POs: A single PO covers recurring orders over months. Multiple GRNs and invoices map to one PO, creating many-to-many matching complexity.
- Price adjustments: Raw material prices fluctuate. The contract allows index-based pricing, but the PO shows a fixed price. Every invoice triggers a price exception.
- No-PO invoices: An estimated 20-30% of invoices at mid-market companies arrive without a corresponding PO—they bypass three-way matching entirely and need separate controls.
- Unit of measure mismatches: PO specifies "cases," invoice bills by "unit." Same goods, different counting—automatic match fails.
These exceptions aren't edge cases. They represent 35-50% of invoice volume at most companies. The match process is only as good as the exception workflow that handles them.
How Automation Handles Three-Way Matching
Manual three-way matching—pulling up POs, cross-referencing receipts, checking prices in spreadsheets—takes 15-20 minutes per invoice. At 500 invoices per month, that's 125-165 hours of clerical work.
Automated matching systems change the math:
Auto-match rate: With properly configured tolerances and clean master data, automation achieves 85-92% straight-through matching. A mechanical engineering company processing 15,000 monthly invoices improved from 65% to 92% match rate by defining tolerances of ±2% price and ±5% quantity, reducing manual checks by 77%.
Exception routing: The 8-15% that don't auto-match get routed intelligently—price exceptions to procurement, quantity exceptions to receiving, missing POs to the requester. Instead of one AP clerk triaging everything, the right person sees the right problem.
Processing time: Average invoice verification drops from 3.2 days to under 1 day. Exceptions that took weeks to chase down resolve in hours because the system surfaces exactly what's mismatched and who needs to act.
The real value of automation isn't eliminating the match—it's eliminating the time spent on exceptions that never should have required manual intervention in the first place.
Key Takeaways
- Definition: Three-way matching compares a purchase order, goods receipt, and vendor invoice to verify accuracy before payment approval
- Purpose: Prevents overpayment, catches billing errors, and ensures you only pay for what was ordered and received
- Reality check: Only 50-65% of invoices match cleanly on first attempt—exception handling is where the real work lives
- Automation impact: Achieves 85-92% auto-match rates and reduces verification time from days to hours
Related Terms
- Invoice Processing - The full AP workflow from receipt to payment, where three-way matching is a critical validation step
- Accounts Payable Automation - Software that automates matching, approvals, and payment execution
- Invoice Approval Workflows - How to build approval chains that handle matched and exception invoices
- Procure-to-Pay Automation - End-to-end automation from purchase order through payment, including three-way matching
- Invoice Processing Automation - Complete guide to automating the invoice lifecycle
Related Topics
Ready to automate your invoices?
See how Ken can extract invoice data in seconds, right in Slack. No credit card required.