Case study — Driver expenses
Receipts arrived a week late,
attached to nothing.
Both operators paid driver expenses out of the same broken loop: money spent on the road, recorded on paper or not at all, surfacing days later with a date that had drifted and a trip nobody could name. Approval then ran on whichever version of the story arrived first.
Before
Chasing paper, and the story around it.
A driver spends on the road — a repair, a fee, a night halt, something loaded or unloaded by hand. The record of it is a slip in a shirt pocket, and it starts drifting the moment it goes in there. By the time it reaches the office the date is approximate, the trip is a guess, and half of them never arrive at all.
What follows is worse than the loss itself: the office chases receipts, the driver reconstructs a week, and approval happens because someone is tired of asking rather than because a number was checked. None of it maps to a trip or a delivery, so none of it ever reaches the cost of the load that caused it. Dangerously inaccurate, and inaccurate in the direction nobody notices.
After
Entered on the spot, against the trip.
The expense is entered in the driver’s app as it arises, against the trip that is already open on that phone. The trip is not typed in and cannot be misremembered — it is the trip the driver is on. Date, time, amount and photograph are captured at the moment of spending, which is the only moment all four are still true.
Approval then has something to work with: a limit for that head, a comparison against the same corridor’s history, an exception raised only where one is warranted. What is approved lands in that trip’s cost immediately, so it reaches per-trip, per-vehicle and per-driver economics instead of a general pool at the end of the month.
An expense captured where it happens does not need a story told about it later. There is no gap between the spending and the record for the details to drift into.
The operating principle behind this change
What actually changes
Three steps, and none of them is chasing paper.
01
Logged where it happens
One entry on the phone, on the road, against the open trip. The driver is not filing a claim later; they are closing a line item now, while the receipt is still in their hand.
02
Approved against a metric
Head, limit, route history. Approval stops being a judgement about a person’s account of a week and becomes a check on a number that was recorded at the time — which is faster for everyone, the driver included.
03
It reaches the trip’s P&L
Because the expense is attached to the trip rather than to a month, the trip’s margin includes it. That is the difference between an expense being paid and an expense being accounted for.
Where these costs end up: unit economics per trip →
The same idea at the gate: compliance recorded as it happens →
Your fleet, your numbers
Put one week of driver spend through it.
More customers
All case studies →Sixty tippers, four ledgers, and a month-end that took eleven days.
Aggregate and cement on short legs around Bengaluru — twelve to sixteen trips a vehicle a day, reconciled from four records that never agreed.
SaiRam Fleet Operations →Free days that ran out in someone else's yard.
Port to ICD and back, with a detention clock nobody was watching. The invoices arrived weeks later and could not be attributed to anyone.
Meridian Container Lines →