Three-Way Matching Explained (With Real Examples)

Quick answer: Three-way matching compares three documents before an invoice is paid — the purchase order (what you agreed to buy), the goods receipt (what actually arrived), and the invoice (what the vendor billed). If all three agree within tolerance, payment proceeds; if not, the invoice stops. It is the strongest routine control in payables.

The three documents

1. Purchase order (PO) — quantity, price, and terms your organisation committed to
2. Goods receipt note (GRN) — what was actually delivered, counted at the dock or confirmed by the requester
3. Vendor invoice — what the vendor wants to be paid

A match confirms three separate assertions: we ordered it, we received it, and we’re being billed what we agreed. Any single missing leg creates a familiar failure mode — paying for undelivered goods, paying above contracted price, or paying for things nobody ordered.

A worked example

Your plant orders 500 bearings at ₹240 each (PO total ₹1,20,000). The store receives 480 — twenty arrive damaged and are rejected on the GRN. The vendor invoices for the full 500.

• Without matching: the invoice looks plausible, gets approved by someone who wasn’t at the dock, and you overpay ₹4,800. Multiply by every line of every invoice, every month.
• With matching: the quantity mismatch (480 received vs 500 billed) stops the invoice automatically. The resolver sees all three documents side by side and short-pays or requests a credit note in one action.

Why manual matching breaks at scale

Matching is arithmetic, which makes it sound easy — but at line level it’s brutal. A 40-line invoice against a 60-line blanket PO with three partial deliveries is a real puzzle, and AP teams face hundreds of these weekly. The predictable results:

• Matching happens at header level only, missing line-level overbilling
• Tolerances are applied generously to keep the queue moving
• Complex matches get rubber-stamped under month-end pressure

Ardent Partners’ research consistently finds manual invoice processing costs $12–15 per invoice, with matching the largest single component.

How AI makes matching touchless

Modern AP automation matches line by line across partial deliveries, unit-of-measure conversions, and price breaks:

• Fuzzy line pairing — “Bearing 6204ZZ” on the PO matches “BRG-6204-2Z” on the invoice
• Tolerance logic — percentage and absolute thresholds per category, applied consistently
• Partial-delivery accumulation — invoices match against cumulative receipts across multiple GRNs
• Exception routing — mismatches go to whoever can actually resolve them, with the evidence attached

Enterprises running AI matching report 80–85% of PO-backed invoices matching without any human touch — see the Procure to Pay module for how the upstream PO and GRN discipline is built.

Two-way vs three-way vs four-way

Match type	Documents	When to use
Two-way	PO + invoice	Services with no receivable goods
Three-way	PO + GRN + invoice	Standard for goods — the default
Four-way	+ inspection/quality record	Regulated or quality-critical materials

Key takeaways

• Three-way matching validates ordered vs received vs billed — before money moves.
• Manual matching degrades silently under volume; line-level rigor is the first casualty.
• AI matching sustains line-level rigor at scale and clears 80%+ of invoices untouched.
• Matching quality is downstream of PO and GRN discipline — fix the process, not just the tool.

Frequently asked questions

What tolerance should we set? Common starting points: ±2% or ₹500 (whichever is lower) on price, zero tolerance on quantity for goods. Tighten or relax per category with data after 90 days.

Can services be three-way matched? Yes, if you record service-entry sheets or milestone confirmations as the “receipt” leg. Otherwise use two-way matching with strong approval controls.

Does matching slow down payments? The opposite — matched invoices skip approval queues entirely, and cycle times typically halve.