What Is Three-Way Matching? Why It Fails for Service Invoices

Three-way matching compares POs, goods receipts, and invoices. It works for goods. For services — freight, maintenance, contract labor — it structurally cannot work. Here’s why.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
What Is Three-Way Matching? Why It Fails for Service Invoices
Three-way matching is the foundational accounts payable control used by every manufacturer. It compares three documents before approving payment: the purchase order (what was ordered), the goods received note (what was delivered), and the invoice (what the vendor is charging). If all three agree within tolerance, the payment is approved. If any disagree, an exception is generated.

How It Works

A manufacturer orders 500 units of raw material at $12 per unit. The PO documents: 500 units, $12/unit, $6,000 total. The warehouse receives the shipment and generates a GRN: 500 units received, condition acceptable. The vendor sends an invoice: 500 units, $12/unit, $6,000. The ERP compares all three. They match. Payment approved. If the invoice says 520 units: the 20-unit discrepancy is flagged against the GRN. If the price says $13: the $1 variance per unit is flagged against the PO. This control catches quantity errors, pricing errors, and unauthorized deliveries. Every ERP supports it.

Where It Fails

Three-way matching requires a goods received note. For services — freight deliveries, maintenance visits, staffing placements, IT support, consulting engagements — no physical receipt exists. There is no warehouse scan for a technician’s visit. No receiving dock for a freight delivery’s billing accuracy. No counting a consulting hour like counting a box of parts. Without the GRN, the ERP falls back on two-way matching: PO vs invoice. This validates that the vendor is recognized and the amount is approximately correct. It cannot validate whether the hourly rate matches the contract, whether the scope falls within the SOW, whether the surcharge was calculated correctly, or whether an SLA credit should offset the charge. This gap affects 30 to 60 percent of manufacturing operating costs — the entire service and indirect spend category. The control that protects goods procurement structurally cannot protect service procurement.

The Solution: Contract-to-Invoice Matching and the Virtual GRN

Contract-to-invoice matching adds the validation layer that three-way matching cannot provide for services. Instead of comparing invoices against a physical receipt, it compares them against the contract terms that define what the vendor should charge. The Virtual GRN reconstructs the missing receipt from three evidence layers: contract terms as structured data, operational evidence (work orders, delivery receipts, timesheets), and historical patterns. This digital service receipt enables the same validation rigor for services that three-way matching provides for goods. The result: complete coverage. Goods validated through three-way matching. Services validated through contract-to-invoice matching with Virtual GRN. No gap remaining.

Questions & Answers

What is three-way matching?

An AP control comparing three documents: purchase order (what was ordered), goods received note (what was delivered), and invoice (what is charged). If all agree within tolerance, payment is approved. Supported by every ERP.

Why does three-way matching fail for services?

No goods received note exists for services. Without the physical receipt, the ERP can only do two-way matching (PO vs invoice), which validates vendor and amount but not rates, terms, scope, or surcharges against the contract.

What is two-way matching?

Comparing only the PO and invoice, without a goods receipt. Used as fallback for services. Catches whether the vendor and general amount are recognized. Cannot validate contract-level terms.

What is a Virtual GRN?

A digital service receipt reconstructed from contract terms, work orders, and operational evidence. Replaces the missing physical receipt for services. Enables contract-level validation that three-way matching cannot provide.

What is contract compliance in the context of matching?

Going beyond transaction matching (PO/GRN/invoice) to validate that invoices honor contract terms — rates, NTE limits, SLA penalties, scope boundaries. The layer that three-way matching was never designed to provide for services.

Margin Drift Resources