Every IFTA return is two data sets pretending to be one: fuel bought, and miles run — by jurisdiction. The fuel side mostly takes care of itself, because fuel comes with receipts. The miles side comes with nothing unless you build the record, and that's exactly why distance records are where fuel-tax audits go wrong. The IFTA guide covers how the quarterly settlement works; this one is about the records that feed it.
Why the miles matter more than the fuel
Your return allocates fuel tax across states in proportion to the miles you ran in each. Get the miles wrong and every downstream number is wrong — the mpg the auditor recalculates, the tax owed to each state, the credit for tax already paid at the pump. An auditor who can't trust your distance records doesn't shrug; they reconstruct your miles using assumptions that are built to be unfavorable. The records aren't paperwork about the return. They are the return.
What a distance record must contain
For each trip, the record should show:
- the date the trip started and ended,
- the origin and destination,
- the route of travel,
- the beginning and ending odometer (or hubometer) readings,
- the total trip distance,
- the distance by jurisdiction — the line the whole system runs on, and
- the unit number of the vehicle.
The pattern to notice: the elements cross-check each other. Odometer readings should reconcile with total distance; the route should explain the jurisdiction split; the dates should line up with your fuel receipts. Auditors read the record the way you'd read a load confirmation — looking for the part that doesn't agree with the rest.
The odometer trail should be continuous across the quarter — the ending reading of one trip meeting the start of the next. Gaps are unexplained miles, and unexplained miles are what an auditor assigns to whichever assumption costs you most. Log every day the truck moves, and note the days it didn't.
Trip sheets vs ELD/GPS
Manual trip sheets work and always have: a sheet per trip with the elements above, totaled monthly by state. Their weakness isn't validity, it's survival — they depend on being filled in every day by someone who just drove eleven hours, and they fail in bulk when that discipline slips for a month.
Electronic records work too — ELD or GPS-based systems that log position frequently enough to reconstruct the route and split miles by state. Two cautions. First, the underlying data has to be there: an app that shows you a quarterly state summary but can't produce the trip-level detail behind it leaves you defending totals with nothing under them. Second, electronic doesn't mean automatic — somebody still has to make sure every mile the truck ran actually passed through the system, personal moves and shop runs included.
Either way, the test is the same: could you hand over trip-level records for any month, two years back, that reconcile with your odometer and your fuel receipts? Yes means the method is fine. No means the method is decorative.
The miles people miss
- Deadhead and bobtail. Every empty mile is a taxable IFTA mile. Missing them is the classic audit finding — the deadhead guide has the economics, but the compliance point is simpler: log them.
- Out-of-route miles. The detour around the closure, the stop for the truck wash — the odometer counted them, so the record must.
- Personal conveyance. Different rules may apply for hours-of-service, but the truck still crossed pavement in a jurisdiction — IFTA distance records account for the miles.
- Shop runs and yard moves. Small, forgettable, and exactly the kind of gap that breaks odometer continuity.
What happens when records are thin
Auditors don't take your word for the totals; they recompute. Thin records invite reconstruction — standard assumptions in place of your actual miles and mpg, applied in the direction that rarely favors you, plus the assessment, interest, and the extra attention next cycle. (The IFTA guide covers the notorious 4.00-mpg treatment thin records can earn.) The cost of the record-keeping habit is ten seconds a day. The cost of not having it is a number an auditor picks.
A habit that does double duty
Here's the good news buried in all this: the record IFTA wants is the record your own business math wants. Daily miles — loaded and empty — feed your cost per mile, your deadhead percentage, and your required rate. Log the day once and the same entry serves the auditor, the accountant, and the load you price tomorrow morning. One habit, three jobs — which is the only kind of habit that survives a driving schedule.
Ten seconds a day, kept forever
AxleVault's daily mileage log takes loaded and empty miles in one entry — sit days counted — and keeps fuel receipts read straight off the photo beside them. The same records run your live cost per mile and stand behind your IFTA quarters. Free for 14 days, no card required.
Try AxleVault freeQuick answers
What records does IFTA require for mileage?
Can I use my ELD or a GPS app for IFTA miles?
Do personal and deadhead miles count for IFTA?
How long do I keep IFTA mileage records?
This guide is general information, not tax advice. Tax rules change and interact with your specific circumstances. AxleVault is bookkeeping software, not a tax advisor — talk to a professional who knows trucking before you file.
