Kilometres run versus kilometres billed
There is a number for the difference between what your fleet actually moved and what you actually invoiced. Most operators have never calculated it, because calculating it requires the two records to exist in the same place — and in most fleets they never have.
Ask an operator what proportion of the work their fleet performed last month was invoiced, and the answer is almost always “all of it”. Ask how that is known, and the answer becomes less firm.
It is not known. It is assumed, on the reasonable basis that trips generate paperwork and paperwork generates bills. The assumption holds most of the time. The question is what happens in the gaps, and whether anyone would notice.
When fleets do measure it — usually for the first time during an implementation — the gap between kilometres run and kilometres billed is typically somewhere between two and six per cent. On a fleet turning over ₹4 crore a year, the middle of that range is roughly ₹16 lakh. It has been leaking annually, and it does not appear anywhere as a loss. It appears as work that was simply never billed.
The five places the gap opens
1. The trip that never became paperwork
An urgent movement arranged over the phone on a Saturday. A vehicle diverted mid-route to pick up an additional load. A short shuttle between two of the customer’s own sites, agreed verbally.
These are real trips with real diesel and real driver hours. They frequently generate no dispatch note, because the arrangement that created them bypassed the process that creates dispatch notes. If nothing exists on Monday, nothing gets billed.
2. Kilometres that shrank in transcription
A trip sheet records 340 km. The invoice says 320. Somewhere between the driver’s entry, the register, the billing clerk’s summary and the final bill, a figure moved.
This is rarely dishonest. It is a transcription chain with three or four hops, and each hop is a chance for a digit to change or a rounding to happen “for simplicity”. The direction of the error is not random, either — rounding in the customer’s favour is socially easier than the reverse, so the errors accumulate one way.
Every hop between the record of work and the invoice is a place value can leak. The fix is not more careful hops — it is fewer hops.
3. Detours and waiting that were never claimed
A customer asks the driver to divert eleven kilometres to a second gate. He does, because refusing is not his job. Nobody records it as a variation, and it is never billed — even where the contract explicitly permits it.
Detention is the same story with a bigger number. Most contracts allow a detention charge after a free period. Most operators claim it rarely, because claiming requires evidence of arrival and departure times that nobody captured. The entitlement exists on paper and is unusable in practice.
4. Legs that closed without a supporting document
The POD went missing, the weighbridge slip got wet, the signed copy stayed with the customer’s storekeeper. The work is not in dispute — but the customer’s accounts department will not process the bill without the document, and the bill goes into a pending pile.
Items in that pile age. After ninety days, most fleets stop chasing, and the amount quietly becomes a write-off nobody ever formally decided to take.
5. Rate drift on long contracts
A rate was agreed two years ago with an escalation clause tied to diesel. Diesel moved. The escalation was never applied, because applying it required someone to notice the trigger and raise it.
This is the quietest of the five and often the largest, because it applies to every trip on that contract rather than to isolated events.
Measuring your own gap
You can do this for one month, by hand, in an afternoon. It is worth doing before deciding whether any of this matters at your scale.
- Total the kilometres your vehicles actually covered last month. Odometer readings are best; telematics distance is fine; trip sheets are acceptable if that is what exists.
- Total the kilometres you invoiced for the same period, from the bills themselves rather than from a summary.
- Subtract, and account honestly for the legitimate difference — empty repositioning, workshop runs, personal use of the pickup. This is real and must come out.
- What remains is your gap. Express it as a percentage of billed kilometres, then apply your average realisation per kilometre to get a rupee figure.
Two per cent means your process is tight and the remaining leakage is probably not worth engineering away. Six per cent means there is a structural problem, and it is almost certainly one of the five above rather than something exotic.
The gap is not usually a fraud problem. It is a filing problem that has been running long enough to look like a margin problem.
Why monthly close cannot fix it
Every fleet already reconciles. The difficulty is when.
A month-end reconciliation asks people to resolve a discrepancy from up to thirty days ago. The driver has run twenty trips since. The slip is somewhere in a bundle. The customer’s storekeeper who signed for it is on leave. The cost of investigating exceeds the value of most individual items, so items below some threshold get written off — not by decision, but by exhaustion.
That threshold is where the leak lives. It is why the gap is remarkably stable year to year: the same category of small discrepancy is being abandoned every month for the same reason.
What actually closes it
Close daily, not monthly. An exception raised the same evening is cheap to resolve, because the driver remembers the halt and the slip is still in the cab. This single change addresses more of the gap than everything else combined.
Make the trip record and the invoice the same record. If the bill is raised from the trip sheet the driver closed, rather than transcribed from it, leak two disappears entirely. Not reduced — removed, because the hop where value leaked no longer exists.
Capture evidence at the point of work. A photograph of the POD or the weighbridge ticket, taken by the driver when it is signed, is worth more than the paper original — because it exists, is timestamped, and cannot get wet. Leak four is largely a photography problem.
Timestamp arrival and departure. Detention entitlements you cannot evidence are not entitlements. Once gate-in and gate-out are recorded automatically, a claim becomes a record rather than an assertion, and fleets start making claims they had quietly given up on.
Put escalation clauses on a calendar. Unglamorous, and frequently the largest single recovery on this list. Every contract with a diesel-linked or annual escalation should have a review date that arrives whether or not anyone remembers it.
What closing it looks like
The fleets we work with that have closed this gap describe the same change, and it is not primarily about the money.
Month-end stops being an investigation. There is nothing to reconstruct, because the reconciliation happened each evening while it was cheap. What was an eleven-day exercise in archaeology becomes an afternoon confirming a short list of exceptions that are already understood.
The recovered revenue is real and it pays for the change several times over. But the durable benefit is that a category of ambiguity leaves the business — and with it, the standing argument with customers about which kilometres were real.
QuamBase raises invoices from the same trip record the driver closed, and surfaces unmatched legs the same evening. Get a demo →