A pallet lands on your dock with a delivery note listing 300 units. Whoever signs for it is busy, so they scrawl a signature and move on. Three weeks later the invoice bills for 300 units at full price, and nobody in accounts payable has a reason to question it. That’s how a company ends up paying in full for goods it never actually received in usable condition.
Skip the check, and you find out during a supplier dispute or an audit, when it’s too late and too expensive to fix. A goods received note is what closes that gap. Below, you’ll learn exactly what a GRN is, what belongs on one, how it differs from a delivery note and an invoice, why you need it, and how to build a process that catches problems at the dock instead of in a spreadsheet three weeks later.
We build receiving software for production and warehouse teams, so we’ve watched this exact failure pattern more times than we’d like.
What Is a Goods Received Note (GRN)?
A goods received note (GRN) is an internal document your receiving team creates the moment a supplier’s delivery arrives. It records exactly what showed up: the items, the quantities, and their condition, checked line by line against the original purchase order. The name changes depending on where you are and what industry you’re in:
- Goods receipt note or receiving note, common in ERP systems like SAP
- GRV (goods received voucher), the standard term across South African and southern African retail
- MRN (material receipt note), used in manufacturing when the delivery is raw materials rather than finished goods
The name changes. The function doesn’t.
Here’s the distinction that matters most, and the one most explainers skip past. A GRN is not proof of what the supplier shipped. It’s your own count, done by your own staff, at your own dock. The supplier’s delivery note tells you what they say they sent. Your GRN tells you what you actually got. When the two disagree, and eventually they will, the GRN is the record you stand on.
Goods received note (GRN): an internal document created by a buyer’s receiving team to confirm the quantity and condition of goods actually delivered by a supplier, checked against the original purchase order before payment is authorized.
What Information Belongs on a Goods Received Note?
A GRN only earns its keep if it captures enough detail to settle a dispute or clear an invoice without anyone needing to chase a follow-up question. Whether your template is a paper pad, a spreadsheet, or an ERP screen, build it around these fields:
| Field | Why It’s There |
|---|---|
| GRN number | A unique, sequential ID that lets AP, procurement, and the warehouse pull up this exact receipt later |
| Date of receipt | The date goods physically arrived, not the delivery note date or the invoice date; it sets the accounting period and the payment-term clock |
| Supplier name and details | Routes any discrepancy to the right vendor, especially when several suppliers ship similar items |
| Purchase order number | The single field that links this receipt back to what was actually ordered and agreed |
| Delivery note reference | Confirms both sides are talking about the same shipment when a question comes up later |
| Item description, quantity ordered vs. received | The core comparison; recording both numbers, not just what arrived, makes shortages visible immediately |
| Condition and discrepancy notes | Damage or shortage written down at the dock carries far more weight than a complaint raised weeks later |
| Receiver’s name and signature | Creates accountability; someone specific can speak to what the goods looked like on arrival |
| Quality inspection result | In regulated or manufacturing settings, a pass or fail note, or a batch and lot reference, before goods move into usable stock |
Leave any of these blank and you’ve created ambiguity that surfaces later, usually while accounts payable is trying to reconcile an invoice against a receipt that doesn’t say enough. Several industries build on top of this base set:
- Manufacturers often add certificate of conformance references and batch numbers for traceability
- Food and pharma distributors typically log temperature and expiry dates at the point of receipt
- Retailers working off blanket POs lean on barcode or RFID scans to populate quantities across hundreds of SKUs
Add fields to fit your industry. Don’t remove any of the base nine.
Goods Received Note vs. Delivery Note vs. Invoice: What’s the Difference?
Confusing these documents is the single most common mistake in receiving, and it’s an easy one to make since they all travel around the same shipment. The difference comes down to who creates each one and what it actually proves.
| Document | Created By | Created When | What It Proves |
|---|---|---|---|
| Purchase order (PO) | Buyer | Before shipment | What was ordered, at what price and quantity |
| Delivery note / packing slip | Supplier | With the shipment | What the supplier claims to have shipped |
| Goods received note (GRN) | Buyer | At the point of receipt | What actually arrived and in what condition |
| Invoice | Supplier | After delivery | What the supplier wants to be paid for |
A delivery note is written by the supplier and travels with the shipment, listing what they say they sent. A goods received note is written by the buyer after physically inspecting the delivery, and it records what actually arrived and its condition. One is a claim. The other is a check.
If your receiving staff are just initialing the supplier’s delivery note and filing it as your GRN, you don’t actually have a GRN. You have a copy of the supplier’s own paperwork with a signature added, and it won’t catch a single case of them shipping less than they claim. If you want delivery paperwork that’s structured enough to check against automatically instead of read by eye, we’ve broken down what machine-readable packing slip data actually requires.
Why Do You Need a Goods Received Note?
Strip away the paperwork and a GRN does five concrete jobs. Treat it as a formality, and you lose all five at once.
- It stops you paying for goods you didn’t get. Without an independent count, accounts payable has nothing to check the supplier’s invoice against except the supplier’s own claim, which is exactly the arrangement fraud and honest shipping errors both rely on.
- It separates receiving from payment authorization. One person receives and signs, someone else approves the payment. Concentrating both jobs in one person removes an internal control designed to catch counting errors and, less often but not never, deliberate fraud.
- It gives you a dated claim window. Damage or shortage noted at the point of receipt is evidence. The same complaint raised after you’ve already signed off is just an assertion, and carriers and suppliers both know the difference when you try to negotiate a credit.
- It keeps your stock ledger honest. Goods shouldn’t count as on-hand inventory until they’re inspected and posted. Until then, they’re physically in the building but not available to pick, sell, or issue to production.
- It builds an audit trail. Auditors treat the GRN as independent proof that goods were received. A missing or thin GRN record is exactly the kind of gap that turns into a finding during a review.
How Does a GRN Fit Into Three-Way Matching?
Two-way matching compares only the purchase order and the invoice: did the supplier bill what they agreed to bill. It never asks whether the goods actually arrived. Three-way matching adds the GRN as the missing check, comparing the PO, the GRN, and the invoice line by line before payment is released. If all three agree, payment clears. If they don’t, the invoice sits in an exception queue until someone resolves the gap.
Three-way matching compares three documents before a supplier invoice is paid: the purchase order (what you agreed to buy), the goods received note (what actually arrived), and the invoice (what the supplier is billing). Payment only goes through once all three line up, which is how shortages, damage, and overbilling get caught before money leaves the company.
Here’s a realistic version of how this breaks without a careful GRN. Say you order 300 units of a component at $18 each, a $5,400 purchase order. The full 300 arrive, but 15 units have crushed packaging and clearly failed inspection. The receiving clerk counts 300 boxes on the dock and writes “300 received” without noting the damage. The supplier invoices for 300 units at $18, totaling $5,400.
Three-way matching checks the PO ($5,400), the GRN (300 units), and the invoice ($5,400). Everything lines up. Payment clears automatically for goods that were never actually usable.
Had the GRN recorded 285 acceptable units and 15 damaged, the mismatch between the GRN (285) and the invoice (300) would have flagged an exception before payment went out, giving you grounds to negotiate a credit instead of quietly eating a $270 loss.
The fix isn’t complicated. Record what’s actually usable, not just what’s physically present, on every line of every GRN.
How to Create a Goods Received Note: A Step-by-Step Process
A reliable GRN process runs the same way every time, whether your team works off paper or a screen.
- Pull the PO and the delivery note before you touch the shipment. Having both in hand gives the receiver a clear reference for what was ordered and what the supplier claims to have sent.
- Count and inspect every line item individually. Don’t accept a carton or pallet count at face value. For anything sold by weight or volume, verify it with calibrated equipment.
- Record every discrepancy with specifics. “Three units damaged” is far less useful than “three units of SKU-4820, crushed outer packaging, visible denting.” Photograph damage where you can.
- Fill in every GRN field. Don’t leave anything blank. A blank field today is a question someone in AP has to chase down next week.
- Get sign-off. The person who inspected the goods signs. For high-value or regulated deliveries, add a second signature from a supervisor or quality inspector.
- Route copies to everyone who needs one. That typically means:
- Accounts payable, for three-way matching against the invoice and PO
- Procurement, for PO closure and supplier performance tracking
- Warehouse or inventory, to update stock levels
- The supplier, if a discrepancy needs a credit note or replacement shipment
For a closer look at how that AP handoff should work once the GRN is done, see how receiving ties into AP and compliance.
Common Goods Received Note Mistakes (and What They Actually Cost)
Most GRN failures trace back to a handful of repeat mistakes, and each one has a specific, avoidable cost attached.
| Mistake | What It Costs You |
|---|---|
| Recording ordered quantity instead of counted quantity | A silent overpayment that passes three-way matching clean, like the $270 example above |
| No PO number on the GRN | An orphaned receipt AP can’t match, stalling the invoice for days while someone hunts for the right order |
| Delayed GRN creation | Lost early-payment discounts and a stalled month-end accrual while paperwork catches up to goods that already arrived |
| One person both receiving and signing off | Removes the control that’s supposed to catch counting errors or a fraudulent receipt |
| Vague condition notes | No dated evidence to support a damage or shortage claim once the shipment is out of sight |
Most of these are receiving-variance patterns, meaning the difference between what the PO or delivery note says and what your team actually counted. We’ve written more specifically about the discrepancy checks worth catching automatically if this table looks familiar from your own receiving log.
Manual vs. Digital Receiving: Why Paper GRNs Break Down at Volume
None of this requires software. A small operation receiving a handful of deliveries a week can run accurate GRNs on a paper pad or a shared spreadsheet, as long as someone actually counts and someone actually checks.
The math changes once volume climbs: multiple daily deliveries, multi-line purchase orders, partial shipments against a single PO, more than one receiving location. At that point, the manual GRN process itself becomes the bottleneck. Someone has to translate a paper delivery note into your ERP by hand, and every re-key is a fresh chance to type 300 when the real count was 285.
Most companies are still carrying exactly this exposure. CIPS’ Global State of Procurement and Supply 2024 report, based on 122 organizations with a combined turnover of $73 billion, found that only 2% of procurement functions were fully automated and 27% were partly automated. The rest are still leaning on the same manual translation step that turned our earlier example into a real, quiet loss.
Three paths close that gap:
- ERP-native receiving. SAP posts a goods receipt through its MIGO transaction, and Oracle runs the equivalent through its Receiving module. Both pull item and quantity data straight from the PO instead of asking someone to retype it.
- Barcode or RFID scanning. Standard in retail distribution centers, where hundreds of SKUs on a single delivery make manual counting impractical.
- AI-assisted receiving. Newer tools read a supplier’s delivery paperwork directly, whether it’s a PDF, a photo, or a scanned form, and populate the GRN fields automatically, flagging a quantity or condition mismatch on the spot instead of waiting for someone to notice it during month-end reconciliation.
If you’re trying to size up whether that shift is worth it yet, we’ve laid out what manual receiving actually costs a production floor and what an AI receiving agent does differently from a scanner-based setup.
Frequently Asked Questions About Goods Received Notes
Who prepares and signs a goods received note?
The receiving or warehouse team prepares the GRN, and the person who physically inspected and counted the delivery signs it. For high-value or regulated goods, a supervisor or quality inspector often adds a second signature, so no single person can both receive the goods and approve what gets recorded.
What’s the difference between a GRN and a delivery note?
A delivery note comes from the supplier and lists what they say they shipped. A goods received note comes from the buyer, written after physically inspecting the delivery, and it records what actually arrived and its condition. They should match. When they don’t, the GRN is the version you act on.
Is a goods received note legally binding?
A signed GRN isn’t a contract, but it functions as documentary evidence in a dispute or audit. Auditors and courts treat a dated, signed record of what arrived, especially one noting damage or shortage at the time, as far more credible than a complaint raised after the fact.
What happens if the GRN doesn’t match the supplier invoice?
The invoice gets held in an exception queue instead of moving to payment. Someone, usually in accounts payable or procurement, investigates the gap between what the GRN recorded and what’s being billed before releasing any money, and resolves it with the supplier if needed.
Can a goods received note be created digitally?
Yes. Most ERP systems generate a GRN as part of the receiving transaction, and AI-assisted receiving tools can read a supplier’s delivery paperwork directly and populate the GRN fields without manual re-keying.
Get the Goods Received Note Right, and the Rest of the Process Holds
A goods received note only works if it’s treated as a check, not a formality. Every job it does, stopping overpayment, protecting your damage claims, keeping your stock ledger honest, feeding an audit trail, depends on someone actually counting and inspecting before they sign, not rubber-stamping the supplier’s own paperwork.
Three steps get you there:
- Standardize a GRN template around the nine core fields covered above, and use it everywhere, paper or digital.
- Split receiving and payment approval across two people, always, no exceptions for a “trusted” supplier.
- Time your receipt-to-GRN gap. If it’s regularly stretching past a day, that’s your signal the process needs to move off paper.
Where does your receiving process actually break down: the counting, the paperwork, or the wait between the two? Here’s how we automate that translation step.
