Your company probably has an AP policy that says "all PO-based invoices must be matched before payment." And your AP team probably skips it half the time because they're drowning in volume. Sound familiar?
Three-way matching is the most effective control in accounts payable for preventing overpayments, catching duplicates, and making sure you only pay for what was ordered and received. But when it's done manually, it creates bottlenecks. So teams cut corners, rely on spot checks, and end up with a leaky payables process where 1-3% of total spend goes to overpayments, pricing errors, and fraudulent invoices.
This guide covers how three-way matching actually works, why it matters specifically in the Indian regulatory context (hint: GST and ITC), how to implement it without creating bottlenecks, and how automation makes it practical at scale.
What Is 3-Way Matching?
Three-way matching is the process of comparing three documents before approving a vendor invoice for payment. The three documents are the purchase order (PO), which records what was ordered and at what price; the goods receipt note (GRN), which confirms what was actually received; and the vendor invoice, which is the supplier's claim for payment.
The matching process verifies that the quantities on the invoice do not exceed the quantities received (GRN), the unit prices on the invoice match the agreed prices on the PO, the total amount invoiced is arithmetically correct and consistent with the PO and GRN, and the tax calculations (GST components) are accurate based on the HSN/SAC codes and supply type.
Why Three Documents?
Each document comes from a different stakeholder. The PO is the buyer's intent and agreed commercial terms. The GRN is the warehouse team's confirmation that goods actually showed up. The invoice is the vendor's claim for money. When all three align, you've got strong assurance the payment is legitimate. When they don't? That's where you find vendor errors, receiving issues, pricing changes, and occasionally, fraud.
What Matching Gaps Actually Cost
Companies without systematic three-way matching tend to overpay vendors by 1-3% of addressable spend. For an Indian company spending INR 100 crore annually on procurement, that's INR 1-3 crore in avoidable overpayments per year. Even a matching process that catches 80% of discrepancies saves INR 80 lakhs to INR 2.4 crore annually. That's not theoretical -- it's money walking out the door.
The Matching Process in Detail
Understanding what gets matched and how tolerances work is essential for designing an effective matching workflow.
Quantity Matching
The system compares invoiced quantity against GRN quantity for each line item. In theory, they match perfectly. In practice? Discrepancies are frequent. Common scenarios: partial deliveries where the vendor invoices for the full PO but only some goods arrived, over-deliveries where the GRN shows more units than the PO authorised, and split deliveries where goods come in multiple shipments but the vendor sends one consolidated invoice.
Quantity matching rules should specify whether the invoice can exceed the GRN quantity (usually not permitted), whether partial invoicing against a GRN is allowed (usually yes), and how to handle tolerance for items measured by weight or volume where minor variations are normal (e.g., plus or minus 2% for bulk commodities).
Price Matching
The system compares the unit price on the invoice against the unit price on the PO. Price discrepancies are more nuanced than quantity issues because legitimate price changes can occur between PO issuance and invoicing. Common causes include agreed-upon price escalation clauses (common in long-term contracts), currency fluctuation adjustments for imported goods, additional charges not captured on the PO (freight, insurance, handling), and simple vendor errors.
Most organisations set a price tolerance threshold, typically 1-5% depending on commodity category. Within tolerance? Auto-approved. Outside? Routed for review. One thing that catches people out: you should configure different tolerance levels for different categories. Raw materials with volatile pricing might warrant 5%. Fixed-price service contracts? Zero tolerance.
Tax Matching
In the Indian context, tax matching is a critical third dimension. The system must verify that the GST rate applied on the invoice matches the rate applicable for the HSN/SAC code, the supply type (intra-state or inter-state) is correctly determined based on the place of supply rules under Sections 10-13 of the IGST Act, the CGST, SGST, and IGST amounts are arithmetically correct, and any cess or additional duties are correctly computed. Tax mismatches are particularly risky because paying an invoice with incorrect GST details can lead to input tax credit (ITC) disallowance during GST reconciliation. If the supplier files their GSTR-1 with different tax amounts than what appears on your invoice, the mismatch will surface in your GSTR-2B and may result in ITC reversal.
2-Way vs. 3-Way vs. 4-Way Matching
Three-way matching is the most common approach, but it is worth understanding the alternatives to choose the right level of control for different transaction types.
2-Way Matching (PO to Invoice)
Two-way matching compares only the PO and the invoice, without verifying the GRN. This is faster but riskier; you could end up paying for goods that were never received. Two-way matching is acceptable for low-value, low-risk transactions where the cost of a full three-way match exceeds the potential loss.
3-Way Matching (PO to GRN to Invoice)
The standard approach described in this guide. Suitable for the majority of procurement transactions where physical goods or quantifiable services are involved.
4-Way Matching (PO to GRN to Inspection to Invoice)
Four-way matching adds a quality inspection step between the GRN and invoice approval. The invoice is approved for payment only after the goods have been received (GRN) AND have passed quality inspection. This is appropriate for high-value materials, regulated industries (pharmaceuticals, food processing), or situations where quality issues are common and returns are costly.
We've seen Indian manufacturing companies use 4-way matching for their top 20% of suppliers by spend value (especially imported raw materials), 3-way matching for domestic vendors, and 2-way matching for service invoices under INR 50,000. The key insight: matching intensity should be proportional to risk. Don't apply the same level of scrutiny to a Rs. 15,000 service invoice as you do to a Rs. 50 lakh material purchase.
Common Discrepancies and How to Resolve Them
If you know the most common discrepancy types upfront, you can design resolution workflows instead of treating every mismatch as a one-off fire drill.
Quantity Over-Invoicing
The vendor invoices for more than what the GRN records. Resolution: reject the invoice line item to the extent of the excess and request a revised invoice. If the vendor claims they delivered the full quantity, initiate a physical verification at the receiving location. This is the most common discrepancy type, accounting for 35-40% of all matching exceptions.
Price Variance Beyond Tolerance
The invoiced unit price differs from the PO price by more than the configured tolerance. Resolution: route to the procurement team for verification. If a price change was agreed upon verbally but the PO was not updated, create a PO amendment and then re-match. Establish a policy that no price changes are valid without a formal PO amendment to prevent this recurring.
Missing GRN
The invoice has been received but no GRN has been created in the system. Resolution: notify the receiving department with a deadline for GRN creation. Common causes include goods received but the warehouse team has not logged them, services rendered but the service acceptance has not been formally recorded, and advance invoices issued before delivery. For service invoices, many organisations use a service acceptance form that serves the same purpose as a GRN for physical goods.
GST Mismatch
The tax rate or amount on the invoice doesn't match what it should be. Resolution: verify the HSN/SAC code classification and applicable rate, check the supply type (vendors frequently apply IGST instead of CGST+SGST or vice versa), and request a revised invoice if the error is theirs. Never approve a GST-mismatched invoice. Ever. It will create ITC reconciliation issues that are far more painful to fix later.
Automating 3-Way Matching
Manual three-way matching is a grind. For each invoice, someone pulls up the PO, finds the matching GRN, and compares fields line by line. At 10-15 minutes per invoice, a company processing 2,000 invoices per month burns 300-500 person-hours on matching alone. There's a better way.
How Automated Matching Works
The system maintains digital records of all POs and GRNs. When an invoice is captured, the matching engine automatically identifies the corresponding PO (using the PO number on the invoice) and GRN (using the PO number and delivery date), compares each line item across all three documents for quantity, price, and tax, applies tolerance rules to determine whether each line matches within acceptable limits, and classifies the invoice as either fully matched (ready for approval/payment) or exception (requires human review).
In a well-configured system, 60-80% of invoices match automatically on first pass. No human involved. The remaining exceptions get routed to the right handler based on discrepancy type, with enough context for quick resolution.
Tolerance Configuration Best Practices
Effective tolerance configuration is the key to a high auto-match rate without sacrificing control. Recommended starting points for Indian businesses include zero tolerance on quantity for discrete items (units, pieces, numbers), 2-3% tolerance on quantity for bulk items measured by weight or volume, 1-2% tolerance on unit price for standard procurement, zero tolerance on unit price for rate-contracted items, and zero tolerance on GST rate mismatches (no amount of variance is acceptable for tax compliance). Review your tolerance settings quarterly based on exception patterns. If a particular tolerance level generates too many false exceptions, consider relaxing it. If you discover overpayments slipping through, tighten the relevant threshold.
How OneFinOps Helps
Where OneFinOps stands out on matching is the GST integration. Most AP tools treat three-way matching as a purely commercial check -- quantities and prices. OneFinOps adds tax matching as a built-in dimension, using the HSN master and GST rate tables to automatically verify that every invoice has correct tax treatment before it's approved for payment. That means no ITC surprises during reconciliation.
The matching engine links invoices to POs and GRNs automatically, runs line-item comparison with configurable tolerance rules, and classifies results without manual intervention. For exceptions, each discrepancy type goes to the right resolver: price variances to procurement, quantity issues to the receiving team, GST mismatches to the AP team with specific details on what's wrong. The platform also tracks how long exceptions sit unresolved and escalates them before they age.
The bottom line: your matching process scales with invoice volume. No additional headcount required.
Getting Started with 3-Way Matching
If your organisation doesn't currently match systematically, don't try to roll it out everywhere at once. Pick one business unit or procurement category with a clean PO and GRN process. Implement matching there. Measure discrepancy rates and overpayment savings. Use those numbers to justify expanding.
If you already match manually, the path to automation is straightforward: document your current rules and tolerance thresholds, clean up PO and GRN master data, configure the automated engine with your existing rules, run parallel (manual and automated) for one month to validate, then switch to automated matching with exception-only manual review.
Three-way matching protects your company from overpayments, strengthens vendor accountability, and supports accurate GST reconciliation. For companies processing more than a few hundred invoices per month, automation is the only way to do it consistently without creating the bottlenecks that delay payments and frustrate vendors.