Zepth Vector · Procurement

Delivery Notes & GRN

Three documents describe every delivery, and only one of them is yours.

Last updated

Zepth Vector module

Delivery Notes & GRN

AI agent built into the module
Per-line delivered / accepted / rejectedGate-side exception captureCumulative PO draw-downSame-day inventory posting

50–60%

of a project’s direct cost is materials — and the gate is the only cheap place to verify them

Industry cost structure

1–3%

of delivery lines carry a discrepancy — short, damaged, or simply wrong

Cross-industry receiving benchmarks

A borrowed number, and we say so. No robust construction-specific short-delivery rate exists — we are not going to invent one on the page about verifying what suppliers claim.

$1B

the upper end of estimated annual US construction site theft — with under 25% ever recovered

US industry bodies’ estimates (NER / NICB)

Estimates, and dated ones. The number is soft; the mechanism is not — stock nobody logged is stock nobody misses.

Overview

The delivery note is the supplier’s claim about what was shipped. The bill of lading is the carrier’s contract of carriage. The goods received note is the buyer’s independent record of what actually arrived, was counted, and was accepted.

Only the GRN is yours. It is the only delivery document the contractor controls, and it is the linchpin of everything downstream: inventory, matching, payment.

Why goods receipt is critical

Materials run to 50–60% of a project’s direct cost, and the gate is the only cheap place to verify them. Everywhere downstream — the laydown area, the workface, the invoice, the recovery audit — verification costs more and proves less.

Cross-industry receiving benchmarks put delivery discrepancies at 1–3% of lines. That is a borrowed figure and we label it as one: no robust construction-specific short-delivery rate exists, and we are not going to manufacture one on a page about verifying other people’s claims. But apply even the low end to a project buying $50 million of materials and you are looking at real money walking out through short deliveries, damage and wrong items.

Then there is theft. US industry bodies estimate construction site theft of materials and equipment in the hundreds of millions to a billion dollars annually, with recovery rates under 25%. Those are estimates, and dated ones. The mechanism, though, is not in doubt, and it is the whole argument for this module: unrecorded receipts are the environment theft thrives in, because stock nobody logged is stock nobody misses.

And the paper-ticket problem compounds all of it. Concrete, asphalt and aggregates arrive with batch tickets that die in cab dashboards and site-cabin drawers. At month end the quantity surveyor reconciles the invoices against an incomplete stack of tickets — and pays anyway, because the concrete is clearly in the building and the alternative is a fight nobody has the evidence to win. The US highway sector found that argument compelling enough to move to e-ticketing at scale. The same logic applies to every commercial site still running on carbon paper.

The role of the GRN in project performance

  • The signature is evidence — spend it carefully. The classic failure has a name on every site: signed for 100, received 90. The gateman signs the supplier’s delivery note under pressure, because the driver is blocking the gate and there is a queue behind him. The count happens later, at the laydown area. And the shortage surfaces after the signature has already become the supplier’s proof of full delivery. The disciplines are simple and nobody does them: count before you release the truck, or sign “received unexamined — subject to count”. Write exceptions on the supplier’s own copy and get the driver to countersign. Raise the GRN the same day.

  • Accepted is not the same as delivered. A proper GRN records three numbers per PO line, not one: delivered, accepted, and rejected — with a reason code on the rejection. Short, damaged, wrong specification, no purchase order. And quality-sensitive materials get a second gate: the material inspection against the approved submittal. The two records have to connect, because if they do not, rejected material gets paid for while its replacement goes untracked, and you have managed to pay twice for one delivery.

  • Partial deliveries need cumulative arithmetic. Rebar, blockwork and cable arrive over weeks against a single purchase order. Every delivery gets its own GRN referencing the same PO line, so the cumulative received quantity is visible at any moment. Without that, the final delivery matches against the full PO quantity — and over-delivery, or a duplicate invoice, walks straight through the hole that three-way matching exists to close.

  • Receipt has to land in inventory immediately. The gap between “received at the gate” and “booked to store” is where materials evaporate. Theft, cannibalisation by another work front, double-issue. Same-day posting to project inventory — with a location and a bin, not just a quantity — closes that gap, and it kills the duplicate requisition, which is one of the quiet drivers of construction’s material waste.

  • Authority to receive is a policy, not an accident. After-hours concrete signed for by a security guard — a person with no idea what was ordered, no way to check it, and no authority to accept it — is how disputes get born at two in the morning. Name your authorised receivers. Hold unmanned-hours deliveries in quarantine status until somebody who knows what they are looking at has counted them. A security guard’s signature is not acceptance.

