The full form of GRN is Goods Received Note: the document a buyer's receiving team creates at delivery, recording exactly what arrived, in what quantity and condition, against which purchase order. It is the middle document of the three-way match, between the purchase order and the supplier invoice, and the point where inventory accuracy is born: stock records should rise by counted GRN quantities, never by what the supplier's paperwork claims.
- The full form of GRN is Goods Received Note: the document a buyer creates at delivery recording exactly what arrived, in what quantity and condition, against which purchase order.
- A complete GRN carries the PO reference, supplier details, line-level ordered vs received quantities, condition and QC results, discrepancies, and signatures, and nothing on it is optional.
- The GRN is the middle document of the three-way match: purchase order (what you asked for), GRN (what you got), supplier invoice (what you are billed for). Pay only when all three agree.
- Its two jobs: catch shortages, damage, and wrong items at the dock while there is still recourse, and start your inventory records true, since accuracy downstream can never exceed accuracy at receiving.
- "Goods receipt note" and "goods receipt" (the SAP-world term) are the same document; a delivery note is the supplier's claim, not your confirmation.
- Digitized, scan-based receiving generates the GRN automatically, which removes the keying errors and the temptation to rubber-stamp.
SECTION 01What is GRN? Goods received note explained
In brief: The full form of GRN is Goods Received Note: a document the buyer's receiving team creates when a supplier delivery arrives, recording exactly which items were received, in what quantities and condition, against which purchase order. It is the buyer's official evidence of what actually arrived, used to update inventory and verify the supplier's invoice before payment.
GRN full form: Goods Received Note. GRN meaning: the buyer's own signed record of what a delivery actually contained, against which purchase order.
The GRN exists because of a gap nobody likes to talk about: what a supplier says they shipped and what actually lands on your dock are two different claims, and only one of them should update your records and get paid. The purchase order records your intent. The supplier's paperwork records their claim. The GRN records the verified truth, counted, inspected, and signed by your own team at the moment of delivery.
You will meet the same document under several names: goods received note and goods receipt note are used interchangeably, and in ERP-speak (particularly SAP environments) the act and the record are called a goods receipt. In parts of Asia and the Middle East the delivery paperwork culture centers on the challan or delivery note, which the GRN answers from the buyer's side. Whatever the label, the function is identical: independent confirmation of what arrived, created by the party receiving it.
SECTION 02What information does a GRN contain? (Format and fields)
In brief: A complete GRN contains a unique GRN number and date, the purchase order reference, supplier name and delivery details, line-level entries showing each item's ordered quantity versus received quantity, condition and quality-check outcome, recorded discrepancies (shortages, damage, excess, wrong items), and the names and signatures of the receiver and, where present, the deliverer.
| Field | What it records | Why it is not optional |
|---|---|---|
| GRN number & date | Unique reference and receipt timestamp | The audit trail hangs off this number |
| PO reference | The purchase order this delivery answers | No PO reference, no three-way match |
| Supplier & delivery details | Vendor, carrier, vehicle or docket number | Disputes need to name the actual delivery |
| Line items: ordered vs received | Per SKU: quantity ordered, quantity actually counted in | The core comparison; the whole point of the document |
| Condition / QC outcome | Accepted, damaged, rejected per line, with batch and expiry where relevant | Damaged units accepted silently become sellable-stock fiction |
| Discrepancy notes | Shortages, excess, substitutions, damage descriptions | This is the evidence for claims and debit notes |
| Signatures | Receiver, and deliverer where practice allows | Accountability, on both sides of the handover |
Goods received note template: the template below shows all of it assembled, filled in with a worked example and available blank. One format rule worth enforcing: record what you counted, never what the paperwork says. A GRN copied from the delivery note is a photocopy of the supplier's claim wearing your signature.
SECTION 03What is the GRN process, step by step?
In brief: The delivery arrives and is matched to its purchase order, quantities are physically counted against PO lines, items are inspected for condition with batch and expiry captured where relevant, discrepancies are recorded and the supplier notified, the GRN is signed and issued, inventory is updated from GRN quantities, and the document goes to accounts for invoice matching.
- 1. Match the delivery to its PO. An unexpected delivery with no purchase order goes to an exception process, not into stock. This single rule ends a surprising amount of chaos.
- 2. Count physically, line by line. Every SKU counted against its PO quantity. Carton labels lie often enough that the count must be of units, or of verified standard cartons, not of shrink-wrap.
- 3. Inspect condition. Damage, defects, and wrong items identified now, while refusal or claim is still simple. For batch-managed and dated goods, capture batch numbers and expiry at this step, because FEFO rotation downstream depends on it.
- 4. Record discrepancies. Shortages, excess, substitutions, and damage go on the GRN in specific terms, and the supplier is notified against the GRN number. This paper trail is what turns a dispute into a settlement.
- 5. Sign and issue. The receiver signs; the GRN becomes the delivery's official record, distributed to purchasing and accounts.
- 6. Update inventory from the GRN. Stock records rise by received quantities, never PO quantities. Accepted stock proceeds to putaway; rejected stock is quarantined, not shelved.
- 7. Send to accounts for matching. The GRN meets the PO and the supplier invoice in the three-way match, which is the next section.
SECTION 04GRN vs purchase order vs invoice vs delivery note
In brief: The purchase order records what you ordered, the GRN records what you actually received, and the supplier invoice records what you are being charged for. Paying only when all three agree, the three-way match, is the standard control that stops payment for short, damaged, or undelivered goods. The delivery note is the supplier's shipping claim and confirms nothing by itself.
| Document | Created by | It proves | Common confusion |
|---|---|---|---|
| Purchase order (PO) | Buyer, before shipment | What was ordered, at what price and terms | Intent, not receipt |
| Delivery note / challan | Supplier, with the shipment | What the supplier claims was sent | A claim, not a confirmation |
| Goods received note (GRN) | Buyer, at delivery | What was actually received, counted, and accepted | The only document verified by your own team |
| Supplier invoice | Supplier, after delivery | What you are being billed | Payable only when it matches PO and GRN |
The three-way match is where the humble GRN earns its keep in money terms: invoices for 500 units get paid for the 480 the GRN proves, damaged goods become debit notes instead of losses, and the "we definitely shipped it" conversation ends with a document instead of a memory. It is the same verify-before-you-pay discipline we apply to marketplace settlements in our payment reconciliation guide, running at the supplier end of the business. One regional note: in India, clean GRN records also matter for GST input credit substantiation, since claiming credit on goods you cannot prove you received is an audit finding waiting to happen.
SECTION 05Why do GRNs matter so much in ecommerce operations?
In brief: The GRN is where inventory accuracy is born: stock records seeded from verified counts stay trustworthy, while records seeded from supplier paperwork inherit every shipping error. It also protects cash through the three-way match, creates the evidence base for supplier claims, and grades supplier reliability with data instead of impressions.
- Accuracy starts here or nowhere. Every downstream discipline, cycle counting, picking accuracy, channel sync, corrects drift from a baseline. The GRN is the baseline. Well-run operations holding ~97.7% inventory accuracy (Opensend, 2025) get there by starting each SKU's ledger with a verified count.
- Cash protection. Without a GRN, the three-way match collapses into a two-way match between the supplier's claim and the supplier's bill, which is no match at all.
- Claims with teeth. Shortage and damage claims live or die on contemporaneous evidence. A discrepancy recorded on a signed, dated GRN settles; one remembered a week later does not.
- Supplier scorecards. GRN discrepancy rates per supplier turn "they seem unreliable" into "7% of their lines short-ship," which changes both negotiations and safety stock math.
SECTION 06What goes wrong with manual GRNs?
In brief: Paper GRNs fail through rubber-stamping (copying the delivery note instead of counting), keying errors when data is transcribed into systems, delays that leave received stock invisible and unsellable for days, lost documents that break the three-way match, and skipped quality checks under dock time pressure.
The GRN's weakness is that it is only as honest as the five minutes spent creating it, and dock pressure attacks exactly those five minutes. The familiar failure modes: the receiver copies the delivery note under time pressure (a photocopied claim, as above); the paper GRN waits days for data entry, during which the stock is physically present but systemically invisible and unsellable; transcription introduces the roughly one-error-per-300-characters tax of manual keying (GS1 benchmark); and the document itself goes missing right before the invoice dispute that needed it. None of these are people problems; they are process problems wearing a person's badge, and the fix is structural.
SECTION 07Digital GRNs: what changes with a WMS?
In brief: In a WMS-run warehouse, receiving is scan-based against the open purchase order: each item scanned at the dock is counted, matched, and quality-flagged in real time, and the GRN generates itself from the scans. Discrepancies surface instantly, stock becomes sellable the moment receiving completes, and the document can never be lost or mistyped.
Digitize receiving and the GRN stops being a form someone fills and becomes a byproduct of the work itself. The receiver opens the expected delivery on a handheld device, scans each item in (the same scan-to-confirm discipline from our RF scanner guide, pointed inbound), and the system counts, matches against PO lines, prompts for condition and batch/expiry capture, and flags every variance as it appears. When the last carton is scanned, the GRN exists, numbered, timestamped, attached to its PO, and already reflected in sellable stock across every channel. Nothing was keyed, nothing can be lost, and rubber-stamping is structurally impossible because the count is the scan. This is receiving as a warehouse management system runs it, and it is where the GRN's paper-era weaknesses simply stop existing.
Good Bug operates this way on EasyEcom, running B2B and B2C fulfillment from one warehouse with purchase orders integrated and shelf life tracked from the moment goods arrive, which is exactly the batch-and-expiry capture at receiving that FEFO rotation depends on later.
SECTION 08How EasyEcom handles goods receiving
In brief: EasyEcom runs scan-based receiving against open purchase orders: counts, QC flags, and batch and expiry capture happen at the dock, the GRN record generates automatically, discrepancies are logged against the PO for supplier follow-up, and received stock becomes sellable across every channel the moment receiving completes.
On EasyEcom, the receiving flow is the digital GRN process described above, wired into everything downstream: verified quantities seed inventory truthfully, QC rejections quarantine instead of shelving, batch and expiry data feeds FEFO picking, discrepancy records back your supplier claims, and the received stock is live on your marketplaces and webstore before the pallet reaches its bin. Received-vs-ordered reporting per supplier builds the reliability scorecard automatically.
See your inbound flow the digital way: explore the EasyEcom warehouse management system. If you would rather see it on one of your own deliveries, book a demo and we will walk it through scan-based receiving.
Frequently asked questions
What is the full form of GRN?
GRN stands for Goods Received Note: the document a buyer's receiving team creates when a supplier delivery arrives, recording what was actually received, in what quantity and condition, against which purchase order. It is also called a goods receipt note, or simply a goods receipt in ERP systems.
Who prepares the goods received note?
The buyer's receiving team prepares it at the point of delivery, counting and inspecting the goods physically. The supplier's driver may countersign where practice allows. It is never prepared by the supplier: the GRN's entire value is that it is the receiving party's independent verification.
What is the difference between a GRN and a delivery note?
A delivery note (or challan) is created by the supplier and states what they claim to have shipped. A GRN is created by the buyer and records what was actually counted and accepted on arrival. When the two disagree, the GRN, being physically verified, is the document your inventory and payments should follow.
What is a GRN used for in accounting?
It is the middle document of the three-way match: accounts payable compares the supplier invoice against the purchase order and the GRN, and pays only when all three agree. This prevents payment for short-shipped, damaged, or undelivered goods, and in India clean GRNs also support GST input credit substantiation.
What is the GRN full form?
GRN full form is Goods Received Note: the document a buyer raises at delivery to record what actually arrived, in what quantity and condition, against the purchase order.
What should a GRN format include?
A unique GRN number and date, the purchase order reference, supplier and delivery details, line-level ordered versus received quantities per SKU, condition and quality-check outcomes with batch and expiry where relevant, discrepancy notes, and the receiver's signature. Recording counted quantities rather than paperwork quantities is the rule that makes it meaningful.
Is a GRN the same as a goods receipt in SAP?
Functionally yes. In SAP and similar ERPs, posting a "goods receipt" against a purchase order is the digital equivalent of issuing a GRN: it records verified received quantities, updates stock, and enables invoice verification. The GRN is the document name; the goods receipt is the ERP transaction.
Can the GRN process be automated?
Yes. In a WMS-run warehouse, receiving is scan-based against the open purchase order: scans count and match items in real time, QC and batch data are captured at the dock, and the GRN record generates automatically with stock becoming sellable immediately. This removes keying errors, delays, and lost documents entirely.