Every IFTA jurisdiction is required to audit at least 3% of its licensed accounts every year, which means a clean multi-year filing history doesn’t make a carrier exempt from selection — it just makes the audit painless when it happens. The carriers who struggle aren’t usually the ones who cheated on their fuel tax filings; they’re the ones who filed honestly but can’t produce the specific, contemporaneous trip and mileage records an auditor actually asks for. IFTA audits are fundamentally a documentation exercise, and knowing exactly what gets checked, in what order, and what counts as acceptable proof is the difference between a routine review and a costly reassessment. That distinction — honest but unproven versus actually wrong — is the single most important thing to understand before ever opening an audit notice.
Key Takeaways
- Random selection accounts for many audits, but large fuel tax refund claims, mismatched jurisdiction data, and unrealistic mile-per-gallon figures are the most common audit triggers a carrier can actually control.
- Trip records need to be created at the time of the trip, not reconstructed afterward — auditors specifically look for records that were built contemporaneously rather than assembled after an audit notice arrives.
- A generic credit card statement is not acceptable fuel documentation — auditors require actual fuel receipts or fuel card reports with jurisdiction, date, gallons, and vehicle identification.
- Auditors increasingly prefer GPS or ELD data over hand-written logs because it provides independently verifiable, timestamped proof of exactly where a vehicle traveled.
- Missing or inconsistent records don’t just risk a denied claim — auditors are permitted to estimate fuel usage using unfavorable formulas, which routinely produces a higher tax liability than the truth would have.
- Records must be retained for four years from the filing date, and a system migration or provider change during that window is one of the most common places a documentation gap quietly opens up.
What Actually Triggers an IFTA Audit
Random selection accounts for a meaningful share of IFTA audits simply because every jurisdiction is required to audit a minimum percentage of accounts annually regardless of filing quality. But several specific patterns move a carrier up the priority list well before random selection ever comes into play. A quarterly return showing unusually large fuel tax refunds — meaning the carrier purchased far more fuel in a jurisdiction than the reported mileage in that jurisdiction would account for — draws direct scrutiny, because it suggests either a mileage allocation error or a fuel purchase that shouldn’t have been claimed there.
Mismatches between what a carrier reports and what another jurisdiction independently observes create a second common trigger. A state that photographs a truck at a toll plaza or weigh station in a jurisdiction where the carrier reported zero miles has grounds to flag the discrepancy to the carrier’s base jurisdiction directly. Reported fuel economy figures that fall outside a realistic range for the equipment type are a third trigger — an auditor reviewing a return showing implausibly high or low miles per gallon has an immediate reason to dig deeper before the audit even formally begins.
A carrier’s own filing pattern over time also factors in. Inconsistent reporting from one quarter to the next — a jurisdiction that shows heavy mileage one quarter and none the next, with no operational explanation — reads as a red flag even without any single number looking obviously wrong. Auditors reviewing multiple quarters side by side are looking for exactly this kind of pattern break, which is one more reason a habit of quarterly reconciliation catches problems a single-quarter review would miss.
Owner-operators leasing to a carrier, rather than running under their own authority, aren’t exempt from any of this scrutiny simply because someone else handles the paperwork. The underlying trip and fuel data still has to exist somewhere, and a lease arrangement that leaves recordkeeping ambiguous between the driver and the carrier is exactly the kind of gap that surfaces at the worst possible time.
The Three Things Auditors Actually Verify
An IFTA audit examines three categories of documentation, and understanding what falls into each one is the difference between preparing broadly and preparing for what actually gets checked. The first is mileage: trip records showing origin, destination, route, and beginning and ending odometer readings for every trip, broken down by the specific jurisdiction miles were driven in. The second is fuel: receipts or fuel card reports documenting date, location, gallons, fuel type, and the specific vehicle for every purchase. The third is reconciliation: whether the total reported miles and total reported fuel purchases across all jurisdictions actually add up to the quarterly return the carrier filed.
Trip records carry the heaviest scrutiny because they’re the category most commonly built after the fact rather than in real time. Auditors are trained to look for exactly this — records that were reconstructed from memory or from a route planner weeks after an audit notice arrived, rather than logged contemporaneously as the trip happened. A trip record built at the moment of travel, even a simple one, carries far more credibility than a detailed one assembled retroactively, because contemporaneous records are inherently harder to fabricate and easier to cross-check against independent data.
The reconciliation step is where many otherwise well-documented carriers still run into trouble, because it requires the mileage side and the fuel side of the operation to actually agree with each other, not just individually look complete. A carrier can have flawless trip logs and flawless fuel receipts and still fail this check if the two data sets, added up, don’t match the totals on the filed quarterly return — a discrepancy that often traces back to a data entry error rather than any underlying compliance failure, but one that still triggers the same scrutiny and the same burden to explain it. Catching that kind of error requires actually running the reconciliation before filing, not assuming that two individually accurate record sets will automatically add up correctly.
Reconciliation errors often trace back to a single recurring source rather than dozens of scattered mistakes: a fuel card that occasionally gets used across two trucks in the same fleet without the driver correcting the vehicle ID, a dispatcher rounding trip mileage instead of pulling exact odometer figures, or a spreadsheet formula that silently breaks after a template gets copied for a new quarter. Finding and fixing that one recurring source is usually more productive than reviewing every individual trip line by line, because the same error tends to repeat itself across many records rather than appearing once.
Why Generic Fuel Records Get Rejected
A common and costly misunderstanding is treating a credit card statement as sufficient fuel documentation. It isn’t. A statement showing a charge at a fuel station tells an auditor a purchase happened, but it doesn’t show the fuel type, the gallons purchased, or which specific vehicle the fuel went into — all of which IFTA requires. Actual fuel receipts or a fuel card program’s detailed transaction report, capturing those specific fields for every purchase, are what auditors require, and a carrier that discovers this gap only after an audit notice arrives has no way to retroactively produce documentation for fuel purchased months or years earlier.
GPS and ELD Data Now Carry More Weight Than Manual Logs
Auditors increasingly treat GPS and ELD data as the preferred form of mileage evidence, specifically because it’s independently generated and timestamped rather than self-reported by the driver after the fact. A hand-written trip log can be edited or reconstructed; a GPS track showing the actual route, with timestamps a carrier didn’t create and can’t retroactively alter, resolves a mileage dispute far more definitively. Carriers running ELDs or fleet telematics platforms for hours-of-service compliance already generate most of this data — the missing step in most fleets isn’t collecting it, it’s actually exporting and organizing it specifically for IFTA purposes rather than treating it purely as an HOS compliance tool.
This overlap matters because it means many carriers already have exactly the evidence an IFTA audit needs sitting in a system built for a different regulatory purpose. Confirming that a fleet’s ELD or GPS platform can export a clean, jurisdiction-by-jurisdiction mileage breakdown — and doing that confirmation before an audit notice arrives, not during the thirty-day preparation window after one does — turns an existing compliance investment into IFTA audit preparation without any additional cost.
Not every ELD or telematics export is built for this out of the box, which is worth confirming well before it matters. Some platforms report only total daily or trip mileage without a jurisdiction-level breakdown, requiring a manual cross-reference against a route map to allocate miles by state — a workaround that works but adds a step an auditor-ready export would have eliminated. Testing a platform’s export format against an actual quarterly filing, once, well ahead of any audit notice, reveals whether that extra step is something the fleet needs to plan around.
What Happens When Records Don’t Hold Up
Incomplete or inconsistent documentation doesn’t simply result in a warning — auditors are explicitly permitted to estimate a carrier’s fuel usage using formulas that default toward higher tax liability when the underlying records can’t support a more accurate calculation. This is one of the more consequential facts about the audit process that catches carriers off guard: an honest carrier who genuinely paid the correct taxes but can’t prove it on paper can end up assessed for more than they actually owed, simply because the estimation method used in the absence of good records isn’t designed to favor the carrier. Fleets managing multi-state operations across varying state-by-state trucking regulations already juggle enough jurisdiction-specific requirements without adding an inflated fuel tax assessment on top of it — which is exactly the outcome incomplete IFTA records tend to produce.
The financial exposure from this estimation method compounds the way any assessment based on extrapolation does: if an auditor samples a handful of trips and finds a 15% mileage discrepancy, that percentage can be applied across every unverifiable trip in the audit period, not just the ones actually reviewed in detail. A gap that looks small in a single sampled quarter can translate into a much larger total assessment once it’s applied across two or three years of filings — which is exactly why the cost of fixing a documentation habit today is almost always smaller than the cost of an assessment built on an unfavorable estimate later.
A carrier that discovers a records gap mid-audit still has better options than doing nothing. Informing the auditor immediately, rather than trying to quietly patch the gap, sometimes opens the door to alternative documentation — bank statements, fuel card reports, or other secondary evidence the auditor may accept in place of the missing primary record. Cooperation and transparency during the process consistently produce better outcomes than an audit where the auditor discovers gaps the carrier tried to conceal.
Making Recordkeeping a Quarterly Habit Instead of a Crisis Response
The carriers who move through an IFTA audit with minimal friction are seldom the ones scrambling during the thirty-day notice window — they’re the ones who reconcile mileage and fuel purchases every quarter as a matter of routine, well before any audit is on the horizon. That habit also pays off independent of audit risk: the owner-operator tax deductions that depend on accurate mileage and fuel records benefit from the same quarterly discipline, since clean records serve both the tax-deduction side and the IFTA-compliance side of the same underlying paperwork.
Records need to be retained for four years from the filing date, which is longer than most carriers assume when they’re deciding how long to keep receipts and trip logs. A carrier that only keeps records for a year or two, assuming that’s sufficient, may discover during an audit notice covering an earlier period that the records they need were already discarded — a gap with no fix available after the fact. A change in fuel card provider, telematics platform, or accounting system during that four-year window is one of the most common places this gap opens up, since old export files sometimes become inaccessible once a subscription lapses. Archiving the underlying data before closing out any old account, rather than just canceling the subscription and moving on, closes that gap before it becomes a problem.
Quick Reference: Before an IFTA Audit Notice Ever Arrives
A short set of habits, maintained quarterly rather than assembled under audit pressure, covers most of what an audit actually checks:
- Log every trip contemporaneously — origin, destination, route, and odometer readings — rather than reconstructing records after the fact
- Confirm the fleet’s GPS or ELD platform can export a clean, jurisdiction-by-jurisdiction mileage breakdown, not just a total mileage figure
- Keep actual fuel receipts or detailed fuel card reports, never relying on a generic credit card statement as fuel documentation
- Reconcile total reported mileage against total reported fuel purchases every quarter, before filing rather than after
- Retain every IFTA-relevant record for a full four years from the filing date, not just for as long as feels reasonably necessary
- Flag unusually large refund claims or unrealistic fuel-economy figures internally before filing, since those are the exact patterns that draw auditor attention
A carrier maintaining these habits every quarter experiences an audit as a paperwork exercise rather than a financial threat, because the documentation an auditor asks for already exists in an organized, exportable form.
The Bottom Line
An IFTA audit is not primarily a test of whether a carrier paid the correct fuel taxes — most carriers who fail an audit paid correctly and simply couldn’t prove it with the specific, contemporaneous records auditors require. Trip logs built after the fact, fuel purchases documented only by credit card statements, and mileage data that doesn’t reconcile against fuel purchases are the three failure points that turn an honest filing history into a costly reassessment.
None of the fixes here require new systems most fleets don’t already have. A quarterly habit of reconciling mileage against fuel purchases, confirming that existing GPS or ELD data can actually produce the jurisdiction-by-jurisdiction breakdown an auditor will ask for, and keeping real fuel receipts rather than statements closes the gap between a filing that’s technically correct and one that can actually prove it during the one in every several years an audit notice shows up. The fleets that treat this as routine paperwork, rather than an occasional emergency, are the ones that experience an audit as a formality rather than a financial event.
