Custom IFTA Fuel Tax and DOT Compliance Platform Development for US Motor Carriers: Building a Jurisdictional Mileage, Fuel Import and Driver File System

Introduction: One Mile, Three Reports, Several Clocks

IFTA and DOT compliance software development begins with a fact most software categories never face: every mile an interstate truck drives is reported more than once. It appears in the driver’s hours-of-service record, it is apportioned across jurisdictions on the quarterly IFTA fuel tax return, and it shapes the carrier’s IRP registration fees for a later year.

Each of those records is read by a different authority, at a different time, and kept for a different length of time: six months for hours-of-service records, four years for IFTA, three years past the registration year for IRP. The driver who drove that mile has a qualification file of their own, kept for the length of their employment and beyond.

That is the reframe this guide is built on. A carrier compliance department does not produce reports; it produces evidence. The IFTA auditor arrives years later, the FMCSA investigator after a compliance review, and an attorney after a crash.

None of these records can be made true after the fact, so the platform’s job is to capture each one correctly the first time and keep it as long as its longest clock requires.

Most carriers today hold that evidence across an ELD portal, fuel card statements, spreadsheets and filing cabinets. IFTA and DOT compliance software development is about bringing it into one system without losing the original data underneath.

This guide covers the features, integrations, regulations and costs of IFTA and DOT compliance software development, and is honest about when buying beats building.

That is the custom software development brief, and it runs through compliance dashboard development, since the mileage review queue, return worksheets, driver file vault and audit dashboard are all web applications.

What a Carrier Compliance Department Actually Runs

The work falls into two families with different regulators and different auditors.

The first is apportionment: dividing taxes and fees fairly among the jurisdictions a fleet travels through. IFTA governs fuel tax, with a quarterly return filed with the carrier’s base jurisdiction. IRP governs apportioned registration, renewed annually. A handful of states add weight-distance or highway use taxes of their own, and Unified Carrier Registration adds an annual registration by fleet size.

The second is safety qualification, governed by FMCSA. Driver qualification files under 49 CFR Part 391. Drug and alcohol testing and Clearinghouse queries under Part 382. Hours-of-service records and their supporting documents under Part 395. Biennial registration updates, now filed through FMCSA’s Motus system.

The people doing this work are usually a small team: a compliance manager, a safety director, someone in accounting who owns the fuel tax return. They spend most of their time chasing data from systems that were not designed to talk to each other.

A platform built for them has one job: make the next audit, in either family, a matter of producing records rather than reconstructing them. The feature checklist for a first release is covered in Carrier Compliance Software Features: What a US Motor Carrier Compliance Department Actually Needs in the First Release.

Jurisdictional Mileage: Where the Truck Actually Went

Everything in apportionment starts with distance by jurisdiction, and it is harder to get right than it looks.

Many carriers assume their ELD already answers the question. An ELD records location for hours-of-service purposes, at intervals and at reduced precision, and hours-of-service records only need to be kept for six months. That may not be enough to place every state-line crossing accurately or to survive an IFTA audit four years later.

Most platforms work from telematics GPS data captured more frequently, calculate the distance between readings, determine where each crossing happened, and total the miles by jurisdiction for each vehicle.

The IFTA Procedures Manual sets out what records produced by vehicle-tracking systems must contain, starting with the original location data itself. That single requirement shapes the architecture: the platform has to keep the raw readings, not just the totals calculated from them, for as long as the audit window runs.

Gaps are the hard part. A device unplugged, a vehicle swapped mid-trip, a unit that went silent for a day. Those gaps must be flagged and resolved by a person from other records, never filled in by estimate. ELD and telematics mileage, fuel imports, return generation and driver file vaults are covered in Electronic Logging Device Mileage by Jurisdiction, Fuel Card Purchase Imports, Quarterly Return Generation and Driver Qualification File Vaults.

Fuel: Purchases, Receipts and the Reasonableness Test

The other half of the IFTA return is fuel: how much was bought, where, and whether tax was paid at the pump.

Fuel card transactions are the backbone, imported from each card program the fleet uses. Around them sit cash and personal-card purchases with paper receipts, bulk fuel dispensed from the carrier’s own tanks, and occasional purchases in jurisdictions where the card was declined.

The IFTA Procedures Manual specifies what a fuel record must show, and receipts missing those elements can be disallowed in an audit. A driver app that captures receipts at the pump, with the unit number attached, closes most of that gap, which makes custom mobile app development a real part of this platform rather than an accessory.

Then comes the reasonableness test. Miles divided by gallons gives fuel economy for each unit and each quarter, and an auditor will look at the same number. A truck that appears to get impossible mileage usually has missing fuel; one that gets terrible mileage may have fuel attributed to the wrong unit.

Reading receipts into structured fields for human verification and flagging those anomalies for review is legitimate AI product and agent development work, with the boundary in the same sentence: it never fills gaps in records, generates receipts, edits hours-of-service records, makes qualification decisions or infers proficiency, national origin or immigration status.

The platform’s job is to flag anomalies for a person to investigate. It never adjusts fuel or mileage to make the ratio look normal, because a smoothed number is precisely what an auditor is trained to find.

Quarterly Returns, IRP Renewals and the Audit Package

With distance and fuel reconciled, the quarterly IFTA return becomes a calculation: taxable miles and gallons by jurisdiction, tax due or credit by jurisdiction at that quarter’s rates, and a net amount owed to or from the base jurisdiction.

Returns are generally due by the last day of the month after each quarter, including quarters with no qualifying operations. Rates change every quarter and differ by fuel type, so rate tables belong in data the platform updates, never in code.

