The International Fuel Tax Agreement (IFTA) lets a carrier that runs heavy vehicles across US states and Canadian provinces file one fuel tax return with its home jurisdiction instead of one with every jurisdiction it drives through. The home jurisdiction then redistributes the tax. The simplification is real, but it rests on one thing: records of how far each vehicle drove in each jurisdiction and how much fuel it took on. That is exactly the data a fleet platform produces — and IFTA's own manuals say what format it must be in to count.
Who needs an IFTA license
The Articles of Agreement (section R245) define a qualified motor vehicle as one used, designed or maintained to transport persons or property that:
| Test | Threshold |
|---|---|
| Two axles | Gross vehicle weight or registered gross vehicle weight over 26,000 lb (11,797 kg) |
| Three or more axles | Any weight |
| Used in combination | Combined gross or registered gross weight over 26,000 lb (11,797 kg) |
Recreational vehicles are excluded. A carrier operating qualified motor vehicles in more than one member jurisdiction obtains a license from its base jurisdiction and carries decals on each vehicle. Licenses and decals are renewed for each calendar year, and under R345 renewal requires that all returns have been filed and all taxes, penalties and interest paid.
The weight test catches fleets that do not think of themselves as trucking companies. A beverage distributor or a propane delivery business with a few three-axle trucks crossing a state line is in scope regardless of how light the loads are.
R1220 sets a penalty of $50 or 10% of delinquent taxes, whichever is greater, for failing to file, filing late or underpaying, and R1230 adds interest on delinquent taxes.
The quarterly return
Under R960, the return and full payment are due on the last day of the month following the close of the quarter — in practice April 30, July 31, October 31 and January 31. If that day falls on a weekend or legal holiday, the next business day is the due date.
The return reports, by jurisdiction, the distance traveled and the fuel consumed, computed from the fleet's average fuel economy. Tax is owed to each jurisdiction on the fuel consumed there, with credit for tax already paid at the pump in that jurisdiction. A jurisdiction where you bought more fuel than you used produces a credit; one where you drove a lot and bought little produces tax due.
Distance records: where your tracking data comes in
The Procedures Manual, section P540, sets out what makes distance records adequate. There are two routes.
Trip records. Records produced without a vehicle tracking system must show, for each trip: the beginning and ending dates; origin and destination; the route of travel; beginning and ending odometer, hubodometer or ECM readings; total distance; distance in each jurisdiction; and the vehicle identification or unit number.
Vehicle tracking system records. If you rely on GPS data, P540.200 requires a record at least every 10 minutes while the engine is on, each containing:
- the date and time of the reading;
- latitude and longitude to at least four decimal places (0.0001);
- the ECM odometer reading (or, if none, beginning and ending odometer or hubodometer readings for the trip);
- the vehicle identification or unit number.
And the data must be accessible as an electronic spreadsheet or delimited file — XLS, XLSX, CSV or delimited text. A static image such as a PDF, JPEG, PNG or Word document is explicitly not acceptable.
The jurisdiction mileage summary your software produces is a convenience. The raw log is the record. If the summary cannot be reconciled to it, an auditor will rely on neither. The same discipline applies to the other data your trackers already collect — see telematics data you already pay for and GPS tracking for fleet vehicles.
Fuel records
Section P550 requires complete records of all fuel purchased, received or used, adequate for an auditor to verify the total fuel placed in qualified vehicles by fuel type. For retail purchases, tax-paid credit is allowed only with a receipt, invoice or seller's transaction listing, a credit card receipt, a third-party transaction listing, or an electronic record of the original receipt. Altered or illegible records are not accepted, and no credit is allowed for fuel put into a vehicle that is not a qualified motor vehicle.
That last rule is why fuel card data needs vehicle-level assignment. A card used to fill a pickup and a tractor in the same week, coded to one unit number, produces a fuel record the auditor will reject for one of them. The controls are the same as those in fuel cost management, with tax consequences added.
Keeping records for four years
Under P510, records must be kept for four years from the date the return was due or filed, whichever is later, plus any period covered by waivers or jeopardy assessments, and made available for audit on request. Switching telematics vendors does not reset that obligation: the position logs for the last sixteen quarters have to survive the migration — a requirement to write into any fleet data migration plan.
A quarterly routine
- Close the quarter on the same cut-off for distance and fuel. P540.300 allows slight deviations from calendar quarters only if cut-offs are consistent and the same for both.
- Reconcile distance: jurisdiction totals from the software against odometer or ECM totals per vehicle. Investigate gaps — a tracker offline for a day shows as missing miles.
- Reconcile fuel: fuel card and bulk fuel records against vehicles, and remove purchases for non-qualified vehicles.
- Check the fleet MPG for outliers by vehicle. An implausible figure usually means missing fuel or missing miles.
- File and pay by the last day of the following month, and archive the raw logs and receipts with the return.
Frequently asked questions
Does a single-state fleet need IFTA?
No. IFTA applies to qualified motor vehicles traveling in two or more member jurisdictions. A fleet operating entirely within one state pays that state's fuel taxes under its own rules.
Can I use my ELD data for IFTA?
Only if the records meet the Procedures Manual standard. If you rely on vehicle tracking data, P540.200 requires readings at least every 10 minutes with the engine on, four-decimal latitude and longitude, the ECM odometer and the vehicle number, exportable as a spreadsheet or delimited file.
How long do I keep IFTA records?
Four years from the date the return was due or filed, whichever is later, plus any period covered by waivers or jeopardy assessments, per section P510 of the Procedures Manual.
What is the penalty for filing late?
Under R1220 of the Articles of Agreement, $50 or 10% of delinquent taxes, whichever is greater, plus interest under R1230. The base jurisdiction may impose other penalties under its own laws.