A GRN — goods receipt note — is the record of what actually arrived at your dock versus what the client said was coming. In a 3PL it does four jobs at once: it fixes the count all downstream inventory accuracy is built on, it starts the storage-billing clock, it captures the batch and expiry data FEFO depends on, and it stands as evidence when a client disputes an invoice. Every error is cheaper to catch at the GRN than anywhere after it.
Why count against the ASN instead of just receiving?
The ASN — the advance shipping notice, or whatever email passes for one — is the client’s claim. The GRN is the fact. The client announced forty pallets; the truck carried thirty-eight. Record “forty, received” because that’s what the paperwork said, and you have just adopted the client’s shortage as your own: six months later a cycle count comes up two pallets short, and the only available explanation is that your warehouse lost them. A GRN that counts against the ASN turns the same event into a discrepancy noted at the dock, on the record, while the truck is still in the yard.
Receiving is also a billable event in its own right — US-published anchors run $25–50 per pallet. Uncaptured receiving is one of the four places revenue leakage hides, and it has a rule of thumb: if the charge isn’t captured at receipt, it rarely gets captured at all.
What belongs on the GRN besides the count?
- Batch/lot and expiry: FEFO is impossible to retrofit — if expiry dates weren’t captured when the goods crossed the dock, no amount of software downstream can invent them.
- Condition and damage notes: recorded while the trucker is still at the dock and liability is still assignable — not discovered at pick time, months later.
- Putaway destination: real bin locations assigned at receipt, so the stock is findable from its first hour on your floor.
- The client: obvious, until a mixed floor has three inbounds on one afternoon — client-level segregation starts at the dock, not in the racking.
When does the storage clock start?
At the GRN date — which makes the GRN a billing document, not just an operational one. Storage snapshots count forward from it, long-term storage surcharge rules key off it, and when a client argues “we shipped those pallets out on the 12th, why are we billed to the 19th?”, the answer is the GRN date, the bin history and the dispatch confirmation, in sequence. Disputes end with evidence or they end with goodwill credits; the GRN decides which.
How does sloppy receiving compound downstream?
A wrong count at the dock becomes phantom inventory in the system, which becomes a mispick on the floor, which becomes a client portal showing stock that doesn’t exist, which becomes an order accepted that can’t ship. WMS vendors claim accuracy moves from roughly 85% to 99%+ post-implementation — vendor-sourced, so hold it loosely — but the direction is right, and it starts at receiving. Binsy makes the GRN the anchor record: counts against the ASN, batch and expiry captured, bins assigned, and the receiving charge written as a billing event before the truck leaves. The full receiving playbook is in the guide; what uncaptured receiving costs at your volumes is in the calculator.
From reading to the rack.
Bring one client's rate card and one month of invoices. We'll walk your flow through Binsy and show where the billing events would have written themselves.
Book a walkthrough