Why settlements matter so much
For a driver, the settlement statement is the company. They do not see your margins, your customer contracts, or the hours your payroll clerk spent on Thursday night. They see one document a week, and it either matches what they think they earned or it does not. When it does not, they call. When it keeps happening, they leave.
For the carrier, settlements are a control point. Driver and owner-operator pay is one of the largest costs in the business, and every error runs in one of two directions: you overpay and lose margin, or you underpay and lose trust. Either way, someone in the office spends time researching, correcting, and explaining.
The good news is that settlement accuracy is a solvable problem. It comes down to clear pay rules, complete data from dispatch, fuel, and ELD systems, a disciplined reconciliation before pay goes out, and a statement a driver can check without calling the office.
Pay types and where they go wrong
Most carriers use more than one pay method, sometimes several on the same trip. Each one needs a written rule, a clean setup in the system, and a clear line on the statement.
| Pay type | How it works | Common sources of error |
|---|---|---|
| Loaded mileage | Rate per mile for miles driven with freight | Mileage method (practical vs. shortest), routing version, missed stop-offs, miles from the wrong origin |
| Empty mileage | Rate per mile for deadhead, sometimes at a different rate | Deadhead not recorded, wrong starting point, inconsistent policy on short empty moves |
| Percentage of revenue | Driver or owner-operator receives a percentage of linehaul or total revenue | Unclear definition of what revenue counts, such as whether FSC and accessorials are included; rerates after settlement |
| Hourly | Pay per hour, common in local, city, and yard work | Clock-in records that do not match ELD or timeclock data, overtime rules, unpaid waiting time |
| Stop pay | Flat amount per additional pickup or delivery | First and last stops counted inconsistently; stops added after dispatch not paid |
| Detention or layover pay | Pay for waiting beyond free time or for overnight delays | Not entered because dispatch never recorded the event; unclear rules about whether pay depends on the customer paying |
| Flat or load pay | Fixed amount per load or run | Run definitions drift; special runs paid from memory |
| Other accessorial pay | Tarping, driver assist, hazmat, border crossing, breakdown | Driver earns it but nobody tells payroll |
Write the pay rules down
If a pay rule only exists in the head of your payroll clerk or a dispatcher, you have two problems: errors when that person is out, and arguments when a driver remembers it differently. For every pay type, document:
- Who it applies to: company drivers, owner-operators, specific divisions or fleets.
- The rate and the unit: per mile, per hour, per stop, percentage, or flat.
- The calculation method, including mileage source and version, rounding, and minimums.
- What triggers it, and what evidence is needed, such as ELD times or a signed delivery receipt.
- When it is paid, especially if it depends on customer billing or paperwork.
Give drivers the rules that apply to them in writing at hire, and again whenever they change.
Get complete data from dispatch, ELD, and fuel
Most short settlements are not calculation errors. They are missing data. The driver sat four hours at a receiver, took an extra stop, or tarped a load, and nobody entered it. The system paid exactly what it was told.
- Record events as they happen. Dispatch should add stops, detention, and layovers to the trip when they occur, not when the driver calls about pay.
- Use ELD and telematics data. Arrival and departure times from the ELD or geofences give objective evidence for detention and hourly pay.
- Connect billing and pay. When a customer is billed detention or a stop charge, the matching driver pay should be prompted from the same record, and vice versa.
- Import fuel card transactions. Fuel purchases and cash advances should flow automatically to the right driver and unit, not be re-keyed from a report.
- Close trips on time. Set a cutoff for paperwork and trip completion before each settlement run, and make missing items visible before pay day, not after.
Deductions, escrow, and recurring charges
Deductions cause more settlement calls than almost anything else, because they are the part of the statement where money goes away. Every deduction should be authorized, expected, and traceable.
| Deduction type | Examples | What drivers need to see |
|---|---|---|
| Advances | Fuel card cash advances, comchecks, payroll advances | Date, location or reference, and amount for each advance |
| Fuel purchases | Owner-operator fuel billed back through the carrier's fuel card | Transaction detail, gallons, price, and any discount applied as the lease specifies |
| Recurring charges | Insurance, equipment lease or rental, plates, ELD or device fees | Description, amount, and remaining balance where applicable |
| Escrow | Owner-operator escrow or maintenance reserve contributions | Contribution this period and running escrow balance |
| Loans or repayments | Repayment of a carrier loan or repair advance | Payment this period and remaining balance |
| Chargebacks | Damage, tolls, permits, or other costs passed through | What the charge was for and supporting documentation |
Some rules of thumb that prevent disputes:
- No surprise deductions. A new deduction should be explained before it first appears.
- Show running balances for escrow, loans, and any deduction that pays down a balance.
- Keep authorization on file for each recurring deduction.
- Review deductions that would leave a driver with an unusually small or negative check before the run is finalized, so the conversation happens before pay day.
Deductions from employee wages and from owner-operator compensation are governed by different rules, and requirements can vary by state. Have your attorney and accountant confirm your deduction practices.
Fuel advances and fuel card reconciliation
Fuel cards are convenient for drivers and a reconciliation challenge for the office. Advances and fuel purchases arrive from the card provider, and each one has to land on the right driver, unit, and settlement period.
- Map every card to a driver and unit, and update the mapping when cards are reassigned or replaced.
- Import transactions automatically on a schedule rather than keying them from a statement.
- Separate cash advances from fuel purchases and other items such as scales or washes.
- Reconcile the fuel card provider's invoice to the transactions applied to settlements, so nothing is missed or charged twice.
- Investigate unmatched transactions every pay period, not at month-end.
- Use the same fuel data for fuel tax reporting so purchases are recorded once and used everywhere.
Reconciliation before pay goes out
A short, disciplined review before each settlement run catches most errors while they are still cheap to fix. Build it into the payroll calendar.
| Check | What to look for |
|---|---|
| Trip completeness | All delivered trips in the period are closed and included; nothing held without a reason |
| Mileage sanity | Trips with unusually high or low miles for the lane; empty miles that look wrong |
| Accessorial match | Detention and stop charges billed to customers have matching driver pay where policy calls for it |
| Percentage pay base | Revenue used for percentage pay matches the final rated invoice, including rerates |
| Fuel and advances | All imported transactions applied; nothing left unmatched |
| Deductions | Recurring deductions applied correctly; balances updated; no duplicates |
| Exceptions | Negative or unusually small settlements reviewed before release |
| Totals | Settlement totals reconcile to the general ledger after posting |
Keep a short log of what you corrected each run and why. After a few weeks, the log tells you which upstream process to fix, whether it is dispatch entry, mileage setup, or fuel card mapping.
Statements drivers can actually read
A good settlement statement answers the driver's questions before they pick up the phone. A poor one sends every driver to the payroll desk. Design the statement around how a driver checks pay:
- Trip by trip. Each trip shows the load or trip number, dates, origin and destination, loaded and empty miles, and each pay line with rate and amount.
- Accessorial pay listed separately. Stop pay, detention, layover, and other items each on their own line with the reason.
- Deductions itemized. Every advance, fuel purchase, recurring charge, and chargeback with a description and reference.
- Balances shown. Escrow, loans, and other running balances updated every period.
- Clear totals. Gross pay, total deductions, and net pay easy to find.
- Year-to-date figures. Useful for drivers and for tax time.
- Who to call. A name and phone extension or email for pay questions.
Test a new statement design with a few experienced drivers before rolling it out. If they can check their pay without help, it works.
Owner-operator considerations
Owner-operators are independent businesses, and their settlements need extra care. When an owner-operator leases equipment to a motor carrier, federal leasing regulations (the Truth-in-Leasing rules at 49 CFR Part 376) set requirements for the written lease, including how compensation is determined, which items may be charged back, and how escrow funds are handled. Settlements must follow the lease exactly.
- Compensation. Pay must be calculated the way the lease describes it. For percentage pay, owner-operators commonly have rights to see the documentation that supports the revenue the percentage is based on.
- Chargebacks. Items deducted from compensation should be listed in the lease, with supporting documentation available.
- Escrow. The lease should spell out how much is held, what it may be applied to, how the balance is reported, and when it is returned after the lease ends.
- Fuel and other programs. Fuel discounts, insurance programs, and equipment programs passed through to owner-operators should be applied as the lease and program terms state.
- Year-end reporting. Payee details and year-end tax forms need to be accurate, so keep remit-to and tax information current.
Confirm legal and tax matters with your advisors
This guide is practical operating advice, not legal or tax advice. Driver pay, deductions, worker classification, escrow, and year-end reporting are governed by federal and state rules that change over time. Have your transportation attorney and accountant review your pay practices, lease agreements, and statements.
Settlement accuracy checklist
- Every pay type has a written rule, and drivers receive the rules that apply to them.
- Driver pay profiles in the system match the written rules.
- Mileage method and version are consistent across pay, billing, and fuel tax.
- Dispatch records stops, detention, and layovers when they happen.
- ELD times support detention and hourly pay.
- Customer accessorial charges and driver accessorial pay come from the same event.
- Fuel card transactions import automatically and reconcile every period.
- Every deduction is authorized, expected, and shown with a balance where applicable.
- A pre-pay review runs before every settlement, with a correction log.
- Statements are trip by trip, itemized, and tested with drivers.
- Owner-operator settlements follow the lease, with supporting documentation available.
- Attorney and accountant have reviewed pay practices and lease terms.
How Strong Tower Consulting helps
Strong Tower Consulting has worked with carrier payroll and settlement teams since 2008, from TMS setup and go-live to custom settlement statements and cheques. Our Reporting & Business Documents practice builds settlement statements drivers can read, Business Process Optimization fixes the hand-offs between dispatch, billing, and payroll, SQL Data Mining & Analytics finds unpaid accessorials and mileage anomalies, and Training & Enablement gets payroll and dispatch staff working from the same rules.
Independent by design
Strong Tower Consulting never requires you to buy our software. Most settlement problems can be fixed in the system you already run, and our only goal is pay your drivers trust.
Frequently asked questions
Why do driver settlement disputes happen?
Most disputes come from a few sources: pay rules that live in someone's head instead of the system, mileage calculated differently than the driver expects, accessorial pay that was earned but never entered, deductions the driver did not expect, and statements that are hard to read.
Should we pay drivers practical miles or shortest miles?
That is a business and contract decision. What matters most is that the method is written down, explained to drivers at hire, configured consistently in the system, and shown clearly on the statement so drivers can check it.
How should fuel advances appear on a settlement?
Each advance should appear as its own line with the date, location or reference, and amount, tied to the fuel card or advance record it came from. Drivers should be able to match every deduction to something they did.
What is different about owner-operator settlements?
Owner-operators are paid under a lease agreement that should spell out compensation, chargebacks, and escrow terms. Settlements must follow that agreement exactly and give the owner-operator the documentation it requires. Confirm legal and tax obligations with your attorney and accountant.
Do we need new payroll software to fix settlements?
Often not. Many settlement problems are fixed by documenting pay rules, cleaning up driver pay profiles, connecting fuel and ELD data, and redesigning the statement in the system you already have. Strong Tower Consulting is independent and never requires buying our sister company's software.