Aviy
TemplatesGoods Received NoteGRN TemplateGRN DocumentGoods Receipt NoteGRN In Procurement

Goods Received Note (GRN) Template Explained

Goods Received Note (GRN) Template Explained - Aviy AI invoicing
21 min read

A goods received note (GRN) is an internal document that records the quantity and condition of goods received from a supplier against a purchase order. It confirms what physically arrived, flags discrepancies or damage, and serves as the receiving record used to verify supplier invoices before payment is approved.

A goods received note template gives your business a consistent, repeatable way to record exactly what arrived from a supplier, in what quantity, and in what condition. It is the document that turns "the boxes showed up" into a verifiable record you can match against a purchase order and a supplier invoice before anyone approves payment. Used well, it protects your cash, catches short deliveries and damage, and gives your bookkeeper a clean audit trail.

If you have ever paid an invoice for 100 units and later discovered only 90 arrived, you already understand why the goods received note (GRN) exists. This guide explains what a GRN is, when you need one, every field a good template should contain, a realistic worked example, the mistakes that quietly cost businesses money, and the best practices that keep your receiving process tight.

What Is a Goods Received Note?

A goods received note is an internal document raised by the receiving party (you, the buyer) when goods are delivered. It records the items, quantities, and condition of everything that physically arrived, checked against the original purchase order. Unlike a delivery note, which is produced by the supplier and lists what they say they sent, a GRN is your own record of what you actually counted and accepted.

The GRN is one leg of what accountants call the three-way match: the purchase order (what you ordered), the goods received note (what arrived), and the supplier invoice (what you are being billed for). When all three agree, payment is safe to release. When they disagree, the GRN is the evidence that stops you overpaying.

A GRN is not usually a legal contract in itself, but it carries real weight. It is the point at which responsibility for the goods often transfers to the buyer, and it becomes a key piece of your accounting and audit records. For that reason it should be accurate, dated, and signed by whoever performed the check.

Why the receiving step matters

Receiving is the most overlooked control point in purchasing. The order is exciting, the invoice gets attention because it demands money, but the moment in between, when goods physically land on your dock, is where errors hide. A short shipment, a substituted product, or a damaged carton that nobody logs becomes a dispute you cannot win three weeks later. The GRN forces a deliberate check at exactly the right moment.

When Do You Need a GRN?

You do not need a GRN for every transaction, but you should use one whenever physical goods change hands against an order and accuracy matters. Typical triggers include:

  • Receiving stock or materials from a supplier against a purchase order
  • High-value deliveries where a discrepancy would be expensive
  • Partial or staggered deliveries where you need to track what has arrived versus what is outstanding
  • Goods that require inspection for quality, quantity, or condition before acceptance
  • Any environment with separated duties, where the person ordering is not the person receiving

A solo freelancer buying a single laptop online probably does not need a formal GRN. A growing agency ordering branded merchandise, a contractor taking delivery of materials on site, a retailer restocking inventory, or a startup receiving hardware for a new hire all benefit from one. The rule of thumb: if a mismatch between order, delivery, and invoice could cost you money or cause a dispute, raise a GRN.

The Essential Sections of a Goods Received Note Template

A strong goods received note template captures enough detail to be useful without becoming a chore to complete. Every GRN should contain the following fields.

  • GRN number - a unique, sequential reference for tracking and audit
  • Date of receipt - the actual date goods arrived and were checked
  • Supplier details - name, address, and contact
  • Purchase order number - links the GRN back to what was ordered
  • Delivery note / despatch reference - the supplier's document number, if provided
  • Delivery location - the site or warehouse that received the goods
  • Received by - name of the person who checked the delivery
  • Item lines - description, SKU or product code, unit, quantity ordered, quantity received, quantity accepted, quantity rejected
  • Condition / inspection notes - damage, defects, or quality issues per line
  • Discrepancy notes - short deliveries, over-deliveries, or substitutions
  • Outstanding / back-order quantity - what is still due for partial deliveries
  • Carrier / haulier - who delivered (useful for damage claims)
  • Signature and date - sign-off by the receiver, and optionally the driver
  • Approval / status - accepted, rejected, or accepted with exceptions

