Ask any operator what causes the most friction with drivers and the answer is rarely the base rate. It is batta — the allowance for being away from home.
Not because the amount is unfair. Because nobody can reconstruct how it was calculated three weeks later.
What batta is meant to cover
The driver’s costs when a trip takes them beyond a normal working day: food, and somewhere to sleep if the trip runs overnight. On outstation work it is not a small adjustment to the payout — over a month of long runs it is a substantial share of what the driver takes home, which is precisely why they track it more carefully than you do.
Set the trigger, not just the amount
Most operators can tell you their batta rate. Far fewer can state the rule that decides when it applies, and that is where the disputes come from.
A rule needs to answer four questions without judgement:
Distance or duration? Beyond a set number of kilometres, beyond a number of hours, or either. Pick one basis and hold it — “it was a long trip” is not a rule.
What about a night? Most operators pay a separate night halt when the driver sleeps away from base. Define what counts: a trip crossing a particular hour, or an actual overnight stay.
Part days? A trip that returns at 9pm is not a night halt but is not a normal day either. Decide in advance whether you pay half, full or nothing, and write it down.
Who approves an exception? There will be exceptions. Naming who can grant one is what stops every driver negotiating individually.
Record it against the trip
This is the part that matters, and it is nearly always the part missing.
If batta appears only as a total on the monthly payout, a driver who disagrees has nothing to check and neither do you. The conversation becomes memory against memory, and the driver loses it — which is how a payout dispute becomes a resignation.
If it is recorded against each trip, at the time, by rule, then a disagreement takes four minutes: open the month, look at the trips, find the one where the rule was applied differently, and either fix it or explain it.
The same principle applies to everything else in a payout — trip earnings, deductions, advances, wallet balance. A driver who can see their own ledger argues far less than one who cannot, and it is not because the numbers changed.
What it costs you to get this wrong
Three costs, in ascending order of expense:
Time. Someone spends the first week of every month reconstructing allowances from memory and messages.
Margin. Batta that was not in the quote gets paid out anyway. On outstation work this is one of the most common reasons a trip that looked profitable was not — the fare was quoted without it and paid with it.
Drivers. The expensive one. Good drivers do not leave over one disputed allowance. They leave after the third, when they conclude the payout is arbitrary. Replacing a driver who knows your regular customers costs more than every batta argument you will ever have.
A checklist
- [ ] The trigger is a rule, not a judgement, and it is written down
- [ ] Night halt is defined separately from daily allowance
- [ ] Part-day handling is decided in advance
- [ ] It is priced into the customer quote before the trip
- [ ] It is recorded against the trip, at the time
- [ ] The driver can see their own ledger without asking anyone
- [ ] Exceptions have a named approver
Seven lines. Most operators have the first and none of the rest.
Where it connects to the quote
Batta is a driver cost and a customer charge, and they are usually not the same number. Quote it into the fare by the same rule that pays it out, and the gap between the two is visible margin rather than a surprise.
Our page on fare and package pricing covers how allowances are applied by rule at quoting time, and the one-way fare calculation post covers where batta sits among the other charges that get forgotten on outstation work.