Driver settlement software calculates what each driver earns per load and per pay period, then produces a settlement statement you can hand to the driver and defend if they question it. For a fleet running company drivers, lease operators and owner-operators at the same time, that means three different pay structures running through one system instead of three tabs in a spreadsheet. Get one driver’s deductions wrong on a Friday and you spend Monday explaining yourself instead of dispatching.
What is driver settlement software?
Driver settlement software is a tool that pulls load data — miles, rate, accessorials, deductions — and turns it into a per-driver, per-period pay statement. It replaces manual settlement spreadsheets by tying pay directly to the load record instead of a second data entry step. The better systems also generate carrier and dispatcher settlements from the same load data, so nobody is re-typing numbers into three different files.
At a minimum, it needs to handle:
- Per-mile pay for company drivers
- Percentage-of-linehaul pay for lease drivers and owner-operators
- Load-specific deductions: fuel advances, cash advances, escrow, insurance
- Accessorials that belong to the driver, not just the customer invoice
- A statement format the driver can read and you can print or export
Why do spreadsheet settlements break down at 10-75 trucks?
A settlement spreadsheet works when you have a handful of drivers on one pay type. Once you mix company drivers, lease drivers and owner-operators, or your fleet crosses roughly 10 trucks, the formulas multiply and someone eventually copies last week’s numbers into this week’s tab by mistake.
The failure points are predictable:
- Formula drift. Someone edits a cell for one driver’s exception and the formula silently breaks for the next five rows.
- No link back to the load. The spreadsheet has a rate and a mileage figure, but not the actual RateCon, BOL, or POD, so disputes take longer to resolve.
- Deduction memory. Fuel advances, tolls, and escrow contributions have to be remembered and carried forward manually every week.
- Version confusion. Dispatch has one version of the sheet, accounting has another, and the driver’s copy doesn’t match either.
If you’ve already made the jump off spreadsheets for dispatch, the article on running dispatch without spreadsheets covers the operational side of that same problem — settlements are usually the next thing to break.
How do you pay company drivers, lease drivers and owner-operators from one system?
You pay them from one system by attaching a pay type to each driver profile, then letting the settlement engine apply the right formula automatically when the load closes. Company drivers get per-mile or hourly pay; lease drivers and owner-operators get a percentage of the linehaul rate, with deductions layered on top. The load record stays the single source of truth for all three.
Company drivers
Company driver pay is usually per mile, sometimes with hourly add-ons for detention or layover. The settlement pulls loaded and empty miles from the load record, applies the driver’s rate, and adds any accessorial pay the dispatcher tagged to that stop — for example, a $50 detention line after two hours of wait time at a shipper.
Lease drivers and owner-operators
Lease and owner-operator pay is typically a percentage of the linehaul rate on the RateCon, minus a list of deductions: fuel advance, cash advance, trailer rental, escrow, cargo insurance. If you’re deciding between percentage and per-mile pay for a lease operator, the breakdown in owner-operator pay percentage vs per mile walks through when each model makes sense for your lane mix.
Example: three drivers, one pay run
The table below is an example settlement pull for one week, mixing all three pay types on the same run.
| Driver | Pay type | Gross linehaul | Deductions | Net pay |
|---|---|---|---|---|
| J. Reyes (company) | Per mile, 1,840 mi @ $0.58 | $1,067.20 | Detention pay +$100 | $1,167.20 |
| M. Okafor (lease) | 72% of linehaul | $2,400.00 | Fuel advance -$300, escrow -$50 | $1,378.00 |
| T. Bell (owner-op) | 74% of linehaul | $3,150.00 | Trailer rental -$150 | $2,181.00 |
This is a worked example only — your percentages, deductions and detention thresholds should match your own driver agreements and carrier setup checklists.
What should driver settlement software actually include?
At minimum, it should generate driver, carrier and dispatcher settlements from the same load data, attach the supporting documents to each line item, and let you export a statement the driver can review. Anything that requires re-entering numbers you already captured on the load is adding risk, not saving time.
Look for:
- Document tie-in. The RateCon, signed BOL and POD should sit on the load record so a settlement dispute can be resolved by opening one screen, not digging through email. The proof of delivery workflow is worth reading if POD collection is still the weak link in your process.
- Deduction templates per driver. Escrow, insurance, and recurring fuel advances should default automatically instead of being typed in fresh every period.
- Accessorial visibility. Detention, layover, and stop pay need to flow from the same accessorial data used to bill the customer. If your detention billing process is inconsistent, the piece on detention and accessorial billing is a good place to tighten that up before it leaks into settlements.
- Carrier and dispatcher settlements, not just driver pay. Brokers and carrier-brokers also need to settle with carriers they’ve booked and dispatchers on commission, ideally from the same load data.
- Exportable statements. A driver should be able to see a clean, dated statement — not a screenshot of your internal spreadsheet.
For a deeper look at the calculation logic itself — gross pay, deduction order, and how net pay gets to the driver — see driver settlement calculation explained. And if your invoicing side is still separate from settlements, freight invoicing settlement basics covers how the two should connect.
What does driver settlement software cost for a small fleet?
Settlement functionality is usually bundled inside a broader transportation management system rather than sold as a standalone tool, so the real question is what the TMS around it costs. Techvia TMS runs $49/month with unlimited users and unlimited trucks, and that plan includes driver, carrier and dispatcher settlements alongside the dispatch board, customer invoicing, and document storage for BOLs, PODs and rate confirmations. It’s a flat rate, not a per-seat charge, which matters once you’re running 10-75 power units and don’t want settlement access to be the thing that decides who gets a login.
If you’re comparing this against other tools by feature and price point, the TMS software pricing guide for small fleets breaks down what typically sits behind different price tiers. For a general reference on what a TMS platform does end to end, the TMS topic hub is a good starting point if you’re still mapping out the full feature list before you commit.
Live GPS tracking from the driver’s phone — no ELD required — and shareable customer tracking links are also part of that same $49/month plan. ELD integrations with Samsara and Geotab, EDI X12 204 load tenders, and the AI Dispatcher that ranks drivers and carriers by deadhead and margin are available on higher plans; you can see the full breakdown at Techvia TMS.
How do you switch from spreadsheets without missing a pay period?
Run both systems in parallel for one full settlement cycle before you retire the spreadsheet. Import your existing driver profiles, pay types, and deduction schedules first, then process one week’s settlements in both the old spreadsheet and the new software and compare the net pay figures line by line. If the numbers match for every driver, you’re clear to drop the spreadsheet the following week.
Keep the last three completed spreadsheet cycles on file even after you switch. Drivers occasionally ask about a settlement from a few weeks back, and having the historical version handy avoids a scramble.
If you’re still weighing a full move off spreadsheets, TMS vs spreadsheets for freight brokers covers the broader tradeoffs, not just settlements.
Driver settlement software is worth setting up correctly the first time, because bad pay data has a way of following a driver into every settlement after it. If you want to see how driver, carrier and dispatcher settlements work alongside dispatch, invoicing and GPS tracking on one flat monthly plan, start a 30-day free trial with no credit card required at tms.techvia.software/register or read more about Techvia TMS.
FAQ
Can driver settlement software handle owner-operators and company drivers at the same time?
Yes, as long as the software supports pay types at the individual driver level rather than one pay structure for the whole fleet. Each driver profile should carry its own formula — per mile, percentage of linehaul, or a hybrid — so the settlement run applies the right calculation automatically.
Does driver settlement software replace payroll?
No. It calculates gross and net pay per driver based on loads, deductions and accessorials, and produces a statement, but tax withholding and payroll disbursement for company drivers typically still run through a separate payroll process. Owner-operator and lease driver settlements are usually paid directly rather than through payroll.
How often should you run driver settlements?
Most carriers settle weekly, tied to a fixed cutoff so late PODs or unresolved detention claims don’t hold up the whole batch. A consistent cutoff also makes it easier to catch a missing document before the settlement goes out, rather than after a driver calls asking where a load went.
What happens if a load’s paperwork is missing when settlements run?
Most systems let you flag that load and exclude it from the current settlement without holding up the rest of the driver’s pay. It