You do not need every field on every job, but a template should make them all available so nothing important gets skipped under pressure.

A Section-by-Section Breakdown

Here is how to think about each block of the template and why it earns its place.

Header: identification and traceability

The header is about traceability. The GRN number is your anchor; it should be unique and sequential so you can never have two notes with the same reference. Pair it with the date of receipt and the purchase order number so the document instantly connects to the rest of the paper trail. If your supplier sent a delivery note, record its number here too, this is what makes reconciliation fast later.

Supplier and delivery context

Record the supplier name and address, the delivery location, and the carrier who made the drop. The carrier matters more than people expect: if a pallet arrives crushed, your claim is often against the haulier, not the supplier, and you will need to have logged who delivered it and when.

The item lines: the heart of the GRN

This is where the real work happens. For each line, capture the description and product code, then three distinct quantity columns:

  • Quantity ordered - pulled from the purchase order
  • Quantity received - what physically arrived
  • Quantity accepted - what passed inspection and you are taking

Keeping "received" and "accepted" separate is the single most useful design choice in a GRN. Twelve units can arrive (received) while only ten are usable (accepted) because two were damaged. Without separate columns, that nuance disappears and you risk paying for goods you rejected.

Condition and discrepancy notes

Use this area to describe anything that is not perfect: dented packaging, broken seals, wrong color, missing components, or a count that does not match. Be specific. "Box 3 of 5 water-damaged, 6 units unusable" is evidence; "some damage" is not. Photographs, where possible, strengthen the record enormously.

Outstanding quantities for partial deliveries

If a supplier delivers in stages, the outstanding quantity column tells everyone what is still due. This keeps the purchase order "open" in your system and stops the invoice being approved for items that have not actually turned up yet.

Sign-off and status

Finally, the GRN needs a name, a signature, and a date. The sign-off is the formal acceptance step. Adding a status field (accepted, rejected, or accepted with exceptions) turns the GRN into a routing instruction: a clean GRN flows straight to accounts payable, while one with exceptions triggers a query to the supplier before anything is paid.

GRN vs Delivery Note vs Packing Slip vs Purchase Order

These four documents travel together and are constantly confused. Here is how they differ.

DocumentWho creates itWhat it provesWhen it is issued
Purchase orderBuyerWhat was ordered and agreedBefore goods ship
Delivery noteSupplierWhat the supplier says they sentShipped with the goods
Packing slipSupplierContents of a specific parcel or cartonInside or on each package
Goods received noteBuyerWhat actually arrived and was acceptedAt the point of receipt

The key distinction is direction and trust. The purchase order, delivery note, and packing slip all describe intentions or claims, the buyer's intention to order and the supplier's claim about what shipped. The goods received note is the only one of the four that records independently verified reality, checked and signed by the receiving party. That is precisely why it carries weight in disputes and why accounts payable relies on it rather than on the supplier's own paperwork.

For deeper comparisons, the related guides on the delivery note template and packing slip template walk through those documents in detail.

A Realistic Goods Received Note Example

Meet Priya, who runs a six-person branding agency. She orders 200 printed brochures and a roll-up banner from a print supplier for a client launch. The purchase order (PO-2041) goes out, and three days later the courier drops two boxes at reception.

Priya's office manager, Daniel, opens the boxes and raises a GRN rather than just signing the courier's handheld device and moving on. He fills in:

  • GRN number: GRN-0087
  • Date received: 18 June 2026
  • Supplier: Northgate Print Ltd
  • PO number: PO-2041
  • Delivery note ref: DN-5532
  • Carrier: SwiftCourier

His item lines look like this:

  • Brochures, A5 gloss (SKU BRO-A5): ordered 200, received 200, accepted 185, rejected 15 - note: "15 brochures smudged on back cover, set aside"
  • Roll-up banner, 850mm (SKU BAN-850): ordered 1, received 1, accepted 1, rejected 0 - note: "good condition"

Daniel marks the status as accepted with exceptions, signs, and dates it. He photographs the smudged brochures and attaches the image to the GRN.

