What the driver is owed, and why the number is argued about

A driver's pay is argued about at month end because three records answer the same question and only one of them was written down when the work happened. The driver remembers the trips, dispatch remembers the ones that were assigned, and the cash box remembers the notes that left it. Nothing is reconciled until the settlement, and by then the weakest memory loses.

Why is the number disputed when the rate was never in question?

Because the rate is agreed and the count is not. Almost every argument is about whether a trip happened, whether it was the trip that was paid for, or whether the advance was the one recorded or the one remembered — not about what a trip pays.

So the settlement's job is not arithmetic. It is to make the count verifiable by the person being paid, before the figure becomes final. A driver who sees his own trips listed, with dates and destinations he recognises, argues about one line instead of the whole month. That is a shorter conversation, and it ends.

What must the trip record carry before pay can be computed?

Five things, and four of them are usually missing on a small fleet: a number, a date, a route, the load, and a signature at the far end.

The number matters because it is how a dispute gets referenced. "Trip 4182" closes a conversation that "the Tuesday one" opens. The signature matters because a trip that was not delivered is not a trip that was worked, and without it both claims are equally plausible — which is the same as saying neither can be settled.

The rate then attaches to a trip type rather than to a trip: a local run, a run to another wilaya, a run that carried a return load. If two types pay differently, the type has to be a field chosen when the trip is opened, never reconstructed at month end from a description of the road.

How do advances and deductions stay attached to the right week?

By carrying a date, a purpose and a signature, and by being written on the day rather than in a column filled in later.

An advance is the commonest source of dispute and the simplest thing to record: the driver takes cash on a Tuesday, signs for it, and the settlement for that period shows it. What breaks is the boundary. Cash handed over on the 28th settles against the period the work belongs to, not the period the notes left the drawer, and the rule has to be written once and applied the same way every month.

Deductions are worse because they are usually unnamed. A fuel shortfall, a damaged tyre, a fine, cash missing from a collection — each is legitimate in some fleets and forbidden in others, and the argument is rarely about the amount. It is about whether the fleet may charge it at all. Whatever your answer, the statement has to show the cause and the date in the driver's own copy before the money is withheld. A deduction that appears for the first time in the final figure will be read as theft, whatever its justification.

What does the settlement statement have to show?

One page per driver per period, in four blocks: what he earned, what he already took, what was deducted and why, and what carries.

Block	Where it comes from	The question it closes
Earned	numbered trips with a signature	what the period paid for
Taken	dated cash vouchers, signed	what he already holds
Deducted	a named cause, a date, a person	why the total is smaller
Carried	the previous statement's balance	what crosses the month

The last row is the one that gets dropped and the one that produces the ugliest scene at the counter: an opening balance nobody can trace turns a correct week into a fight about a number from three months ago. Publishing that figure in one shape, to the person it concerns, is the provenance the W3C's data on the web best practices ask of any number that is going to be relied on.

In what order do you fix this?

1. Number every trip, and make the number appear on the note the customer signs.
2. Write the rate against trip types, not against individual trips, somewhere drivers can read it.
3. Record advances on the day, with a signature, in the same system that holds the trip.
4. List the deductions your fleet permits, and name the person who may approve each one.
5. Produce one statement per driver per period and hand it over before the money, not after.
6. Keep the signed copy. It is the only evidence that the number was accepted rather than imposed.

Where this goes wrong

• Trips are counted from fuel logs or toll receipts. Both prove travel. Neither proves a delivery.
• Advances live in the owner's notebook. Real money, invisible to whoever computes pay, so it is deducted twice or not at all.
• The rate changes mid-month with no effective date, leaving two rates in one period and no way to say which trip took which.
• A deduction is applied with no cause code, so the statement shows a smaller total and no sentence explaining it. The driver learns to distrust the total instead of the deduction.
• The statement arrives after the cash, which turns an accounting document into a notification of a decision already taken.
• Every period is rebuilt by hand from a phone full of voice notes. The month is right and cannot be reproduced, so nobody can check the one before it.

What this does not cover

This is not payroll. Income tax, social contributions and the employment contract belong to your accountant and to the labour rules of your country, and stating them here would be guessing. It assumes drivers are paid per trip, or a salary with one variable component; a commission on revenue is a different model that produces a different argument. And it assumes a fleet small enough that one person still knows every driver — past a few dozen, the same records are needed but the settlement also needs an approval step and a second pair of eyes.

We build transport systems where the trip is the record and the statement is printed from it: trips, advances, deductions and the signed settlement in one place, on the phone the driver already carries.