Proof of Delivery: The Record That Closes the Loop
The delivery note that comes back unsigned, illegible, or not at all is the reason an invoice gets disputed six weeks later. What proof of delivery has to capture, why the signature matters less than the identity, and how to close the loop when the driver has no signal.
A distributor delivers eleven drops on a route, and ten of them are uneventful. The eleventh becomes an invoice query five weeks later: the customer says three cartons were short, the driver says everything went in, and the delivery note in the file has a signature that could be anybody's and no printed name beside it.
That dispute is not usually about honesty. It is about a record designed to prove that a vehicle arrived rather than to prove what was accepted, by whom, in what condition. Those are different claims and only the second one is ever contested.
The four things a delivery record must carry
| Captured | Why the dispute turns on it |
|---|---|
| Who accepted it — name and role, not just a signature | A scrawl proves somebody signed; a printed name proves who |
| What was accepted — line by line, with shortfalls noted | A single signature on a full delivery note cannot express "ten of twelve" |
| When — the actual time of acceptance | Timing decides claims about condition, especially for chilled goods |
| Condition and exceptions at the door | Damage found later is arguable; damage noted at handover is not |
The first row is where most Kenyan delivery paperwork fails. A signature without a printed name and role is unattributable — and when a claim arises, the customer's side will not identify who signed, because they do not know either. A printed name turns a dispute into a phone call to a specific person.
A signature proves somebody signed. A printed name and role proves who — and the difference is the whole value of the document six weeks later.
Part-deliveries are the real design problem
Any delivery process handles a complete delivery adequately. The one that separates a working process from a paper one is the partial: eleven of twelve cartons accepted, one refused as damaged, one line substituted, one delivered to a different door.
If the record cannot express that at the moment it happens, one of two things follows. The driver marks it complete and the shortfall becomes an invoice dispute, or the driver marks it undelivered and a customer who received most of the order is not invoiced for any of it. Both are common and both are expensive.
-
Capture acceptance per line, not per delivery
Quantity accepted against quantity sent. This one change removes the majority of delivery-related invoice queries.
-
Record the reason for any shortfall
Damaged, refused, not ordered, short-loaded. The reason determines whether it is a credit note, a re-delivery or a warehouse problem.
-
Decide the return route at the door
Goods coming back on the vehicle need to arrive back in stock. Undocumented returns are how van stock quietly diverges from the record — see van stock and site custody.
-
Close the loop the same day
Delivery outcomes entered on return, not at the end of the week. A shortfall recorded on Friday for a Monday delivery is already a negotiation.
Photographs settle what signatures cannot
A photograph at the point of handover — the goods at the door, the damaged carton, the delivery note being signed — costs a driver ten seconds and resolves a category of dispute that signatures cannot touch: condition. "It arrived damaged" and "it was damaged after arrival" are indistinguishable in a paper trail and obvious in a photograph.
The practical requirement is that the image is attached to the delivery record rather than sitting in a phone gallery. A photograph nobody can find is not evidence, and drivers change phones. Attach it to the record and it survives.
Chilled and pharmaceutical deliveries need the time as well
Where condition depends on elapsed time out of temperature, the acceptance timestamp is part of the proof and not merely administrative. Note that this is a record of when handover occurred — not temperature monitoring, which we do not do.
When there is no signal
A great deal of Kenyan delivery happens where connectivity is unreliable, and any proof-of-delivery process that assumes a live connection at the door will be abandoned within a fortnight. Drivers do not stop working when the network drops — they revert to paper, and then you have two systems and a reconciliation nobody does.
Offline capture with synchronisation on return is the only arrangement that survives contact with a real route: the record is created at the door where the facts are, and it reaches the system when the device does. Two things to be honest about — the record does not exist centrally until it syncs, so a delivery cannot be confirmed by an office chasing it in real time; and conflicts have to be resolved when two versions of the same record meet. The wider pattern is set out in offline-capable for stock and asset movement field workflows.
The delivery note is a receivables document
This is the framing that gets delivery discipline taken seriously by people who do not care about logistics. A signed, attributable, line-level delivery record is the evidence behind an invoice, and its quality determines how fast that invoice is paid.
Two identical deliveries, five weeks later
Illustrative, in KES. The credit note is the visible cost; the twenty-three days of delayed payment on the whole invoice is usually the larger one. Delivery documentation is a receivables control that happens to look like a logistics task.
What we do and do not do
What AWRA OpsHub does today
- Stock movements with named custody, so goods leaving a warehouse with a driver are a recorded transfer rather than a disappearance.
- Mobile offline capture with synchronisation, so records are created at the door and arrive when the device reconnects.
- Photographs and attachments against records, stored rather than left on a phone.
- Optional location capture on movements, where you require it.
- Deliveries reconciled against the order, so a shortfall is visible against what was sent.
- Customer records, invoices and credit notes, so a delivery exception becomes the correct commercial document.
- Signature capture at the point of handover, with the signer's printed name and the timestamp stored beside the drawing, rendered on the printed and emailed note, and working with no signal.
More we can add to your workspace
- Route planning or optimisation. Which drops in which order is decided by you.
- Live vehicle tracking: a real-time map of where the fleet is. Location is captured on a movement today.
- Customer delivery notifications, telling a customer their delivery is on its way or has arrived.
- A certified e-signature on a captured mark. What ships is operational evidence about a handover, with no certificate, no key pair and no eIDAS, ESIGN or UETA claim attached to it. A signer at a distance needs remote document e-signature instead.
Signature capture shipped in August 2026, after this article was first written, and the two lines above are the honest split: the mark exists, and it is a control rather than a legal instrument. The rest of the argument is unchanged — a printed name, a role, line-level quantities and a photograph are still doing the heavy lifting, and a drawing without a name beside it is still worth nothing. See why the squiggle is not the evidence.
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 needsOur take
Capture who accepted the delivery by name and role, record quantities line by line so a partial is expressible, photograph anything unusual, and close the loop the same day. Treat it as a receivables control rather than a logistics chore — the twenty-three days of delayed payment on a disputed invoice cost far more than the credit note that eventually settles it.
See signature capture and offline operations
A mark taken at the door with the signer's name and the time beside it, records captured with no signal and synchronised on return, custody on stock movements, and deliveries reconciled against the order.
Explore signature captureFrequently asked questions
Can drivers capture a customer signature?
Yes. Signature capture takes a hand-drawn mark on a phone or tablet at the point of handover, and stores the signer's printed name and the timestamp beside it — the drawing on its own is illegible and unattributable, which is why the name is the part that matters. It works with no signal, because the mark travels inside the movement record rather than as a separate upload. What it is not is a certified e-signature: no certificate, no key pair, and no eIDAS or ESIGN claim. If a customer contractually requires a certified signature, that is remote document e-signature and a different mechanism.
How should a partial delivery be recorded?
Line by line, with quantity accepted against quantity sent and a reason for any shortfall — damaged, refused, not ordered, short-loaded. This is the single change that removes most delivery-related invoice queries. Without it a driver either marks the delivery complete, creating a dispute, or marks it undelivered, so a customer who received most of the order is invoiced for none of it.
What happens when there is no network at the delivery point?
The record is created offline at the door and synchronises when the device reconnects, which is the only arrangement that survives a real Kenyan route — a process requiring live connectivity gets abandoned within a fortnight and drivers revert to paper. Two honest consequences: the delivery is not visible centrally until it syncs, so the office cannot confirm it in real time, and conflicting versions of a record have to be resolved when they meet.
Do you track where the vehicles are?
No. Location can be captured on a movement record if you require it, but there is no live vehicle tracking and no map of the fleet — if that is what you need, it is a separate telematics product. What this covers is what left, who has it, what was accepted and what came back, which is the part that determines whether your invoices get paid.
Why does a delivery note affect how fast we get paid?
Because it is the evidence behind the invoice. A query on a delivery with a named acceptor, line-level quantities and a photograph is usually withdrawn; the same query on a delivery with an illegible signature turns into weeks of negotiation and a credit note to close it. The credit is the visible cost and the delayed payment on the whole invoice is usually the larger one.
