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: Compliance for US Carrier Software

This article is part of our series on Custom IFTA Fuel Tax And DOT Compliance Platform Development for US Motor Carriers: Building a Jurisdictional Mileage, Fuel Import And Driver File System

Introduction: Two Families of Rules, One Set of Miles

A motor carrier answers to two families of rules that rarely talk to each other, and together they define the motor carrier compliance software requirements any platform has to meet.

Fuel tax and registration apportionment, under IFTA and IRP, is administered by state and provincial agencies and audited by the carrier’s base jurisdiction. Safety qualification, under FMCSA’s regulations, is enforced through investigations, roadside inspections and safety data.

They share the same trucks, the same drivers and often the same miles, and they disagree about how long records must be kept and what those records must contain. A compliance platform has to satisfy both without letting either set of rules quietly override the other.

This article walks through each obligation named in the title and what it means for software, since together they define the motor carrier compliance software requirements a build has to satisfy.

This is educational content, not legal or tax advice. Confirm positions with transportation regulatory counsel and your base jurisdiction. Compliance is the regulatory layer of the full custom software development guide to IFTA and DOT compliance software development, and it shapes every screen of compliance dashboard development.

IFTA and IRP Jurisdictional Reporting

IFTA

Qualified motor vehicles operating in more than one member jurisdiction are licensed through a base jurisdiction, which collects quarterly returns and distributes tax to the others.

Returns are generally due by the last day of the month after each quarter, including quarters with no operations. Records must be kept for four years from the due date or filing date, whichever is later.

The Procedures Manual specifies distance records, including specific elements for records produced by vehicle-tracking systems beginning with the original location data, and fuel records.

IRP

Apportioned registration fees are based on distance traveled in each jurisdiction during a defined prior period.

Distance records supporting the application must be kept for three years after the close of the registration year, which in practice can mean around six and a half years of data. Inadequate records lead to assessments.

What This Means for Software

Keep raw location data and fuel records for the longer of the two periods, and generate both returns from the same reconciled distance. Those two sentences are most of the motor carrier compliance software requirements on the apportionment side. Neither program certifies software; any vendor claiming IFTA certified is describing marketing, not a credential.

FMCSA Driver Qualification Files Under 49 CFR 391

Part 391 sets who may drive a commercial motor vehicle, and 391.51 lists what the carrier must keep to prove it: the employment application, motor vehicle records from each licensing state, the road test certificate or equivalent, the safety performance investigation with previous employers, the annual driving record review, and evidence of medical certification. The file is generally kept for the length of employment plus three years.

Medical certification changed in June 2025. For CDL drivers, results now flow from examiners to the state’s driving record, and carriers verify from that record. Transition waivers applied while states onboarded, so verify current status. Non-CDL drivers still follow the paper certificate process.

Two other developments affect qualification. English proficiency, a long-standing requirement, became an out-of-service condition in June 2025. And FMCSA’s 2026 final rule narrowing non-domiciled CDL eligibility is in effect and being litigated.

For software, both point to the same discipline: verify license validity and expiration from the license and driving record, and never infer proficiency, national origin or immigration status from data.

Drug and Alcohol Clearinghouse Queries

The Clearinghouse records drug and alcohol program violations by CDL drivers. Carriers must run a full query before a driver performs safety-sensitive functions and a limited query at least annually for every current driver.

Each query requires consent: a general written consent for limited queries, and the driver’s electronic consent inside the Clearinghouse for full queries. A limited query that shows information triggers a full query within a set period, which also needs consent.

Since November 2024, a driver in prohibited status also loses commercial driving privileges on their license until the return-to-duty process is complete.

Testing procedures are shifting. A May 2026 DOT rule clarified when oral fluid testing becomes available, and fentanyl was proposed for the testing panel in 2025. Verify the current state before relying on either.

For software, the essentials are tracking every query date, consent and result; scheduling return-to-duty and follow-up tests; and keeping drug and alcohol records in a confidential partition with restricted, logged access.

Hours of Service Supporting Document Retention

Carriers must keep records of duty status and supporting documents for six months. Supporting documents are the records that verify a driver’s on-duty time: bills of lading, itineraries, schedules, dispatch records, expense receipts, electronic mobile communication records and payroll records, among others, within limits on how many must be kept per driver per day.

They must be organized so they can be matched to the driver and the day, and produced on request during an investigation.

Two protections for drivers shape what software may do with this data. Carriers may not coerce a driver to violate the hours rules, and the ELD rule prohibits harassing drivers based on ELD data. Edits to an ELD record require annotation and driver confirmation, and the original is kept.

For software: organize and retain supporting documents on the six-month clock, dispose of them on schedule unless held for another reason, and never build features that pressure drivers or alter their records. How each of these obligations becomes a product feature is mapped in Carrier Compliance Software Features: What a US Motor Carrier Compliance Department Actually Needs in the First Release.

UCR, Motus Registration and Weight-Distance Taxes

Unified Carrier Registration is an annual registration for interstate carriers, brokers and certain other entities, with fees set by fleet-size bracket. Registration for the coming year typically opens in the fall ahead of enforcement in the new year. Verify the current year’s dates and fees.

FMCSA registration moved to the Motus system in May 2026, replacing the legacy portal. USDOT numbers continue, MC numbers were not eliminated at launch, and the biennial MCS-150 update is now filed there. Verify details before scoping automation.

Several states impose weight-distance or highway use taxes separate from IFTA, with their own registration, reporting and records. Commonly cited examples include Oregon, New York, Kentucky, New Mexico and Connecticut. Verify the current list.

For software: a registration calendar per entity and state, built from the same distance data, with every filing stored alongside the figures behind it.

Privacy, Confidentiality and Fair Screening

Driver files hold some of the most sensitive data an employer keeps: license numbers, driving histories, medical certification, drug and alcohol results, background reports.

Drug and alcohol records are confidential under DOT rules. Reports from consumer reporting agencies carry Fair Credit Reporting Act duties. Medical information carries ADA confidentiality expectations, and state privacy laws apply. A carrier holding a medical certificate is not a HIPAA covered entity, so HIPAA framing does not belong in this content.

Screening must be fair as well as thorough. Requirements apply to every driver equally, and nothing in the platform should infer protected characteristics or immigration status from names or data.

Settling this scope before architecture is fixed is covered in Rebuilding Twice Is the Default: How Early Consulting Prevents Paying for a Custom Compliance Platform Twice.

Conclusion

Platforms that keep raw mileage and fuel data for the longest clock, version driver files rather than overwrite them, partition drug and alcohol records, organize hours-of-service documents without turning them against drivers, and track a regulatory landscape that changed repeatedly in 2025 and 2026 end up with records that satisfy both families of auditors.

This is educational content, not legal or tax advice. Confirm your position with transportation regulatory counsel and your base jurisdiction, and brief the software companies in the United States quoting you on where the platform’s job stops.

If you are scoping a platform that must satisfy state tax auditors and FMCSA investigators at once, mapping each record to its regime and retention clock before architecture is fixed is what keeps compliance from becoming a reconstruction project.

FAQ