The FedEx Ground Payroll Audit: What It Checks, and How to Be Ready Before They Ask
Two of the most-read pieces on this site end the same way. The 10,000 GVWR rule closes by noting that FedEx audits this. The mixed-fleet overtime trap warns that hidden overtime exposure is much cheaper to find today than when it “surfaces in a FedEx payroll audit later.”
Both stop at the doorway. This article walks through it: what a FedEx Ground payroll audit actually examines, why it is not the ambush most contractors brace for, and the one structural reason you can walk into it already clean instead of scrambling.
The short version up front: a payroll audit is a classification check, and it runs on records you already hold a copy of every week. Treat audit-readiness as a property of your weekly pay run rather than a fire drill, and the audit becomes a review you walk into already clean.
A note before we start: this article is informational and not legal advice. Wage-and-hour law varies by state and changes over time. Have your specific compensation structure reviewed by a qualified employment attorney before adoption.
What a payroll audit is actually checking
A FedEx Ground payroll audit is, at its core, a single question asked across all your drivers: was each driver paid in a way that matches the truck they actually ran?
That question unpacks into the wage-and-hour rule that governs this whole business. Drivers operating vehicles above 10,000 lbs GVWR fall under the federal Motor Carrier Exemption and are not owed federal overtime, so a daily-rate structure is clean. Drivers operating vehicles at or below 10,000 lbs GVWR are non-exempt and must be paid time-and-a-half over 40 hours in a workweek. A reviewer is checking that the pay structure for each driver lines up with that rule — and, critically, that you can demonstrate it with records.
So an audit looks at roughly four things:
- Classification. Which drivers ran sub-10K vehicles, in which workweeks, and were those weeks paid as overtime-eligible?
- The exemption holds where you claim it. For your daily-rate drivers, did they in fact operate vehicles above 10,000 lbs GVWR, so the Motor Carrier Exemption genuinely applies?
- The math. Where overtime was owed, was the regular rate computed correctly and the premium actually paid?
- The paper. Can you produce the per-driver, per-week record that shows all of the above — without reconstructing it from memory?
None of this is a FedEx policy invention. It is the Fair Labor Standards Act, and FedEx’s interest in it is self-protective rather than adversarial: systematic misclassification across its contractor network is exactly the kind of structural problem that invites joint-employer claims against FedEx itself. The audit is the network confirming it operates within the law. If your records are clean, the review confirms it and moves on. If they have gaps, the review surfaces them while they’re still small.
If the terms MCE, GVWR, or the small-vehicle exception aren’t already second nature, read the 10,000 GVWR rule and the mixed-fleet overtime trap first — this piece assumes them.
It runs on records you already have
Here is the part most contractors don’t realize, and it changes the whole posture toward an audit.
The audit isn’t reaching for some private file you’ve never seen. The record of which driver ran which route on which day is the Weekly Service Worksheet (DSW) — the same .xls you download from MyGroundBiz every week to reconcile your settlement. That worksheet already ties a driver to a route, and your truck assignments tie that route to a vehicle. The raw material of a classification audit is, in other words, sitting in your own downloads folder fifty-two times a year.
That cuts both ways. It means the exposure is knowable in advance — there is no mystery data that only an auditor can pull. And it means the work of being ready is the same work you’re already half-doing every week when you process pay. You are not preparing for a separate event. You are deciding whether the pay run you already do is precise enough to defend.
Audit-readiness is a posture, not a fire drill
The companion overtime-trap article lays out a 90-day self-audit — pull every vehicle’s GVWR, sort above and below the 10,000-pound line, then comb the last quarter for workweeks a driver touched a sub-10K vehicle. That is the right exercise to run once, to find exposure you’ve already accumulated.
But a once-a-quarter manual comb is the wrong tool for staying clean. Exposure doesn’t accumulate quarterly; it accumulates one Tuesday Sprinter run at a time. The contractor who only checks when an audit is announced is always reconstructing months of vehicle assignments under pressure, from memory, against a deadline — which is exactly when mistakes and omissions creep in.
The alternative is to fold the check into the thing you already do every week. Each time you process the DSW into pay, that is the moment to ask: did any normally-exempt driver run a sub-10K truck this week, and if so, was that week computed the overtime-eligible way? Answered every week, the question never piles up. Answered never, it becomes a back-pay calculation that reaches across every workweek at once.
The difference between those two worlds is not effort. It’s when the effort happens — fifty-two small checks you control, or one large reconstruction you don’t.
What audit-ready records look like
Concretely, “ready” means you can hand a reviewer — or your own attorney — a record with these properties:
- Per-driver, per-week. The workweek is the unit the rule turns on, so that’s the unit the record has to resolve to — a monthly or annual summary can’t answer the question.
- Truck-aware. Each driver-week shows whether a sub-10K vehicle was involved, because that’s the fact that flips a week from exempt to overtime-eligible.
- Correctly computed where overtime applies. A sub-10K week paid hourly with a proper time-and-a-half premium, or a daily rate with the overtime reverse-engineered and documented — not a daily rate quietly applied to a week that wasn’t eligible for it.
- Defensible line by line. Every number traceable back to the DSW it came from, so “show me how you got this driver’s pay for that week” has a one-step answer.
Producing that by hand — re-checking, week after week, which driver ran which truck and whether a sub-10K week was paid the right way — is the chore that wore me down, and it’s why I stopped running payroll in spreadsheets. RouteContractor Payroll, the software I built to run my own stations, reads the same Weekly Service Worksheet (DSW) FedEx already gives you and turns it into a driver-by-driver gross-pay register you can defend line by line. You mark which trucks are 10,000 lb GVWR or less; it flags every week a driver ran one and computes that week hourly with overtime, trued up to daily pay if that’s higher. It is the calculation layer only — it doesn’t move money, file taxes, or render a legal opinion, and the GVWR you mark on each truck is yours to get right — but it makes “audit-ready” the default state of your payroll instead of a project you do under pressure. You can run a pay run on your own DSW at RouteContractor Payroll and look at the register yourself.
The posture: a review you walk into clean
There are two ways to experience a FedEx payroll audit.
In the first, the notice lands and your stomach drops, because you genuinely don’t know what months of mixed-fleet assignments will reveal once someone reconstructs them. You spend a week building the record you should have had all along, hoping the back-pay math is survivable.
In the second, the notice lands and it’s administrative. You already maintain the per-driver, per-week record, you already pay sub-10K weeks the overtime-eligible way, and producing the documentation is a matter of exporting what you keep anyway. The audit confirms what you already knew.
The distance between those two experiences isn’t luck and it isn’t the auditor’s mood. It’s a decision you made fifty-two weeks earlier about how precisely you’d process each pay run. An audit doesn’t create the exposure; it just reveals whichever posture you’d already chosen.
The single sentence to take with you
If you remember one sentence from this article, make it this one:
A FedEx payroll audit checks whether each driver was paid to match the truck they ran — and because it runs on the same Weekly Service Worksheet you download every week, “audit-ready” is a posture you set one pay run at a time, not a record you reconstruct under a deadline.
Find your exposure once with the 90-day self-audit. Then keep it at zero by making the check part of every weekly pay run — so the audit, whenever it comes, is paperwork you can already produce.