How IFTA Fuel Tax Rates Work Across Jurisdictions

Every IFTA member jurisdiction, each US state and most Canadian provinces, sets its own fuel tax rate, and that rate can differ by fuel type: diesel, gasoline, propane, and other fuels are often taxed at different rates within the same jurisdiction. A fleet running mixed fuel types across a multi-state route is dealing with a genuinely different rate for nearly every combination of jurisdiction and fuel type it touches in a quarter.

This is why a question like "what's the IFTA rate in Texas" or "what's the IFTA rate in Ohio" doesn't really have a single stable answer worth memorizing. The honest answer is always "check the current quarterly matrix," because the specific number for any one jurisdiction can and does move, and treating a rate you remember from a previous filing as still current is exactly how small, avoidable errors creep into a quarterly report.

IFTA, Inc. publishes an updated rate matrix every quarter, and individual jurisdictions can and do change their rates between quarters. That means a rate you used correctly last quarter isn't automatically correct for this one. Filing off a stale rate table is one of the more common, entirely avoidable errors fleets make, especially when someone is filling out the report from a saved spreadsheet template instead of pulling the current matrix.

The matrix itself is organized by jurisdiction and fuel type, and it's published far enough ahead of each filing deadline that there's no real excuse for using an outdated version, other than a manual process that just hasn't been updated. Fleets that file quarterly through a spreadsheet someone built once and keeps reusing are the ones most likely to be working from last quarter's numbers without realizing it.

The rate matrix only matters once you know two things for each jurisdiction: how many miles you drove there, and how much fuel you bought there. The report multiplies your jurisdiction-specific miles by an average fuel consumption rate to estimate fuel used in that jurisdiction, applies that jurisdiction's tax rate, and then credits you for tax already paid at the pump. Drive a lot of miles in a high-tax jurisdiction but buy fuel mostly in a low-tax one, and you'll typically owe more there. Do the reverse, and you're often due a credit.

This is also why fuel-buying strategy and IFTA outcomes are linked, whether or not a fleet manager thinks about it that way. Drivers who consistently fuel up in whichever state happens to be cheapest at the pump aren't doing anything wrong, but it does mean the quarterly IFTA reconciliation is doing more work to true up the difference between where fuel was bought and where it was actually burned.

Beyond using an outdated rate, the other frequent errors are mixing fuel types in one bucket (diesel and gasoline miles need to be tracked and reported separately), rounding mileage and fuel purchases inconsistently between what's reported and what receipts actually show, and missing a jurisdiction entirely because a short pass-through trip didn't get logged. Any of these can trigger a closer look during an audit even when the total tax paid is roughly right.

A subtler mistake is applying the wrong quarter's matrix to a trip that straddled a rate change. If a jurisdiction updates its rate mid-quarter, which does happen, the filing still has to reflect whatever rate was in effect on the actual dates driven, not just whatever rate happens to be current when the report gets filed weeks later.

None of this is complicated math, but it's tedious and error-prone to do by hand across dozens of vehicles and a full quarter of driving. A telematics platform that already knows exactly when a vehicle crossed each jurisdiction boundary can apply the current rate matrix to real mileage automatically, which removes both the stale-rate problem and the missed-jurisdiction problem at the same time.

The practical benefit shows up most clearly for fleets running short, frequent cross-border trips, exactly the kind that are easiest to under-report manually because no single trip feels significant enough to track carefully on its own. Automated jurisdiction tracking doesn't have that blind spot; it logs every boundary crossing regardless of trip length.

A short pre-filing checklist catches most of the errors covered above before they become a filed mistake: confirm you're pulling the current quarter's rate matrix rather than a saved copy, confirm mileage and fuel purchases are split correctly by fuel type where a jurisdiction taxes them differently, spot-check a handful of fuel receipts against your reported purchases for that jurisdiction, and confirm every jurisdiction your vehicles actually entered during the quarter, including short pass-through trips, is represented in the report.

None of these checks take long individually, but skipping them is exactly how a fleet ends up filing a report that's internally consistent but wrong, the kind of mistake that doesn't get caught until an audit compares your numbers against fuel receipts and toll or weigh-station records that show a different picture.