GUIDE · REVENUE LEAKAGE · TRANSPORT AND DISTRIBUTION
Work you completed. Money you never collected.
Almost every owner-operated transport business is carrying deliveries that were finished, accepted by the client and never invoiced. Not through theft — through a delivery note in a cab and a completion that never reached anyone whose job it was to bill it. Here is how to find yours.
01 / HOW WORK GOES UNBILLED
Five ways completed work stops turning into money.
None of these look like a problem while they are happening. That is what makes them expensive — each one is an ordinary Tuesday, and the loss is only visible in aggregate months later.
- 01The completion never reached finance
The delivery happened, the driver moved on to the next job, and nobody told the person who raises invoices that this one was finished.
- 02The proof exists but cannot be produced
The signed note is real and it is in a vehicle, a jacket or a chat thread. The client queries it, you cannot produce it quickly, and the invoice quietly stops being pursued.
- 03The client rejected the submission
A missing signature or the wrong recipient name, discovered weeks later. The delivery is disputed rather than paid, and by then correcting it is impossible.
- 04It was submitted and never acknowledged
The paperwork went to the client. Nobody confirmed receipt, nobody followed up, and it sits in a state that nobody owns.
- 05The job was never in a system at all
An urgent job arranged by phone, done well, and never written down anywhere that finance would look.
02 / FIND YOURS THIS WEEK
A four-step audit you can run without buying anything.
Do this for one month — ideally a busy one, three to six months back so the payment cycle has fully closed. It takes an afternoon and the number at the end is usually larger than the owner expects.
- 01List every delivery instruction issued
From wherever they come — a book, a spreadsheet, WhatsApp, a client portal. You need the total count, not a clean dataset.
- 02Match each one to an invoice
Take your invoice list for the following month and match them. Anything that does not match is either not delivered or not billed.
- 03Split the unmatched into three piles
Not delivered, delivered but unprovable, and delivered and provable but never invoiced. The third pile is money you can still go and collect. The second is the one that tells you what to fix.
- 04Put a shilling value on each pile
This is the step people skip and it is the one that changes behaviour. A percentage is arguable; a figure is not.
03 / WHAT TO CHANGE
Claimed is not the same as complete.
Underneath every one of these failures is a single confusion: treating a driver saying a delivery happened as though it were proof that it happened.
A driver saying it was delivered is a claim. A validated proof of delivery is evidence. Everything downstream — the client submission, the invoice, the payment and the dispute — depends on the business being able to tell those two apart, and most operations collapse them the moment the driver phones in.
Keep them separate and most of the leakage closes on its own, because a job that is claimed but not evidenced is visibly unfinished rather than quietly assumed done.
- 01Write down what each client requires as proof
One wants a stamp, one wants confirmed quantities, one wants photographs. Record it per client once instead of remembering it per delivery.
- 02Check the evidence on the day
A defect found while the truck may still be reachable is fixable. The same defect found at submission is a write-off.
- 03Make “delivered but not invoiced” a standing list
Not a monthly reconciliation. A list that exists all the time and that somebody looks at daily.
- 04Track submissions until they are acknowledged
Sent is not received. Give the unacknowledged ones an owner and an age.
04 / WHERE VERIDOM COMES IN
The Delivery Desk was built for exactly this.
It turns the photograph a driver already sends to a WhatsApp number into structured proof of delivery attached to the right job, checks it against what that specific client requires, and flags defects while correction is still possible. No driver app, no login, no training.
Then it puts the money on one screen: deliveries completed with full evidence and no corresponding invoice, submissions sent but never acknowledged, and invoices past terms — each with a value against it.
One workflow, live in fourteen days, measured for thirty against how the work ran before. Most operators have never seen that number, because nothing in the business was ever built to produce it.
QUESTIONS
Revenue leakage questions.
Ask anything not covered here on WhatsApp. You will get a straight answer.
01How much revenue do transport operators typically lose to unbilled work?
We will not quote you an industry percentage, because the honest answer is that nobody has a reliable one and the figures that circulate are marketing. What we can tell you is that the audit on this page costs an afternoon and produces your number rather than somebody else’s. Run it on one busy month and you will know.
02How do I find deliveries that were never invoiced?
List every delivery instruction issued in a month, match each against the invoices raised in the following month, and split the unmatched into three piles: not delivered, delivered but unprovable, and delivered and provable but never billed. The third pile is recoverable now. The second tells you what to change.
03Why does completed work go unbilled at all?
Because completion is a physical event and invoicing is an administrative one, and in most operations nothing reliably connects the two. The delivery finishes in a yard; the invoice is raised in an office by somebody who was not there and who only knows the job is done if a person remembers to tell them.
04Is it worth chasing an invoice for a delivery from three months ago?
If you can produce the evidence, usually yes, and clients pay far more readily than operators expect when the proof is attached. If you cannot produce the evidence, the chase is what damages the relationship. Which is the real argument for capturing proof at the moment of delivery rather than reconstructing it later.
05Do we need to change how our drivers work to fix this?
No, and you should be suspicious of anything that requires it. Driver behaviour is the hardest thing to change in this sector and the most common reason these projects fail. The Delivery Desk works from the photograph a driver already takes on the phone he already owns.
06What counts as proof of delivery?
It depends on the client, which is the root of most disputes. Commonly a signed delivery note with the recipient’s name, the date and the quantities received, and for some clients a company stamp or photographs of the goods. The practical answer is to record each client’s requirement once and check every delivery against the right one.
ONE WORKFLOW · LIVE IN 14 DAYS · MEASURED FOR 30
Find the work you never billed for.
Thirty minutes with whoever handles deliveries and invoices is enough to scope the first implementation and put a figure on what is sitting uncollected. You keep the workflow map either way.
Related: The Delivery Desk, or the overview of AI for logistics operations in Kenya.