Two days later, Northgate's invoice arrives for the full 200 brochures and the banner. Because the GRN clearly shows only 185 brochures accepted, Priya queries the invoice, Northgate issues a credit note for the 15 rejected units, and the agency pays only for what it actually used. Without the GRN, that $40 overcharge would almost certainly have been paid, and on a larger order the same gap could be hundreds or thousands.

That small document, raised in five minutes, did three things: it protected cash, gave the supplier clear evidence to act on, and left a clean record for the agency's bookkeeper at month end.

How the GRN Fits Into Your Purchasing Workflow

A goods received note is not a standalone form; it is a link in a chain. Here is the typical end-to-end flow and where the GRN sits.

  1. Requisition - someone identifies a need (often via a purchase requisition form).
  2. Purchase order - you issue a PO to the supplier confirming items, quantities, and prices.
  3. Despatch - the supplier ships the goods with a delivery note and packing slips.
  4. Receipt and GRN - you check the delivery, raise the GRN, and record received versus accepted quantities.
  5. Three-way match - accounts payable compares PO, GRN, and supplier invoice.
  6. Approval and payment - if all three agree, the invoice is approved and paid; if not, the GRN evidence drives a query, a credit note, or a price adjustment.
  7. Inventory update - accepted quantities update your stock records.

The GRN is the hinge between the physical world (goods arriving) and the financial world (invoices and payments). Skip it and you lose the ability to verify what you are being billed for. For businesses formalising this whole chain, the purchase order handbook and invoice approval workflow guides show how the pieces connect.

Where the GRN feeds inventory and accounting

Once accepted quantities are confirmed on the GRN, two downstream systems update. First, your inventory records increase by the accepted quantity only, never the received quantity, so rejected stock never appears as sellable. Second, in accrual accounting the receipt of goods can create a "goods received, invoice not received" accrual, recognizing the liability at the point of receipt rather than when the invoice lands. This keeps your books aligned with reality at period end and is exactly the kind of cut-off accuracy an auditor looks for. If your bookkeeper has ever struggled to reconcile stock value against purchases, the missing link is almost always a weak or absent GRN step.

Separation of duties

A well-run workflow deliberately splits responsibilities: one person raises the purchase order, a different person receives and signs the GRN, and a third approves the invoice for payment. This separation is a basic internal control that makes fraud and error far harder, because no single individual controls a purchase from order to payment. Even in a small team, having the GRN signed by someone other than the person who placed the order materially strengthens the control.

Pros and Cons of Using a Formal GRN Process

A GRN process adds a small amount of admin in exchange for meaningful control. Here is the honest trade-off.

Pros

  • Prevents overpayment by matching invoices to what actually arrived
  • Catches short deliveries, damage, and substitutions at the right moment
  • Creates a clear audit trail for bookkeeping and external audits
  • Clarifies the point at which responsibility for goods transfers to you
  • Strengthens claims against suppliers and carriers when something goes wrong
  • Keeps inventory records accurate by recording accepted quantities only

Cons

  • Adds a step to the receiving process that takes a few minutes per delivery
  • Requires discipline; a GRN nobody completes properly is worse than none
  • Can feel like overkill for very small or one-off purchases
  • Needs a numbering system and a place to store completed notes
  • Manual paper GRNs are easy to lose and hard to reconcile at scale

For most growing businesses the pros decisively outweigh the cons, especially once the process is digital and the few minutes per delivery are largely automated.

GRN Formats: Paper, Spreadsheet, or Software

The same set of fields can live in very different formats, and the format you choose shapes how reliable the process actually is in practice.

Paper GRN books

The traditional approach is a duplicate or triplicate GRN pad: one copy stays in the book, one goes to accounts, one is filed with the delivery paperwork. Paper works for low volumes and needs no technology, but it has real weaknesses. Handwriting is misread, copies go missing, totals are added up wrong, and reconciling a stack of notes at month end is slow. If you receive only a handful of deliveries a month, paper is workable, but it does not scale.

Spreadsheet GRNs

