IFTA reporting is the quarterly fuel use tax return an interstate carrier files with a single base jurisdiction, covering total distance traveled and fuel purchased in every member state and province. The base jurisdiction then redistributes the tax to the jurisdictions where the fuel was actually burned. The agreement adds no new tax; it reallocates existing fuel tax based on use rather than point of purchase.
Quarter-end gets difficult for a specific reason. Vehicle-tracking mileage rarely matches odometer summaries exactly, fuel-card transactions arrive without unit numbers, and withdrawals from a project-site bulk tank mix highway-truck fuel with excavator and dozer fuel. Every jurisdiction total on the return has to trace back to the truck, trip, and fuel record that produced it, and an unresolved gap carried into a filing becomes something to explain during an audit instead.
The sections below cover which vehicles qualify, the filing deadlines and penalties, the records the agreement requires and in what format, how the return is calculated, and how document-processing workflows handle the reconciliation underneath it.
What IFTA Reporting Requires
The structure is one return to one base jurisdiction, four times a year. Everything else depends on which vehicles in the fleet fall within the agreement's scope.
Which Vehicles Qualify
Under the 2026 IFTA Articles of Agreement, a qualified motor vehicle is one used to transport people or property that has two axles and a gross or registered gross weight exceeding 26,000 pounds, has three or more axles regardless of weight, or is used in a combination exceeding 26,000 pounds. Recreational vehicles used exclusively for personal pleasure are excluded.
For a heavy fleet, that scope can pull in interstate dump and ready-mix trucks, lowboy equipment haulers, and qualifying service trucks that meet the weight or axle thresholds. Self-propelled excavators, bulldozers, and scrapers that never travel public highways under their own power are not qualified motor vehicles. Intrastate-only vehicles generally fall outside IFTA credential requirements, though the exemption is set jurisdiction by jurisdiction rather than nationally.
When Returns Are Due, and What Late Filing Costs
Standard deadlines are April 30, July 31, October 31, and January 31 for the quarters ending in March, June, September, and December, with the next business day as the due date if a deadline falls on a weekend or legal holiday. An active licensee must file every quarter, even with no activity to report, and a skipped no-operation return can put the license itself at risk.
Late filing carries a real cost. Texas, for example, assesses $50 or 10 percent of the delinquent tax, whichever is greater, and interest can accrue on tax owed to each jurisdiction separately. Penalties apply even to a zero-tax-due return, and repeated noncompliance can end in license suspension or revocation.
Which Records the Agreement Requires
The 2026 IFTA Procedures Manual sets out what has to exist before a return can be defended. Compliance staff needs total fleet distance, distance by jurisdiction, taxable distance, fuel purchases by jurisdiction and fuel type, and a vehicle identifier attached to every applicable record. Because the return is assembled per vehicle, a fleet whose records sit in per-system silos rebuilds the same unit history every quarter.
Manual trip records: Trip dates, origin and destination, route, beginning and ending odometer readings, total distance, jurisdiction distance, and a VIN or unit number.
Vehicle-tracking records: Timestamps, latitude and longitude, odometer data, and the VIN or unit number, with a reading created at least every 10 minutes while the engine is running.
Audit-ready export format: XLS, XLSX, CSV, or delimited text. Reject anything that arrives as a fixed rendering rather than readable data; manually name PDFs, JPEGs, PNGs, and Word documents specifically. Fleets that archive tracking reports as PDFs fail this without knowing it.
Retail fuel records: Purchase date, seller name and address, quantity, fuel type, unit price or total price, qualified-vehicle identification, and purchaser name.
Retention: Four years from the date the return was due or filed, whichever is later.
One terminology note worth carrying into a vendor conversation: the Procedures Manual writes its requirement around a vehicle tracking system using latitudes and longitudes, not around an electronic logging device (ELD). An ELD export may satisfy it, but the obligation is not defined by the ELD.
How a Return Is Calculated
Every jurisdiction's return follows the same five-step structure, set by the agreement rather than by any one state's form:
Total qualified-vehicle miles and all fuel placed into or consumed by those vehicles for each fuel type, excluding bulk fuel still sitting in storage.
Fleet average miles per gallon for each fuel type, dividing total qualified-vehicle miles by that fuel total.
Taxable gallons per jurisdiction, dividing taxable miles in that jurisdiction by fleet MPG.
Subtract tax-paid gallons purchased in that jurisdiction.
Multiply net taxable gallons by the applicable quarterly rate.
Rates change every quarter, so the calculation runs against IFTA, Inc.'s current tax rate matrix rather than a prior return or a saved spreadsheet. Confirm current rates, jurisdiction-specific exemptions, and tax-paid credits before submitting through the base jurisdiction's approved method.
Why Heavy-Civil and Construction Fleets Are a Distinct Case
Mixed-use fuel is what separates a heavy-civil fleet from a long-haul carrier on this return. A single project-site tank can fuel a qualified dump truck, a lowboy tractor, a service truck, an excavator, and a generator across one shift, and only some of that fuel belongs on the return.
Bulk-withdrawal records must identify the storage location, date, quantity, fuel type, and the vehicle or equipment receiving the fuel, and they must distinguish qualified highway vehicles from off-road equipment before claiming any tax-paid credit. Those logs usually live with the project records rather than in the fleet system.
Off-highway treatment then varies by jurisdiction, which defeats any single company-wide assumption. Washington's 2026 rules exempt certain diesel off-highway miles, while West Virginia's 2026 rules treat off-highway miles as taxable. Each jurisdiction's rules need to be validated against the projects actually operating there.
Where Quarter-End Preparation Time Goes
The 2026 IFTA Audit Manual identifies distance and fuel discrepancies, MPG variances, fuel without corresponding distance, and unsupported bulk withdrawals as the conditions that draw scrutiny. Those conditions cluster into three places where preparation time actually goes, and all of them are visible months ahead to anyone running continuous compliance monitoring rather than a quarter-end scramble. MPG variance is the exception that surfaces last, because it only appears once the quarter's totals exist.
Reconciling Mileage by Jurisdiction
Compare tracking and GPS records against odometer summaries, trip sheets, dispatch records, and unit rosters. Missing coordinates, stale unit assignments, and unexplained mileage gaps all distort total distance or jurisdiction allocation, and each one is cheaper to resolve now than to explain later.
Validating Retail and Bulk Fuel
Each fuel-card export needs the date, vendor, gallons, price, vehicle identifier, and purchaser name that a tax-paid credit depends on. When fields are missing, transactions match back to drivers, units, and routes without assigning a purchase to the wrong truck.
Project-site bulk records arrive as handwritten logs or spreadsheets with inconsistent equipment names. The one check that matters is whether every withdrawal maps to a qualified highway vehicle, to non-IFTA equipment, or to an unresolved exception somebody owns.
Assembling Audit Evidence
Filed jurisdiction totals have to reconcile to source records while preserving the detail an auditor will ask for. That means a traceable path from each total back to the trip, receipt, bulk withdrawal, rate, and adjustment behind it.
IFTA Reporting Software and Configured Workflows
Two distinct categories get shopped under the same search term. Dedicated IFTA filing software calculates the return and submits it to the base jurisdiction, usually pulling mileage from a telematics feed and fuel from a card provider. Its limit is that it trusts whatever those two feeds contain.
Fleet management platforms instead bundle IFTA as a module alongside maintenance and dispatch, which suits a fleet already standardized on one vendor and constrains which sources the module can read. Neither category addresses the reconciliation upstream of the calculation, where mileage, fuel, and equipment records disagree, and that is where most quarter-end hours go.
Datagrid's agents do not replace an IFTA filing system and cannot submit returns to a base jurisdiction. A configured workflow can connect approved sources and follow instructions defined by compliance staff, and every extracted field, cross-check, exception flag, and draft schedule stays subject to compliance review.
Reconcile Mileage and Fuel Evidence
Before calculating the return, source records need normalizing, and attribution gaps need identifying. Agents can connect approved mileage, fuel, equipment, finance, and project records, extract the required fields, compare records by unit and period, and produce an exception table. Compliance staff decide which source is correct, whether each mile or gallon qualifies, and how to document or exclude unresolved records.
Conflicting mileage totals: Where tracking exports and odometer summaries disagree, structured records in approved sources such as Excel, Google Sheets, SharePoint, or supported databases can be compared to produce an exception list by unit and period. That list identifies the variance and cannot say which source is right, so dispatch records, unit history, or field confirmation still resolve it. Datagrid's Fast Search Agent can search connected spreadsheets, project files, and databases during that reconciliation.
Fuel-efficiency variances: Where fleet MPG shifts sharply between quarters, trends can be compared and the underlying extracted fields checked for gaps. Cause stays open because idling, terrain, payload, and a recording error all look alike without field context.
Fuel against distance: A unit with fuel purchases and no corresponding miles, or miles and no fuel, can be surfaced with its dates, jurisdictions, and reconciliation difference attached.
Calculate and Review the Draft Return
Once mileage, fuel, and equipment-attribution exceptions are resolved or formally documented, configured formulas can assemble fleet MPG, taxable gallons, tax-paid gallons, and net taxable gallons by jurisdiction, then compare current inputs against approved rate tables and prior periods. Historical figures indicate what to question, not what the answer should be.
Compliance staff approves formulas, rates, exemptions, surcharges, rounding, exception treatment, and the final submission. Before each deadline, unresolved unit IDs, miles without fuel, fuel without miles, and unattributed withdrawals should sit in one reviewed queue, with a decision recorded against each.
Retain the Filing and Audit Package
After the return is approved, the source-to-filing trail has to survive four years. Datagrid's Audit Agent can assemble that package, validate it against defined requirements, and flag the gaps for compliance staff to close.
Measure the workflow by controls rather than by generic productivity claims. Count mileage records mapped to a jurisdiction, fuel purchases missing vehicle IDs, unmatched bulk-tank withdrawals, and open items still sitting there at the filing deadline. A quarter where those four fall is a quarter that went better, whatever the hours say.
Automate IFTA Evidence Assembly With Datagrid's Agentic AI
Datagrid's AI agents can handle the reconciliation and evidence work between compliance decisions, so quarter-end is spent on judgment calls rather than on finding records:
Mileage reconciliation: Compare vehicle-tracking exports against odometer summaries, trip sheets, and unit rosters, and produce an exception list by unit and reporting period.
Fuel-receipt field validation: Check retail records for every field a tax-paid credit requires, and flag gaps before claiming the credit rather than after an auditor finds them.
Bulk-withdrawal attribution: Cross-check project-site tank logs against an approved equipment roster and separate qualified highway vehicles from off-road equipment.
Filing-readiness queue: Gather every open exception into one reviewed list before the deadline, so nothing gets carried into a return by default.
Audit package assembly: Build the retained package so each filed jurisdiction total traces back to the trip, receipt, withdrawal, rate, and adjustment behind it.
Compliance staff still determine which source is authoritative, whether each mile or gallon qualifies, and what gets filed.
Get started with Datagrid and take last quarter's filed return apart against its source records. The exceptions it carried rather than resolved are the ones an auditor would find first.
Frequently Asked Questions About IFTA Reporting
What Is an IFTA Report?
It is the fuel use tax return filed once a quarter with a carrier's single base jurisdiction, showing distance and fuel for each member state or province. That jurisdiction then splits the tax among the places the fuel was actually burned.
What Vehicles Are Exempt From IFTA?
Recreational vehicles used exclusively for personal pleasure are excluded. Intrastate-only vehicles generally sit outside IFTA credential requirements, and self-propelled equipment that does not travel public highways under its own power is not a qualified motor vehicle.
Can GPS or Tracking Records Be Submitted as PDFs?
No, an auditor needs data they can sort and total, so a fixed rendering of a tracking report fails, no matter how complete it looks. Keep the underlying export in a spreadsheet or delimited-text format alongside whatever the telematics vendor generates for internal use.
How Should Bulk-Tank Withdrawals Be Recorded for IFTA?
Record each withdrawal against the specific vehicle or piece of equipment receiving the fuel, along with the storage location, date, quantity, and fuel type, then classify it as qualified highway use or off-road use before claiming any tax-paid credit.
