Fuel Tracking and IFTA Mileage: How Telematics Handles Fuel Tax Reporting

By GPSWOX Editorial Team

IFTA reporting splits into two data streams a fleet has to capture accurately: miles by jurisdiction and tax paid fuel by jurisdiction. Telematics picks up the mileage stream on its own, the device in the vehicle is recording border crossings whether anyone asks it to or not, and then the platform imports the fuel card transactions so that both streams end up in the same place before the filing deadline.

Definition: Telematics based IFTA reporting works by recording GPS coordinates at every state and provincial border crossing a vehicle makes, converting those crossing records into jurisdiction level mileage totals, and then pulling in the fuel purchase data from the fleet’s fuel card provider so that the mileage and the fuel sit in one system when the quarterly return needs to be filed.

A fleet with two trucks where the owner also does the compliance paperwork, and occasionally drives the second unit when the regular driver is out, will typically spend an entire working day each quarter assembling IFTA mileage from fuel receipts and card statements and whatever handwritten notes the drivers kept. The same size fleet running a telematics platform spends ten minutes on the quarterly filing, sometimes less, because the mileage data is already broken out by jurisdiction and the fuel card data was imported automatically weeks ago. The dollar amount owed to each jurisdiction comes out the same in both cases, the same tax at the same rates on the same miles. The labour behind the number is where the difference sits.

This guide covers how telematics actually produces the IFTA ready mileage figures, what the fuel side requires alongside the mileage, where the integration gaps are between the two, and how to run a clean telematics based IFTA process that survives audit.

What IFTA actually requires

IFTA, the International Fuel Tax Agreement, covers the 48 continental US states and 10 Canadian provinces, and the basic idea is that a fleet registers with one base jurisdiction and files a single quarterly fuel tax return there rather than filing separate returns in every state and province it drove through. The return reconciles two numbers per jurisdiction the fleet operated in:

• The miles driven in that jurisdiction.
• The gallons of tax paid fuel purchased in that jurisdiction.

The settlement runs from the comparison. A fleet that bought more fuel in a state than it consumed there is owed a refund on the difference. A fleet that consumed more fuel in a state than it bought there owes tax on the difference. What the base jurisdiction does is collect the net result across every jurisdiction on the return and then distribute the individual settlements, sending money to the states that are owed and crediting the states that overpaid.

Both numbers have to be defensible to a level that survives an audit. Audits are conducted by member jurisdictions on a sample of licensees each year, and the audit standard is documentary: receipts, logs, GPS data, fuel card listings, with paper trip logs alone increasingly inadmissible without supporting electronic data. [1]

The mileage side: state line detection in real time

What modern telematics platforms do on the mileage side is log every state and provincial border crossing as it happens, without the driver doing anything or even being aware that a record was just created. The device records its position every five to thirty seconds while the vehicle is in motion, and the platform identifies when a position crosses a known boundary. The crossing record that results from that detection carries three data points, the timestamp, the GPS coordinates, and the odometer reading from the engine control module, and all three together are what make the record auditable. [1]

From that crossing data, the platform computes jurisdiction level mileage in real time:

• Miles between two crossings count toward the jurisdiction the vehicle was in.
• Adding up all the in jurisdiction segments for a given vehicle over the quarter gives the jurisdiction total, and the platform runs that addition automatically each time a new crossing is recorded, so the number is always current rather than something that has to be computed at filing time.
• At the end of the quarter, or really at any point during it, the platform can produce a summary filtered by vehicle, by month, or by jurisdiction, and that summary is already in the format the IFTA return requires.

Before GPS based tracking, the standard practice was for drivers to write down the odometer reading each time they crossed a state line, and the problem with that method, which auditors flagged more than any other issue, was that drivers forgot crossings, transposed digits, or recorded the reading a few miles late, and those small errors compounded into mileage figures that did not hold up at audit. With GPS crossing data, the mileage record and the audit evidence are the same thing, because the coordinates and timestamps that prove where the vehicle was are also the data points that produce the jurisdiction totals. [2]

Example: A driver crosses from Pennsylvania into Ohio at 14:23 with odometer reading 187,402, drives Ohio for ninety minutes, and crosses into Indiana at 16:08 with odometer reading 187,508. What the platform does with those two crossings is attribute the 106 miles between them to Ohio and add that figure to the Ohio quarterly total, and the driver never entered anything or even confirmed that a state line was crossed.

The fuel side: fuel card data does most of the work

Fuel purchases for IFTA reporting must show the date, the seller’s name and address, the fuel type, the gallons, the price, the purchaser, and the unit number of the vehicle that received the fuel. [3] Each individual receipt that meets that standard is acceptable, but the more useful artefact is the fuel card transaction listing, which carries every required field on every transaction automatically.

