Goods Receipt Note (GRN): The Complete Procurement Guide

TL;DR

A Goods Receipt Note, or GRN, is the document that records what actually arrived when a supplier delivers against a purchase order. It confirms quantity, condition, and item details at the point of receipt, and it becomes the middle piece of the three-way match that protects a business from paying for goods it never received or received incompletely. A GRN is not just a warehouse formality. It is the moment your entire procurement cycle gets validated: what you requested, what the supplier quoted and committed to, what the purchase order specified, and what physically showed up all get reconciled here. This guide explains what a GRN is, what it contains, how it fits into the procure-to-pay flow, the three-way match, common mistakes, and how getting the front end of the cycle right with structured RFQs in AuraVMS makes the GRN stage dramatically cleaner.

What Is a Goods Receipt Note?

A Goods Receipt Note is a document generated by the buyer's receiving team when goods are delivered. Its job is to formally record the receipt of goods against a specific purchase order and to capture the details of what was actually received: which items, how many, in what condition, and on what date.

Think of it as the official answer to a simple but expensive question: did we get what we ordered? Until that question is answered in writing, the business has no reliable basis to approve the supplier's invoice for payment. The GRN provides that answer. It is the bridge between the physical event of delivery and the financial event of payment.

The GRN is sometimes called a goods received note, a receiving report, or a material receipt. Different organizations and different ERP systems use slightly different names, but the function is universal. Whenever goods change hands, someone on the receiving side records what arrived, and that record is the GRN.

It is worth being precise about what a GRN is not. It is not a delivery note. The delivery note, sometimes called a dispatch note or packing slip, is prepared by the supplier and states what they say they shipped. The GRN is prepared by the buyer and states what the buyer confirms they received. Those two documents should match, but the entire reason the GRN exists is that sometimes they do not. Relying on the supplier's delivery note alone is like accepting a restaurant bill without checking whether the food actually arrived.

Why Goods Receipt Notes Matter

For a small or mid-sized business, it is tempting to see the GRN as bureaucratic overhead. Someone in the warehouse already knows the boxes arrived, so why fill out a form? The answer is that the GRN protects the business at exactly the point where money is most likely to leak out.

Here is what a properly maintained GRN process actually does.

It prevents overpayment. Without a GRN, the accounts payable team has no independent confirmation of receipt. They see a purchase order and an invoice, both saying 1,000 units, so they pay for 1,000 units. If only 940 arrived, the business just paid for 60 units it never got. Multiply that across hundreds of deliveries a year and the leakage is significant.

It creates an audit trail. The GRN timestamps and documents receipt, which matters for financial audits, tax compliance, and internal controls. Auditors want to see that payments are backed by evidence of receipt, and the GRN is that evidence.

It supports inventory accuracy. The GRN is usually the trigger that updates inventory records. Stock levels, valuation, and reordering all depend on receipts being recorded promptly and correctly. A missing or late GRN means your inventory system is lying to you.

It manages disputes. When there is a shortage, damage, or wrong item, the GRN is the contemporaneous record that supports a claim against the supplier. Trying to raise a discrepancy weeks later without a GRN is a losing battle. The GRN captures the problem the moment it is discovered.

It anchors the three-way match, which we will come to shortly, and which is the single most important financial control in procure-to-pay.

What a Goods Receipt Note Contains

While formats vary, a complete GRN captures a consistent set of information. The essential fields are:

• GRN number, a unique reference for the receipt
• Purchase order number it relates to, linking the receipt back to the order
• Supplier name and details
• Date and time of receipt
• Delivery note or dispatch reference from the supplier
• Item descriptions and part numbers for each line received
• Quantity ordered versus quantity actually received, per line
• Condition of goods, noting any damage
• Quantity accepted versus quantity rejected
• Location or warehouse where goods were received
• Name and signature of the person receiving

The most important of these are the quantity comparison and the condition assessment, because they are where discrepancies surface. A GRN that simply says "goods received" without recording the actual counts against the ordered counts is close to useless. The whole value is in the comparison.

Good GRN discipline also means recording partial deliveries accurately. If a purchase order for 1,000 units is fulfilled in two shipments of 500, each delivery gets its own GRN, and the system tracks the cumulative received quantity against the order. This is how you know when an order is fully satisfied and when a balance is still outstanding.

Where the GRN Fits in the Procure-to-Pay Cycle

To understand the GRN properly, you have to see the whole cycle it sits inside. The typical procure-to-pay flow runs like this:

1. A need is identified and a purchase requisition is raised internally.
2. An RFQ, or request for quotation, goes out to suppliers to collect and compare quotes.
3. A supplier is selected and a purchase order is issued, confirming what will be bought, at what price, and by when.
4. The supplier delivers the goods.
5. The receiving team records a Goods Receipt Note, confirming what actually arrived.
6. The supplier submits an invoice.
7. Accounts payable performs a three-way match between the purchase order, the GRN, and the invoice.
8. If everything matches, the invoice is approved and paid.

