Settlements, payroll, IFTA, 2290, driver files and truck service — one system that already understands how linehaul actually works. Not a spreadsheet stack that grew one tab at a time.
| Legs on the settlement statement | 42 |
| Legs you actually ran | 44 |
| Tour chain broken — truck never returned to base hub | 2 flagged |
| Ready to take back to FedEx | Yes |
Most linehaul contractors run the business across a settlement workbook, a payroll sheet, an IFTA file somebody built years ago, and a driver roster nobody checks until a driver is already out of compliance.
Generic fleet software doesn't fix this, because generic fleet software has never seen a FedEx settlement statement. It doesn't know what a run is, what availability percentage means, or why declines matter.
Every feature here exists because a contractor needed it on a specific Tuesday — not because it tested well.
Import your settlements and every leg is reconciled against the runs you actually covered. The system flags broken tour chains, legs that never returned to a base hub, and mileage that doesn't match the lane's history.
You get a specific, defensible list to take back to FedEx — not a suspicion that something's off.
Trucks float between your entities and drivers cover whichever run needs covering. Miles and pay are charged to the company that owns the run — not whichever truck happened to be free.
When a truck crosses companies, the week shows you exactly which legs moved and where they were charged.
Rate changes are effective-dated. Change a rate or move somebody from trainee to driver and payroll you already submitted stays exactly as submitted.
Every change is dated and reviewable — so when someone asks why a number is what it is, the answer is in the system.
IFTA and 2290 assemble from data already in the system, rather than from a workbook you rebuild every three months.
Each quarter the system checks IFTACH and stages the new rates for you to review and approve.
Nothing changes a filing on its own — you see what moved before anything is applied.
Fuel imports, mileage records and settlements are compared against each other, so you find the discrepancy before the state does.
Generate a completed 2290 for each company from the trucks already in the system.
Linehaul Command Center prepares your figures and the supporting detail by jurisdiction. You review and file them.
CDLs and physicals turn red on the page as they approach expiry. No report to run, no reminder to remember to set.
Tracked weekly, with B service flagged inside 8,500 miles and DOT inspections flagged inside 30 days.
Retire a truck and it leaves the working tables while its full history stays intact for IFTA, 2290 and audits.
.ics importNot designed for a market segment. The missing-leg audit, the run-versus-truck attribution, the effective-dated pay rates — each exists because a contractor hit the problem and needed it solved that week.
Most contractors run multiple entities. LCC charges miles, revenue and pay to the right one instead of making you reconcile it afterward.
Historical payroll freezes. Retired trucks keep their miles. Terminated drivers keep their records. Nothing quietly disappears.
Import FedEx settlement statements, WEX fuel and Motive mileage. Historical years import too, so you start with a full picture rather than an empty system.
Built-in integrity checks compare your sources against each other and show you where they disagree.
Settlements, payroll, tracker and service all run off the same data. Enter something once.
IFTA and 2290 figures assemble from data already in the system.
No — it runs in your browser.
Yes. Data syncs across your team and access is set page by page — your dispatcher doesn't need to see payroll, and your payroll clerk doesn't need to see IFTA.
No. It prepares the figures and the supporting detail by jurisdiction. You review and file. Linehaul Command Center is not a tax or legal advisor.
Historical data imports, so you don't start from an empty system.
Social Security numbers are stored encrypted, restricted to administrators, and every access is logged.
The fastest way to judge this is against numbers you already understand. Import a week you know cold and see whether it agrees with you — and what it catches that you didn't.