IFTA Audit Defense: Mileage, Fuel Records & Compliance Guide

IFTA regulations require carriers to retain all supporting mileage and fuel records for a minimum of 4 years from the date the quarterly IFTA tax return was due or the date it was filed, whichever is later. This retention rule is uniform across all US and Canadian jurisdictions bound by the International Fuel Tax Agreement. Records covered include GPS or ELD raw mileage data (not just monthly summaries), individual fuel receipts (credit card statements alone are insufficient), trip records with origin/destination/route/jurisdiction miles, copies of every filed quarterly return with supporting worksheets, and any amended returns. In cases of suspected fraud, some jurisdictions extend the lookback window to 6 years; fleets handling overall federal tax records commonly retain everything for 7 years for that reason. The critical structural requirement introduced January 1, 2024: when using vehicle tracking systems for mileage records, the system must retain data at 10-minute minimum intervals when the engine is on, capturing VIN or unit number, date and time, latitude and longitude to at least 4 decimal places (0.0001), and ECM odometer readings (dashboard or hubometer acceptable if no ECM available). If your telematics platform does not retain data in this format for 4 years, download and archive the raw data quarterly as backup — the auditor will accept your archived copy even if the platform vendor no longer has it.

Five factors drive IFTA audit selection. First, random selection: each base jurisdiction is required under IFTA to audit approximately 3% of its licensees annually, so any active IFTA carrier has a baseline probability of selection every year regardless of filing quality. Second, filing inconsistencies: quarter-over-quarter variance in miles, fuel gallons, or MPG outside typical ranges triggers pattern-matching flags. Large swings in reported jurisdiction miles without corresponding operational changes are particularly noticeable. Third, MPG outside plausibility bands: Class 8 diesel fleets typically report 5-9 MPG (with weighted average around 6-7). MPG substantially outside that range (either implausibly high suggesting underreported fuel, or implausibly low suggesting overreported miles) invites extended review. Fourth, late or amended filings: repeatedly missing quarterly deadlines or amending previously filed returns increases audit selection probability. Two consecutive missed quarters can trigger license revocation independent of audit. Fifth, cross-jurisdiction data mismatches: base jurisdictions share data with member jurisdictions, and reported miles in one jurisdiction that do not match fuel purchase patterns or roadside inspection records from that same jurisdiction can flag discrepancies visible only through the shared database. Compliance-focused fleets treat all five triggers as things to manage year-round, not just when returns are due.

Almost never. IFTA requires actual fuel receipts containing all required data elements: date of purchase, location (name and full address), gallons purchased, fuel type, and vehicle receiving the fuel identified either by unit number or through fuel card tracking that ties the transaction to a specific vehicle. Standard credit card statements provide only the merchant name, date, and dollar amount — they lack the gallons, fuel type, and vehicle-specific information the audit requires. Auditors will accept detailed fuel card reports (from carriers like Comdata, WEX, Fleet One, T-Chek, and similar programs) as adequate substitutes for individual receipts because these reports capture the full required data set electronically at the point of transaction. Generic credit card statements alone will result in disallowed tax-paid credits, meaning higher tax owed for those fuel purchases even if the fuel was legitimately purchased. The practical fix for most fleets is a fleet fuel card program that produces the detailed transaction data automatically, combined with a mobile receipt capture app for the rare cash purchases (with a company policy requiring same-day photograph and upload of any cash-purchase receipt). Modern IFTA-focused platforms integrate directly with major fuel card providers and pull transaction data on a daily basis, eliminating the receipt-collection burden entirely.

Yes, GPS and ELD data can satisfy IFTA mileage requirements and is increasingly the audit-preferred format, provided the data meets specific standards effective January 1, 2024. The tracking system must record and retain data at minimum 10-minute intervals when the engine is on, with each record containing five data elements: the vehicle identification number or unit number, the date and time of the reading, the latitude and longitude to at least 4 decimal places (0.0001), the odometer reading from the engine control module (ECM — or a beginning and ending dashboard/hubometer reading for the trip if no ECM is available), and adequate detail to reconstruct per-jurisdiction miles for the trip. Two important cautions. First, there is no official "IFTA-certified" ELD; vendor claims of IFTA certification are marketing, not regulatory approval. Verify the specific data elements yourself. Second, FMCSA ELD rules and IFTA data requirements are separate regulatory frameworks — an ELD compliant with FMCSA hours-of-service requirements may not meet IFTA data-retention standards for mileage. Confirm your platform captures and retains all five IFTA data elements for the required 4-year retention window. If your platform only retains raw GPS data for a shorter period, you must download and archive the raw data quarterly to maintain the full 4-year audit-ready record. Monthly, quarterly, or annual mileage summaries generated by the platform are not acceptable at face value during an audit — they must be supported by the underlying raw source data.

Consequences scale with the nature and severity of the audit findings. For small fleets (5-50 trucks) with sloppy but non-fraudulent record-keeping, assessments typically range from $3,000 to $25,000, covering additional tax owed plus penalties (typically 10% of unpaid tax) and interest (approximately 1% per month on unpaid tax from the original due date). Missing receipts and inability to produce raw GPS data are the most common contributors to assessments in this range. For more serious findings involving apparent fraud — deliberately understated miles in high-tax jurisdictions or fabricated fuel receipts — assessments can reach six figures and may trigger federal involvement including IRS coordination and potential criminal referral. Beyond direct assessment costs, the base jurisdiction can revoke the IFTA license after two consecutive missed quarters or after audit findings indicating pattern non-compliance. License revocation stops interstate operations until the license is restored, which requires paying the assessment in full plus reinstatement fees and often demonstrating corrective action. Fleets have 30 days from final audit notice to appeal in writing to their base jurisdiction, which coordinates the appeal with any other member jurisdictions where tax may be owed. The most reliable audit-defense strategy is quarterly reconciliation between telematics data and reported returns, which catches gaps within 10 days of each quarter close while data is fresh and correctable rather than 12-30 months later when the auditor arrives.