GRN (Goods Received Note): The Complete Guide

A goods received note, or GRN, is the buyer's record of what actually arrived when a delivery is made: the items, the quantities and the condition, checked and confirmed against the original order. It is a small document with an outsized role, because it is the proof of receipt that stands between an order being placed and an invoice being paid. This guide explains what a GRN is, what it contains, who raises it, where it sits in the procure-to-pay flow, how it powers three-way matching, how to handle discrepancies, and how software makes the whole thing automatic.

What is a goods received note?

A goods received note is a document the buyer creates at the moment a delivery arrives, recording exactly what was received against what was ordered. It captures the items, the quantities delivered, and the condition of the goods, and it ties that record back to the original order through a shared reference number. In short, it is the buyer's own account of the delivery, written from the receiving dock rather than from the supplier's warehouse.

The GRN matters because it converts a physical event, goods landing on the loading bay, into a formal record that the rest of the organisation can rely on. Finance needs to know that goods were received before it pays for them. Stores needs to know what has entered inventory. Auditors need evidence that a payment corresponds to a genuine receipt. The GRN answers all three questions with a single, dated, signed document.

Because it is raised by the buyer and not the supplier, the GRN is an independent check rather than a restatement of the supplier's paperwork. The supplier will send a delivery note claiming what they dispatched, but the GRN records what genuinely turned up after someone counted and inspected it. That distinction, the buyer's verified truth versus the supplier's claim, is the entire reason the document exists and the reason it carries weight in the wider procurement process.

The purpose of a GRN

A GRN serves several purposes at once, and it helps to separate them because each one protects the organisation in a different way. Taken together they explain why disciplined buyers refuse to pay an invoice that has no receipt behind it.

• Confirming delivery. The GRN is documentary proof that goods actually arrived, not merely that they were ordered or invoiced.
• Verifying quantity. It records the number of units received so any short delivery or over delivery is caught at the door rather than on the invoice.
• Checking condition. It notes damage, defects or wrong items, so faulty goods are rejected before they enter stock or get paid for.
• Updating inventory. It triggers the stock record, so what has physically entered the warehouse is reflected in the system.
• Supporting payment. It provides the receipt evidence that accounts payable matches against the order and the invoice before releasing money.

The common thread is verification. Every purpose above is a form of checking reality against expectation: did the right goods, in the right number, in the right state, actually arrive? By capturing that answer the moment the delivery lands, the GRN stops small problems, a missing carton, a cracked unit, the wrong model, from quietly flowing through to inventory and payment where they are far harder and more expensive to unwind.

What a goods received note contains

A useful GRN leaves no room for doubt about what happened at delivery. Layouts vary between organisations and systems, but a complete goods received note covers a predictable set of fields that together describe the receipt in full:

Alongside those core fields, a GRN commonly carries the delivery note number from the supplier, the carrier or transport reference, a place to flag partial deliveries, and a signature or system sign-off confirming the check was done. The linked purchase order number is the thread that runs through the whole transaction: quote it on the delivery and the GRN, and matching the eventual invoice becomes almost effortless.

Precision here is not bureaucracy, it is protection. A GRN that simply says goods arrived tells finance nothing useful. A GRN that records eight of ten units received, two rejected for damage, checked and signed by a named person on a stated date, is a document that settles disputes, supports an accrual and survives an audit. The few extra seconds spent recording condition and shortfalls save hours of argument later.

Who raises a GRN and when

The GRN is raised by the buyer, and specifically by the people who physically receive the delivery. In most organisations that means the goods-in, stores or warehouse team, though in smaller businesses it may be an office manager or whoever signs for the parcels. The point is that it is created by the receiving side, at the moment of receipt, by someone who can see and count the goods in front of them.

The timing is what gives the GRN its value. It is completed at delivery, not reconstructed later from memory or from the invoice. When the delivery arrives, the receiver opens the goods, counts them against the supplier delivery note and the purchase order, inspects them for damage, records the result, and signs off. Anything raised days after the fact, or copied straight from the supplier's paperwork without a physical check, is not really a GRN at all; it is a rubber stamp that defeats the control.

This separation of duties also matters for control. The person who raises the order is often not the person who receives it, and the person who pays the invoice is usually a third team. Because the GRN is created independently by the receiver, it acts as a check on both the order and the bill, which is exactly why it is trusted as evidence in the payment process.

The GRN in the procure-to-pay flow

A GRN is not a standalone document but one step in the controlled flow that runs from the first request to the final payment, often called procure-to-pay. Seeing where it sits makes its role obvious, because each stage hands something to the next:

• Requisition and approval. Someone raises an internal request to buy, which is approved by a budget holder.
• Purchase order. The approved request becomes a purchase order and is issued to the supplier.
• Delivery. The supplier ships the goods with a delivery note describing what they claim to have sent.
• Goods received note. The receiving team checks the delivery against the PO and raises the GRN confirming what actually arrived.
• Invoice and match. The supplier issues an invoice, which is matched against the PO and GRN before payment is released.

The GRN is the hinge between ordering and paying. Everything before it is about intent and commitment, what the organisation decided to buy. Everything after it is about settlement, paying for what was supplied. The GRN is the point where the physical world is checked in, converting a promise of delivery into a confirmed fact that the invoice can finally be measured against.

Skip this step and the chain breaks. Without a GRN, accounts payable has no independent evidence that the goods on the invoice ever arrived, and is reduced to trusting the supplier's bill. The receipt is the link that lets a well run buying process pay with confidence rather than on faith, which is why it belongs to the same discipline that governs a modern supply chain.