The integration with telematics works in two directions:

Telematics platform pulls fuel data. Most fleet platforms integrate with the major fleet fuel card providers, importing the transaction listing on a schedule. The fuel data lands alongside the mileage data in the same platform, and the IFTA report writes itself from the combined data set. [4]

Telematics platform matches fuel to vehicles and trips. With both data streams in the same place, the platform can match each fuel purchase to the vehicle that received it, the trip the vehicle was running at the time, and the jurisdiction the purchase happened in. The match removes most of the manual reconciliation a paper based IFTA process consumes.

There are two cases where this integration does not work and the data has to come from somewhere else:

• Cash fuel purchases. When a driver pays cash, no fuel card transaction exists for that fill, so the paper receipt has to come back to the office and someone has to key it into the platform manually, including the vehicle unit number and the jurisdiction where the purchase happened, because the system has no other way to pick it up.
• Bulk fuel drawn from yard tanks. The fuel card provider has no record of fuel dispensed from a fleet’s own storage, which means the delivery receipts for the tank and the per vehicle withdrawal logs have to be kept and entered separately, each withdrawal tagged to the vehicle and jurisdiction it belongs to.

What the quarterly process looks like

A telematics based IFTA workflow reduces the quarterly task to verification rather than reconstruction.

1. Last day of the quarter. The person responsible for IFTA compliance confirms that all trips have been uploaded, that the fuel card data has been imported for the full quarter, and that any manual fuel entries, cash purchases, and bulk fuel withdrawals have been logged in the platform. Then they run whatever pre IFTA check or validation report the platform offers.
2. First week after quarter end. Pull the draft IFTA report from the platform and compare the jurisdiction level mileage and fuel totals against the previous quarter’s numbers, because a large deviation in any single jurisdiction, say Ohio mileage dropping 40% quarter over quarter when the routes did not change, almost always points to a data gap or an unuploaded trip rather than an actual operational shift.
3. Reconcile exceptions. Any unmatched fuel purchases, missing unit numbers, or vehicles with mileage but no fuel purchases get checked and resolved.
4. Generate the return. What most platforms produce at this stage is IFTA formatted output, either a file that can be uploaded directly to the base jurisdiction’s electronic filing portal or a summary formatted for transcription onto the paper return.
5. File by the deadline. Returns are due April 30, July 31, October 31, and January 31. [5] What makes late filing particularly costly, beyond the penalty itself, is that it extends the four year data retention clock on all the supporting records, because IFTA measures the four years from the filing date or the due date, whichever comes later, so a return filed three months late adds three months to the retention obligation.
6. Archive the supporting data. Mileage records, fuel records, the card provider’s transaction listings, and the filed return itself stay on file for a minimum of four years from the due date or filing date, whichever is later, and the retention setting inside the platform needs to reflect that window specifically, because a number of platforms ship with a shorter default that will auto purge IFTA relevant data before the retention obligation expires.

Example: A regional carrier running eight trucks finished the second quarter with operations across five states, Pennsylvania, Ohio, Indiana, Illinois, and Michigan, and the platform’s mileage data showed 142,000 total miles split across those five jurisdictions. The fuel card data showed purchases in all five of those states and also in a sixth state where the fleet had zero recorded mileage, which flagged it as an anomaly. The operator pulled the trip history for the vehicle that made the purchase, found that the driver had taken a personal detour on a day off and fueled during it, and excluded those gallons from the IFTA fuel total before submitting the return.

Example: A two truck fleet that hauls cross border loads between the northeastern US and Ontario uses the telematics platform as its only source of IFTA data, and every time a truck crosses at Buffalo or Detroit or Champlain, the platform creates a crossing record and starts counting mileage in the new jurisdiction without the driver or the office doing anything. The fuel card data includes the Canadian purchases tagged by province. Eight jurisdictions appear on that fleet’s quarterly return, five US states and three Canadian provinces, and the filing takes the owner about forty minutes because the real work is confirming that the border crossings look right and that the Canadian fuel purchases are tagged to the correct provinces.

The audit defence

IFTA member jurisdictions audit a sample of carriers each year, and the audit itself is a records check, the auditor pulls the submitted return and then asks the carrier to produce the mileage records and fuel records that support the numbers on it. Most of the ways carriers fail these audits are well documented by the jurisdictions themselves, and a fleet running IFTA through telematics avoids the common ones mostly because the data is structured in a way that does not leave the gaps auditors typically find, not because the platform applies any special logic.

