How to Calculate Your IFTA Taxes

Every IFTA calculation follows the same basic sequence, jurisdiction by jurisdiction: figure out total fuel consumed across the whole quarter, allocate a share of that fuel to each jurisdiction based on the miles driven there, apply that jurisdiction's tax rate to get tax owed, then subtract tax already paid on fuel actually purchased in that jurisdiction. What's left is either a balance owed or a credit.

In formula terms: Total Miles ÷ Fleet MPG = Total Gallons Consumed. Then, for each jurisdiction: (Jurisdiction Miles ÷ Total Miles) × Total Gallons Consumed = Gallons Used in That Jurisdiction. Multiply that by the jurisdiction's tax rate for the quarter to get tax owed, then subtract tax already paid at the pump in that jurisdiction.

This same sequence repeats for every jurisdiction a vehicle touched during the quarter, which is exactly why the process gets tedious fast: a fleet running routes through six or eight jurisdictions in a quarter is running this same set of calculations six or eight times, per vehicle, every quarter.

Say a truck drives 10,000 total miles in a quarter at an average of 6 miles per gallon, using 4,000 of those miles in Jurisdiction A and 6,000 miles in Jurisdiction B. Total fuel consumed: 10,000 ÷ 6 = about 1,666.7 gallons. Jurisdiction A's share: (4,000 ÷ 10,000) × 1,666.7 = about 666.7 gallons. Jurisdiction B's share: (6,000 ÷ 10,000) × 1,666.7 = about 1,000 gallons.

Now apply tax rates, using illustrative placeholder rates only, not real current published rates: say $0.20 per gallon in Jurisdiction A and $0.25 per gallon in Jurisdiction B. Tax owed in A: 666.7 × $0.20 = about $133.34. Tax owed in B: 1,000 × $0.25 = $250. If the fleet actually bought 500 gallons in Jurisdiction A and 1,100 gallons in Jurisdiction B at those same illustrative rates, tax already paid in A was 500 × $0.20 = $100, and in B was 1,100 × $0.25 = $275. Net result: Jurisdiction A owes an additional $33.34 (drove more there than it bought fuel there), while Jurisdiction B is due a $25 credit (bought more fuel there than it actually burned there).

Notice what drove the result in each direction: Jurisdiction A owed more because the truck drove proportionally more miles there than the fuel it bought there would cover, while Jurisdiction B ended up a credit because the opposite was true. That relationship, miles driven versus fuel bought in the same place, is the entire mechanism behind every IFTA outcome, whether it's a five-dollar credit or a five-hundred-dollar bill.

The formula itself rarely trips anyone up. What goes wrong in practice is the inputs feeding it: using an outdated quarterly tax rate, an MPG figure that doesn't reflect the actual vehicle or route conditions, or jurisdiction mileage that's estimated from memory instead of measured. Any one of those errors compounds across every jurisdiction in the calculation, since the whole formula depends on getting miles, fuel, and rates right for every single jurisdiction touched that quarter.

A single fleet-wide MPG figure is also a common simplification that introduces error at scale. A loaded truck climbing mountain routes burns fuel differently than the same truck running flat highway miles, and averaging all of that into one MPG number across very different route types can meaningfully skew the gallons-consumed calculation for fleets with varied route profiles.

The part of this calculation that's genuinely hard to do accurately by hand isn't the math, it's knowing exactly how many miles were driven in each jurisdiction. A GPS platform that logs every jurisdiction boundary crossing removes that entire step: the mileage inputs are measured automatically instead of reconstructed from route memory, which is where most of the real-world error in this calculation actually comes from.

Once mileage by jurisdiction is measured rather than estimated, the rest of the formula becomes a matter of plugging in the current rate matrix and letting the arithmetic run, which is exactly the kind of repetitive, error-prone calculation that's worth automating rather than doing by hand across a real fleet every quarter.