What Is the Difference Between Invoice Validation and 3-Way Matching?
3-way matching checks invoices against POs and receipts. Invoice validation checks against contract terms. Here is why the difference matters for services.
Direct Answer
Three-way matching compares an invoice against a purchase order and a goods receipt to confirm that the quantity ordered, the quantity received, and the quantity invoiced all agree. Invoice validation compares an invoice against the contract terms — rates, scope, service-level agreements, discount schedules, and accessorial rate cards — to confirm that the amount invoiced is contractually correct. Three-way matching confirms consistency across internal documents; invoice validation confirms compliance against the commercial agreement.
The distinction matters because 3-way matching works well for physical goods and fails structurally for services.
How 3-Way Matching Works
The 3-way match is the standard AP control in every major ERP (NetSuite, Dynamics 365, SAP, QuickBooks Enterprise, Acumatica, Epicor). The logic is simple:
-
Document 1: Purchase Order. Internal record of what was ordered — item, quantity, unit price
-
Document 2: Goods Receipt (or Item Receipt). Internal record of what was physically received at the warehouse or loading dock
-
Document 3: Vendor Invoice. External document from the vendor stating what they are billing for
If all three documents agree (within a configurable tolerance), the invoice is approved. If they disagree, the invoice is flagged for review.
This control is effective when all three conditions hold: (1) the purchase is for a discrete quantity of physical items, (2) the items are received at a specific location and logged in the ERP, and (3) the unit price on the PO matches the negotiated price.
Where 3-Way Matching Breaks Down
For services spend, one or more of those conditions typically fails:
No goods receipt for services. When a consultant works a week, when a maintenance technician performs a repair, when a freight carrier delivers a shipment — there is no physical “receipt” event in the ERP. Some companies create manual service receipts or work-order confirmations, but this is a custom process that most mid-market companies do not have. Without a goods receipt, the 3-way match degrades to a 2-way match (invoice vs. PO) — which only checks whether the total is within the PO amount.
POs carry totals, not rates. A purchase order for “consulting services, $50,000” does not contain the rate card (“senior consultant $178/hr, junior consultant $125/hr, project manager $195/hr”). When the vendor invoices 250 hours at $200/hr, the ERP checks whether $50,000 ≤ the PO value, not whether $200/hr matches the contract.
Scope is narrative, not numeric. Three-way matching works on numbers — quantities, amounts, unit prices. Service contracts define scope in paragraphs of text. A 3-way match cannot determine whether the “additional project management” line item on the invoice was within scope.
Accessorial charges are variable. Freight invoices include 10–30 possible accessorial charge types, each with its own rate and applicability conditions. None of these are in the PO. The 3-way match does not check them.
What Invoice Validation Adds
Invoice validation goes beyond the 3-way match to check the commercial agreement:
| Check | 3-Way Match | Invoice Validation |
|---|---|---|
| Quantity matches PO | Yes | Yes |
| Quantity matches goods receipt | Yes (physical goods) | Yes |
| Total within PO tolerance | Yes | Yes |
| Rate matches contracted rate card | No | Yes |
| Service hours confirmed as performed | No | Yes |
| Accessorial charges match contracted schedule | No | Yes |
| Scope within statement of work | No | Yes (structured scope terms) |
| Early payment discount applicable | Partial (payment terms only) | Yes (alerts on discount window) |
| Near-duplicate detection (fuzzy) | No (exact match only) | Yes |
The result: 3-way matching catches approximately 70–80% of goods-related invoice errors. It catches approximately 20–30% of services-related invoice errors, because the remaining errors are in the rate, scope, and accessorial dimensions that the 3-way match does not evaluate.
What This Means Practically
If your company processes a mix of goods and services invoices, your ERP’s 3-way matching is providing a false sense of control on the services side. The invoices are being “matched” and approved, but the match only confirms that the total is within the PO amount — not that the rates, scope, and terms are contractually correct.
The fix is to add a validation layer specifically for services spend: a system or process that compares invoice line items against contracted rates and terms before approval. This can be built internally (custom ERP development), performed manually (quarterly audit), or automated with a dedicated tool (FynFlo). (see Tipalti vs FynFlo)
FynFlo is a proprietary AI-native invoice validation product of ValueXPA.
Related Reading
Questions & Answers
Does this mean 3-way matching is useless?
No. 3-way matching is essential for goods-based purchases and catches quantity and total-amount discrepancies effectively. The gap is specifically on services, where the matching inputs (goods receipt, line-item rates) are absent.
Can I extend my ERP’s matching to cover services?
Partially. You can create custom service-receipt workflows and add rate-card lookup tables. This requires development effort (SuiteScript for NetSuite, Power Automate for Dynamics 365, SDK for SAP Business One) and ongoing maintenance as contracts change. Most companies that attempt this build the service-receipt piece but do not build rate-card validation.
How much does the gap cost?
For companies with $5M+ in annual services spend and no contract-term validation: typically 1–3% of services spend, or $50,000–$150,000 annually. A diagnostic quantifies the exact amount.