Mileage that does not tie to GPS. A carrier that submits mileage based on paper trip sheets gives the auditor nothing to verify the numbers against except the driver’s handwriting on a form, and when the auditor finds discrepancies, which is common because drivers record odometer readings inconsistently and sometimes skip crossings altogether, the contested mileage gets disallowed and the carrier owes tax on the reassessed figure. GPS sourced mileage is harder for the auditor to challenge because the crossing records carry coordinates and timestamps that are generated by the device, not written by a person, so disputing the mileage means disputing the GPS data itself rather than a summary number.

Fuel purchases that do not tie to a vehicle. Receipts without unit numbers cannot be assigned to a specific truck’s fuel total. A platform that requires a unit number on every fuel record, and prompts drivers when a card transaction lands without one, removes the problem at the source.

Inconsistencies between mileage, fuel, and MPG. What auditors typically do early in a review is calculate the implied miles per gallon for each jurisdiction and compare that number against the industry range for the truck type. If a figure comes out unreasonably high or unreasonably low, which usually means the mileage or the fuel data for that jurisdiction has an error in it, it triggers a detailed review of the underlying records. Fleets that run both data streams through a telematics platform tend not to produce those outliers, and the reason is straightforward: the mileage and the fuel data are matched inside the same system using the same vehicle identifiers, so the transposition errors and jurisdiction misattributions that happen when someone is reconciling the two in a spreadsheet do not arise in the first place.

Missing records past the four year window. If the auditor asks for the mileage and fuel records for a given quarter and the carrier cannot produce them, the consequence under IFTA is that every fuel tax credit that lacks documentation gets disallowed individually, line by line, and a carrier that was expecting a neutral or refund position can end up with a five figure assessment. A platform configured to retain GPS crossing data and fuel records for at least four years from the filing date eliminates that exposure automatically, because the records are there when the auditor requests them regardless of whether anyone in the office remembered to archive them. [3]

The cases telematics does not solve on its own

Three operational situations still need attention even with the cleanest telematics integration.

Bulk fuel from yard tanks. The deliveries to the tank and the per vehicle withdrawals from it have to be logged in a separate process, because the fuel card data stream has no way of knowing that fuel was dispensed from a yard tank rather than purchased at a retail station. A lot of platforms have a bulk fuel module that handles this, but it has to be set up, and the withdrawal records have to be entered, which means someone at the yard has to actually log every fill.

Cash fuel purchases. A driver who pays cash at the pump, usually because the fleet card would not go through or the station only took cash, creates a fuel purchase that exists nowhere in the electronic record, so the paper receipt has to come back to the office and get entered by hand with the date, gallons, vehicle number, and jurisdiction. Fleets with a well enforced fuel card programme keep cash purchases to a few per quarter at most, but even that small volume represents a gap the telematics integration cannot cover on its own.

Idle time fuel and PTO fuel. Fuel that gets burned by power take off equipment, refrigeration units on reefer trailers, hydraulic systems on service trucks, and mounted generators is generally eligible for a fuel tax refund because it was not consumed for on road propulsion, but only if it is tracked and reported separately. If nobody accounts for PTO fuel separately, those gallons end up in the general fuel total and pay jurisdictional road tax they do not actually owe.

A telematics platform that handles these three cases natively is doing the full IFTA job. One that handles only the on road fuel side leaves the refund money on the table or the bulk fuel out of the figures.

GPSWOX fleet management platforms include automated IFTA mileage reporting with state line detection and fuel card integration, and the quarterly summary outputs can be configured per fleet to match the base jurisdiction’s filing format.

5 telematics IFTA mistakes that produce audit findings

1. Trusting the platform’s mileage report without spot checking

State line crossings are accurate in most cases and occasionally wrong in tunnel networks, GPS multipath zones, and at state lines that follow rivers or curves the GPS data over corrects for. The quarterly review should include a spot check on a few crossings against the actual route taken.

2. Letting drivers correct mileage figures manually

What happens when a driver edits trip data to correct what they think the platform got wrong is that an auditable record has now been altered, and if the audit turns up the edit, the auditor treats it as a record integrity issue rather than a good faith correction. When a GPS error genuinely needs correction, the fix should go through a supervisor who documents what was changed and why, with the original record preserved in the system, because if the correction is ever reviewed during an audit, the auditor needs to see both versions.

3. Not capturing the unit number on every fuel transaction

Fleet fuel card providers generally allow the card to be configured so that the pump asks for the vehicle unit number before dispensing, and some providers make that prompt mandatory by default while others leave it off. When the prompt is not active, the transaction listing arrives without a vehicle identifier on some or all of the purchases, which pushes the matching work to the office, and the reality is that transactions without a unit number tend to sit unmatched because nobody has the time to look up which truck was at which station on which day.

4. Filing the return without reviewing the per jurisdiction MPG

