IFTA Quarterly Filing Readiness: A Jurisdiction-Data Control Study

Published: September 18, 2026.

Quarterly fuel tax reporting under the International Fuel Tax Agreement asks a carrier a simple question with an uncomfortable amount of detail behind it: how many miles did each qualified motor vehicle travel in each jurisdiction, and how many taxable gallons were purchased there? The arithmetic is straightforward. The records usually are not.

Research question and scope

This study asks how a carrier can determine whether it is ready to file an IFTA quarterly return before the due date arrives. It treats readiness as a record-completeness and reconciliation question. It does not calculate a carrier's tax liability, interpret a jurisdiction's law, or offer tax advice. Filing mechanics and rates belong to IFTA member jurisdictions and to qualified tax professionals.

The narrow claim tested here is whether a filing can be supported by distance and fuel records whose jurisdiction fields are complete, traceable to a source, and reconciled to an independently produced total.

What the agreement asks a carrier to report

Under the IFTA framework, a licensee reports total miles traveled in all member jurisdictions and total taxable gallons purchased in each. Each jurisdiction's tax rate is applied to the difference between fuel consumed in that jurisdiction and fuel purchased there, and the results are netted. A jurisdiction with more consumption than purchases produces tax due; the reverse can produce a credit, subject to the agreement's rules.

The IFTA Procedures Manual and the Tax Rate Matrix are published by IFTA, Inc., the organization that administers the agreement. Those documents define the structure of a return but not the condition of a carrier's data. A filing can be arithmetically correct and still rest on incomplete jurisdiction fields. The readiness question is therefore about the records, not the return form.

The two source record sets

IFTA readiness draws on two record families that are often maintained by different people.

Distance records show where a qualified vehicle traveled. Depending on the fleet, they may come from an electronic logging device, a telematics platform, a trip report, or a manual driver log. Each record needs a vehicle identifier, a date, a jurisdiction, and a distance. A distance record with a missing or ambiguous jurisdiction is not ready.

Fuel records show where fuel was purchased. They usually come from fuel cards, vendor invoices, or bulk fuel reports. Each record needs a purchase date, a jurisdiction, a quantity in gallons, and a vehicle identifier. A fuel transaction that is missing a jurisdiction or is assigned to a generic region is not ready.

Because these two families come from different systems, the reconciliation between them is where most readiness problems surface.

Jurisdiction assignment is the hard part

Assigning a jurisdiction is easy on an interstate corridor and hard everywhere else. A trip that crosses a state line mid-day, a fuel stop near a border, a yard move inside a terminal city, and a deadhead that returns across the same border all raise questions that a simple distance total will not answer.

Establish a written assignment rule before the quarter closes. The rule should state which system is authoritative for jurisdiction, how border crossings are treated, how unknown segments are flagged, and who resolves a conflict. Apply the rule consistently across the quarter. When a segment cannot be assigned, leave it in an exception list rather than distributing it across jurisdictions by assumption. An assumption that quietly moves miles between states is the kind of change that is difficult to reconstruct later.

Reconcile before filing, not after

Two reconciliations catch most readiness failures.

First, reconcile distance. Compare the sum of per-jurisdiction distance to the fleet's independently reported total miles for the quarter. A gap means either a missing trip, a duplicate trip, or a jurisdiction assignment that dropped a segment. Investigate the gap and document the explanation even when the total looks plausible.

Second, reconcile fuel. Compare the sum of jurisdictional gallons purchased to the fleet's total fuel purchases for the quarter from an independent source, such as the fuel card program's own summary. A gap points to a missing transaction, a transaction logged outside the quarter, or a bulk delivery that was recorded differently.

Do this before the filing is prepared. A reconciliation performed after submission cannot change what was filed, and it turns a routine control into a correction.

A readiness checklist and exception log

A filing is ready when each of the following can be answered from the record:

