Every quarter, the same scramble hits independent carriers and small fleets: dig out fuel receipts, figure out which miles ran through which states, do the math on tax owed per jurisdiction, and get the filing in before the deadline. Plenty of carriers search for an "IFTA calculator" hoping something will just handle all of that. The reality is a little more specific, and understanding the distinction saves you from a bad filing and a potential audit headache.
This article breaks down what an IFTA calculator actually does, what it cannot do for you, and how HaulerPro handles the mileage side of the equation automatically. For a broader look at how a TMS fits into your compliance workflow, see the full guides index.
What the IFTA Formula Actually Is
IFTA tax is not simply gallons purchased multiplied by a rate. The formula works like this: for each member jurisdiction, you take the miles you ran there, divide by your fleet's average MPG to get the gallons "consumed" in that state, then multiply by that state's tax rate. You then subtract any tax you already paid at the pump in that jurisdiction. The result is either a net tax owed or a net credit. Credits from low-rate states can offset what you owe to high-rate states.
That means an IFTA calculation has two distinct inputs that are equally important: miles per jurisdiction and fuel purchased per jurisdiction. A calculator can crunch the numbers once you have both, but getting both inputs accurate is the real work.
Where Most Carriers Run Into Trouble
Many carriers find that miles-per-jurisdiction is the harder input to produce cleanly. Fuel receipts are physical documents you have in hand. But reconstructing which portion of a multi-state run went through Oklahoma versus Kansas versus Missouri requires either a mileage log tied to your routes or a system that tracks it for you.
Common gaps that auditors may examine include:
- Total miles on the vehicle not matching the sum of jurisdiction miles across all quarters
- Fuel purchase records that don't align with the states a truck was actually operating in
- Missing receipts for cash fuel purchases
- Mileage figures reconstructed from memory or estimated rather than logged per trip
Auditors typically work from source documents, meaning the odometer readings, route records, and fuel receipts that support the numbers on your return. If your quarterly filing rests on a spreadsheet with manually typed state-by-state mile estimates, that is the first thing a thorough audit will probe.
What HaulerPro Does on the Miles Side
When you dispatch a load in HaulerPro, the system routes the trip through OSRM and intersects that route with jurisdiction polygons covering the 48 contiguous states and DC. The miles for each state the route passes through are captured automatically against that load. At the end of the quarter, you open the IFTA panel, which aggregates all of those per-jurisdiction miles across your fleet, and you export an ifta_miles.csv file.
That CSV is your mileage input for your quarterly filing. It is organized by jurisdiction so you can match it against your fuel receipts and run the calculation, or hand it to your accountant or a dedicated tax tool to finish the job. Because the miles come from the actual dispatched routes rather than after-the-fact reconstruction, the data quality is meaningfully stronger than a manual log.
A few things to understand about the scope: mileage capture covers the 48 contiguous states, so the data going into your IFTA filing is already scoped to U.S. jurisdictions. Alaska, Hawaii, Mexican routes, and Canadian provinces are not covered by the polygon system.
What HaulerPro Does Not Do
Be clear-eyed about this before you build your workflow around it:
- Fuel is not auto-attributed to jurisdiction. Drivers scan fuel receipts and they are stored on the load and expense record. HaulerPro does not automatically allocate gallons to the state where fuel was purchased. You reconcile fuel against the miles export at filing time.
- The CSV is not a filing-ready return. HaulerPro exports per-jurisdiction mileage data you use as input to your quarterly IFTA filing. It does not produce a formatted return or submit anything to a state agency.
- There is no calculation engine inside HaulerPro. Tax rates, net tax owed per jurisdiction, and credit calculations happen in your state's filing system or whatever tool you use to complete the return.
This is an honest split: HaulerPro handles the hardest part of the data-collection problem, the per-jurisdiction miles, and leaves the tax computation to the appropriate filing tool or professional.
How to Use the Export in Your Quarterly Workflow
A practical quarterly rhythm looks like this:
- Dispatch all loads through HaulerPro so every route is captured in the system.
- Have drivers scan fuel receipts on each load so receipts are attached to the right load record and stored as expenses.
- At quarter end, open the IFTA panel and export the ifta_miles.csv.
- Pull your fuel receipt totals by state from your expense records.
- Take the miles file and your fuel data into your state's IFTA filing system, or give both to your accountant.
The miles are already broken out by jurisdiction. You are not starting from scratch or reconstructing routes from memory. That is the time-saving part.
Start Your Trial
HaulerPro's IFTA mileage capture is included on every plan, and your first load can be live in under 10 minutes from signup. No credit card required during the trial. Start your 14-day free trial and see what your quarterly jurisdiction miles look like when the data is already waiting for you.