Auditors almost always start by calculating the implied MPG for each jurisdiction on the return, and a jurisdiction where the number is noticeably off from the rest, say 9.2 MPG in Indiana when every other state is between 5.8 and 6.4, tells the auditor that either the mileage or the fuel data for that jurisdiction has a problem in it. Scanning the MPG figures across all jurisdictions before submitting, which takes about two minutes on most platforms, catches those outliers at a point where they can still be investigated and corrected without the carrier having to explain them in an audit response.

5. Deleting the underlying data at six months for privacy reasons

The four year IFTA retention obligation is specific and it overrides whatever shorter retention period the fleet might apply to GPS data for privacy or data minimization reasons, and the problem with setting the platform to auto delete trip data at six months is that the audit defence disappears three and a half years before the retention window actually closes, which means a fleet that gets audited in year three has no records to produce.

Frequently asked questions

Does telematics replace paper IFTA records entirely?

For the mileage side, in most fleets, yes. Paper trip logs are increasingly inadmissible at audit without corroborating GPS data, and a telematics based mileage record satisfies the audit standard on its own. [2] For the fuel side, paper receipts are still required for cash fuel purchases, and the bulk fuel logs still have to be maintained, but card based fuel purchases are covered by the integrated fuel card data.

How do I make sure the GPS mileage is audit defensible?

The platform’s mileage records should include the timestamp, the coordinates, and the odometer reading at each state line crossing. [1] All three together form the audit defence. A platform that stores only the jurisdiction level totals, the summary figures, without keeping the individual crossing records underneath them is weaker at audit because the auditor cannot verify how those totals were calculated, and if the auditor questions the mileage in a particular jurisdiction, there is no raw data to show.

What happens if the telematics device fails for part of a trip?

The buffered data uploads when the device recovers, filling in most outages. Outages that last longer, or cases where the device buffer was full and data was lost, require the fleet to fall back to odometer readings or paper records for the affected segment, and the gap should be documented at the time it is discovered, not reconstructed weeks later at filing time when nobody remembers the details.

Do I still need fuel receipts if I have fuel card data?

For card transactions, the transaction listing is the primary record and the paper receipt is backup. [4] For cash transactions, the paper receipt is the only record and has to be retained. For bulk fuel, the delivery receipts and withdrawal logs are the records; the fuel card stream does not cover them.

Can a fleet do IFTA from telematics if it operates only in one state?

IFTA only applies to vehicles that cross jurisdictional lines, so a fleet that operates entirely within one state or one province does not file IFTA returns and does not need IFTA credentials. Telematics is still useful for that fleet’s internal fuel reporting, route analysis, and operational record keeping, but the quarterly IFTA filing obligation does not attach until the fleet puts a qualified motor vehicle across a state or provincial boundary.

The Bottom Line

IFTA has never really been a tax problem, the rate times miles math is simple once the numbers are right, and it has always been a data problem instead, because producing accurate mileage by jurisdiction and accurate fuel by jurisdiction in a format an auditor can verify is where the actual labour sits. Telematics takes the mileage data collection out of the driver’s hands entirely and automates the matching between mileage and fuel inside one platform, and that is the reason the quarterly process goes from a full day of assembling records to a short review session where the person filing is checking the numbers the platform already put together rather than building them from scratch.

The part that determines whether any of this actually works in practice is the configuration: the state line detection has to be turned on and validated, the fuel card integration has to be connected and importing the transaction listing on the provider’s schedule, the unit number prompt at the pump has to be active so the fuel data arrives with vehicle identifiers attached, the retention settings have to cover the full four year IFTA window, and someone in the office has to actually look at the pre submission report each quarter instead of filing the platform’s output without review. A fleet that runs that setup files clean returns the audit cannot disturb. A fleet that uses telematics for the map but does IFTA on paper alongside it is paying for the platform twice and getting half the value.

Article Sources

1. Iowa Department of Transportation. “IFTA Record Keeping Requirements.” https://iowadot.gov/motor-carriers/ifta-international-fuel-tax-agreement/ifta-record-keeping-requirements
2. Indiana Department of Revenue. “Motor Carrier IFTA and IRP Audit Tips.” https://www.in.gov/dor/motor-carrier-services/files/audit-tips.pdf
3. Minnesota Department of Public Safety. “IRP and IFTA Audit Record Keeping Requirements.” https://dps.mn.gov/divisions/dvs/business/irp-and-ifta/irp-and-ifta-audit/irp-and-ifta-audit-record-keeping-requirements
4. Virginia Department of Motor Vehicles. “International Fuel Tax Agreement (IFTA) Frequently Asked Questions.” https://www.dmv.virginia.gov/businesses/motor-carriers/ifta/ifta
5. Illinois Department of Revenue. “Motor Fuel Tax (IFTA) Filing & Payment Requirements.” https://tax.illinois.gov/research/taxinformation/motorfuel/mfut/filepay.html