The GRN sits at step five, and its position is deliberate. It comes after delivery and before payment, acting as the checkpoint that validates the physical reality of the transaction before any money moves. Every step before it, especially the RFQ and the purchase order, defines what should happen. The GRN records what did happen. The gap between those two is where all the risk lives.

This is why the quality of your GRN stage is heavily determined by the quality of everything upstream. If the RFQ collected vague or inconsistent quotes, the purchase order will be imprecise, and the GRN will have nothing clean to check against. Discipline at the front end pays off at the receiving dock.

The Three-Way Match: The GRN's Most Important Job

The three-way match is the core financial control that the GRN makes possible, and it deserves a section of its own because it is where the GRN earns its keep.

A three-way match compares three documents before an invoice is paid:

• The purchase order, which says what the buyer agreed to buy and at what price.
• The goods receipt note, which says what the buyer actually received.
• The supplier invoice, which says what the supplier is charging for.

When all three agree on quantity and price, the invoice is approved automatically and paid with confidence. When they disagree, the invoice is flagged for investigation before any payment is made. This simple cross-check catches a huge range of problems: supplier overbilling, quantity shortfalls, duplicate invoices, price discrepancies, and outright errors.

Consider a concrete example. Your purchase order says 500 units at $10 each, a total of $5,000. The supplier's invoice also says 500 units at $10, so on a two-way match it looks fine and gets paid. But the GRN records that only 460 units actually arrived. The three-way match catches this immediately. You pay for 460 units, $4,600, and you raise a discrepancy with the supplier for the missing 40. Without the GRN, that $400 walks out the door quietly, and it does so on every under-delivery, forever.

The three-way match is only as reliable as the GRN feeding it. A GRN that is rushed, inaccurate, or skipped entirely turns the three-way match back into a two-way match, and the financial control collapses. This is why receiving discipline is not clerical busywork. It is the enforcement mechanism for the entire purchasing budget.

Common GRN Mistakes and How to Avoid Them

Even businesses that run a GRN process often run it badly. The recurring failures are predictable.

Recording receipt without actually counting. The receiving clerk signs off on the delivery note quantity without physically verifying it. This defeats the entire purpose. The whole value of a GRN is the independent count. If you are just copying the supplier's numbers, you have no control at all.

Delayed GRN entry. Goods arrive Monday, but the GRN is not entered until Friday, or until the invoice shows up and prompts someone to look. By then, damage is hard to attribute, discrepancies are hard to prove, and inventory has been wrong all week. GRNs should be raised at the point of receipt, not retroactively.

Ignoring condition. Quantity gets checked, but condition does not. Damaged or defective goods get received into stock, and the problem only surfaces when production or a customer hits it. A good GRN records condition and separates accepted from rejected quantities on the spot.

Poor linkage to the purchase order. If the GRN is not cleanly tied to a specific PO line, reconciliation becomes guesswork. This is often a symptom of upstream sloppiness, where the PO itself was vague because the quote it came from was vague.

No handling of partial deliveries. The process assumes one delivery per order and breaks when a supplier ships in installments. A mature GRN process tracks cumulative received quantity against the order and knows exactly what balance remains.

Most of these mistakes share a root cause: the further upstream information was captured loosely, the more the receiving team has to improvise at the dock. Which brings us to the connection most procurement guides miss.

How Clean RFQs Make Clean GRNs

The GRN is a checking document. It checks reality against a promise. If the promise was recorded vaguely, the check is weak. That is why the quality of your goods receipt process is quietly determined weeks earlier, at the quoting stage, and this is where AuraVMS makes a practical difference.

AuraVMS is RFQ software that lets procurement teams send one structured request to multiple suppliers and collect their quotes in a single, consistent, comparable format. Every supplier answers the same defined fields: exact item specifications, quantities, unit prices, and firm delivery commitments. Instead of five suppliers replying with five different email formats and specifications buried in attachments, you get standardized, structured quote data.

That structure flows downstream directly into a cleaner GRN stage:

• Because item specifications and quantities were captured precisely in the RFQ, the resulting purchase order is precise, and the GRN has an unambiguous reference to check received goods against.
• Because AuraVMS produces a clean, documented record of what each supplier committed to, the three-way match has a solid purchase order to compare with, reducing the discrepancies that stall accounts payable.
• Because suppliers respond to AuraVMS without any signup or account creation, you get faster, more complete quote responses, which means fewer gaps and assumptions that would otherwise surface as surprises at receiving.
• Because AuraVMS supports anonymous bidding, the specifications and quantities you compare on are the real commitments each supplier stands behind, so the PO you eventually raise reflects genuine agreement rather than a hurried estimate.

