Quick answer: Auditing a driver settlement means checking five things before you release pay — miles paid against miles actually driven and invoiced, the pay rate calculation itself, deductions and advances, detention or accessorial pay, and fuel or IFTA charges that shouldn't double up. Do this on every settlement, every week, using a repeatable checklist rather than a memory-based glance, and reconcile against your ELD and TMS records, not just the settlement sheet itself. Fleets that skip this step tend to find the error after the driver has already complained — which costs more time than catching it beforehand.
Key takeaways
- A single mismatched mile-rate line can cost a fleet hundreds of dollars per driver per week if it repeats across settlement cycles without anyone catching it.
- The most common settlement errors involve mileage source mismatches (ELD vs. TMS vs. rate confirmation), duplicate deductions, and fuel surcharge or IFTA charges applied more than once.
- A documented audit trail — who checked what, and when — is what actually resolves a driver's pay dispute quickly instead of turning it into a week-long back-and-forth.
- Automated settlement tools can flag mismatches in real time, but a human still has to review and approve every exception before money moves.
Step 1: Understand why this step can't be skipped
A settlement error rarely stays a one-time event — it usually repeats until someone catches it, because the same rate table or deduction rule generates the next settlement too. If a driver is underpaid $180 on a load because the mileage source was wrong, and nobody catches it, that same rate error can follow them for weeks.
The cost isn't just the dollar amount. Settlement disputes eat dispatcher and accounting time — pulling up the load, checking the rate con, comparing mile logs, and explaining the math to a driver who's already annoyed. Multiply that by a fleet of 40 drivers and even a 2% error rate turns into a recurring administrative drag.
There's also a retention cost that's harder to put a number on. Drivers talk to each other, and a reputation for "settlements you have to fight for" pushes good drivers toward carriers who get pay right the first time. We covered the fuller cost breakdown in What Driver Settlement Errors Really Cost Your Fleet, but the short version is: the audit is cheaper than the dispute, every time.
Don't skip this: Never release a settlement based only on what the pay system calculated. Cross-check the underlying load and mileage data first — the calculation is only as accurate as the numbers feeding it.
Step 2: Verify mileage and load data before anything else
Start here because every other number in the settlement depends on it. If the miles are wrong, the mileage pay, fuel deduction, and even detention timing calculated off dispatch records will all be wrong too.
Check these before moving to pay calculations:
- Confirm the load count matches dispatch records. Every load the driver was paid for should have a corresponding completed status in your dispatch system — no phantom loads, no missing ones.
- Compare ELD miles to TMS miles for each load. These two systems calculate mileage differently often enough that a gap of a few miles is normal, but a gap of 50+ miles on a single load needs an explanation.
- Check the rate confirmation for the agreed mileage or flat rate. The number the broker or customer agreed to should match what's in the settlement — not an estimate, not a rounded figure.
- Verify empty and deadhead miles are handled per your pay policy. Some carriers pay full rate on deadhead, some pay a reduced rate, some don't pay it at all — the settlement should reflect whichever policy applies to that driver's pay agreement.
- Confirm loaded vs. unloaded status matches what was actually delivered. A load marked delivered in the TMS but still showing "in transit" in driver-submitted documents is a red flag worth chasing down before payment.
Step 3: Recalculate the pay itself, not just spot-check it
Recalculating the pay means running the math independently — mileage rate times verified miles, or percentage pay times the actual linehaul revenue — rather than trusting that the settlement software got it right. This matters most for percentage-of-revenue pay, where a rounding error on the load rate can throw off every driver paid a cut of it.
For mileage-based pay, multiply the verified mileage (from Step 2) by the driver's contracted rate. Confirm the rate itself is current — a driver whose pay agreement changed mid-quarter is a common source of using an outdated rate by mistake.
For percentage pay, confirm the percentage is applied to the correct base. Some carriers calculate the percentage off gross linehaul revenue, others off revenue minus fuel surcharge or other deductions first. Using the wrong base is one of the most common — and hardest to spot — settlement errors, because the final number looks reasonable even when it's off. We go deeper on how this differs by pay type in Owner-Operator vs Company Driver Settlement Calculations.
For detention and layover pay, confirm the wait time logged against the load actually exceeds the threshold in the driver's pay agreement (commonly two hours before detention pay kicks in, though this varies by carrier and by customer contract) and that the rate applied matches the agreement.
Step 4: Trace every deduction and advance back to a source document
Every deduction on a settlement should be traceable to something specific — a cash advance request, a fuel purchase, an equipment charge, a reimbursement offset. If a deduction line doesn't have a document behind it, that's the first thing to flag.
Common deduction errors worth specifically checking:
- Duplicate deduction entries. A driver advance entered once by dispatch and again by accounting is one of the most frequent errors in manual settlement processes, especially when advances are tracked in more than one place.
- Deductions applied against the wrong settlement period. A repair cost from three weeks ago showing up on this week's settlement, when it should have already been deducted, means the driver is being charged twice — or the fleet is missing revenue it thought it already recovered.
- Reimbursements not offsetting the right charge. If a driver paid for a repair out of pocket and submitted it for reimbursement, confirm it's added back, not just noted.
- Escrow or maintenance reserve deductions matching the agreed schedule. These should follow a fixed percentage or dollar amount per the driver's contract — not a number that drifts week to week.
Step 5: Check fuel and IFTA charges for double counting
The most expensive version of this error is a fuel surcharge or fuel deduction applied twice — once through a per-mile fuel charge and again through a separate IFTA-related line item. Because IFTA (International Fuel Tax Agreement) reporting and driver fuel deductions sometimes pull from overlapping data sources, it's easy for a fuel cost to get counted in both places without anyone noticing until a driver adds up their own numbers.
Confirm that:
- The fuel deduction on the settlement reflects an actual fuel purchase or a documented per-mile fuel charge — not both.
- IFTA fuel tax calculations, which carriers must file quarterly according to IFTA's reporting requirements, stay separate from individual driver settlements unless your pay structure specifically passes fuel tax costs to drivers.
- Fuel price adjustments — especially during periods of diesel price volatility — are applied using the correct rate for the week the load ran, not a stale or averaged rate. We walk through this scenario in detail in How to Recalculate Driver Settlements When Diesel Spikes.
| Error type | How it usually happens | What to check |
|---|---|---|
| Mismatched mileage | ELD and TMS calculate distance differently | Compare both sources per load, flag gaps over 50 miles |
| Duplicate deduction | Advance logged in two systems or by two people | Trace every deduction to one source document |
| Double fuel charge | Fuel deduction and IFTA line item overlap | Confirm each fuel cost appears in exactly one place |
| Rounding drift on percentage pay | Percentage applied to wrong revenue base | Recalculate manually against the rate confirmation |
| Stale pay rate | Driver's rate changed but old rate still used | Confirm current pay agreement before calculating |
Step 6: Build a repeatable audit workflow, not a one-off check
A workflow means deciding, in advance, who checks what and when — so the audit happens the same way every week regardless of who's covering payroll that day. Without a defined workflow, audits tend to happen only when someone's suspicious, which means most errors slip through.
A practical structure for most small-to-midsize fleets:
- Daily spot-checks on high-value or unusual loads — anything with detention pay, a manual rate override, or a load that took noticeably longer or shorter than expected.
- Weekly full review before settlements are released, covering every driver, using the five-step check above.
- One named owner per step. Dispatch confirms load and mileage data, accounting confirms pay calculation and deductions, and a manager signs off before release — three sets of eyes, not one person doing everything under time pressure.
- A documented trail for every settlement, even the ones with no issues. When a driver disputes a number three weeks later, "we checked it and here's the record" resolves it in minutes. "Let us look into that" turns into a multi-day back-and-forth.
Step 7: Use automation to catch what manual review misses
Settlement software reduces audit time by flagging mismatches automatically instead of requiring someone to manually cross-reference three systems for every driver, every week. A tool that reconciles ELD mileage against dispatched loads, checks deduction entries against source documents, and applies the correct pay rate from a driver's current agreement removes most of the manual comparison work described in Steps 2 through 5.
This is the workflow behind Yolda's settlement reporting: every earnings item — load pay, bonuses, deductions, reimbursements, prepayments — passes through an approval queue before it enters a driver's weekly settlement, and nothing is auto-approved or auto-paid. The system builds a side-by-side view of pay slip against load data so a reviewer can see the reconciliation directly instead of hunting for it across separate reports, and every settlement generates a documented, viewable record. Yolda calculates and reports the settlement — the company still pays the driver through its own bank or payroll, so the human review step in Step 6 doesn't disappear, it just gets faster and has fewer blind spots. If you're evaluating what a switch like this actually costs against the time it saves, Driver Settlement Software Cost for Fleets breaks that down.
What to do next
Start by picking one week's worth of settlements and running the five-step check above manually, even if it takes longer than usual. That exercise alone usually surfaces whether your current process has a systemic gap — a mileage source that never matches, a deduction category that keeps duplicating — worth fixing at the source rather than catching after the fact each week.
- Confirm your ELD and TMS mileage figures reconcile for at least one full week of loads
- Trace every deduction on that week's settlements to a source document
- Check for any fuel or IFTA charge appearing in more than one place
- Recalculate at least three settlements by hand to confirm the pay math independently
- Write down who owns each audit step going forward, and when it happens in your weekly cycle
