IFTA Software: What a Fleet Owner Should Check Before Trusting the Return

IFTA software collects a fleet's miles by jurisdiction and its fuel purchases, then builds the quarterly International Fuel Tax Agreement return. The good ones also keep the supporting records an auditor will ask for. The software does not change who is responsible: IFTA says that using a product does not replace your recordkeeping or filing obligations.

This guide is for fleet owners and back-office staff choosing or checking their software, and it draws on the IFTA carrier page and the current manuals. It covers what the return needs, what the records must contain, how the arithmetic works with a worked example, and the places software quietly goes wrong. Hemut Command is a TMS built for asset-based trucking carriers, and one section explains where it fits.

What does IFTA software actually do?

It does four jobs. It gets distance data from a telematics feed, a logging device export or trip sheets. It gets fuel data from fuel card files or receipts. It assigns both to a vehicle and a jurisdiction. Then it applies the current tax rate for each jurisdiction and produces the return and a report you can keep.

The return itself has a fixed shape. The IFTA Procedures Manual lists the required items: total distance, total fuel, the average fuel consumption factor to two decimal places, and for each jurisdiction the tax rate, total miles, taxable miles, taxable volume, tax paid volume and net taxable volume. Anything that cannot fill those columns from your records is a spreadsheet with a logo.

Most of the value is therefore upstream of the math. Subtracting gallons is easy. Knowing which truck bought which gallons, and which truck drove which miles in which state, is the hard part. The related guide on the IFTA calculator for owner operators walks through that record preparation by hand, and the manual's record rules explain why it matters.

Which trucks and which filings does IFTA software have to cover?

IFTA applies to a qualified motor vehicle. The IFTA carrier page defines it as one with two axles and a gross or registered gross weight above 26,000 pounds, three or more axles regardless of weight, or one used in a combination above 26,000 pounds. A carrier based in a member jurisdiction that runs such a vehicle in two or more member jurisdictions should hold an IFTA license from its base jurisdiction.

Filing is quarterly. The same page lists the due dates: April 30 for January to March, July 31 for April to June, October 31 for July to September, and January 31 for October to December. When a date lands on a weekend or holiday, the next business day applies. The Articles of Agreement add that a return is required even if no operations were conducted, with an annual option only for licensees under 5,000 miles outside the base jurisdiction who get approval.

Your software should therefore handle a license with several trucks, a quarter where one truck sat idle, and a zero-activity return. Ask the vendor to show each case. Also confirm how it treats a truck that changed fuel type or left the fleet mid-quarter, because the return is built per fuel type.

What records does IFTA software need to keep?

Records are where audits are won or lost. The Procedures Manual says a licensee must retain records for four years after the return was due or filed, whichever is later, plus any period covered by waivers or jeopardy assessments. Software that stores only the finished return, and lets the underlying data age out, fails that test.

Distance records have specific content rules. A trip record needs start and end dates, origin and destination, route, odometer or ECM readings, total distance, distance in each jurisdiction and the vehicle identifier. For a tracking system, the manual says a reading must be created at least every 10 minutes while the engine is on, with latitude and longitude to four decimal places and an ECM odometer reading. The data must be available as XLS, XLSX, CSV or delimited text, and a PDF, JPEG, PNG or Word export is not acceptable.

Fuel records are just as specific. A retail receipt or transaction listing needs the purchase date, seller name and address, quantity, fuel type, price or total, the vehicle that was fueled and the purchaser. The base jurisdiction will not allow credit for fuel placed into a vehicle that is not a qualified motor vehicle, and it can refuse altered or illegible records. Bulk tank fuel has its own receipt, inventory and withdrawal requirements.

How does IFTA software calculate the fuel tax return?

The method is a fleet-wide average applied jurisdiction by jurisdiction. Divide total miles by total gallons to get the fleet's miles per gallon. Divide each jurisdiction's taxable miles by that figure to get the gallons you burned there. Subtract the gallons you bought there with tax paid. Multiply the result by the jurisdiction's rate. A negative result is a credit, and the return sums all jurisdictions.

Here is an example with invented inputs. Say a small fleet drove 120,000 miles in the quarter and bought 20,000 gallons, so fleet MPG is 6.00. The rates below are the diesel rates per gallon shown on the IFTA tax matrix for the fourth quarter of 2026, which the matrix says is not final until December 4, 2026. Volumes are rounded to whole gallons, as the return columns are.

