Driver Salary Management Software Built on the Trip Record
Driver pay in most transport offices is not a monthly number. It is a per-run number, agreed by route, which makes the trip record the only honest input to it. KO Fleetz builds the payout from the runs that actually closed, keeps what is owed apart from what has been paid, and names the trips where nobody has added a pay line yet.
He is standing at the counter and the trip was never closed
Pay is agreed by the run. So much for the long leg, something extra for the night halt, a figure for the return. The office keeps it on a register and a phone. At the end of the month a clerk reconstructs four weeks of driving out of memory, out of the driver's insistence, and out of a booking file that stopped being trustworthy somewhere around the second week.
The runs that never got closed are where it breaks. The vehicle came back, the load was delivered, the customer is happy, and nobody marked the trip complete or added the pay against it. In the system it is still ongoing, in a month where that driver has since done four more. He knows precisely what he is owed for it. The office has to take his word or make him wait.
So he waits. Then he asks again. Then he asks in the yard, in front of the other drivers, and the delay stops being an administrative gap and starts being a reputation. Nobody in the office is being mean; the paperwork simply did not close. It costs the same either way. A man who chases his own money for a fortnight takes the next offer from the operator down the road.
The trip is the payroll input
A completed run carries the pay owed for it, and KO Fleetz holds salary to be paid against salary paid. That is the same discipline the advance ledger uses, for the same reason: agreeing what a man has earned and handing it to him are two separate facts, and offices that merge them lose track of both.
Trip Planner does the chasing. Completed trips with no salary added are listed as exactly that, alongside the ones missing an expense entry and the ones with no freight bill raised. A clerk works a short list of named runs rather than auditing a month, and the driver's month closes because his trips closed. The list is uncomfortable the first time you open it. That is the point of it.
Be clear about the boundary. This is not payroll. KO Fleetz does not calculate PF or ESI, does not handle professional tax or TDS, does not file a return and does not issue a statutory payslip. It answers what this driver earned for the work he did and what has been paid against it. That figure goes into whatever payroll or accounting system you already run. It does not replace it, and anyone who tells you a fleet system does is selling you a problem.
Capabilities
What KO Fleetz salary & payouts gives your team
Pay carried on the run
The earning sits on the trip that produced it, so a month's payout is assembled from closed work rather than from a clerk's reconstruction.
Owed and paid as separate figures
Salary to be paid and salary paid are held apart, so a payout everyone agreed on but nobody executed cannot disappear into a single total.
Salary not added flags
Closed trips with no pay line against them are listed by name in Trip Planner, turning the gap into a work item instead of a scene at the counter.
Attendance in the same platform
Employee attendance and working hours records live alongside, so any monthly component can be checked against the days a man was actually marked present.
Advance balance shown beside the payout
What a driver still holds as unsettled advance is visible next to what he has earned, so both sides of the deduction start from the same record.
Payout history per employee
Each driver has a readable history of what he was paid and for which runs, which ends most disputes before they need a manager in the room.
Pay lands in the trip's cost
Driver earnings post as a cost against the run that generated them, so the money reaches lane costing instead of resting only in a monthly wage head.
Payment records against the ledger
Disbursements are recorded in Finance next to expenses and payables, so wages are not the one cost category kept in a separate book.
How it works
How KO Fleetz does it
Step 1: Agree the rate for the work
Per run, per tonne, per day, or a monthly figure with trip additions — the pay for a job is what you enter against that job, in whatever shape your business uses.
Step 2: Close the trip properly
A run marked complete is the trigger for everything downstream. This is the step that quietly does not happen today, which is why it is listed as a step.
Step 3: Add the pay and see the commitment
The earning posts to salary to be paid. It is now a number the office owes, visible before the driver arrives to remind anyone about it.
Step 4: Pay it and clear the column
The disbursement moves the amount to salary paid and the run's obligation is closed. Anything still in the first column is a question with an answer.
Outcomes
What changes
- Pay assembled from closed runs, not from memory
- Trip-linked
- Completed trips missing a pay line are listed
- Named gaps
- The commitment and the disbursement stay distinct
- Owed vs paid
- A pay figure, not a statutory payroll engine
- Honest scope
Frequently asked questions
No, and it is important you hear that before a demo rather than after an implementation. There is no PF, ESI, professional tax or TDS calculation here, no statutory filing and no compliant payslip. What KO Fleetz does is establish what a driver earned for the work he performed, hold it against what has been paid, and hand you a clean figure. Your payroll or accounting system takes it from there. The gap it closes is between the trip and the wage, which is the gap payroll software has never been able to see.
Some of it. If pay never varies with the work, the trip linkage matters less and attendance matters more — days present, working hours and the leave that goes with them are recorded in the same platform. Where it still earns its place is cost attribution: a fixed wage is still a cost your lanes consume, and spreading it onto runs is what lets you cost a corridor honestly. Fleets running a small fixed base plus trip earnings, which is very common, get both halves.
Those states exist on the trip record and each carries its own pay conversation. A driver who reached halfway before a breakdown turned him back has done real work and is usually owed something for it. The platform does not compute that figure — no rule for it would survive contact with a real yard — but it keeps the trip, its state and the distance it managed, so the person deciding the amount decides from a record rather than from an argument.
It does not guess. Rates in this business are negotiated, seasonal and occasionally personal, and a system that auto-priced a driver's earnings would be wrong often enough to be worse than useless. What you enter against the run is what is owed for it. The value is not in the arithmetic; it is in making sure every completed run has a pay line at all, which is the failure that actually costs you drivers.
They are pay entries against the run, the same as the base earning, and they travel into the trip's cost with it. What is not here is statutory overtime computation under labour law with its thresholds and multipliers. If your arrangement is the usual transport one — a halt allowance, a bonus for a tight delivery, something extra for a difficult stretch — you record it and it flows. If you need legally computed overtime, that belongs in payroll.
You see both figures together and record the decision. The unsettled advance sits beside the earned but unpaid salary, so the netting is done with the whole picture in front of whoever is authorising it. The platform does not subtract one from the other on its own, because that deduction is a conversation with a person and frequently a negotiation — a system doing it silently is how a driver finds out at the counter and stops trusting the office.
Close the trips, close the month
Show us one depot's completed runs from last month. We will show you how many of them KO Fleetz flags as closed with nobody's pay attached.