How to calculate driver settlements without losing your mind

Why settlement day is everyone’s least favourite day

Ask any fleet manager what the worst day of the month is and most will say the same thing: settlement day. Not because the concept is complicated: pay drivers for the trips they did, minus what they owe. But because the execution, done manually, turns into a forensic accounting exercise that consumes an entire day and still produces disputes.

Driver settlements in South African fleet operations are uniquely complex. Unlike salaried employees, most long-haul and distribution drivers are paid on a combination of per-trip rates, kilometre allowances, overnight allowances, and deductions. Every one of those components has to be calculated individually, verified against trip records, and cross-referenced against advances and deductions before a figure can be agreed.

How the manual process actually works

The typical manual settlement process looks like this. At the end of the settlement period, usually two weeks or a month, someone pulls together all the trip sheets. These are paper forms or WhatsApp photos of paper forms, captured in the field by drivers or their assistants. Each sheet records the route, load, delivery confirmations, fuel drawn, and any tolls or other expenses.

From the trip sheets, a clerk builds a settlement spreadsheet. Each row is a trip. Columns capture the rate, distance, allowances, and any deductions. Advances drawn during the period are tracked in a separate section. Fuel deductions are calculated based on the fuel log, which is often maintained by someone in the yard separately from whoever does the settlements.

Once the spreadsheet is built, a supervisor reviews it. Drivers are called in one by one to sign off on their individual settlements. This is where the arguments start.

Where errors creep in

Manual settlement processes fail at multiple points.

Trip sheet accuracy. Drivers fill in trip sheets under pressure, often at the end of a long haul. Distances get estimated. Delivery times get approximated. Sheets go missing or arrive back at the office incomplete. The person building the settlement spreadsheet has to make judgment calls on incomplete data.

Rate card misapplication. Rate cards in South African logistics are often route-specific or client-specific, with different rates applying depending on the load type, vehicle, or destination. Applying the correct rate manually to each trip requires the settlement clerk to know the rate card structure in detail, and rate cards change without always being communicated to the settlement desk.

Fuel deduction calculation. Fuel deductions should be based on the actual fuel drawn against the expected consumption for the distance driven. In practice, they are often based on fuel log entries that are not tied to specific trips, resulting in deductions being applied to the wrong period or the wrong driver.

Advance tracking. Cash advances drawn mid-period are easily forgotten or double-counted. A driver who drew an advance in week one and another in week three may have one of them missed, producing an overpayment, or have both counted twice, producing an underpayment and a dispute.

The argument factor. When a driver disputes a trip (“I did that Durban run, I have the delivery note”), the only way to resolve it is to go back through the trip sheets and any supporting records. In a paper-based system, this can take hours. In a WhatsApp-based system, it means scrolling through weeks of voice notes and photos. Either way, it is time that nobody budgets for.

The real time cost

A fleet of 30 drivers with an average of 15 trips per driver per settlement period has 450 trip lines to process. At 5 minutes per line, capturing the trip, applying the rate, checking fuel, and cross-referencing advances, that is 37 hours of settlement processing per period. Then add dispute resolution, corrections, and reissuing. A realistic manual settlement process for a 30-driver fleet consumes 2–3 full working days per month.

That is before you consider the cost of errors. Settlement disputes that cannot be resolved quickly damage driver relationships and contribute to turnover. Overpayments that go unchallenged become an expectation. Underpayments that get accepted create resentment. Neither outcome is good for retention.

What automation actually looks like

An automated settlement system starts from GPS and trip data rather than paper trip sheets. When a trip is completed, the system already knows the distance driven, the start and end points, and the time elapsed. It applies the correct rate card automatically based on the route and vehicle. Fuel consumption is calculated from the distance and the vehicle’s fuel type. Advances recorded in the system are deducted automatically.

The settlement summary is generated in minutes rather than days. Disputes can be resolved by pulling the actual GPS track, not by arguing about what someone wrote on a form. Drivers can see their own settlement breakdown before sign-off, which eliminates most disputes before they escalate.

For fleet operators, the shift from manual to automated settlements is not just a time saving. It is a move from a process that produces errors to one that produces an audit trail.

SkyLog automates driver settlements end-to-end, pulling directly from CarTrack trip data and applying your rate cards without manual re-entry.