Driver Pay Calculations Explained: Per-Mile, Flat Rate, and Percentage

· 7 min read

Ask ten trucking owners how they pay their drivers and you'll get ten variations on three themes: per-mile, flat-per-load, or percentage. The right answer for your fleet depends on your lanes, your driver pool, and how much variability you can absorb week to week. The wrong answer shows up six months later as a retention problem you can't trace back to its source.

This post walks through each pay model — what it rewards, what it punishes, what data it requires — and how to set it up so the weekly settlement runs itself without anyone touching a calculator.

Per-mile pay

The dominant model in over-the-road trucking. The driver gets a fixed rate per mile driven, paid weekly based on miles delivered in that week.

Typical rates: $0.45 to $0.75 per mile for company drivers, depending on experience, equipment, and lane mix. Owner-operators pulling their own trailer often run $0.85 to $1.25.

What it rewards

  • Volume. The driver who runs more miles makes more money. Aligns with company revenue (assuming your customer rates are also per-mile.)
  • Predictable pay structure. Drivers can do the math themselves: rate × miles = paycheck. No surprises.
  • Easy A/P math. Weekly settlement is just a sum across the driver's delivered loads.

What it punishes

  • Detention and dock waits. If a driver sits four hours at a shipper, they earned zero in those four hours. Detention pay can offset this, but only if you actually invoice for it and pass it through.
  • Dense urban lanes. A 200-mile run that takes 8 hours because of traffic pays the same as a 200-mile run that takes 3 hours on the interstate. Drivers learn to refuse the bad lanes.
  • Wrong miles. Most spreadsheet operations underpay per-mile drivers because they use straight-line distance instead of actual road miles. The two can differ by 15-25%, which on a $0.55/mi rate is $50-100 per load the driver isn't getting.

That last point matters more than people think. FreightBoard pulls Google Directions road miles for every delivered leg automatically — door-to-door, the same number Google Maps shows in the car. The weekly per-mile calc uses that number, not haversine. It also caches the result per load so you only hit the API once.

Flat-per-load pay

The driver gets a fixed dollar amount per load, regardless of miles. Common in local + last-mile delivery, dedicated lanes, and any operation where the loads are roughly the same size.

Typical rates: $100 to $300 per pickup or delivery for local trucks, $400 to $800 for regional dedicated runs.

What it rewards

  • Speed. The driver who finishes faster takes more loads in a day. The pay structure aligns with throughput.
  • Local + last-mile efficiency. You pay the same whether traffic is good or bad — the driver absorbs the variability, but they also keep the upside on a fast day.
  • Simple to communicate. No miles math, no percentage math. "It's $200 per pickup" — done.

What it punishes

  • Big miles loads. A 50-mile and a 500-mile load pay the same — the driver loses money on the long one. You can't run a regional fleet on flat-per-load without adding mileage tiers.
  • Detention. Same problem as per-mile. The driver eats waiting time.

Flat pay is the right model for the local and last-mile legs of a consolidator move. When you punch in a load with a local pickup truck, you enter the flat amount once — the driver's weekly settlement picks it up automatically alongside any per-mile loads they ran the same week.

Percentage of linehaul

The driver gets a fixed percentage of the linehaul revenue on each load. Common with owner-operators and percentage-pay company drivers.

Typical rates: 25% to 35% for owner-operators not pulling their own trailer, 65% to 75% if they're a complete owner-operator running on your authority.

What it rewards

  • Aligned incentives. Driver makes more when you charge more. Easier to push rate increases through to drivers without resistance.
  • Lane-mix flexibility. Driver doesn't care about miles per se — they care about revenue per day. Frees you to mix dense local and long-haul without renegotiating pay.
  • Owner-operator economics. The percentage covers fuel, maintenance, and depreciation in a way per-mile doesn't unless you also do fuel surcharge passthroughs.

What it punishes

  • Discounted rates. If you cut a customer rate, the driver's pay drops in lock-step. Drivers get angry about decisions you made for strategic reasons (winning a customer back, filling capacity).
  • Accessorial leakage. If you don't separate linehaul from fuel surcharge / detention / lumper, the driver gets percentage on everything — which can over-pay them on revenue you needed to cover real out-of-pocket costs.

That last one is why FreightBoard tracks linehaul revenue as a separate field from accessorials. Percentage drivers get paid on linehaul; the accessorial total is internal and doesn't dilute the driver's percentage base.

Hybrid models

Most real fleets don't pick one model. They pay one driver per-mile because they run regional dedicated, another driver flat because they run local, and a third driver percentage because they're an OO. The TMS needs to handle all three at once.

FreightBoard stores the pay model on each driver record. When the weekly A/P calc runs, it looks at each delivered leg, checks the assigned driver's pay setting, and applies the right math:

  • Per-mile → road miles × rate
  • Flat-per-load → driver's flat rate
  • Percentage → linehaul × percentage

If a single leg has a flat-pay override (which is what happens on a local pickup leg with a flat amount entered at load creation), that overrides whatever the driver's default model is for that leg. Useful for one-off contractor pickups where the rate is per-pickup regardless of how the driver normally bills.

Adjustments and deductions

Real driver pay isn't just the load math. Every week brings adjustments: detention reimbursement, fuel advances pulled back, equipment damage chargebacks, performance bonuses, safety deductions. The settlement screen needs a way to add these per driver per week without touching the load records.

FreightBoard's A/P tab has a one-click "Add Adjustment" on every driver row. Pick the type (bonus, deduction, reimbursement), enter the amount and a description, save. The adjustment shows on the printable settlement remit alongside the load lines, and the net pay updates automatically.

Settlement remits drivers actually trust

The hardest part of payroll isn't the math — it's the relationship. A driver who trusts the settlement number doesn't have to call you about every paycheck. A driver who doesn't trust it spends Monday morning arguing about Friday's pay.

The settlement remit needs to show the driver:

  • Every load they ran in the week
  • The miles or flat or percentage that drove the pay calc
  • The pay per load
  • Any adjustments line by line
  • Gross, deductions, net

FreightBoard generates a one-page printable remit per driver per week. Hand it to them or email it. The line items match what they ran. Disputes drop to almost zero because the receipt is itemized.

One last thing about A/P automation

The biggest time-save in driver A/P isn't the math — it's not having to assemble the data every week. In a spreadsheet operation, someone (usually the owner or a part-time bookkeeper) sits down on Monday and:

  1. Pulls the week's delivered loads from the dispatch sheet
  2. Looks up each driver's pay rate
  3. Calculates miles or flat or percentage for each load
  4. Adds adjustments from a separate notes file
  5. Subtracts deductions
  6. Types the final number into a check or ACH push

That's 2-4 hours a week, every week, forever. In FreightBoard, that workflow is opening the A/P tab, scanning for any flagged "$0 pay" rows that need attention, and clicking Print Settlement on each driver. Total time: 15-20 minutes once you're set up. The system already calculated everything because it had the load data, the driver records, the road miles, and the adjustment log all in one place.

See it in action with the A/P tab on a delivered load week.