GRN and three-way matching

The single most important control the GRN enables is three-way matching. Before an invoice is paid, three documents are compared: the purchase order, which records what was ordered; the goods received note, which records what actually arrived; and the supplier accounts payable invoice, which records what is being billed. When all three agree on quantity and price, the invoice is approved. When they do not, the exception is flagged for a human to resolve.

The GRN is the middle document, and without it the match collapses into a two-way comparison of the order and the invoice, which proves only that the bill matches the order, not that the goods ever came. With the GRN in place, an invoice is paid only when what is billed matches both what was ordered and what was genuinely received. That is what blocks payment for short deliveries, damaged goods and quantities that never turned up, and it is the quiet, systematic defence against both honest error and deliberate fraud.

Discrepancies and how to handle them

Deliveries do not always match orders, and the GRN exists precisely to catch the gaps. The value of the document is not that it assumes everything is fine but that it forces someone to record when it is not. The common discrepancies are easy to name and each has a sensible response:

• Short delivery. Fewer units arrived than ordered. Record the quantity actually received on the GRN, so any invoice for the full amount is stopped at matching.
• Over delivery. More units arrived than ordered. Note the excess and follow policy on whether to accept, store or return it, rather than let it slip into stock unpriced.
• Damaged or defective goods. Reject the affected units on the GRN, note the reason, and raise the issue with the supplier for replacement or credit.
• Wrong items. Record that the delivered goods do not match the order lines, and hold them separately pending return or correction.
• Partial delivery. Log what arrived and keep the order open for the balance, so the outstanding quantity is tracked to completion.

The discipline is the same in every case: record what really happened, do not sign off a clean receipt for a messy delivery, and let the accurate GRN drive the downstream response. A recorded shortfall means the invoice for the full quantity is automatically flagged. A recorded rejection means damaged goods are never paid for. The moment a receiver signs a GRN that does not reflect reality, the whole control fails, so honest recording at the dock is the single most important habit in goods receipting.

Benefits and controls

Organisations that insist on a GRN for every delivery are not adding paperwork for its own sake; they are buying a set of concrete advantages that informal receipting cannot offer. The benefits stack up across finance, operations and governance.

The first is payment protection. Because no invoice is paid without a matching receipt, the GRN blocks payment for goods that never arrived, arrived short or arrived damaged. It turns accounts payable from a trusting function into a verifying one, and it is the practical reason three-way matching stops overcharges before the money leaves rather than clawing it back afterwards. The second is inventory accuracy: because the GRN triggers the stock record, what the system shows in the warehouse reflects what physically entered it, which keeps stock counts, reorder points and valuations honest.

The third is auditability and control. A complete GRN trail gives auditors independent evidence that payments correspond to real receipts, supports accurate accruals at period end, and demonstrates that a proper separation of duties was observed between ordering, receiving and paying. Together these controls make spending defensible and reporting reliable. To see how receipt, order and invoice fit a modern buying platform, explore the ProcureWave procurement solution.

How software automates GRNs

Running goods receipting on paper or spreadsheets is slow and error-prone. Delivery notes are filed in one place and purchase orders in another, GRNs are re-keyed from handwritten forms, and matching an invoice means hunting for the right receipt by hand. Every manual step adds delay and a chance to make a mistake, which is why procurement teams of every size have moved goods receipting into software.

An automated system pulls up the open purchase order at the receiving dock, lets the goods-in team confirm or adjust quantities against it, capture condition and rejections, and raise the GRN in a few taps without re-typing anything. The moment the receipt is recorded, inventory updates and the GRN is available for matching. When the supplier invoice arrives, the software performs the three-way match automatically and only surfaces the exceptions, short deliveries, price mismatches, missing receipts, that need a human. What used to take days of chasing paper happens in minutes, and every step is logged for audit.

That is exactly what ProcureWave is built to do: connect the purchase order, the goods received note and the invoice into one auditable flow so receipts are captured accurately, stock stays current and matching is automatic. If you want to see goods receipting and three-way matching run end to end on your own deliveries, book a demo with our team.

The goods received note is one of the most important documents in buying because it is where a promised delivery becomes a confirmed, auditable fact. Get the GRN right, make raising it at the point of receipt routine, and record discrepancies honestly, and you gain payment protection, accurate inventory and a clean trail from the first order to the final payment.

Frequently asked questions

What is a GRN (goods received note)?

A goods received note, or GRN, is a document raised by the buyer when a delivery arrives. It records what was actually received, in what quantity and in what condition, and confirms it against the original order. The GRN is the proof of receipt that later supports payment.

Who raises a goods received note?

The buyer raises the GRN, not the supplier. Usually a warehouse, stores or goods-in team completes it at the point of delivery by checking the physical goods against the purchase order and the supplier delivery note before signing off.

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

A supplier sends a delivery note stating what they claim to have shipped. The buyer creates the GRN to record what was genuinely received after checking. The delivery note is the supplier's claim; the GRN is the buyer's verified confirmation.

How does a GRN fit into three-way matching?

Three-way matching compares the purchase order, the GRN and the supplier invoice before payment. The GRN supplies the middle proof of what actually arrived, so an invoice is only paid for goods the receipt confirms were received in good order.

Is a GRN a legal or accounting document?

A GRN is not an invoice and does not itself demand payment, but it is an important control and accounting record. It evidences receipt, supports stock and accruals, and provides the audit trail that links an order to the payment made against it.