Driver advances: the ledger that eats your margin

A driver leaves the yard at six in the morning with ₹4,000 for diesel, tolls, food and whatever the road produces. Over the next four days he spends some of it, is given ₹2,000 more by a supervisor at a halt, buys a tyre repair for ₹600 against a receipt that goes soft in his pocket, and returns with ₹900 and a handful of paper.

Somebody now has to work out what he owes or is owed. That somebody is usually reconstructing it from a diary, a WhatsApp thread, and a conversation. It will take twenty minutes, it will be approximately right, and it will be done again for every driver, every trip, all month.

The individual error is small. The aggregate is not, and the erosion of trust is worse than the money.

Why this ledger is uniquely hard to keep

Every other cost in a fleet has a natural document. Diesel has a slip. Tolls have a FASTag statement. Maintenance has an invoice. Advances have nothing — they are cash, handed over, often by a person who is not the person who will later account for it.

Four properties make it worse:

• It is issued by several people. The yard supervisor, the branch manager, sometimes the owner directly. Each has their own note-keeping, and the notes rarely meet.
• It spans trips. A balance carried from last week’s trip does not reset when this week’s begins, so the correct figure depends on a history nobody is holding.
• It mixes categories. Advance against salary, batta earned, expenses reimbursed and float returned are four different things that all move as cash between the same two hands.
• It is settled from memory. The conversation at settlement is the reconciliation, which means whoever remembers more confidently tends to win.

The four categories, kept apart

Separating these is most of the fix, and it costs nothing but discipline.

Advance

Money given against future earnings. It is a receivable from the driver, and it should sit on a running balance that does not reset at trip end or month end. This is the only one of the four that genuinely accumulates, and it is the one most often confused with the others.

Batta

Allowance earned for time on the road — daily, night, or per-trip depending on your policy. It is a payable, it accrues according to a rule, and it should be computable without anyone’s judgement. If two people in your office would compute a driver’s batta for the same trip differently, the policy is not written clearly enough.

Expenses

Money spent on the fleet’s behalf — tyre repair, weighbridge fee, a night halt, loading charges. These are reimbursable against evidence, and they are the category where the paper trail is weakest, because the evidence lives in a shirt pocket for four days.

Float

Cash issued for a specific trip’s running costs, expected back if unspent. Not an advance — it was never against earnings — but constantly treated as one, which is how a driver ends up appearing to owe money he has already returned.

Once these four are kept separately, most settlement disputes dissolve, because the disagreement was almost always about which category a particular ₹2,000 belonged to.

What a running balance changes

The single highest-value change is not better forms. It is that the driver can see his own balance at any time, without asking.

Under the reconstruct-at-settlement arrangement, the driver has no visibility into a number that directly affects his household. He finds out what he is owed when he is told. Even where the figure is entirely correct, this is a structurally distrustful arrangement, and drivers respond to it the way anyone would: by keeping their own count, and by treating settlement as a negotiation.

A running balance the driver can check — a message, a number, whenever he wants it — changes the settlement conversation into a confirmation. It also surfaces disagreements early, while both parties still remember the halt in question, rather than at month end when neither does.

Most advance disputes are not about the money. They are about one party having a number and the other party not.

The operational costs nobody counts

Beyond the direct leakage, the reconstruct-every-month arrangement carries three costs that rarely make it onto anyone’s sheet.

Office time. Twenty minutes per driver per settlement, on a forty-driver fleet settling weekly, is roughly two full working days a month of someone’s time spent on arithmetic that should have been a by-product of the work.

Working capital. Where balances are unclear, fleets over-issue — because refusing an advance to a driver who may genuinely be owed money is worse than issuing one. Unclear ledgers reliably mean more cash on the road than necessary.

Retention. Good drivers leave fleets where settlement feels arbitrary. Replacing an experienced driver who knows your corridors and your customers costs considerably more than the disputed amount ever did, and the cost does not appear as a settlement loss. It appears as a vacancy.

What to change first

1. Separate the four categories. Even in a paper register. Four columns, not one. This single change resolves the majority of disputes because it resolves the ambiguity that caused them.
2. Make issue a two-party event. Whoever hands over cash records it at that moment, and the driver acknowledges it — a photo of the entry, a WhatsApp confirmation, anything with two parties and a timestamp.
3. Give the driver his balance. Weekly at minimum, on request ideally. This is the change drivers notice, and it is the one that most changes the relationship.
4. Compute batta by rule, never by judgement. Write the policy down to the point where the number is arithmetic. If it requires a decision, it will produce a dispute.
5. Make expenses claimable from the road. A photograph of the tyre bill, sent when it is paid, is worth more than the original receipt arriving four days later — because it exists, and because the paper one may not.

None of this requires software. All of it is easier with software, mainly because software does not forget and does not have a stake in the outcome. But the discipline is the substance; the system only enforces it.