Quick answer: The IFTA filing mistakes that most often trigger an audit are mismatched mileage between trip records and fuel receipts, missing or illegible fuel receipts, math errors when converting between miles and kilometers or gallons and liters, and jurisdiction totals that don't add up to the total miles reported. Most of these come from manual recordkeeping — pen-and-paper logs, spreadsheets, and paper receipts stuffed in a folder. IFTA software fixes this by capturing mileage and fuel data automatically and flagging mismatches before you file, not after an auditor finds them.
Key takeaways
- Base jurisdictions select carriers for IFTA audits partly through data mismatches — like reported miles that don't match ELD or fuel data — according to the International Fuel Tax Agreement's audit guidance followed by member jurisdictions.
- The International Fuel Tax Agreement requires carriers to keep trip and fuel records for four years from the filing due date, per the IFTA Procedures Manual.
- A single misplaced decimal in a kilometers-to-miles conversion can throw off an entire quarterly return and is one of the most common clerical triggers for a follow-up review.
- Software that pulls mileage from ELD data and matches it to fuel purchases automatically removes the two biggest sources of human error: transcription mistakes and lost receipts.
Nobody plans to get audited. It usually happens because small errors pile up over several quarters until a state's IFTA auditor notices a pattern — miles that don't match fuel gallons, or a jurisdiction total that's suspiciously round. Here's the step-by-step version of how those mistakes happen, and what to do at each stage to avoid them.
Step 1: Know What Actually Triggers an Audit Before You File
Audits aren't random. Base jurisdictions run automated checks on every return, and certain red flags push a filing into manual review.
The most common triggers include:
- Mileage that doesn't match fuel purchases. If your reported miles suggest a fuel economy that's wildly better or worse than what your trucks actually get, that's a flag.
- Missing trip records for a jurisdiction where fuel was purchased. If you bought fuel in Ohio but didn't report any Ohio miles, expect questions.
- Consistently round numbers. Real trip mileage is rarely a clean number like 500 or 1,000. Auditors know this.
- Late or amended filings, especially repeated ones. A pattern of correcting the same type of error every quarter suggests a systemic recordkeeping problem rather than a one-time mistake.
- A sharp swing in reported miles per gallon from one quarter to the next with no fleet changes to explain it.
Before you file, pull your own numbers and sanity-check them against last quarter's. If something jumps by more than 10-15% with no obvious reason — a new truck, a new lane, a fuel price spike — dig into it before the state does.
Step 2: Fix the Recordkeeping Habits That Cause Mismatches
Most audit triggers trace back to how records are captured, not to fraud. The fix starts with tightening up four habits.
Trip records that don't match odometer readings. Paper logs and manual spreadsheets are where this usually breaks down — a driver estimates mileage instead of logging the actual start and end odometer reading, and the totals drift from what the truck's ELD recorded. Route mileage should always be reconciled against ELD or GPS data, not driver memory.
Fuel receipts that go missing or become unreadable. A gas station receipt printed on thermal paper fades within weeks. If you're storing paper receipts in a shoebox, some percentage of them will be unreadable or lost by the time you file, let alone by the time an auditor asks for four years of history.
Jurisdiction totals that don't add up. Every mile driven has to land in a jurisdiction. When dispatch changes a route mid-trip and nobody updates the log, the jurisdiction breakdown stops matching total miles — a mismatch auditors check for specifically.
Personal or non-taxable miles mixed into taxable totals. Bobtail miles, deadhead miles, and personal conveyance all get treated differently depending on the jurisdiction. Lumping them together inflates or deflates your fuel tax liability and creates exactly the kind of unexplained variance that draws scrutiny.
Don't skip this: the International Fuel Tax Agreement requires you to retain complete trip and fuel records for four years from the filing due date. Losing receipts isn't just a filing headache — it's a compliance gap that shows up the moment an audit reaches back further than your paper folder does.
Step 3: Get the Math Right — Especially Unit Conversions
Unit conversion errors are one of the most preventable causes of an amended return. IFTA requires reporting in miles and gallons or kilometers and liters, and carriers running mixed U.S. and Canadian routes have to convert between the two.
A driver who logs 500 kilometers but a clerk enters it as 500 miles has just overstated the trip by roughly 200 miles. Multiply that across a quarter of mixed-border runs and the jurisdiction totals stop reconciling — which is exactly the kind of discrepancy that turns into a request for supporting documents.
The same risk applies to fuel volume. A liter and a gallon differ by a factor of roughly 3.785, and if that conversion is done inconsistently across drivers or clerks, your average fuel economy per jurisdiction starts to look erratic even though nothing actually changed on the road.
The fix isn't "be more careful." It's removing the manual conversion step entirely. Software that logs distance and fuel in their original units and converts automatically, using a fixed and consistent formula, eliminates this category of error completely.
Step 4: Reconcile Before You Submit, Not After You Get a Notice
Reconciliation means checking that total miles across all jurisdictions equal your total fleet mileage, and that total fuel purchased matches what your fuel cards and receipts show, before you hit submit. Doing this after filing means you're reacting to a jurisdiction's letter instead of catching the problem yourself.
A basic pre-filing reconciliation checklist:
- Confirm total jurisdiction miles equal total fleet miles for the quarter.
- Match every fuel receipt to a corresponding trip and truck.
- Verify unit conversions were applied consistently across all drivers.
- Check that non-taxable miles (bobtail, personal conveyance) are separated from taxable miles.
- Compare this quarter's average MPG per truck to the prior quarter and investigate any large swing.
- Confirm every truck in your fleet is accounted for — a missing unit is as much a red flag as a mismatched one.
- Keep digital copies of every fuel receipt, not just the physical originals.
This is also where a lot of small fleets get caught off guard: reconciliation by hand across a dozen trucks and four quarters of paper records is genuinely time-consuming, which is exactly why the errors above happen in the first place. We covered the filing mechanics in more detail in IFTA Reporting Explained: What Every Fleet Owner Needs to Know, but the short version is: reconciliation is not optional, and it has to happen before you file, not after.
Step 5: Let Software Handle the Parts Humans Get Wrong
IFTA software prevents audits by removing the manual data entry that causes most of the mistakes above. Instead of a driver writing down mileage and a bookkeeper transcribing it weeks later, the system pulls mileage directly from ELD data and fuel purchases from card transactions, then matches them automatically.
Here's how that changes each failure point from Step 2:
| Manual Process | Common Failure | Software Approach |
|---|---|---|
| Driver logs odometer readings by hand | Estimated or transposed numbers | Pulls exact mileage from ELD/GPS |
| Paper fuel receipts filed in a folder | Faded, lost, or duplicate receipts | Digital capture at time of purchase |
| Clerk converts km to miles manually | Inconsistent or wrong conversion factor | Fixed, automatic conversion every time |
| Spreadsheet totals jurisdiction miles | Totals don't match fleet mileage | Automatic reconciliation flags mismatches |
| Quarterly filing built from memory | Missed deadlines, rushed entry | Pre-filled return with a review step |
This is also where the difference between older systems and newer ones matters. A traditional TMS often still requires someone to manually import or reconcile fuel data, while an AI-driven system flags anomalies — like an unexplained MPG swing — before you file, not after a jurisdiction notices it. We go deeper on that distinction in AI TMS vs Traditional TMS: What's the Real Difference.
For a fleet running five trucks, the record volume might still be manageable by hand, if barely. For a fleet running fifty, manual reconciliation across four quarters and multiple jurisdictions becomes close to impossible to do accurately every single time — which is usually the point where recordkeeping errors stop being occasional and start being systemic.
What to Do Next
Start with your last filed quarter. Pull the trip records and fuel receipts you used and check them against the reconciliation checklist above. If you find mismatches now, you have time to correct them before they compound into a pattern that draws attention.
If the review turns up more gaps than you expected, that's usually a signal the recordkeeping process itself needs to change, not just this quarter's numbers. Yolda AI builds IFTA reporting into its transportation management platform specifically so that mileage and fuel data are captured automatically instead of reconstructed by hand at filing time. If you want to see what that looks like for your fleet, reach out to the Yolda AI team for a walkthrough.