What happens without receiving discipline

No GRN, so invoices match against the purchase order alone — which means you are paying for undelivered quantities, invisibly, on a cost base that is more than half materials.

Unqualified signatures at the gate, so shortage claims are impossible to make, so the site quietly re-orders the shortfall at full price and the original loss is never even recognised as a loss.

Rejected goods never linked to a return, so they get paid for, and the credit is chased for months and eventually written off. Receipts never posted to inventory, so the stock is invisible, so somebody orders it again.

Every one of those costs multiples of the sixty seconds the gate check would have taken.

How Zepth runs delivery notes and GRNs

Receiving is a field workflow rather than a paper trail. Deliveries are logged against their PO lines with accepted and rejected quantities recorded per line, photographs attached, and discrepancies captured at the gate while the driver is still standing there — which is the only moment they can be resolved cheaply.

Accepted stock posts to project inventory on acceptance, with its location. Rejected stock goes to quarantine and is tracked until it physically leaves.

And every GRN feeds the three-way match automatically, linking to its material inspection where one applies. One connected record, from the truck to the payment — so what you pay for is what you accepted, not what somebody claimed.

The value

Why it matters

What you pay for is what you accepted — because the GRN is an independent record, not a countersignature on the supplier’s claim.

Shortages are caught while the driver is still at the gate, which is the only moment they cost nothing to resolve.

Stock is visible in inventory the day it arrives, closing the window in which it evaporates.

The receipt leg of the match actually exists — without it, matching degrades into paying the supplier’s claim against the supplier’s invoice.

Capabilities

What you can do

01

Per-line delivered / accepted / rejected

Three numbers per PO line, with reason codes on the rejection. Not one number and a signature.

02

Gate-side exception capture

Discrepancies recorded with photographs while the driver is still present — the only moment a shortage is cheap to resolve.

03

Cumulative PO draw-down

One GRN per delivery, all against the same PO line, so cumulative received quantity is visible and the final delivery cannot match against the full order.

04

Same-day inventory posting

Accepted stock to location and bin on acceptance — closing the gap between “at the gate” and “in the store” where materials disappear.

05

Quarantine and return tracking

Rejected stock marked and tracked until it physically leaves site, with the credit chased against the original PO.

06

Linked to inspection and match

The GRN connects to its material inspection where one applies, and feeds the three-way match as the receipt leg.

The workflow

How it actually runs

  1. 1

    Pre-notify the delivery

    Expected against a known PO line, with gate hours and offloading arranged. On an urban site that means crane slots and delivery windows — a truck that cannot be offloaded is a truck that gets signed for in a hurry.

  2. 2

    Count at the gate

    Against the delivery note, before the truck is released. Condition inspected. Photographs of the load, the note, and any damage — timestamped, because the timestamp is what makes them evidence.

  3. 3

    Capture the exception while the driver is there

    Shortages and damage written on the supplier’s own copy, countersigned by the driver. Once the truck leaves, a shortage becomes your word against theirs — and their word is a document you signed.

  4. 4

    Raise the GRN the same day

    Delivered, accepted and rejected per line, with reason codes. Quality-sensitive items routed to material inspection against the approved submittal.

  5. 5

    Post to inventory, quarantine the rest

    Accepted stock to its location and bin immediately. Rejected stock quarantined, marked, and tracked until it leaves site — because rejected material near the workface gets installed.

  6. 6

    Feed the match

    The GRN becomes the receipt leg of three-way matching. Payment follows what was accepted, not what was claimed.

AI that does the work

How AI changes Delivery Notes & GRN management.

Ticket capture.

Delivery-note data extracted from a photograph at the gate — quantities, items, batch numbers — with confidence scores. The storekeeper verifies rather than transcribes, and the paper ticket stops mattering the moment it is photographed, which is the whole problem with paper tickets solved.