The insight is that a GRN cannot manufacture precision that never existed. It can only compare what arrived against what was ordered. If what was ordered was itself derived from a clean, structured quote, the entire downstream chain of purchase order, goods receipt, and three-way match becomes tighter and faster. Teams using AuraVMS often compress a three to four day RFQ cycle into a couple of hours, and the less obvious payoff is that they also spend far less time untangling receiving discrepancies later, because the specifications were nailed down at the start.

In other words, the cheapest place to prevent a receiving dispute is the RFQ, not the dock.

Digital vs Paper GRNs

Many smaller businesses still run paper GRNs, a printed form the receiving clerk fills in by hand. It works, but it has obvious limits: paper gets lost, handwriting gets misread, entry into the accounting system is delayed and error-prone, and reconciliation across paper GRNs, POs, and invoices is manual and slow.

Digital GRNs, whether within an ERP, an inventory system, or a lightweight receiving app, solve most of this. Receipt is recorded at the point of delivery, often on a mobile device. The GRN links automatically to the purchase order. Inventory updates in real time. And the three-way match can run automatically, flagging only the exceptions that need human attention.

For a growing SMB, the move from paper to digital GRNs is usually one of the higher-return process upgrades available, because it converts a slow, error-prone manual check into an automated control. But even the best digital GRN system still depends on clean upstream data. A digital GRN checking against a vague purchase order is faster, but no more accurate. Precision has to start at the quote.

A Practical GRN Best-Practice Checklist

To run a GRN process that actually protects the business:

• Raise the GRN at the point of receipt, not later.
• Physically count and inspect, do not copy the supplier's delivery note.
• Record quantity received against quantity ordered, per line.
• Record condition and separate accepted from rejected quantities.
• Link every GRN clearly to its purchase order.
• Handle partial deliveries with cumulative tracking against the order.
• Feed the GRN into a three-way match before any invoice is paid.
• Investigate every discrepancy before payment, not after.
• Where possible, use digital GRNs linked to your PO and inventory systems.
• Get the specifications right upstream, in the RFQ, so the GRN has something precise to check against.

Follow these and the GRN stops being paperwork and becomes what it is meant to be: the checkpoint that makes sure you only ever pay for what you actually received.

FAQ

What is the difference between a GRN and a delivery note?

A delivery note is prepared by the supplier and states what they claim to have shipped. A Goods Receipt Note is prepared by the buyer and records what the buyer confirms was actually received, including quantity and condition. The two should match, but the GRN exists precisely because sometimes they do not. The GRN is the buyer's independent record and the one used for financial controls like the three-way match.

Is a GRN a legal requirement?

A GRN is generally not a statutory legal requirement in itself, but it is a critical internal control and is often needed to support financial audits, tax records, and dispute resolution. Many businesses treat it as mandatory because without it there is no reliable evidence of receipt to back up payments. In audited organizations, the absence of GRNs is a serious control weakness.

What is the three-way match and why does the GRN matter for it?

The three-way match compares the purchase order, the goods receipt note, and the supplier invoice before an invoice is paid. It ensures you only pay for goods that were both ordered and actually received, at the agreed price. The GRN is the middle piece that confirms physical receipt. Without it, you fall back to a two-way match of PO against invoice, which cannot catch under-deliveries or damaged goods, so overpayments slip through.

Who is responsible for creating the GRN?

The GRN is created by the buyer's receiving or warehouse team at the point goods are delivered. The person physically checking the delivery counts and inspects the goods, records the details, and signs the GRN. It should be someone independent of the person who raised the purchase order and the person who approves the invoice, to preserve segregation of duties as a control.

How do partial deliveries affect the GRN?

Each partial delivery gets its own GRN recording the quantity received in that shipment. The system then tracks the cumulative quantity received against the total ordered on the purchase order, so you always know how much of the order is still outstanding. Handling partial deliveries correctly is essential for accurate inventory and for knowing when to expect and match the final invoice.

How can I reduce discrepancies at the goods receipt stage?

The most effective lever is upstream precision. When item specifications, quantities, and delivery terms are captured cleanly at the RFQ stage, the purchase order is precise and the GRN has an unambiguous reference to check against. Using structured RFQ software like AuraVMS to collect standardized, comparable quotes means fewer vague specifications flow into your purchase orders, which directly reduces the surprises and disputes that appear at receiving.

Get the Front of the Cycle Right

A Goods Receipt Note can only check received goods against what was ordered, and what was ordered is only as good as the quote it came from. AuraVMS lets you send one structured RFQ to every supplier, collect precise and comparable specifications and delivery commitments with zero supplier signup, and feed clean, unambiguous data into every purchase order, GRN, and three-way match that follows, all for a fraction of the cost of enterprise procurement suites.

Book a demo of AuraVMS at https://www.auravms.com and start eliminating receiving disputes at their source, the RFQ.