Geotab IFTA Reporting: How Automated Fuel Tax Reports Save Fleets Hours

An IFTA return asks for two numbers per jurisdiction: how far your qualified vehicles travelled there, and how much fuel you bought there. Fuel comes from receipts and fuel-card statements, which fleets already keep. Distance is the problem. Before telematics it came from trip sheets, drivers' notes and a map, reconstructed a quarter later, and it was the number auditors disallowed most often, because a reconstruction is an estimate however carefully it is made.

That is the whole of what automated IFTA reporting fixes. A device on the vehicle records position continuously, the platform matches those positions to jurisdiction boundaries, and the total distance in each one is a measurement rather than a memory. The return still has to be filed, the fuel still has to be reconciled, and the fleet still has to keep records — but the number that used to take an afternoon per truck now takes a report.

The GO device logs GPS positions and odometer throughout every trip. MyGeotab's IFTA report takes those logs for a date range and a set of vehicles, assigns each stretch of travel to the state or province it occurred in using boundary data, and totals the distance per jurisdiction per vehicle. Because the input is the same trip data used for everything else — dispatch, maintenance, the ELD — there is nothing separate to switch on or maintain; a fleet that is tracked is a fleet whose IFTA distance is being recorded.

Two things determine whether the output is audit-grade. The first is coverage: every qualified vehicle needs a working device for the whole quarter, because a gap in the log is a gap in the distance, and the report cannot invent what the device did not see. The second is grouping: the report should be run on the vehicles that are actually IFTA-qualified — generally power units over 26,000 pounds or with three or more axles — so that a pickup in the same fleet does not add its kilometres to the return.

The report gives you distance. It does not give you fuel purchases, which come from your fuel cards or receipts, and it does not file the return. Some fleets pair the export with a fuel-card integration so both inputs land in one spreadsheet; either way, the reconciliation of distance against fuel per jurisdiction is the last manual step, and it is a short one.

IFTA audits are conducted by the base jurisdiction, and what an auditor asks for is the distance records behind the return. A system-generated report tied to GPS data, with the trip logs behind it, is a fundamentally different thing to hand over than a folder of reconstructed trip sheets. The distances can be traced to individual trips, the trips to individual positions, and the auditor's sampling comes back matching the return because both came from the same data.

It also changes the conversation about gaps. Every fleet has them — a device unplugged during a repair, a truck that sat with a dead battery. With telematics the gap is visible and bounded, and the fleet can document it, rather than being unable to say which weeks of a truck's quarter are estimates.

Run the report once a quarter, before the filing deadline at the end of the following month: April 30, July 31, October 31 and January 31. Review the per-vehicle distances for anything that looks wrong — a jurisdiction you do not operate in, a vehicle with too few kilometres against its odometer, a border crossing nobody mentioned — and resolve those before filing rather than after. Export the report, set it beside the fuel purchases per jurisdiction, and file through the base jurisdiction's portal.

Then keep the export with the fuel records for the audit period, which is commonly four years. The value of the report is not only the hours it saves each quarter; it is that four years from now the number can still be explained.