Accounts payable and payment controls
What Is a Goods Received Note? GRN Control Guide
Direct answer
A Goods Received Note, or GRN, is an internal record of goods delivered to a location and the quantity accepted after receiving checks. It connects physical receipt to the purchase order, inventory and supplier invoice. A GRN should distinguish delivered, accepted, rejected and short quantities; it is operational evidence and not the supplier’s tax invoice or a universal statutory form.
Acronym: GRN. Also known as: goods receipt note, material receipt note.
Key takeaways
- A GRN records accepted receipt; it should not convert damaged or missing units into usable inventory.
- Delivered, accepted, rejected and short quantities must remain separate so AP can pay only supported value.
- The receiver should create the record at the receiving point using source evidence, not from the later supplier invoice.
- A GRN is an internal control document, while GST invoice and credit-note requirements come from separate legal records.
- Reliable GRN data feeds the next learning-path control: three-way matching.
What a GRN does in procure-to-pay
The GRN gives the business a timestamped answer to a basic question: what did this location actually accept? It links a delivery to the purchase order, warehouse, receiver and item lines. Inventory can use accepted quantity; AP can compare it with the invoice; procurement can pursue shortages; quality teams can track rejection reasons.
Operational guidance: create the GRN from the physical count and inspection, preferably while the vehicle and delivery documents are available. Do not copy invoice quantity into the GRN merely to close an exception. The CGST Act includes receipt of goods or services among conditions relevant to input tax credit, but it does not make a particular internal GRN format a universal statutory document. Tax eligibility requires a separate facts-and-law review.
Fields that make a GRN useful
| Field group | Examples | Control purpose |
|---|---|---|
| References | GRN number, PO number, supplier challan, vehicle or shipment reference | Connect records without relying on free text |
| Receipt context | Location, dock, date and time, receiver | Establish where and by whom goods were checked |
| Line detail | Item code, description, batch, unit of measure | Avoid matching the wrong product or pack size |
| Quantity states | Ordered, delivered, accepted, rejected, short | Keep physical outcomes visible |
| Quality evidence | Reason code, photographs, inspection reference | Support rejection and supplier follow-up |
Use immutable source timestamps and record later corrections as adjustments with approver identity. A changed GRN should not erase the original receiving event.
A controlled receiving workflow
- Identify the PO and delivery location before unloading.
- Count goods independently of the invoice total and verify item and unit of measure.
- Inspect condition, batch, expiry or other quality attributes relevant to the product.
- Separate accepted units from quarantined or rejected units physically and in the record.
- Record shortages and over-deliveries rather than forcing quantity to the PO.
- Attach the delivery challan, photographs and inspection evidence.
- Post accepted quantity to inventory and send exceptions to procurement and AP.
- Require independent approval for material corrections or back-dated receipts.
The exact sequence is company policy. For high-velocity sites, barcode scans and blind counts can reduce keying and expectation bias, but exception ownership still matters.
Quick-commerce shortage and rejection example
Fictional example: FlashBasket’s dark store orders 800 chilled beverage packs from FreshArc Foods at ₹95 per pack, excluding tax. The vehicle delivers 786 packs. During receiving, 12 delivered packs are crushed and rejected, leaving 774 accepted.
| Status | Quantity | Value at ₹95 | Action |
|---|---|---|---|
| Ordered | 800 | ₹76,000 | PO reference |
| Not delivered | 14 | ₹1,330 | Shortage claim |
| Delivered but rejected | 12 | ₹1,140 | Segregate and document damage |
| Accepted | 774 | ₹73,530 | Post to usable inventory |
The supplier invoice bills 800 packs for ₹76,000. AP supports ₹73,530 before tax and holds ₹2,470 covering 26 units. The GRN records both causes instead of a single net variance. Procurement requests a credit note or agreed replacement; the business reviews GST treatment against the actual resolution and applicable documents.
How a GRN affects inventory and payment
| Quantity state | Inventory treatment | AP treatment |
|---|---|---|
| Accepted | Available or routed to quality status under policy | Eligible for matching to PO and invoice |
| Quarantined | Not available for normal use | Hold until inspection outcome is evidenced |
| Rejected | Exclude from usable stock; track return disposition | Block value pending replacement or credit |
| Short | No stock receipt | Block unmatched invoice quantity |
| Over-delivered | Segregate or record under policy | Do not pay without approved commercial resolution |
Inventory and AP may use different statuses, but they should reconcile to the same physical facts.
GRN review controls and warning signs
- Monitor GRNs created long after delivery or just before an invoice is released.
- Review repeated corrections by receiver, supplier, site and reason.
- Block one delivery reference from producing duplicate active receipts.
- Compare rejected stock physically with return-to-vendor or disposal records.
- Reconcile open PO quantity to accepted receipts, cancellations and approved amendments.
- Age uninvoiced receipts and invoices waiting for receipt evidence separately.
- Restrict users who receive goods from approving supplier invoices or payments where practical.
These controls are operating recommendations, not statutory audit procedures. Scale them to volume, materiality and product risk.
Frequently asked questions
Is a GRN the same as a delivery challan?
No. The supplier or transporter generally provides the delivery challan, while the receiving business creates the GRN to record its own count, inspection and acceptance outcome.
Is a GRN the same as a tax invoice?
No. A tax invoice is the supplier’s document and must be evaluated against applicable GST requirements. A GRN is the buyer’s internal receipt record.
Should rejected goods appear on the GRN?
Yes. Show them separately from accepted goods with a reason and evidence. Omitting them can overstate usable inventory and conceal why invoice quantity was blocked.
Can a GRN be corrected?
Yes under controlled policy. Preserve the original entry, correction reason, supporting evidence, time and independent approver instead of silently overwriting the receiving event.
What happens after a GRN is posted?
Accepted lines become available to inventory processes and three-way matching. Short, rejected, excess or unidentified lines move to exception owners for resolution.
Sources and further reading
- Legislative Department, India Code: Central Goods and Services Tax Act, 2017Verified Jul 25, 2026
- Central Board of Indirect Taxes and Customs: Tax Invoice, Credit and Debit Notes - Invoice RulesVerified Jul 25, 2026
Educational disclaimer: This material is general information, not legal, tax, or accounting advice. Check current official guidance and your facts with a qualified professional.
From definition to workflow
Apply this concept with connected finance operations
Finnoto connects source records, approvals, reconciliation evidence, and exception ownership so teams can move from knowing the rule to operating the control.
Explore accounts payable controls