Monday in the courier office
Every Monday the office manager opens last week's job sheets and the dispatch system export, and starts building pay for thirty owner drivers. Driver A is paid per drop on a multi-drop route, plus a bonus for Saturday. Driver B is paid per mile on same-day work, plus waiting. Driver C hires a van from you and has a weekly deduction. Driver D swapped a route with Driver E on Wednesday. Two drivers have queries from the previous week.
By Tuesday afternoon the statements go out. On Wednesday three drivers ring to say something is missing. Two of them are right.
Why driver pay is so manual
The work data and the pay rules live in different places. Your dispatch or courier software knows which jobs were done, but not always by whom when routes are swapped, and rarely what each driver's pay terms are. The rates, deductions and one-off adjustments live in a spreadsheet that has evolved over years.
| Pay element | Where it usually comes from |
|---|---|
| Jobs or drops completed | Dispatch system export, corrected by hand |
| Mileage | Driver's claim or a map lookup |
| Waiting time and extras | Job sheets and phone calls |
| Driver's rates | A spreadsheet tab per driver |
| Deductions | Van hire, fuel cards, damage, uniform, in another spreadsheet |
| Self-billing statement | Built in a word processor or accounts package |
Self-billing arrangements with owner drivers also carry their own paperwork requirements, which your accountant will advise on. The statements need to be complete and consistent.
What manual pay costs you
Office time every week, and the errors that come with it. Drivers who are underpaid lose trust quickly, and good owner drivers have plenty of other firms to work for. Overpayments are hard to claw back. And disputes take longer than the pay run itself, because reconstructing what a driver did last Tuesday means digging through sheets and messages.
It also slows growth. Every extra driver adds to the Monday workload.
Pay errors have a knock-on effect on your own accounts too. Deductions for van hire or fuel cards that are missed one week are awkward to add the next, and the balances between what drivers owe you and what you owe them drift until someone has to sit down and reconcile a whole year.
The pay system we build
- Completed jobs pulled from your courier software or dispatch board, with the driver who actually did them, including swaps recorded by controllers.
- Pay rules per driver: per drop, per mile, per hour, day rates, bonuses, waiting, with effective dates so changes are tracked.
- Deductions held as scheduled items or one-offs: van hire, fuel card spend imported from the card provider, agreed damage deductions.
- A draft pay statement per driver for the period, with every job listed and its pay, available to the driver on their phone before payment.
- A query button on each line, so drivers raise questions against a specific job and the office sees them in one list.
- Final self-billing statements generated in the format your accountant approves, and bills or payments passed to Xero, QuickBooks or Sage, or a payment file for your bank.
What Mondays look like afterwards
Pay is prepared from the week's jobs automatically. The office checks the exceptions and the queries rather than building statements. Drivers see their jobs and pay before payday and raise questions early, against specific jobs. Disputes shrink because both sides are looking at the same record.
Signs your driver pay needs this
- Pay is built from job sheets and exports every week.
- Each driver has their own rates tab in a spreadsheet.
- Route swaps cause pay errors.
- Drivers ring after payday about missing jobs.
- Fuel card and van hire deductions are applied by hand.