Every procurement team knows the feeling. An invoice arrives. The AP team needs to pay it. But did the goods actually arrive? In the right quantity? In the right condition? At the right price?
The document that answers all three questions is the Goods Received Note — the GRN. It is not the most glamorous document in the procurement cycle, but when it is missing, delayed, or managed manually, enterprises pay for goods they never received and lose the financial accuracy that CFOs and audit teams depend on.
This guide covers everything procurement and finance professionals need to know about GRNs — what they are, what they contain, how they work in the procure-to-pay cycle, how they connect to three-way matching, and how modern enterprises are automating them.
What is a Goods Received Note (GRN)?
A Goods Received Note is an internal document created by the buyer's receiving or warehouse team to confirm that goods delivered by a supplier have arrived in the correct quantity, quality, and condition. It is created after physical inspection of the delivery — not when the goods are dispatched, and not when the invoice arrives. The GRN records what actually happened at the receiving dock, after someone physically checked the delivery against the purchase order.
Three things the GRN confirms:
- The goods ordered actually arrived
- They arrived in the quantity ordered
- They arrived in the condition expected
What the GRN is not:
- It is not the supplier's delivery note (which the supplier creates and sends with the shipment)
- It is not the purchase order (which authorises the purchase)
- It is not the invoice (which requests payment)
The GRN is the buyer's own record — the internal confirmation that the delivery was verified and accepted.
What Does a GRN Contain?
A complete GRN should capture the following fields:
| Field | Purpose |
|---|---|
| GRN number | Unique identifier for tracking and cross-referencing |
| Date of receipt | When goods physically arrived — critical for payment terms and warranty start dates |
| Purchase order reference | Links the receipt to the authorised purchase |
| Supplier name and details | Identifies the vendor for performance tracking and dispute resolution |
| Item description | What was received — must match PO description |
| Quantity ordered / received | What was expected vs what actually arrived — may differ |
| Condition of goods | Damage, defects, or discrepancies noted at receipt |
| Batch number / expiry date | For traceability — critical in food, pharma, and manufacturing |
| Storage location | Where goods were placed in the warehouse |
| Receiving team member | Who inspected and accepted the delivery |
| Discrepancies noted | Short delivery, damage, incorrect items — recorded before goods are accepted |
| Signature and approval | Authorised sign-off confirming receipt |
Where Does the GRN Sit in the Procure-to-Pay Cycle?
The procure-to-pay (P2P) cycle has seven stages. The GRN sits at stage five — between delivery and invoice matching. Without it, three-way matching cannot happen, and without three-way matching, enterprises cannot verify they are paying for goods they actually received.
| Stage | Step |
|---|---|
| 1 | Purchase Requisition — internal request for goods or services |
| 2 | Purchase Order — approved PO sent to supplier |
| 3 | Supplier Acknowledgement — supplier confirms the order |
| 4 | Delivery — supplier ships goods with delivery note or delivery challan |
| 5 — GRN created here | Goods Receipt — receiving team inspects delivery and creates the GRN |
| 6 | Three-Way Matching — PO + GRN + Invoice matched before payment |
| 7 | Payment — approved invoices paid per terms |
Who Uses the GRN?
The GRN is not just a warehouse document. It is used by multiple functions across the enterprise:
| Team | How They Use the GRN |
|---|---|
| Receiving / warehouse team | Creates the GRN at point of delivery, confirms quantities and condition |
| Procurement team | Uses GRN to close out POs, track supplier performance, manage partial deliveries |
| Accounts payable | Uses GRN as one of three documents in the three-way match before approving payment |
| Finance | Uses GRN for GRNI (Goods Received Not Invoiced) accounting entries at period end |
| Inventory management | Uses GRN to update stock levels — goods enter inventory only after GRN is confirmed |
| Audit | Uses GRN as evidence that goods were received — supports financial statement accuracy |
| Legal / compliance | GRN provides documented proof of delivery for dispute resolution |
GRN and Three-Way Matching
The most important role the GRN plays is in three-way matching — the financial control that prevents enterprises from paying for goods they did not receive. Three-way matching compares three documents:
- Purchase Order — what was authorised to be ordered
- Goods Received Note — what was actually received
- Supplier Invoice — what the supplier is claiming payment for
All three must agree — on item, quantity, and price — before the invoice is approved for payment. The GRN is the weakest link in this chain in most enterprises because it depends on someone in the warehouse physically logging the receipt — and in many enterprises, this happens late, incompletely, or not at all.
GRN and GRNI (Goods Received Not Invoiced)
GRNI — Goods Received Not Invoiced — is a balance sheet accrual that represents goods that have been received (confirmed by GRN) but for which no invoice has yet been received. Under accrual accounting, the expense must be recognised in the period when the goods were received. The GRN is the trigger event for the GRNI accrual — which means that accurate, timely GRN creation is not just an operational issue but a financial reporting requirement.
Types of GRN
| GRN Type | When It Applies | Key Considerations |
|---|---|---|
| Full receipt GRN | All ordered items arrive in full | Standard — PO closed after GRN |
| Partial receipt GRN | Only some of the ordered quantity arrives | PO remains open for outstanding balance |
| Quality rejection GRN | Goods arrive but fail quality inspection | Rejected goods documented, supplier notified |
| Return GRN | Previously received goods returned to supplier | Reverse inventory entry, credit note request |
| Service receipt confirmation | No physical goods — services or intangibles delivered | Service entry sheet or milestone confirmation |
| Internal transfer receipt | Goods moved between internal locations | Inter-facility transfer confirmed, no supplier payment triggered |
Common GRN Challenges — and What They Cost
| Challenge | How It Manifests | Cost |
|---|---|---|
| Late GRN creation | Invoice held in AP queue pending receipt confirmation | Delayed payment, lost early payment discounts, damaged vendor relationships |
| Manual data entry errors | Wrong quantities, item codes, or dates entered | Invoice mismatches, reconciliation effort, potential overpayment |
| Missing GRNs | Goods received but never formally logged | Payment approved without verification — fraud and overpayment risk |
| Partial delivery not recorded | Full GRN created for partial delivery | Overpayment on undelivered goods |
| Quality issues not documented | Defective goods accepted without GRN discrepancy note | No basis for credit note request or supplier penalty |
| Paper-based process | GRNs on paper, filed physically | Not searchable, not auditable, lost in AP queue delays |
GRN Best Practices
- Create the GRN at the point of delivery — not after. The GRN should be created as goods are received and inspected, not at the end of the day or the next morning.
- Inspect before accepting — the GRN should reflect what was actually checked, not what the supplier's delivery note says.
- Record every discrepancy — short deliveries, damaged goods, and incorrect items should be documented in the GRN at the time of receipt.
- Capture batch codes and expiry dates — for food, pharma, and manufacturing, these are the foundation of traceability and cannot be reconstructed later.
- Connect the GRN to the AP workflow in real time — GRNs created in a separate system introduce the same delays as paper-based processes.
- Set a GRN creation SLA — best-in-class organisations target GRN creation within 24 hours of delivery, many target same shift.
- Never pay an invoice without a confirmed GRN — this is the fundamental financial control the GRN exists to enforce.
GRN in India: Specific Considerations
Indian enterprises operating under GST have additional considerations that make GRN accuracy particularly important:
- Input Tax Credit (ITC) depends on accurate receipt — under GST, a buyer can claim ITC only for goods that have been actually received. The GRN is the internal evidence of receipt and supports the ITC claim in an audit.
- Delivery challan is not the same as a GRN — in Indian procurement, goods are often transported with a delivery challan, a document issued by the supplier. The GRN is the buyer's document. They are not interchangeable.
- e-Way Bill accompanies the delivery, not the receipt — the e-Way Bill is a GST compliance document for goods in transit. The GRN is created by the buyer after goods arrive. They are separate documents serving different purposes.
- GRNI accruals under IndAS — expenses must be recognised when goods are received, not when invoices arrive. Timely GRN creation is a financial reporting requirement under Indian Accounting Standards.
Frequently Asked Questions
GRN stands for Goods Received Note. It is also sometimes called a Goods Receipt Note. Both terms refer to the same document — an internal record created by the buyer confirming that goods from a supplier have been received and inspected.
The GRN is created by the buyer's receiving or warehouse team — the people who physically receive and inspect the delivery. In automated systems, the GRN is created on a mobile device at the point of delivery.
No. A delivery note is created by the supplier and travels with the goods during shipment. A GRN is created by the buyer after inspecting the goods at the receiving location. They record the same delivery from two different perspectives — the supplier's and the buyer's.
Without a GRN, three-way matching cannot be completed. This means either the invoice is held (delaying payment) or the invoice is paid without verification (creating overpayment and fraud risk). Inventory records also cannot be accurately updated without a confirmed GRN.
A partial GRN is created when only some of the goods on a purchase order are delivered. The GRN records the quantity actually received. The PO remains open for the outstanding balance, awaiting a future delivery.
Under GST, ITC can be claimed only for goods that have been actually received. The GRN is the internal evidence of receipt. In a GST audit, the GRN — alongside the supplier's invoice and e-Way Bill — supports the ITC claim. Accurate GRN creation is therefore a GST compliance requirement, not just an operational practice.
A GRN is the document confirming receipt of goods. GRNI (Goods Received Not Invoiced) is a balance sheet accrual representing goods that have been received but for which no invoice has yet arrived. The GRN creates the basis for the GRNI accrual under accrual accounting standards.
Automate GRN creation at the point of delivery
Hubler's Procurement AI Agent creates GRNs via mobile app, ERP integration, delivery challan OCR, or ASN — connected directly to three-way matching before any invoice is approved for payment. Part of the full procure-to-pay suite.
See GRN Management in Hubler →