Table of Content
- “My dispatcher files my IFTA” is the wrong mental model
- The split most operators get wrong
- “We file IFTA for you” is where the trap lives
- ELD per-state miles aren’t IFTA-ready, and your dispatcher knows it
- Fuel receipts are not retroactive. That’s on you.
- Audits don’t start with bad intent. They start with bad data.
- A real dispatch-coordinated IFTA week, not the brochure version
- Red flags in any dispatcher-IFTA pitch
- The line you actually want from a dispatcher
Your dispatcher pulls the miles. You sign the return. That line matters more than most operators realize.
You’ve heard both versions. “Your dispatcher handles IFTA.” “IFTA is your responsibility.” Both are true. Neither is useful when you’re staring at a Q3 deadline and not sure who pulled the South Dakota miles.
The handoff line isn’t where most operators think it is. And when it breaks, the audit lands on you, not the dispatch service.
“My dispatcher files my IFTA” is the wrong mental model
IFTA is a tax. You filed for the license under your authority. You signed the base-jurisdiction agreement. The return goes out under your name and your signature.
A dispatcher cannot own that. What a dispatcher can own is the data feeding the return: trip records, per-state miles, fuel summaries, audit-ready backup. That’s the workflow. The legal liability stays with you.
Quarterly fuel tax filing covers the IFTA member jurisdictions you ran in. Miles per state, gallons per state, payment to your base state. Deadlines are April 30, July 31, October 31, January 31. The full membership map and forms live on the International Fuel Tax Association site. That’s the entire framework. Everything else is operational discipline.
The split most operators get wrong
Read the table once. Then check it against what your current dispatch service actually does, and what they only claim to do.
| Stays with the operator | Dispatcher coordinates |
|---|---|
| IFTA license and decals (renewed annually with base jurisdiction) | Trip-by-trip mile tracking input |
| Quarterly return filing (legal signature) | Per-jurisdiction mile and gallon summaries |
| Fuel receipt retention (4 years) | Pulling fuel data from card vendor when permitted |
| Tax payment to base jurisdiction | Filing-ready quarterly summary delivery |
| Audit defense (you’re audited, not the dispatch service) | Records pull on request during audit prep |
If your dispatcher’s IFTA promise doesn’t fit the right column, they’re either overselling or quietly setting you up for a bad quarter. A real dispatch workflow makes filing easy. It does not make the filing yours to skip.
This is also where scoped dispatch earns its rate. Clean per-state mile splits, quarterly summaries delivered before the deadline, fuel data reconciled against your card vendor. You still sign. You sign with confidence.
“We file IFTA for you” is where the trap lives
Some dispatchers say it. Few have the agency authority to back it. You sign a return you didn’t review. Two years later, the base jurisdiction opens an audit. The errors are yours. The dispatcher is gone, or “no longer offers that service.”
Ask one question: “Do I review and sign every return before it goes out?” If the answer is no, the workflow is broken. Sign nothing you haven’t checked.
ELD per-state miles aren’t IFTA-ready, and your dispatcher knows it
You’ve seen the export. Per-state miles down to the tenth. Looks clean. It isn’t filing-grade.
ELD mile splits use GPS pings on intervals. Border crossings get rounded. Off-highway miles get included. State lines on multi-lane highways get misattributed. None of this is wrong for hours-of-service. All of it is wrong for IFTA.
A dispatcher reconciling your IFTA data isn’t trusting the ELD export blindly. They’re cross-checking it against trip sheets, fuel-stop locations, and known route geometry. That’s the work. If your dispatcher just forwards the ELD CSV and calls it a summary, you’re filing on raw data the auditor will pick apart.
The reconciliation also catches the small stuff that ages badly. A 12-mile sliver in Indiana that should have been Ohio. A toll-road segment counted twice. Yard moves logged as on-highway miles. Each one is small. Stack four quarters of them and the auditor has a pattern.
Fuel receipts are not retroactive. That’s on you.
Lost the receipt for a $640 fill in Laramie? Your dispatcher cannot reconstruct it. Card statement entries help, but the base jurisdiction can disallow the credit. You pay the higher rate and eat the difference.
Keep four years of receipts. Photograph every one at the pump. Drop them in a folder by quarter. This is the cheapest discipline in the entire IFTA workflow, and the one most owner-operators still skip.
When IFTA week turns chaotic on clean receipts, the break is upstream of the filing. Pull last quarter’s fuel log and find where the state miles stop matching.
Audits don’t start with bad intent. They start with bad data.
Most operator IFTA audits are not flagged for evasion. They’re flagged for data quality. Your base jurisdiction looks for three things:
- Mileage-to-fuel ratios outside normal MPG ranges for your equipment class.
- Jurisdictional anomalies, miles claimed in a state with no fuel purchased, or fuel purchased with no miles run.
- Late or amended filings, especially repeated across quarters.
Hit any of those, and a desk audit opens. The dispatcher pulls records on request. You answer for them. That’s why the data work upstream matters.
An audit doesn’t have to be hostile to be expensive. You’re pulling weeks of trip records, matching them to fuel receipts, and explaining ratios. Time you’re not booking loads. Clean quarterly data shrinks that defense from days to hours.
A real dispatch-coordinated IFTA week, not the brochure version
Here’s what the workflow actually looks like when it’s running clean:
- Weekly: dispatcher reconciles trip miles by jurisdiction, flags border-crossing rounding errors, confirms fuel-card sync.
- Monthly: per-state mile and gallon roll-up reviewed by you. Discrepancies caught before they harden.
- Quarter-end (week before deadline): filing-ready summary delivered. You review, sign, file. Payment goes to base jurisdiction.
- Year-end: license renewal, decals ordered, receipt archive verified for four-year retention.
None of this is exotic. It’s the discipline that separates operators who file in 20 minutes from operators who lose a weekend every quarter. Service value comes down to whether your dispatcher actually runs this loop or just sends a spreadsheet at the deadline. The same logic applies to dispatch rate across booking, paperwork, and back-office work.
Red flags in any dispatcher-IFTA pitch
Three phrases should stop the conversation:
- “We handle everything.” No dispatcher legally handles your tax filing without explicit agency authority. Ask to see it.
- “Your IFTA is automated.” Software produces summaries. People reconcile data. Anyone selling pure automation is selling the ELD export problem.
- “No need to keep receipts, we have the card data.” Card data is not a receipt. The auditor wants the receipt.
Quick decision rule
- If the dispatcher delivers reviewed quarterly summaries a week before deadline, expect to file in under 30 minutes.
- If the dispatcher only forwards raw ELD exports, plan to reconcile yourself or change services.
- If the dispatcher signs anything with your name on it, end the relationship today.
- If you don’t have four years of fuel receipts archived, fix that before the next quarter, not after.
The line you actually want from a dispatcher
You want the data clean, the summary delivered early, the receipts pulled on request, and the signature staying yours. That’s the right split. Anything more is overreach. Anything less is you doing the dispatcher’s job at the end of every quarter.
If your current setup leaves you reconciling miles the night before the deadline, the workflow is broken, not the regulation. That’s the gap we built Logity around.
