Goods Receipt Note (GRN): The Complete Guide

What a Goods Receipt Note Is

A goods receipt note (GRN) is a document created by the receiving party to record the goods actually delivered against a purchase order. It captures what arrived, in what quantity, and in what condition, and it serves as the formal confirmation that an order has been fulfilled — in whole or in part. The GRN is the physical-world checkpoint of procurement: the moment where what was ordered on paper is reconciled against what showed up on the loading dock.

That single document does more work than its humble appearance suggests. It triggers inventory updates, underpins supplier performance tracking, and — most importantly — forms one of the three legs of three-way matching, the core control that protects accounts payable from paying for goods never received. Without a reliable GRN, an organisation is effectively paying invoices on trust. This guide explains what a GRN contains, how the receipt process works, how it differs from a delivery note and an invoice, and where automation now removes the manual effort. It sits within the broader seven stages of procurement, at the receipt and matching stage.

What a Goods Receipt Note Contains

A complete GRN carries the information needed to reconcile the delivery against the order and to feed downstream systems. While formats vary, the essential fields are consistent across organisations:

• GRN number and date: a unique identifier and the date goods were received.
• Purchase order reference: the PO number that links the receipt back to the order — the single most important field for matching.
• Supplier details: the vendor name and, often, the delivery note number for cross-reference.
• Line items: description, ordered quantity, received quantity, and unit of measure for each item.
• Condition notes: any damage, shortages, or rejections recorded at inspection.
• Receiver sign-off: the name of the person who received and verified the delivery.

The received-quantity and condition fields are what give the GRN its control value. A delivery that arrives short, damaged, or wrong is documented at the point of receipt, when the evidence is fresh and the supplier can still be held to account. Catching a discrepancy here costs minutes; catching it after payment costs a dispute.

Different organisations layer additional fields onto this core depending on their sector and ERP. Manufacturers often add batch or lot numbers and inspection results for quality traceability; regulated industries capture certificates of analysis or conformity; and high-value capital purchases record serial numbers for asset tracking. The principle is consistent regardless of the extras: the GRN should capture enough detail that anyone reviewing it months later can reconstruct exactly what was received, by whom, and in what state. That reconstructability is what makes the GRN useful not just for matching but for supplier performance scoring — on-time and in-full delivery rates are built directly from receipt data, so a sloppy GRN undermines your ability to hold suppliers to account over time.

The Goods Receipt Process Step by Step

The receipt process is short but consequential. It typically runs as follows: the delivery arrives accompanied by the supplier's delivery note; the receiving team locates the matching purchase order; goods are counted and inspected against the PO line items; quantities and condition are recorded; discrepancies are noted and, where necessary, items are rejected; the GRN is created and signed; and the receipt is posted to the ERP, updating inventory and creating the record that AP will match against.

The discipline that separates a clean process from a messy one is verifying against the purchase order, not the delivery note. The delivery note reflects what the supplier says they sent; the GRN must reflect what you actually received and ordered. When receiving teams simply rubber-stamp the delivery note, errors and short-shipments flow straight through to payment. A receipt posted promptly and accurately is also what keeps the downstream purchase order process and invoice matching from stalling on missing-receipt exceptions.

The GRN's Role in Three-Way Matching

Three-way matching compares three documents before an invoice is paid: the purchase order (what was ordered), the goods receipt note (what was received), and the invoice (what is being billed). When all three agree on quantity, price, and item, the invoice clears for payment automatically. When they disagree, an exception is raised for human review. The GRN is the leg that grounds the whole control in physical reality — without it, matching collapses to a two-way check that can confirm an order was placed and billed, but not that anything was actually delivered.

This is why GRN quality is one of the biggest determinants of touchless-matching rates. Our analysis of AI three-way matching consistently finds that real-world automated match rates land in the 75–85% range rather than the 95%+ vendors advertise — and missing or late goods receipts are among the most common reasons an invoice that should match instead lands in the exception queue. Platforms such as Tipalti and Stampli in the invoice and AP automation category can only match against receipts that exist and are accurate.

GRN vs Delivery Note vs Invoice vs PO

These four documents are constantly confused, yet each is created by a different party for a different purpose. Getting the distinctions right is essential to understanding the control chain.

The crucial insight is that the GRN and the delivery note can disagree — and when they do, the GRN wins, because it reflects an independent count by the buyer rather than the supplier's claim. That independence is the whole point of creating a separate receipt record instead of just filing the delivery note. The GRN, in turn, originates from the requisition and PO chain that began the purchase.

Best Practices for Goods Receipt

A handful of practices separate organisations with clean receipt data from those drowning in matching exceptions. Receive promptly: post the GRN to the ERP the same day goods arrive, so AP isn't blocked by invoices waiting on a receipt that hasn't been recorded. Inspect against the PO, not the delivery note, and record actual received quantities even when they differ from what was ordered. Document condition and discrepancies at the point of receipt, with photos where damage is involved, so disputes have evidence. And enforce a "no receipt, no pay" discipline alongside "no PO, no pay" — an invoice should not clear until the goods it bills for are confirmed received.

For services rather than physical goods, the equivalent of a GRN is a service-completion confirmation — a documented sign-off that the work was delivered to specification. The principle is identical: payment should follow confirmed receipt, not just an invoice. Standardising these practices is what makes the downstream procure-to-pay process run with minimal manual intervention.

Quantity tolerances deserve a deliberate policy. Few deliveries match the order to the exact unit — a supplier may ship 98 of 100 items, or 102. Defining acceptable tolerance bands (for example, accepting receipts within a small percentage of the ordered quantity without raising an exception) keeps trivial variances from clogging the matching queue while still flagging meaningful discrepancies. Setting those tolerances too loose, however, lets real shortages slip through, so the band should reflect the value and criticality of the category. This is exactly the kind of judgement that AI matching learns to apply per vendor over time, but it starts with a human policy that the receipt process enforces consistently.

