What Is a Goods Received Note (GRN)?
The document that turns "the delivery arrived" into a fact the system can trust — what a GRN records, why it must be independent of the buyer, and how it anchors the three-way match.
A Goods Received Note (GRN) is the record of what actually arrived — created at the moment goods are received, against the purchase order that ordered them. It states which items came in, in what quantity, in what condition, on what date, received by whom. It is the difference between "the supplier says they delivered 100" and "we counted 100 in", and that difference is where a surprising amount of money is defended or lost.
What a GRN records
- The linked PO — so what arrived can be checked against what was ordered, and the open balance updated.
- Item and quantity received — the counted reality, which may be less than, equal to, or more than the PO line.
- Condition on arrival — damage, short shelf life, wrong specification, all noted before anyone signs.
- Date and receiver — the who and when, which becomes part of the audit trail.
- Discrepancies — short deliveries, over-deliveries, and rejects, flagged rather than silently absorbed. A short delivery is also a costing event, since the freight already paid has to be carried by the goods that did arrive — see spread over what arrived.
A GRN is not a delivery note
The delivery note comes from the supplier and states what they say they sent. The GRN is created by you and states what you actually counted in. Signing the driver’s delivery note unread and calling it "received" is the single most common receiving failure — it records the supplier’s claim as if it were your verification. The GRN exists precisely to be the buyer’s independent record.
Why independence matters
The person who ordered the goods should not be the only person who confirms they arrived — otherwise a single individual can order, receive, and approve payment for goods that never came, and no document contradicts them. Independent receiving is a textbook segregation of duties control: the GRN is created by the store or receiving function, against the buyer’s PO, so two different hands touch the transaction before money moves. The note is only as honest as the count behind it, which is why receiving means weighing and counting at the door, not initialling paperwork.
The GRN as the anchor of the three-way match
The GRN is the middle document of the three-way match: PO (what was ordered) ↔ GRN (what was received) ↔ invoice (what is being charged). Without it, the match collapses into a two-way check — PO against invoice — which verifies that you agreed a price but never that the goods actually arrived. That is exactly the gap through which you pay for short deliveries and phantom stock. The GRN is what lets an invoice be paid on the strength of "we received this", not "we ordered this".
| Scenario at receiving | What the GRN records | What it prevents |
|---|---|---|
| Ordered 100, received 80 | GRN quantity 80; PO balance 20 stays open | Paying the full invoice for 100 |
| Ordered 100, received 110 | GRN flags 10 over-delivery for a decision | Silently absorbing (and paying for) unordered stock |
| Goods damaged on arrival | GRN notes condition; rejects excluded from stock | Damaged units entering inventory and being sold or issued |
| No delivery, invoice arrives | No GRN exists to match | Paying for goods that never came |
From paper pad to system record
On paper, the GRN is a pad in the store that finance never sees until month-end, and the match happens (if at all) as a manual reconciliation weeks later. In a system, receiving against the PO is the GRN: stock updates the instant goods are booked in, the PO, receiving, and matching live as linked documents, and any discrepancy surfaces immediately instead of at a quarterly audit. It is one step in the wider procure-to-pay flow — the step where a promise on paper becomes stock you can actually count.
What AWRA OpsHub does today
- Check-ins linked to the purchase order, updating stock immediately rather than at some later posting step.
- Batch, lot, expiry, manufacture date, supplier and source PO captured on receipt, which is what makes traceability and FEFO possible downstream.
- Warehouse and bin location recorded, so received stock has a place rather than a total.
- A reason drawn from a configured catalogue on every movement — the operation is refused if none is configured.
- Landed cost lines allocated across the receipt, feeding the weighted average cost.
- Payment held while the order does not reconcile, released only by someone with the authority to override and only with a recorded reason.
- An over-receipt guard, refusing a receipt that would exceed the ordered quantity beyond your configured tolerance, counting deliveries already booked against the same order.
- A file attached to the receipt — the supplier delivery note, signed and scanned, stored against the check-in.
- Trace events per batch and serial, so a receipt can be reconstructed later.
More we can add to your workspace
- Only two of the three legs are matched. Ordered against received is reconciled and shown on the order. The supplier invoice is not: no invoice lines are captured, so nothing checks what you were billed against what arrived.
- Refusing a short delivery outright, rather than booking it in as a discrepancy. A partial delivery books in and appears against the order as a discrepancy today, and that is deliberate: refusing goods that are physically on the floor is how a receiving process gets bypassed.
- An inspection or quality-hold step at receipt. Batches carry a quality status you can set today; a gate that holds stock pending inspection before it becomes available is the build.
This block previously said the opposite of two of these, in both directions, and both are worth stating plainly. It claimed nothing compared received against ordered at the door — that guard now exists, refuses an over-receipt before anything is written, and counts what was already received so a split delivery cannot creep past the ordered quantity one receipt at a time. It also claimed attachments were unavailable on the receiving record, which was never true: a check-in has always accepted a file, which is where your supplier delivery note goes. The remaining honest additions are the invoice leg and a payment gate.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsBook goods in against the PO, at the door
AWRA OpsHub turns receiving into a live check-in linked to the PO, updating stock instantly and recording batch, expiry and location at the door.
See receiving and matchingFrequently asked questions
What is the difference between a GRN and a delivery note?
The delivery note is issued by the supplier and states what they claim to have sent. The Goods Received Note is created by you and states what you actually counted and inspected on arrival. The GRN is your independent verification; the delivery note is the supplier’s claim. Signing the delivery note is not the same as raising a GRN.
Why should the person who ordered goods not be the one who receives them?
Because concentrating ordering, receiving, and payment approval in one person removes every check against fraud or error — they could authorise payment for goods that never arrived. Independent receiving (segregation of duties) means the GRN is created by a different hand than the PO, so the transaction is verified, not just asserted.
How does a GRN fit into three-way matching?
It is the middle document. Three-way matching compares the purchase order (ordered), the GRN (received), and the invoice (charged). The GRN is what proves goods actually arrived; without it you can only do a two-way match of PO against invoice, which confirms an agreed price but never confirms delivery.
Do small businesses need formal GRNs?
The principle scales down even if the paperwork does not. Count every delivery against the order before signing, note shortages and damage, and pay only against what was actually received. That is a GRN in spirit. The point where a scribbled pad stops coping — volume, multiple receivers, partial deliveries — is usually the signal to move receiving into a system.