Cumulative-position awareness.

“This delivery takes PO line 7 to 103% of the ordered quantity.” Flagged at the gate, while the truck is still there and the conversation is still possible — rather than at month end, when it is an invoice dispute.

Discrepancy patterns.

Suppliers with recurring shortages or damage surfaced as a pattern, with the photographic evidence attached. That turns a suspicion held by one storekeeper into a commercial conversation with a supplier — which is a different thing entirely.

Receipt-to-invoice readiness.

Unmatched receipts, and invoiced-but-never-received lines, surfaced continuously — keeping the match clean from both ends rather than discovering the gap when the payment run stalls.

The engineer’s judgment stays in charge; the AI removes the latency and the blind spots.

Best practices

  • Count before you release the truck — or sign “received unexamined, subject to count”. A clean signature on a short delivery converts the supplier’s shortage into your problem, permanently.
  • Write the exception on the supplier’s copy and get the driver to countersign it. Once the truck has left the gate, you have an argument. Before it leaves, you have a document.
  • Post accepted stock to inventory the same day. The window between “received” and “booked” is where material evaporates — and where the duplicate requisition gets raised.
  • Name your authorised receivers, and hold after-hours deliveries in quarantine until one of them counts it. A security guard’s signature is not acceptance, and everybody knows that except the supplier’s invoice.

Dashboards & reporting

The receipt register per PO line — delivered, accepted, rejected, with reason codes and photographs. Cumulative draw-down against every open order. Discrepancy patterns by supplier, with the evidence attached. Quarantined stock tracked to return and credit. And the unmatched-receipt and invoiced-but-never-received views that keep the three-way match honest from both directions.

Live dashboards
Drill-down & filters
Export to Excel / PDF
FAQ

Common questions

What is the difference between a delivery note, a GRN and a bill of lading?

The delivery note is the supplier’s statement of what was shipped. The bill of lading is the carrier’s contract of carriage. The goods received note is your own record of what actually arrived and was accepted. Three documents describe every delivery, and only the GRN is yours — which is why it is the only one that is evidence.

Who should sign for deliveries?

Named, authorised receivers — the storekeeper or the site engineer, with a QA countersignature on quality-sensitive materials. If the authorised receiver is not available, as with after-hours deliveries, the goods sit in quarantine status until somebody counts them. A security guard’s signature is not acceptance, however convenient it is at two in the morning.

Read the full answer
What do you do when the count does not match the delivery note?

Record the exception on the supplier’s copy before the truck leaves, get the driver’s countersignature, photograph everything, and raise the GRN with the actual accepted quantity. A clean signature on a short delivery converts the supplier’s shortage into your problem — and it does so permanently, because you signed it.

How do GRNs handle partial deliveries?

One GRN per delivery, all referencing the same PO line, with the cumulative received quantity tracked. The purchase order is drawn down delivery by delivery, and invoices match against cumulative accepted receipts rather than against the order total.

Why is the GRN essential for three-way matching?

It is the receipt leg. Without an independent record of what was accepted, “three-way matching” quietly degrades into paying the supplier’s claim against the supplier’s invoice — which is two documents from the same party and no verification at all. The GRN is what makes the match mean something.

What happens to rejected materials?

Rejected quantities recorded with reason codes, stock quarantined and clearly marked, a supplier return and credit initiated, and the replacement tracked against the original purchase order. Rejected material left near the workface gets installed — which is how a receiving failure becomes a quality failure, and then an NCR.

Sources

  • Cross-industry receiving benchmarks — 1–3% of delivery lines carrying a discrepancy. Cross-industry, and labelled as such: no robust construction-specific short-delivery rate exists, and we have not invented one.
  • National Equipment Register / NICB — construction site theft. These are industry-body estimates, and dated ones. Framed as estimates throughout.
  • FHWA e-ticketing research and the National Materials E-Ticketing Task Force
  • FMI research — time lost to hunting for project information

Zepth is the construction project delivery platform — it runs construction, procurement and asset management on one record, and does the work: reading the drawings, reviewing the submittals, matching the invoices and flagging the risks, with a human sign-off on anything consequential.

See it on your project.

A short, tailored walkthrough on your real workflow — no generic demo.