ELD and IFTA: How Fuel Tax Reporting Works
For trucking companies operating across multiple states or Canadian provinces, keeping track of mileage and fuel purchases is an important part of IFTA reporting.
An Electronic Logging Device (ELD) can make this process easier by providing detailed vehicle and location data. However, an ELD does not automatically replace the records required for IFTA, and mileage tracking for tax reporting is not part of the federally required ELD data under 49 CFR Part 395. FMCSA specifically notes that manufacturers may offer mileage tracking for tax reporting as part of a fleet management package.
Understanding how ELD data fits into the IFTA process can help carriers keep better records and reduce manual work.
What is IFTA?
IFTA stands for the International Fuel Tax Agreement.
It is an agreement among the 48 contiguous U.S. states and 10 Canadian provinces that simplifies fuel tax reporting for qualified interstate motor carriers.
Instead of filing separate fuel tax reports with every jurisdiction where a truck operates, an IFTA licensee generally files a consolidated return with its base jurisdiction. The base jurisdiction processes the return and distributes the applicable taxes to the member jurisdictions.
IFTA reporting is generally done quarterly. The IFTA Articles of Agreement state that the tax return covers the previous calendar quarter, although certain jurisdictions may have specific provisions or exceptions.
How does ELD data fit into IFTA reporting?
An ELD primarily exists to record a driver's duty status and support compliance with federal Hours of Service requirements.
However, modern ELD systems may also collect vehicle location and mileage information.
That additional information can be useful when preparing IFTA records.
A simplified workflow looks like this:
ELD and vehicle data → Mileage by jurisdiction → Fuel records → IFTA calculations → Quarterly return
The important point is that the ELD is a data source, not the entire IFTA reporting system.
FMCSA makes this distinction clear: mileage tracking for tax reporting is not part of the ELD data required by 49 CFR Part 395, although an ELD manufacturer may provide it as an additional fleet-management feature.
What information is needed for IFTA?
IFTA reporting involves more than simply knowing how many miles a truck traveled.
Carriers generally need records that allow them to determine:
- Total distance traveled
- Distance traveled in each jurisdiction
- Fuel purchased
- Fuel consumed
- Fuel type
- Vehicle information
- Supporting fuel purchase documentation
IFTA guidance on electronic distance records includes information such as GPS or location data, date and time, vehicle location, beginning and ending readings, calculated distance, route of travel, total distance, distance by jurisdiction, and vehicle identification.
Fuel records are also important. IFTA recordkeeping guidance includes information such as the purchase date, vendor, quantity, fuel type, price or total purchase amount, vehicle, and purchaser.
This is why an ELD alone should not be treated as a complete IFTA recordkeeping solution.
ELD mileage vs. IFTA mileage
One common mistake is assuming that the mileage displayed by an ELD is automatically the exact mileage that should be entered on an IFTA return.
It may not be.
An ELD can provide useful mileage and location information, but carriers still need to apply the appropriate IFTA rules to their records.
For example, a carrier may need to distinguish between:
- Miles traveled in different jurisdictions
- IFTA and non-IFTA miles
- Taxable and non-taxable miles where applicable
- Different vehicle operations
- Miles supported by other records
IFTA rules can also vary by jurisdiction. The IFTA organization publishes jurisdiction-specific information, including exemptions and fuel tax rates.
Therefore, ELD mileage should be treated as part of the overall reporting process rather than as an automatic final IFTA number.
How carriers can use ELD data for IFTA
A practical process can look like this.
1. Collect vehicle mileage data
The first step is to gather mileage and location information from the vehicle or fleet-management system.
Depending on the ELD platform, this may include trip history, vehicle locations, and mileage information.
2. Organize mileage by jurisdiction
The next step is determining where the vehicle traveled during the reporting period.
For interstate carriers, this can be one of the most time-consuming parts of the process when records are maintained manually.
Location data can help organize trips and identify the jurisdictions where mileage was accumulated.
3. Collect fuel purchase records
Mileage is only one part of IFTA reporting.
Carriers also need accurate fuel purchase records. Fuel receipts and other supporting documentation should be maintained according to the applicable IFTA requirements.
4. Compare mileage and fuel data
Reviewing mileage alongside fuel purchases can help identify unusual numbers before the quarterly return is prepared.
For example, a fleet manager may discover:
- Missing fuel receipts
- Unexpected mileage
- Incorrect vehicle assignments
- Trips that appear incomplete
- Data gaps
- Differences between fuel and mileage records
5. Prepare the quarterly IFTA return
After the mileage and fuel information has been reviewed, the carrier can use the applicable jurisdictional information to prepare its IFTA return.
The base jurisdiction handles the filing and tax processing for the member jurisdictions under the IFTA system.
Why accurate mileage matters
Mileage is one of the fundamental inputs used in IFTA calculations.
If jurisdictional mileage is incomplete or inaccurate, the final tax calculation can also be affected.
For fleets that operate across many states, manually reconstructing every trip can become difficult, particularly when vehicles travel continuously throughout the quarter.
This is where digital vehicle data can provide practical value.
Instead of relying entirely on handwritten notes or manually reconstructed routes, fleet managers can use available electronic data to organize vehicle activity and review mileage information.
Common ELD and IFTA mistakes
Using an ELD does not automatically eliminate IFTA reporting problems.
Some common mistakes include:
Treating ELD data as the entire IFTA record
An ELD can provide valuable mileage and location information, but fuel records and other required documentation still matter.
Failing to review jurisdiction mileage
Simply recording total vehicle mileage is not enough for a carrier that needs to report mileage by jurisdiction.
Missing fuel receipts
Mileage data cannot replace the need for proper fuel purchase records.
Assuming every ELD calculates IFTA automatically
Not every ELD provides the same tax-reporting functionality.
FMCSA states that mileage tracking for tax reporting may be offered as an additional fleet-management service, rather than being part of the federally required ELD data.
Waiting until the end of the quarter
Trying to reconstruct three months of vehicle activity at once can make it harder to identify missing or inconsistent records.
Regularly reviewing fleet data can make quarterly reporting more manageable.
How fleet managers can prepare for IFTA reporting
A consistent process can make quarterly reporting easier.
Fleet managers can:
- Review vehicle mileage regularly.
- Monitor jurisdictional travel.
- Keep fuel receipts organized.
- Check for missing or unusual trip data.
- Compare mileage with fuel purchases.
- Maintain supporting documentation.
- Review records before submitting the quarterly return.
The goal is not simply to collect more data. It is to keep the data organized enough that it can be reviewed when the reporting period ends.
Can an ELD replace IFTA software?
Not necessarily.
An ELD and an IFTA reporting system can serve different purposes.
The ELD is primarily designed around Hours of Service and electronic records of duty status. An IFTA solution, meanwhile, focuses on organizing mileage, fuel information, jurisdictional calculations, and tax reporting.
Some fleet-management platforms combine these functions, while others require separate systems.
Before relying on an ELD for IFTA reporting, carriers should check exactly what mileage, jurisdiction, fuel, and reporting features the platform provides.
How Unity ELD can support fleet data management
Unity ELD can help carriers centralize electronic vehicle information and make fleet activity easier to review.
Depending on the platform's available features, fleet managers can use vehicle and location data as part of their broader recordkeeping workflow.
For IFTA reporting, the important consideration is how the available mileage and location data can be combined with fuel records and the carrier's reporting process.
An ELD should be viewed as one part of the workflow rather than a replacement for the carrier's IFTA obligations.
FAQ
Does an ELD automatically calculate IFTA taxes?
No. An ELD does not automatically become an IFTA tax reporting system simply because it records vehicle information.
Some ELD and fleet-management platforms may offer IFTA-related functionality, but carriers should verify the specific features of their system.
Does FMCSA require ELDs to track IFTA mileage?
No. FMCSA states that mileage tracking for tax reporting purposes is not part of the ELD data established in 49 CFR Part 395. Manufacturers may offer it as an additional fleet-management service.
What records are important for IFTA?
Carriers generally need accurate mileage information by jurisdiction along with fuel purchase records and other supporting documentation required by their base jurisdiction.
How often is an IFTA return filed?
IFTA returns are generally filed quarterly for the previous calendar quarter. The carrier files through its base jurisdiction.
Can GPS data be used for IFTA records?
Electronic distance records can include GPS or other location data, along with information such as date, time, location, route, total distance, jurisdictional distance, and vehicle identification.
Is ELD mileage always the same as IFTA mileage?
Not necessarily. ELD mileage can be an important source of information, but carriers must apply the applicable IFTA requirements and account for the appropriate mileage categories and fuel records.
Final thoughts
ELD technology can make it easier for trucking companies to collect and organize vehicle mileage and location information. That data can be useful when preparing IFTA records, especially for fleets operating across multiple jurisdictions.
However, ELD compliance and IFTA compliance are not the same thing.
The most reliable approach is to use ELD data alongside accurate fuel records, jurisdictional mileage information, and the reporting requirements provided by the carrier's base jurisdiction.
That gives fleet managers clearer picture of vehicle activity throughout the quarter and makes the final IFTA reporting process easier to review.