What GRN and invoice mismatches look like on a plant floor
A GRN and invoice mismatch occurs when the quantity, price or line reference on a supplier invoice does not agree with the goods receipt note posted against the purchase order, which blocks the invoice from passing a three-way match.
Matching is where most AP time goes when it goes wrong. Ardent Partners research reports an average invoice exception rate of 14%, and an average cost of $9.40 to process a single invoice.[1] In a plant that receives hundreds of deliveries a week, even a small share of stuck invoices becomes a standing queue.
Picture a Tuesday delivery of 40 pallets of steel coil at a stamping plant. The receiving clerk checks the packing slip, signs the carrier's paperwork and moves on to the next truck. The receipt is keyed on Friday, against the blanket PO line from last month, in kilograms instead of metric tons. The supplier's invoice arrived Wednesday. By the time anyone looks, AP has held a correct invoice for a week and the supplier's credit team is calling.
AP Manager / Controller
Holds a growing queue of invoices that are probably right but cannot be proven right without a receipt.
"I can't pay what the system says we never received."Receiving Supervisor
Runs the dock with too few people and treats system posting as paperwork for later.
"The truck matters now. The screen can wait."Buyer / Purchasing
Spends mornings answering supplier calls about payments instead of managing supply.
"They shipped on time. Why am I apologizing?"CFO / Finance Leader
Sees accruals and received-not-invoiced balances swing at month-end with no clean explanation.
"Why do our GRNI numbers never reconcile?"Are receipt mismatches holding your supplier payments?
Tick every statement that is true today. Three or more means the problem is likely costing you real money.
Six root causes of goods receipt and invoice mismatches
Chasing each held invoice clears today's queue and refills next week's. These are the underlying causes we see most in plants and multi-site manufacturers.
Receipting is treated as back-office work
Receiving teams are measured on unloading trucks and keeping lines fed, not on posting receipts. Posting waits until the end of the shift or the week.
Partial and split deliveries are hard to record
A PO for 1,000 castings arrives in three loads. Clerks post one receipt for the lot, or skip the partials, and the invoices for each load no longer line up.
Units of measure differ across documents
The PO says rolls, the packing slip says meters and the invoice says square meters. Without conversion factors on the item master, a correct invoice fails the match.
Blanket and scheduling agreements are loosely referenced
Releases against a blanket PO get received against the wrong line or release, so quantities look over on one line and short on another.
Tolerances are one size for everything
The same zero or tiny tolerance applies to bulk resin sold by weight and to machined parts sold by the piece, so normal weight variance creates holds.
Nobody owns the hold
AP sees the exception but cannot fix a receipt. Receiving can fix it but never sees the queue. The invoice waits between the two.
What receipt mismatches cost a manufacturer
Published AP benchmarks show how quickly exceptions add time and cost to every invoice.
The direct cost is AP and receiving time spent investigating, correcting and re-matching held invoices, plus late fees and lost early payment discounts. The indirect costs weigh more in manufacturing: suppliers that get paid late move you down their allocation list when capacity is tight, raise prices or tighten credit terms, and your month-end accruals stay unreliable because received-not-invoiced balances cannot be trusted. Average invoice processing time already sits at 8.2 days across the industry, and every stuck receipt pushes a payment further past terms.[2]
Estimate the cost of receipt-related holds
Enter your figures. Nothing is stored or sent anywhere.
The expert playbook: six practices that clear receipt holds for good
These practices work with any ERP or even a spreadsheet. Start with data on why invoices hold, then fix the dock, then tune the matching rules.
"Years of working on procure-to-pay, including the Ariba Network at SAP, taught me that many held invoices are not wrong. They are early. The supplier moved faster than the buyer's own receiving process. Post the receipt when the truck is unloaded and most three-way match exceptions never happen, so AP can focus on the few that matter."Md. Kafil, Co-founder and CEO, Zapro. Former senior product specialist on SAP Ariba Network and procurement transformation manager at KPMG.
Classify every hold by cause for a month
Make same-shift receipting the dock standard
Record partial deliveries as they arrive
Fix units of measure on the item master
Set tolerances by category and supplier
Give each hold an owner and an age limit
"At Voonik we had 5,000 to 6,000 suppliers emailing invoices into one inbox and calling to ask where their money was. We moved payments from 30 days to 1 to 2 days, and the lesson was that the delay is almost never the payment run. It is one missing record upstream that nobody feels responsible for."Daniel Sagayaraj, Co-founder and CTO, Zapro. Previously built and ran supplier onboarding and payments for a 15,000-supplier marketplace at Voonik.
How Zapro keeps receipts and invoices in step
Zapro links the purchase order, the goods receipt and the supplier invoice in one record, so a hold shows who needs to act and what is missing instead of sitting in an AP queue.
| Root cause | Zapro capability | What changes |
|---|---|---|
| Nobody owns the hold | AP Automation: dispute and exception handling | Each exception is routed to the person who can fix it, with the PO, receipt and invoice side by side. |
| Correct invoices fail a rigid match | Two-way and three-way matching with Z1 | Z1 matches invoices to POs and receipts and flags risk, so AP reviews real differences instead of every line. |
| Receipts and stock data out of step | Inventory Management | Stock levels across plants update from receipts and transfers, so received quantities and inventory tell the same story. |
| Loose PO references | Procurement: purchase requests and approval workflows | POs are created from approved requests with clear lines, so receipts and invoices have a clean reference to match. |
| Suppliers chase payment by phone | Vendor Management and ERP payment status sync | Supplier conversations and documents sit on one vendor profile, and payment status syncs from your ERP. |
Zapro syncs vendor and master data two ways with your ERP or accounting system and takes invoices in through API or SFTP, so receipts, invoices and payment status stay aligned. See Zapro integrations.
A 30, 60, 90 day plan
Days 1 to 30: Diagnose
- Pull every invoice held in the last 90 days
- Tag each hold by cause, plant and supplier
- Measure receipt lag at each dock
- List the items with unit of measure conflicts
Days 31 to 60: Fix the dock
- Pilot same-shift receipting at the worst plant
- Correct units and conversion factors on top items
- Set tolerances for bulk and weighed categories
- Assign hold owners and a five-day age limit
Days 61 to 90: Hold the gains
- Roll dock receipting out to all plants
- Publish a weekly hold report by plant
- Ask top suppliers to quote PO lines on invoices
- Review tolerance rules against the new data
KPIs to track progress
| KPI | How to calculate | Review |
|---|---|---|
| First-pass match rate | Invoices that pass three-way match with no manual touch divided by all PO invoices | Weekly |
| Receipt-related hold share | Holds caused by missing or late receipts divided by all holds | Weekly, by plant |
| Receipt lag | Median hours between delivery and posted goods receipt | Weekly, by dock |
| Average hold age | Average days open for invoices currently on hold | Weekly |
| On-time payment rate | Invoices paid within agreed supplier terms divided by all invoices paid | Monthly |
| Aged GRNI lines | Value of goods received not invoiced lines older than 60 days | Monthly |
Go deeper with our guide to accounts payable automation guide.
What a Zapro customer saw after moving this work into one workflow
"Implementing Zapro improved our vendor coordination significantly, leading to a substantial reduction in costs and faster vendor onboarding."Akhil Sikri, CTO, Zolo
Why Zapro for this challenge
Receipt mismatches are a handoff problem between the dock and AP, not a supplier problem. Zapro puts the PO, receipt and invoice in one record and routes each gap to the person who can close it.
Matching that knows the difference
Z1 matches invoices to POs and receipts and flags risk, so AP spends time on real price and quantity gaps rather than timing noise.
Built around the supplier relationship
Documents, conversations and payment status sit on one vendor profile, so buyers answer payment calls in seconds.
Multi-plant from the start
Inventory across locations and transfers between plants sit in the same system as receipts and invoices.
Works with the ERP you run
Two-way ERP sync and invoice intake by API or SFTP mean you do not replace your core system to fix matching.
When Zapro may not be the right fit
- Your receiving and matching already run inside a mature ERP warehouse module with scanners at every dock, and first-pass match rates are high.
- You buy almost entirely through a few suppliers on consignment or self-billing, where invoices are generated from your own receipts.
- You need shop-floor execution such as production scheduling or quality inspection lots. Zapro covers procurement, receipts, AP and stock levels, and works alongside those systems.
Frequently asked questions
What is a GRN in accounts payable?
A goods receipt note (GRN) is the record that confirms what quantity of an ordered item actually arrived. In a three-way match, AP compares the purchase order, the GRN and the supplier invoice. If the GRN is missing or differs from the invoice, the invoice is held until someone confirms what was received.
Why do correct invoices get stuck in three-way match?
Usually because the receipt was posted late, posted short, posted in a different unit of measure or posted against the wrong PO line. The supplier billed what they shipped, but the system cannot prove it yet. Fixing receipting discipline and item master data removes most of these holds.
What match tolerance should a manufacturer use?
There is no single right number. Many teams set small percentage and value tolerances for materials sold by weight or length, where some variance is normal, and keep piece parts tight. Review tolerances against your hold data every quarter rather than setting them once.
Who should fix a hold caused by a missing receipt?
The team that received the goods. AP can see the hold but cannot confirm a delivery. Route missing-receipt holds to the receiving lead at the plant, give them a deadline and report hold age by plant each week.
Can we fix receipt mismatches without new software?
Partly. Same-shift receipting, corrected units of measure and a weekly hold report make a real difference. Software such as Zapro helps once you have several plants, high invoice volume or AP staff re-matching invoices by hand every day.
About the experts behind this page
Sources
- Tungsten Automation, AI in Accounts Payable: Metrics that Matter (citing Ardent Partners 2025), 2025
- Medius, Ardent Partners' 2025 State of ePayables Report, 2025
Editorial note: this page is published by Zapro, which sells procurement software. Best practices are written to work with any tool, and figures are cited to their original publishers. Last reviewed 29 September 2026; next review due March 2027. See how the Procurement Challenges Directory is researched and reviewed.