The Friday Settlement Marathon
What running driver pay on spreadsheets actually costs in time, errors, and trust.
Every small carrier has the Friday afternoon ritual.
The dispatch spreadsheet, open. The fuel report, open. The advance log, open. The settlement template from last week, open. A pad of paper for the deductions nobody wrote down.
The owner or office manager works through it driver by driver, line by line, hoping nothing is missed. Three hours in, the kid calls. The phone rings twice. By the time the checks are cut, it is 7pm. Tomorrow, two drivers will text asking why detention from Tuesday isn't on the statement.
This is normal. It is also a slow-motion business problem that gets worse the longer it runs.
What the marathon actually looks like
The settlement run is the most data-intensive thing a small carrier does every week. It pulls from at least five sources that almost never agree with each other.
- Dispatch records. Which trips closed this week, what miles, what stops.
- Driver pay agreements. Per mile, per stop, percentage of revenue, flat rate, hybrid. Different drivers, different rules.
- Accessorials and reimbursements.Detention, lumper, layover, scale, tolls. Some agreed on the phone, some on text, some never written down.
- Deductions. Fuel advances, escrow contributions, equipment damage, ELD subscriptions, cell phone, occupational accident insurance.
- Advances and prior-week corrections. Money sent on the road earlier this week, errors from last week now being corrected.
Each source lives in a different place. Most of them require a human to remember they exist and pull them in. The spreadsheet does not enforce a check. It just trusts that whoever is running the marathon caught everything.
The four costs nobody adds up
Owners running the Friday marathon usually price it at zero, because they are doing it themselves and not billing anyone for it. The actual cost shows up in four places.
| Cost | What it looks like | Annual impact |
|---|---|---|
| Owner time | Five to seven hours every Friday. Multiply by 52. On a 20-truck fleet, this scales linearly with headcount. | 250 to 350 hours per year, every year. The equivalent of a part-time employee, unbilled. |
| Math and entry errors | Wrong rate applied. Stop pay missed. Deduction duplicated. Decimal in the wrong place. | 1 to 3 percent of total driver pay, in either direction. On a $1.5M annual driver payroll, that is $15,000 to $45,000 of either underpayment (which damages trust) or overpayment (which is pure loss). |
| Driver disputes | Driver flags an error, owner re-runs the math, cuts a supplemental check, fields the next call. Each dispute eats two to three hours minimum. | 100 to 200 hours per year on dispute resolution alone for a 20-truck fleet, plus the relational cost. |
| Driver churn | The most expensive line item, and the one nobody measures. Drivers who are tired of explaining their own pay quietly start looking. The fleet loses a driver every few months over pay issues that look small individually. | $8,000 to $12,000 to replace each experienced driver. One avoidable departure per year wipes out the entire cost of fixing the settlement system. |
Add the four together for an honest 20-truck-fleet number and you land somewhere between $45,000 and $90,000 a year. That is the gross margin on more than a truck. It is also entirely invisible on the P&L, which is why most owners never run the math.
The dispute spiral
The most damaging cost is the one nobody puts a number on.
A driver gets a settlement statement on Friday. Something looks off. They text the dispatcher. The dispatcher promises to check on Monday. Monday is busy. Tuesday the owner says it will be on next week's check. Next week's check has its own issue.
Over time, the driver stops asking. Not because the issue is resolved, but because asking takes more energy than it's worth. They keep working. They keep watching. They start scrolling job boards on the weekends.
The dispute that ends a driver relationship is rarely the big one. It is the small one that nobody got back to.
Driver retention in trucking is built on a simple promise: you do the work, you get paid correctly and on time. Every settlement error chips at that promise, and every chip costs more than the dollar amount in dispute.
Why it gets worse with growth, not better
Owners often assume that hitting some scale will fix this. Hire a bookkeeper. Hire an office manager. Outsource it to an accountant.
None of those work, because none of them change the underlying problem: the data lives in spreadsheets that do not enforce relationships. Adding a person just adds a second human-memory step in front of the marathon.
What actually scales is moving the trigger off the human. When a trip is closed, the settlement line items should already exist. When a deduction is incurred, it should already be queued for the next pay run. When an advance is sent, it should already be on the deduction list.
What good actually looks like
The best signal that you have outgrown spreadsheet settlements is that the marathon takes longer this year than last year, and longer last year than the year before. Spreadsheets do not get easier with practice. They get heavier with every truck and every line item.
The fix is not faster spreadsheets. It is removing the human-memory step that creates errors in the first place.
A few things to look for, regardless of which system you evaluate:
- Settlements draft themselves. A trip closes, the system builds the line items automatically from the agreed pay rules. The Friday work becomes review, not creation.
- Accessorials are captured at the moment they happen. Detention starts a timer. Lumper is logged from the truck. The system never relies on someone remembering on Friday.
- Drivers see their own pay forming in real-time. A driver who can watch their pay accumulate during the week never has the Friday surprise that triggers a dispute.
- Disputes have an audit trail. Every line item links back to the trip and the source it came from. A driver who asks why is shown exactly why, in under a minute.
Frequently asked questions
How long does a typical Friday settlement marathon take?
For a 20-truck fleet running pay on spreadsheets, four to seven hours is normal. The owner or office manager pulls dispatch records, settlement sheets, fuel reports, advance logs, and accessorial notes, reconciles them by hand, builds each driver's line items, and writes the checks. Plenty of fleets do not finish until Saturday morning.
What is the most common settlement error on spreadsheets?
Missing line items, by far. A detention paid out to the driver from petty cash on Wednesday gets forgotten by Friday. A fuel advance sent on the road never makes it onto the deduction list. A multi-stop trip gets paid for the long leg only because the stop pay column was not populated. None of these are math errors. They are memory errors that compound across the week.
How do I know if I have a driver pay dispute problem?
If a driver has ever asked "where is the rest of my check?", you have one. The deeper signal is silence. Drivers who stop asking questions about their pay and just start looking at job boards are the ones you lose. Most owners only notice the disputes that get raised. The expensive ones happen quietly.
What does losing a driver over a pay dispute actually cost?
The replacement cost for an experienced driver runs $8,000 to $12,000 between recruiting fees, downtime, training, and the productivity gap before the new driver is up to speed. A single avoidable settlement error that loses a driver costs roughly twenty times what fixing the settlement system would have cost.
Can I just use QuickBooks for this?
QuickBooks pays the check. It does not generate the settlement. The reason small carriers spend the marathon on spreadsheets is the part QuickBooks does not handle: pulling completed trips, applying per-mile or per-stop or percentage pay rates, layering in deductions and advances, and producing a defensible line-item breakdown the driver can review. That work has to live somewhere upstream of QuickBooks.
Will a TMS actually fix this, or just move it?
It depends entirely on whether the TMS makes settlements flow from completed trips automatically, or just digitizes the existing manual process. The fix only works if the system can take a completed trip and produce a draft settlement line item without anyone asking it to. If the dispatcher is still expected to remember to log accessorials at the end of the week, the marathon moves into the database but stays the same length.
Get your Fridays back
We'll walk through how a system that drafts settlements automatically actually works in practice. 30 minutes, with realistic data, no slide deck.
Schedule a walkthrough