• Is the period defined and closed?
• Is the qualified vehicle population listed and matched to the distance source?
• Is every distance record assigned to a jurisdiction or flagged?
• Is every fuel transaction assigned to a jurisdiction or flagged?
• Do jurisdictional distance and fuel totals reconcile to independent totals?
• Are prior-quarter exceptions resolved or carried forward with a note?
• Are the source files and retrieval dates retained?

The exception log is the most useful artifact. It records each unresolved item, the reason it is unresolved, the owner, and the date. A short list of named exceptions is a stronger basis for a filing decision than a claim that the data is clean.

A boundary case

Imagine a fuel purchase recorded at a card reader near a state line, with the merchant address in one jurisdiction and the vehicle's next movement in another. One analyst assigns the purchase to the merchant address; another assigns it to the jurisdiction where the vehicle was operating. The two assignments shift taxable gallons between states.

Retain the merchant record and the vehicle position record, and apply the written rule rather than improvising per transaction. If the rule does not cover the case, add the case to the exception log and resolve it consistently for the quarter. Changing the rule mid-quarter makes the return internally inconsistent.

Reviewer agreement and reproducibility

Have a second person reproduce the jurisdiction totals from the source files without relying on the first person's spreadsheet. The reviewer should be able to recover the same per-jurisdiction distance, the same fuel purchases, and the same exception list. Ask the reviewer to specifically test border crossings, manual entries, and any transaction that changed jurisdiction between draft and final.

Record any correction as a dated version of the preparation file. When the preparation can be reproduced by a second reviewer, the filing has an audit trail independent of the preparer's memory.

Interpretation boundaries

A readiness review measures whether records support a filing. It does not determine the correct tax treatment, the correct rate, or the amount owed. A reconciliation gap is not evidence of underpayment or evasion, and a clean reconciliation does not certify compliance. Those determinations belong to the jurisdictions and to qualified professionals.

The output of this method is a documented state of readiness with named exceptions, which is a different and more limited claim than a tax opinion.

Limitations

Readiness methods inherit the limits of the source systems. Telematics gaps, clock drift, card data that lacks a clean jurisdiction, and manual adjustments all reduce confidence. A quarter that relies on manual reconstruction may reconcile on paper while remaining fragile. Records retained in different formats across a fleet increase the chance that a reviewer recovers a different total.

The findings apply to the named fleet, period, and record systems. They are not a benchmark for another carrier and should not be used to compare compliance among fleets.

Source treatment

IFTA, Inc. publishes the agreement's framework documents and the current tax rate matrix. The Code of Federal Regulations and the National Archives provide general expectations for record preservation. Those sources frame what a defensible record looks like. They do not validate any individual carrier's jurisdiction fields or filing position, and nothing in this brief is tax advice.

Evidence-led conclusion

An IFTA quarterly filing is ready when the distance and fuel records behind it are jurisdiction-complete, reconciled to independent totals, and accompanied by a named exception list. The filing software is the least important input. The controls that matter are the assignment rule, the reconciliation, and the reviewer who can reproduce both.

References

1. IFTA, Inc. International Fuel Tax Agreement. https://www.iftach.org/. Retrieved 2026-09-18.
2. IFTA, Inc. IFTA Procedures Manual. https://www.iftach.org/manual2020.php. Retrieved 2026-09-18.
3. IFTA, Inc. Tax Rate Matrix Download. https://www.iftach.org/taxmatrix4/TaxDownload.php. Retrieved 2026-09-18.
4. IFTA, Inc. Important Notices. https://www.iftach.org/important-notices.php. Retrieved 2026-09-18.
5. Electronic Code of Federal Regulations. 49 CFR Part 379, Preservation of Records. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-A/part-379. Retrieved 2026-09-18.
6. Electronic Code of Federal Regulations. 49 CFR Part 390, FMCSA General Rules. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-390. Retrieved 2026-09-18.
7. National Archives and Records Administration. Records Management Policy. https://www.archives.gov/records-mgmt/policy. Retrieved 2026-09-18.