Finally, treat the receiving function as a genuine control point staffed by people who understand its importance, not as an afterthought handed to whoever is nearest the dock. The receiver is the last line of defence before money starts moving toward a supplier, and a well-trained receiving team that knows how to inspect, document, and reject pays for itself many times over in avoided overpayments and disputes. Pairing that human judgement with the right tooling — barcode capture, mobile posting, and AI-assisted matching — is what turns the goods receipt note from a rubber-stamp formality into a real financial control.

Automating Goods Receipt

Receipt is increasingly automated, though it remains more physical than other procurement stages. Barcode and RFID scanning capture received quantities directly into the ERP, eliminating manual keying errors. Mobile receiving apps let warehouse staff confirm deliveries from the dock. Advanced shipping notices (ASNs) let the system anticipate what's arriving and pre-populate the GRN. And on the matching side, AI reconciles receipts against POs and invoices, learning vendor-specific patterns — such as suppliers that habitually ship in partial batches — so that benign variances don't generate needless exceptions.

The limiting factor, as with all of AP automation, is data quality. An AI matching engine can only reconcile receipts that are accurate, complete, and timely; a warehouse that posts receipts days late or records them carelessly will undercut even the best tooling. Organisations weighing receipt and matching automation should start by auditing their current GRN accuracy and timeliness, then model the upside — our source-to-pay market analysis and the broader purchase order automation category are the companion resources for that evaluation.

Common Goods Receipt Problems

Most matching pain downstream traces back to a small set of recurring receipt problems. The most common is the late receipt: goods arrive and are physically accepted, but the GRN isn't posted to the ERP for days. When the supplier's invoice arrives in the meantime, AP has nothing to match against, and a perfectly legitimate invoice lands in the exception queue. The fix is a same-day posting discipline, ideally enforced by mobile receiving that captures the receipt at the dock rather than hours later at a desk.

The second is the rubber-stamped receipt, where staff confirm the full ordered quantity without actually counting, simply because counting takes time. This defeats the entire purpose of the GRN: short-shipments and damage flow straight through to payment, and the supplier is never held accountable. The third is the partial-delivery tangle, where a vendor splits an order across several shipments and each one needs its own receipt against the same PO. Without a system that tracks cumulative received quantity against the order, partial deliveries quickly become a reconciliation nightmare — and partial shipments are one of the largest single sources of matching exceptions.

A fourth problem is the services blind spot. Physical goods get a receipt, but services — consulting, maintenance, software — often skip the equivalent confirmation, so invoices for work are paid with no independent verification that the work was completed to specification. Establishing a service-completion sign-off as the GRN equivalent closes that gap. Across all of these, the common thread is that the GRN's control value depends entirely on the rigour of the person and process creating it; the document is only as trustworthy as the count behind it.

The GRN, Inventory, and Accruals

Beyond matching, the goods receipt note carries real accounting weight. Posting a receipt updates inventory in the ERP, so stock records reflect what's actually on hand — critical for planning, replenishment, and avoiding both stockouts and overstock. It also creates the basis for accruals: the moment goods are received, a liability exists even if the invoice hasn't arrived yet. The GRN is what lets finance recognise that liability in the correct period rather than waiting for the invoice, which is what keeps month-end close accurate.

This GR/IR (goods-received/invoice-received) reconciliation is a standard control in ERP systems such as SAP and Oracle. When goods are received, the system books a provisional liability; when the invoice is matched and posted, that provisional entry clears. Unreconciled GR/IR balances — receipts with no matching invoice, or invoices with no matching receipt — are a classic audit flag and a sign that the receipt-to-pay chain is leaking somewhere. Clean, timely GRNs are therefore not just a procurement concern but a financial-control one, which is why finance and procurement share ownership of the receipt stage. The accuracy of that data flows directly into the spend records that power the next sourcing cycle, closing the loop back to the strategic front end of the procurement lifecycle.

Frequently Asked Questions

What is a goods receipt note?

A goods receipt note (GRN) is a document created by the buyer's receiving team to record the goods actually delivered against a purchase order, including quantity received, condition, and date. It confirms that an order has been fulfilled and serves as the receipt leg of three-way matching, the control that prevents paying for goods never received.

What is the difference between a goods receipt note and a delivery note?

A delivery note is created by the supplier and accompanies the goods in transit, stating what the supplier says they shipped. A goods receipt note is created by the buyer and records what was actually received after an independent count and inspection. When the two disagree, the GRN takes precedence because it reflects the buyer's own verification rather than the supplier's claim.

Why is a goods receipt note important in three-way matching?

The GRN is the document that proves goods were actually received, grounding the match in physical reality. Three-way matching compares the purchase order, the goods receipt note, and the invoice; without the GRN, the check can only confirm an order was placed and billed, not that anything was delivered. Missing or late GRNs are a leading cause of invoice matching exceptions.

Is a goods receipt note the same as an invoice?

No. An invoice is created by the supplier to request payment for goods or services, while a goods receipt note is created by the buyer to confirm what was received. The two are matched against each other (along with the purchase order) during three-way matching, but they serve opposite functions — one bills, the other verifies.

Can the goods receipt process be automated?

Yes. Barcode and RFID scanning, mobile receiving apps, and advanced shipping notices automate the capture of received quantities, while AI matching reconciles receipts against purchase orders and invoices. However, automation only delivers value when receipt data is accurate and posted promptly, so data discipline at the dock remains essential.

Explore more foundational procurement guides on the ProcurementAIAgents.com blog, or compare the platforms that automate receipt and matching in our invoice and AP automation directory.