IRP draws on the same distance data on a different schedule. The annual renewal reports distance by jurisdiction for a defined prior period, and that drives apportioned fees. Weight-distance and highway use taxes in the states that impose them use the same miles again, with their own filing cycles.

The audit package is where a platform proves its worth. When the base jurisdiction schedules an audit, the carrier must produce the source records for a sample of vehicles and periods: original location data, distance calculations, fuel records, and summaries tying them to the returns.

A platform that can generate that package from what it already holds turns weeks of reconstruction into an export, which is why the return review and audit dashboard deserve the attention web application development gives a primary workspace.

The Driver Qualification File

The second family of obligations centers on the driver, and its core record is the driver qualification file required by 49 CFR 391.51.

It holds the employment application, motor vehicle record inquiries from each state where the driver held a license, the road test certificate or its equivalent, the investigation of the driver’s safety performance with previous employers, the annual review of the driving record, and evidence of medical certification.

That last item changed in June 2025. For CDL drivers, medical examiners now report results electronically, states post them to the driver’s motor vehicle record, and carriers verify certification from that record rather than from a paper card. Non-CDL drivers of commercial motor vehicles still follow the paper certificate process.

A platform models each requirement with its due date and expiration, holds the evidence, and alerts the safety team before anything lapses. Integrated with dispatch, it can block assignment of a driver whose required item has expired, which is the right use of automation here.

Deciding whether someone is qualified to drive is not. That stays with qualified people. And the platform should never infer English proficiency, national origin or immigration status from names or other data. Proficiency is assessed by people, and license validity is confirmed from the license and the driving record.

Drug and Alcohol Clearinghouse and HOS Supporting Documents

FMCSA’s Drug and Alcohol Clearinghouse records violations by CDL drivers. Carriers run a full query before hiring and at least annual limited queries on current drivers, each requiring the driver’s consent. Since November 2024, states also downgrade the license of any driver in prohibited status until the return-to-duty process is complete.

The platform tracks query dates, consents and results alongside the rest of the testing program. Drug and alcohol records are confidential under DOT rules, so they belong in a partition with restricted access, not in the general driver file everyone can open.

Hours-of-service records carry their own obligation. Beyond the ELD record itself, carriers must keep supporting documents, such as bills of lading, dispatch records, expense receipts and payroll records, for six months, organized so they can be matched to a driver’s day.

Here the rule for software is simple. The ELD record belongs to the driver’s day. Edits require the driver’s confirmation, coercing a driver to violate the hours rules is prohibited, and so is using ELD data to harass them. A compliance platform stores and organizes these records; it never pressures anyone with them.

Compliance: Two Regulatory Families, Different Auditors

The two families are enforced very differently, which is why a single platform is useful and why it is hard. This is educational content, not legal or tax advice.

IFTA and IRP are administered by state and provincial tax and registration agencies. The carrier’s base jurisdiction audits on behalf of all the others, and inadequate records lead to assessments that can far exceed the tax actually owed. The rules live in the IFTA Articles of Agreement and Procedures Manual, the IRP Plan, and each jurisdiction’s administrative practice.

FMCSA’s rules are federal and enforced through compliance investigations, roadside inspections and safety data. In the last two years several have shifted: medical certification moved onto the driving record, Clearinghouse violations now cost drivers their licenses, English proficiency became an out-of-service condition, eligibility rules for non-domiciled CDLs changed and are being litigated, and registration moved to the new Motus system.

Underneath both runs the retention problem. One mile can be evidence for six months, four years and longer at the same time, and a platform that keeps everything on one schedule will either keep too little or keep sensitive records longer than necessary. The full compliance guide is covered in IFTA and IRP Jurisdictional Reporting, FMCSA Driver Qualification Files Under 49 CFR 391, Drug and Alcohol Clearinghouse Queries, Hours of Service Supporting Document Retention and UCR Registration.

Cost: From MVP to Full Platform

The platform stages naturally, starting where the money is. All figures are 2026 planning ranges, not quotes.

The MVP, a fuel tax core covering mileage by jurisdiction from one or two telematics sources, import from the primary fuel card, gap and fuel economy flags, the quarterly IFTA worksheet and an audit export, runs roughly $130K to $240K over 5 to 7 months.

Stage 2, full fuel tax and registration, adds additional data sources, driver receipt capture, bulk fuel, IRP renewal mileage, weight-distance reporting, amended returns and complete audit packages. Roughly $90K to $170K over 4 to 6 months.

Stage 3, the driver qualification vault, covers requirement models, MVR and Clearinghouse tracking, medical certification via the driving record, expirations and dispatch hard stops, and confidential drug and alcohol records. Roughly $120K to $220K over 5 to 7 months.

Stage 4 adds hours-of-service supporting documents, UCR and registration tracking, and an audit readiness dashboard. Roughly $90K to $170K over 4 to 6 months.

A full platform lands broadly in the $430K to $800K range over about 18 to 26 months with overlap. The stage-by-stage budget, the items carriers forget and a frank section on when not to build are covered in From MVP to Full Platform: What US Motor Carriers Pay at Each Stage.

Conclusion

Carriers that treat compliance records as evidence, capturing each mile, gallon and driver document correctly the first time, keeping the raw data underneath every total, and holding each record for its longest clock, end up with audits that are exports rather than emergencies.

Those that keep hours-of-service data out of dispatch pressure and qualification decisions with people protect their drivers and themselves at once.

The most expensive mistake in this category is building the first version on assumptions that force a second, which is covered in Rebuilding Twice Is the Default: How Early Consulting Prevents Paying for a Custom Compliance Platform Twice, and it is the standard to set with the software companies in the United States quoting you.

If you are evaluating a custom compliance platform, mapping every record you keep to the regime, auditor and retention clock it answers to is what keeps the first build from becoming the first of two.

FAQ