A spreadsheet template in Word or Excel is the natural next step. It is free, easy to customize, and lets you store completed notes in folders. The downside is that spreadsheets do not enforce discipline: numbers can be skipped, the same GRN reference can be typed twice, and there is no automatic link to the purchase order or invoice. You also lose version control the moment two people edit separate copies. Spreadsheets suit small teams who want structure without committing to dedicated software.

Software-generated GRNs

The most reliable approach generates the GRN from the purchase order inside a system that also holds your POs and invoices. Item lines and ordered quantities pre-fill automatically, numbering is assigned sequentially with no duplicates, and the three-way match can run with little or no manual effort. The receiver only enters received and accepted quantities plus notes. This removes transcription errors, makes reconciliation instant, and keeps an immutable audit trail. For any business receiving deliveries weekly, the time saved quickly justifies the move.

The right choice depends on volume and risk. A useful rule: as soon as you find yourself manually reconciling GRNs against invoices and it takes real time, you have outgrown paper and spreadsheets.

Common Mistakes to Avoid

Even businesses that use GRNs often undermine them with avoidable errors. Watch for these.

Treating "received" and "accepted" as the same thing

If your template has only one quantity column, you cannot record that goods arrived but were rejected. Always separate received from accepted so damaged or wrong items are visible and never silently paid for.

Signing before checking

Signing the courier's device or the GRN before actually counting and inspecting the goods defeats the entire purpose. The signature should mean "I have verified this," not "the boxes are here." Once you sign for a clean delivery, disputing a shortage later becomes very hard.

Vague discrepancy notes

"Some damage" or "looks short" gives a supplier nothing to act on and weakens any claim. Be specific about quantities, locations, and the nature of the problem, and attach photos where you can.

A GRN without a PO number floats free of context. The PO link is what lets accounts payable perform the three-way match and what makes reconciliation fast rather than forensic.

Skipping the GRN on partial deliveries

Partial deliveries are exactly when a GRN matters most, because they are where invoices and stock most easily drift out of sync. Always record what arrived and what remains outstanding, even if it feels fiddly.

Inconsistent or duplicate numbering

Two GRNs with the same number, or a numbering scheme that resets unpredictably, breaks traceability. Use a single sequential series so every note is unique and findable.

Best Practices for Goods Received Notes

Follow these practices to make your GRN process fast, reliable, and audit-ready.

  1. Use sequential GRN numbers. A single unbroken numbering series makes every note traceable and instantly tells you if one is missing.
  2. Check before you sign, every time. Count quantities and inspect condition against the PO before accepting. Note exceptions on the spot.
  3. Always reference the purchase order. The PO number is the thread that ties order, receipt, and invoice together for three-way matching.
  4. Separate received from accepted quantities. This is non-negotiable for catching damage and short deliveries.
  5. Photograph damage and discrepancies. A timestamped photo attached to the GRN is far stronger evidence than a written note alone.
  6. Make the GRN mandatory for invoice approval. No GRN, no payment. This closes the biggest overpayment loophole.
  7. Store GRNs digitally and centrally. Paper notes get lost; a searchable digital store means you can reconcile and audit in seconds. The guides on digital filing systems and document automation are useful here.
  8. Review exceptions promptly. A GRN marked "accepted with exceptions" should trigger a same-week query to the supplier so credit notes are issued while the delivery is fresh.
  9. Keep the template simple enough to complete under pressure. A receiving team that is busy will skip a form that demands too much. Capture what matters and no more.

Summary

A goods received note template is a small document with an outsized impact on cash control. It records what actually arrived against what you ordered, flags damage and shortages at the only moment you can prove them, and gives accounts payable the evidence to verify supplier invoices before payment. The essential fields, GRN number, date, supplier, PO reference, item lines with separate received and accepted quantities, condition notes, outstanding amounts, and a signed sign-off, are what turn a casual delivery into a controlled, auditable event.

Treat the GRN as the hinge in your purchasing workflow between goods arriving and invoices being paid, keep the numbering clean, always check before you sign, and make it mandatory for invoice approval. Do that, and you will stop paying for goods you never received, resolve supplier disputes with evidence rather than memory, and keep your inventory and books accurate. Whether you are a solo consultant buying equipment or an agency restocking client materials, a disciplined goods received note process is one of the simplest controls you can put in place.

