IFTA makes fuel tax reporting easier for carriers operating across multiple states or provinces, but it still comes with specific reporting and recordkeeping responsibilities. Fleets need accurate mileage, complete fuel records, current credentials, and supporting documentation for every quarterly return.
For fleet managers and back-office teams, the difficult part is often knowing exactly what needs to be tracked throughout the quarter. These answers cover the key IFTA reporting requirements and the records that should be ready before filing time arrives.
IFTA reporting is built around two main pieces of information: where qualified vehicles traveled and where fuel was purchased. Those records are reported through the carrier's base jurisdiction each quarter.
|
Requirement |
What Fleets Need To Know |
|
Filing Frequency |
Quarterly |
|
Mileage |
Track total distance and distance by jurisdiction |
|
Fuel |
Record fuel purchases and tax-paid fuel |
|
Records |
Keep supporting mileage and fuel records |
|
Credentials |
Maintain a current IFTA license and decals |
|
Filing Location |
File with the base jurisdiction |
|
No Activity |
A return may still be required |
|
Electronic Tracking |
ELD and GPS records must meet recordkeeping requirements |
IFTA generally applies when a qualified motor vehicle operates in two or more IFTA member jurisdictions. Interstate operation alone does not automatically mean every commercial vehicle falls under IFTA.
A qualified motor vehicle is used to transport people or property and generally meets at least one of these conditions:
Carriers that normally operate within one jurisdiction but occasionally travel elsewhere may have other options, such as trip permits. The correct choice depends on the carrier's operation and jurisdiction requirements.
Some hotshot operations fall under IFTA and others do not. The answer depends on vehicle or combination weight, axle configuration, and whether the vehicle operates in multiple IFTA jurisdictions.
Hotshot operators should look at their actual setup rather than assuming a pickup truck is automatically exempt. Weight thresholds can be reached quickly when a truck and trailer are considered as a combination.
The quarterly return uses fleet distance and fuel information to determine fuel tax obligations across the jurisdictions where qualified vehicles operated.
Accurate records should be collected throughout the quarter instead of reconstructed when the filing deadline approaches.
Fleets need total distance as well as distance traveled in each jurisdiction. Records should make it possible to determine where a qualified vehicle traveled during the reporting period.
Trip dates, routes, odometer or ECM readings, vehicle identification, and jurisdiction mileage can all support that record.
The distinction between total mileage and jurisdiction mileage matters when working through IFTA tax calculations, since fuel use must ultimately be allocated across the jurisdictions where the fleet operated.
Fleets need records of fuel purchased, received, and used in their operations. Separate totals should also be maintained for different fuel types.
A fuel receipt or transaction record should contain enough information to identify the purchase. Important details include the date, seller, gallons or liters, fuel type, purchase amount, and the vehicle or unit receiving the fuel.
Keeping receipts organized during the quarter can prevent the office from chasing drivers for missing paperwork weeks or months later.
Fleet fuel economy helps determine how much fuel was consumed across the jurisdictions traveled. This is why mileage and fuel records need to reconcile.
An unusually high or low MPG number does not always mean something is wrong, but it should prompt a review before the return is submitted.
IFTA returns are filed four times each year. The standard deadline is the last day of the month following the end of each reporting quarter.
The standard schedule is:
|
Reporting Period |
Standard Deadline |
|
January Through March |
April 30 |
|
April Through June |
July 31 |
|
July Through September |
October 31 |
|
October Through December |
January 31 |
If a deadline falls on a weekend or recognized holiday, the filing date can move to the next business day. Carriers should confirm the final deadline through their base jurisdiction.
An active IFTA account may still require a quarterly return even when qualified vehicles had no IFTA operations during the period.
Do not assume that zero miles means there is nothing to file. Check the instructions from your base jurisdiction and complete any required zero or no-operation return.
The figures on an IFTA return need supporting records. Those records should allow the base jurisdiction to validate the total distance and fuel reported for each jurisdiction.
A good recordkeeping process also makes quarterly reconciliation much easier for the fleet.
For trip records that are not generated by a vehicle tracking system, useful information includes trip dates, origin and destination, route traveled, beginning and ending odometer or ECM readings, total trip distance, distance by jurisdiction, and the vehicle identification or unit number.
When electronic tracking is used, fleets also need to retain the underlying location and vehicle data required under IFTA rules.
Yes. ELD and GPS data can reduce manual mileage tracking and give the office a clearer record of where trucks traveled.
Current IFTA procedures require qualifying vehicle tracking records based on latitude and longitude to create and maintain a location record at least every 10 minutes while the engine is on. The required electronic data must also be accessible in a spreadsheet compatible format such as CSV, XLS, XLSX, or delimited text.
That is an important distinction. A static screenshot or PDF alone may not provide the electronic data required for this type of recordkeeping.
Using BIT ELD can help fleets capture location and odometer information that supports state-by-state mileage tracking while also keeping daily driver workflows on the same platform.
IFTA supporting records generally need to be retained for four years. Records connected to an audit or unresolved dispute may need to be kept longer.
This includes fuel records, mileage information, electronic tracking data, trip details, and other documentation used to support quarterly returns.
Fleets should capture the complete movement of qualified vehicles instead of recording only loaded revenue miles. Leaving movements out can create mileage gaps between odometers, GPS data, dispatch records, and quarterly totals.
Deadhead and bobtail miles still represent vehicle movement and should not simply disappear from the fleet's distance records.
The same principle applies to HOS statuses. A driver using personal conveyance is dealing with an hours-of-service classification, but the vehicle is still moving. Fleets need to handle that distance according to applicable IFTA reporting rules rather than assuming an HOS status removes it automatically.
Tax-exempt mileage can also vary by jurisdiction. Document the mileage and apply the appropriate jurisdiction rules instead of excluding it without supporting records.
IFTA credentials are issued through the carrier's base jurisdiction. An IFTA licensee receives a license and two decals for each qualified motor vehicle.
A copy of the license should be kept in each qualified vehicle, along with the required current decals. Credentials are renewed as required through the base jurisdiction.
The base jurisdiction is also the main point of contact for quarterly returns, current tax rates, licensing questions, additional credentials, and audits.
Keeping IFTA credentials current should be part of a broader fleet compliance checklist, rather than something the office checks only when a renewal notice arrives.
IFTA reporting gets harder when mileage, fuel receipts, and route information are spread across different systems. BIT IFTA helps bring the data needed for quarterly reporting into a more manageable workflow.
With BIT ELD and the Blue Ink Tech App, fleets can track in-state mileage, capture odometer readings at state line crossings, and maintain detailed vehicle routes. Drivers can also enter and upload fuel receipts so the office has access to fuel purchase information without waiting for paper receipts to return with the truck.
The BIT portal lets fleet teams review overall miles by state, daily state-by-state vehicle mileage, fuel purchases, estimated MPG, and detailed routes. Data can be filtered by vehicle or state, with CSV and PDF export options available for reporting.
These IFTA reporting tools are designed to reduce manual tracking and give the back office better information when quarterly returns are prepared.
BIT IFTA does not calculate state tax rates. Fleets still need to use the correct rates and complete the final return according to the requirements of their base jurisdiction.
Before filing a quarterly return, make sure the underlying records tell the same story.
A few checks throughout the quarter are much easier than rebuilding three months of records before a filing deadline.
Qualified carriers generally need to file quarterly returns showing total distance, jurisdiction distance, fuel purchases, and tax-paid fuel. They also need supporting mileage and fuel records and current IFTA credentials.
IFTA reports are filed quarterly. Standard deadlines are April 30, July 31, October 31, and January 31, subject to weekend and holiday rules.
Yes. ELD and GPS data can support mileage reporting when the records meet applicable IFTA data collection, accessibility, and retention requirements.
Fuel records should identify details such as the purchase date, seller, fuel quantity, fuel type, purchase amount, and the vehicle or unit that received the fuel.
Supporting records generally need to be retained for four years. Records associated with an audit or unresolved matter may need to be retained longer.
BIT IFTA helps fleets organize state mileage, routes, fuel receipts, vehicle data, and reporting information. It does not calculate state tax rates or replace the fleet's responsibility to complete the final return with its base jurisdiction.