Check the arithmetic: 2,223.00 minus 466.60 minus 492.25 is $1,264.15 due. Total gallons balance, so net taxable gallons sum to zero, yet the return is positive. The fleet bought 14,000 gallons in Texas, the lowest rate of the three, but burned only 11,667 there, while Pennsylvania used 5,000 gallons and only 2,000 were bought. Tax follows where the fuel was burned, not where it was bought. Rates change each quarter on the matrix, so a tool that carries last quarter's table will misstate the return.

Where does IFTA software go wrong?

The first failure is matching. In carrier data we have looked at, one quarter of fuel card transactions for a California-based carrier matched a specific truck 90.4% of the time. The unmatched tenth is where mileage tax and cost per truck reports quietly go wrong, because gallons with no truck fail the vehicle identification requirement for tax-paid credit. Ask any vendor for the match rate on your own card file, and see who resolves the leftovers.

The second failure is weak distance data. The Procedures Manual lets a base jurisdiction add an assessment when records are inadequate: it can reduce the reported fleet MPG to 4.00, or reduce the reported consumption factor by 20%. Using the example above with MPG forced to 4.00, Texas becomes 17,500 taxable gallons less 14,000 bought, or 3,500 net, which is $700.00. Pennsylvania becomes 7,500 less 2,000, or 5,500 net, which is $4,075.50. Illinois becomes 5,000 less 4,000, or 1,000 net, which is $738.00. The total is $5,513.50 against $1,264.15 with sound records, a gap of $4,249.35.

The third failure is lateness. The Articles of Agreement let a base jurisdiction assess a penalty of $50 or 10 percent of delinquent taxes, whichever is greater, for failing to file, filing late or underpaying, plus interest. On the $1,264.15 example, 10 percent is $126.42, which is greater than $50. Interest is separate and, for a U.S.-based fleet, set at two percentage points above the IRS underpayment rate. The penalty is something a jurisdiction may assess, not a fixed bill, so confirm treatment with your base jurisdiction.

How do you evaluate IFTA software before you buy?

Run one finished quarter through it and compare to what you filed. Differences are the lesson. A vendor demo with clean sample data proves nothing about your fuel card file or your logging export. Use these tests, each tied to a requirement above.

• Rate table: does it show which quarter's rates it used, and can you compare them to the published matrix?
• Distance source: can it ingest the 10-minute tracking data and export it as CSV or a spreadsheet, as the Procedures Manual requires?
• Fuel matching: what share of your transactions match a truck, and where do the others go?
• Retention: will the raw data stay available for four years after the due date?
• Filing: does it file for you, or produce a return you submit through your base jurisdiction? Electronic returns depend on what the base jurisdiction authorizes.

Also ask who answers for an error. The IFTA organization states that a subscriber does not provide IFTA credentials, decals, licenses or tax return support. Your base jurisdiction does. A free spreadsheet and a paid platform sit under the same obligation. If you only need to sanity check arithmetic, the free IFTA calculator on this site is enough, and the IFTA fuel tax reporting guide covers the filing steps.

Where does Hemut Command fit for IFTA reporting?

If your mileage and fuel data already live in your TMS, you avoid the largest source of errors, which is copying mileage and fuel between systems. Hemut Command imports EFS fuel card transactions and builds IFTA reports from the fleet's own miles and fuel. Fuel lines come in on the same system that holds your loads and your trucks, so the match problem is visible in one place rather than discovered at filing time.

Hemut also includes playbooks such as "Quarterly IFTA and IRP filing review", which prompts a review before the deadline. It is a prompt to check the work, not a replacement for it. Run your own quarter through it as described above. See the TMS overview for trucking carriers for what else sits in the same system.

IFTA software checklist for this quarter

1. Write down your license number, base jurisdiction and the next due date from the quarterly table.
2. List every qualified motor vehicle, with fuel type, for the quarter.
3. Export distance data as a spreadsheet and check it has a reading at least every 10 minutes while the engine runs.
4. Count fuel card transactions and the share matched to a truck, then fix the rest.
5. Confirm the rate table matches the current matrix for the quarter.
6. Recompute fleet MPG yourself: total miles divided by total gallons.
7. Save the raw data and the return together, and set a four-year retention date.