Three-Way Matching in Accounts Payable: A Practical PO, GRN and Invoice Guide for Indian MSMEs

Updated 7 November 2026. Practical guidance for Indian founders and small businesses.What three-way matching actually meansThree-way matching compares three records before a goods-related supplier invoice is approved: the purchase order, the goods receipt record and the invoice. The purchase order shows what was authorised, the receipt shows what arrived, and the invoice shows what the supplier is charging. Matching does not prove that every transaction is legitimate, but it can reveal quantity, price and duplicate-billing problems. For an Indian manufacturer or distributor, the process is especially useful when purchases arrive in parts or different teams order, receive and pay for goods.Why growing firms need itIn a founder-led company, the owner may approve a WhatsApp quote, the storekeeper may receive materials and the accountant may pay from an emailed invoice. Without a shared reference, the accountant cannot easily tell whether the invoice covers received stock. A mismatch can cause overpayment, supplier disputes or incorrect inventory values. The solution is not necessarily an ERP implementation. A numbered PO register, receiving log and invoice exception sheet can provide a basic control. Assign separate approval responsibility where staffing permits.The three records and their fieldsA purchase order should show PO number, supplier, item description or SKU, agreed unit, quantity, price, taxes where relevant, delivery terms and approver. A goods receipt note should show receipt date, PO reference, quantity accepted, rejected or pending, and the receiver. An invoice should show supplier identification, invoice number and date, relevant tax details, line quantities, rates and total. Match line items rather than only totals. Two invoices can have the same grand total while charging different products or quantities.Example with numbersA small factory orders 100 units at ₹800 each, before applicable tax. The purchase order value is ₹80,000. The receiving team accepts 92 units and records eight as pending. The supplier invoices all 100 units. A basic receipt-based comparison flags eight units, or ₹6,400 before tax, as not yet received. The correct next step depends on the contract and invoicing terms. It may involve holding the disputed portion, obtaining a corrected invoice or recording an approved exception. Do not automatically rewrite a supplier's tax invoice yourself.The matching formulaAt line level, quantity variance equals invoiced quantity minus accepted received quantity available for billing. Price variance equals invoice unit price minus approved PO unit price. For 92 accepted units invoiced at ₹820 against a PO price of ₹800, the price difference is ₹20 per unit and the extended difference is ₹1,840 before tax. Keep units consistent: boxes versus pieces, kilograms versus grams, and gross versus net weight are common sources of false mismatches. Record both the raw difference and the reason.Partial receipts and partial invoicesA purchase order may cover 500 units delivered across three weeks. Record cumulative accepted quantity, previously invoiced quantity and the remaining uninvoiced receipt balance. Suppose 200 units were accepted in week one and already invoiced. Another 150 arrive in week two. The next invoice for 150 should match the newly available receipt balance, not the original 500-unit order. If the second invoice repeats the first 200 units, the system should flag possible duplicate billing. This requires a running PO line ledger rather than a one-time comparison.Returns and quality rejectionsThe receiving team must distinguish physically delivered units from accepted units. If 50 units arrive but five fail inspection, an invoice for 50 should not automatically be approved as if all 50 were usable. Record rejected quantities, return authorisation and any agreed replacement or credit process. Some contracts allow payment despite pending quality tests, so document exceptions rather than applying an arbitrary universal rule. Attach inspection evidence to the receipt. Keep the supplier informed early to avoid an unexpected dispute near the payment due date.A spreadsheet layoutUse one sheet for PO lines, one for receipts, one for invoices and one for exceptions. The common keys are supplier ID, PO number and line number. PO fields include ordered quantity and agreed rate. Receipt fields include accepted quantity and date. Invoice fields include invoice number, billed quantity and rate. A lookup can bring the approved rate into the invoice sheet, while a summary calculates available receipt balance. Use data validation for units and supplier IDs. Protect formula cells and keep a change history.Tolerance rules need approvalSome firms allow small rounding differences or an agreed freight adjustment. Define a tolerance policy with the finance and procurement leads, not by copying an arbitrary percentage from the internet. For example, an internal rule might route any price variance above ₹500 or 1% for review. This is an illustrative management threshold, not a tax rule. Record the person approving the exception, why it was accepted and whether the PO should be amended. Never use tolerance to bypass a disputed delivery or unsupported tax amount.GST and accounting considerationsA commercial three-way match does not replace GST invoice validation or input-tax-credit checks. Confirm supplier details, tax treatment, applicable documentation and other statutory conditions with your accountant. A goods receipt note is operational evidence, not a substitute for a valid tax invoice. Avoid treating an invoice with a correct grand total as automatically tax-compliant. If the supplier issues a credit note, reconcile it to the original invoice and the accounting entries. Keep the tax review separate enough that staff can see which issues are commercial and which are statutory.When not to use a goods receipt matchRent, utilities, consulting services and software subscriptions may not have physical goods receipts. For those transactions, a two-way match or service acceptance record can be more suitable. Compare the contract or PO with the invoice and obtain confirmation that the service period or deliverable was accepted. Do not invent a GRN simply to satisfy a spreadsheet. Different categories need different controls. The goal is evidence of authorisation and delivery, not a rigid form count.A 30-day rolloutWeek one: select ten frequent suppliers and standardise PO numbers. Week two: require receivers to record accepted and rejected quantities. Week three: build the invoice match and exception log, then test it against twenty historical transactions. Week four: review false alerts, agree tolerances and train the payment approver. Start with one product category rather than the whole company. Track unmatched invoice count, average resolution days, duplicate invoices caught and supplier disputes. Use these measures to decide whether automation is justified.Cost-benefit exampleImagine 250 supplier invoices per month. A manual check takes four minutes per invoice, or roughly 16.7 staff hours. At an illustrative fully loaded cost of ₹350 per hour, the monthly checking effort is about ₹5,833. If the process prevents one ₹12,000 duplicate payment in a quarter, the average monthly avoided loss is ₹4,000, although actual outcomes will vary. The calculation does not prove positive ROI because setup, dispute handling and exception review also cost money. Use your own invoice volume and observed errors before investing.Common mistakes and FAQsDo not match only the invoice total. Do not ignore unit-of-measure conversion. Do not treat unreceived goods as received because the supplier says they shipped them. Do not allow the same person to change the PO and approve a large exception without review. Can small firms do this in Excel? Yes, with controlled access and periodic reconciliation. Should every invoice be held? Only according to an approved risk-based policy and contract terms. What about urgent purchases? Record the authorised exception and retrospectively attach evidence.Sources and first actionFor established approaches to invoice and receipt matching, consult Oracle documentation and your accounting platform's current user guide. Review the GST portal for tax-document guidance relevant to your business. Start with the last twenty invoices for one supplier. Count how many can be linked to an approved order and an accepted receipt without asking a colleague for missing evidence. That baseline shows where to fix the workflow first.Featured image credit: Alberto Rodríguez, Unsplash License. Image is illustrative, not a photograph of a named Indian business or event.