Frequently asked questions

What is a goods received note?

A goods received note (GRN) is an internal document the buyer raises when goods are delivered. It records the items, quantities, and condition of everything that physically arrived, checked against the original purchase order. The GRN confirms what was actually received and accepted, flags any damage or shortages, and becomes the receiving record used to verify supplier invoices before payment is approved.

What should a goods received note template include?

A complete GRN template should include a unique GRN number, date of receipt, supplier details, purchase order number, delivery note reference, delivery location, and the receiver's name. The item lines should show description, product code, quantity ordered, quantity received, quantity accepted, and quantity rejected, plus condition and discrepancy notes, outstanding back-order amounts, carrier details, and a signed sign-off with a status.

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

A delivery note is created by the supplier and lists what they say they sent. A goods received note is created by the buyer and records what actually arrived and was accepted after checking. The delivery note is a claim; the GRN is independently verified reality. Because the GRN reflects a physical count, accounts payable relies on it rather than the supplier's paperwork.

Who is responsible for raising a goods received note?

The receiving party raises the GRN, usually the person or team that physically takes the delivery, such as a warehouse operative, office manager, or site supervisor. Ideally this is someone other than whoever placed the order, so duties are separated. The receiver counts and inspects the goods, completes the note, and signs it to formally accept the delivery.

How does a GRN fit into three-way matching?

Three-way matching compares three documents: the purchase order (what you ordered), the goods received note (what arrived), and the supplier invoice (what you are billed for). When all three agree, the invoice is safe to pay. When they disagree, the GRN provides the evidence to query the invoice, request a credit note, or adjust payment, preventing overpayment.

A GRN is generally an internal business record rather than a standalone legal contract. However, it carries significant practical and evidential weight: it often marks the point at which responsibility for the goods transfers to the buyer, supports claims against suppliers or carriers, and forms part of your accounting and audit trail. For specific legal questions, consult a qualified professional in your jurisdiction.

Do small businesses need a goods received note?

Not for every purchase, but a GRN is worth using whenever a mismatch between order, delivery, and invoice could cost money or cause a dispute. High-value items, partial deliveries, goods needing inspection, and any setup where the buyer and receiver are different people all benefit. A simple, lightweight GRN protects cash and creates a clean record even for very small teams.

What is the difference between quantity received and quantity accepted?

Quantity received is everything that physically arrived; quantity accepted is the portion that passed inspection and you are taking. They differ when items are damaged, wrong, or fail a quality check. Keeping them as separate columns is the most useful feature of a GRN, because it ensures you only pay for goods you actually accepted, not for rejected stock.

How should I number my goods received notes?

Use a single, unbroken sequential series, for example GRN-0001, GRN-0002, and so on, so every note is unique and traceable. Avoid resetting the sequence unpredictably or allowing duplicate numbers, as that breaks the audit trail. Digital systems can assign numbers automatically, which removes human error and makes it obvious if a note is ever missing.

Can I create a GRN for a partial delivery?

Yes, and you should. Partial deliveries are exactly where invoices and stock records drift out of sync. Record the quantity received for the items that arrived, mark the outstanding quantity still due, and keep the purchase order open. When the remaining goods arrive, raise a further GRN against the same PO so the full order is accounted for accurately.

Conclusion

A goods received note template is one of the highest-leverage documents a buyer can standardize. It captures what actually arrived, separates received from accepted quantities, flags damage and shortages at the only moment they can be proven, and feeds the three-way match that keeps you from paying for goods you never got. Get the fields right, keep numbering clean, and make the GRN mandatory before any invoice is approved.

Whether you are a freelancer buying equipment, a contractor receiving materials, or an agency restocking client supplies, building a disciplined goods received note process protects your cash, sharpens your inventory records, and gives every supplier dispute an evidence base. Pair it with consistent purchase orders and a clean invoice approval flow, and your purchasing operation becomes accurate, auditable, and far harder to overcharge.

Sources and further reading