How TMS integration automates detention pay recovery

Your TMS already captures the data needed to recover detention pay — load timestamps, rate confirmation terms, facility information, delivery records. After each load delivers, that data sits unused while your fleet loses an estimated $11,000 to $19,000 per driver per year to unrecovered detention. TMS integration closes that gap by turning existing load data into automated recovery.

Last updated: April 2026 · Bastion Recovery Research Team

Why manual detention tracking breaks at fleet scale

At 50+ trucks, detention events happen daily. Manual tracking means someone reviews every load for detention after delivery. Someone assembles documentation from multiple sources — TMS, ELD, driver notes. Someone files the claim within the 24-72 hour deadline. And someone follows up at 7, 14, and 30 days.

At 200 trucks with 50 to 100 or more detention events per month, that is a full-time job — or more likely, a job nobody is doing consistently. The claims that get filed are the ones someone happened to notice. The rest disappear.

ATRI's 2024 data shows that fewer than half of detention invoices get paid across the industry. The filing gap is the main reason. Fleets are not losing claims — they are never filing them in the first place.

What data your TMS already has

Most TMS platforms already store 80-90% of what a detention claim requires. The data is there — it is just not being used for recovery.

• Load records — pickup and delivery locations, scheduled times, actual times
• Rate confirmations — detention terms including free time, hourly rate, and claim deadline
• Facility information — shipper and receiver addresses, contact information
• Delivery timestamps — when the driver checked in, when loading or unloading started, when they departed
• Broker information — who to bill, payment terms, claims portal

The remaining 10-20% comes from ELD data (GPS verification of facility arrival and departure) and the driver (photos, facility sign-in logs). With TMS and ELD data combined, most claims can be assembled without any driver action beyond what they already do.

How automated detention recovery works with your TMS

Step 1 — Data flows from your TMS to the recovery platform. Load records, timestamps, and rate confirmation terms are sent automatically after delivery via API or webhook. There is no manual export, no CSV upload, no portal to log into. The integration runs in the background on every completed load.

Step 2 — The recovery engine evaluates each load for detention. It compares actual facility time against the rate confirmation's detention terms. If detention exceeds free time and the amount is recoverable, the system flags the load and assembles the claim evidence — timestamps, rate confirmation terms, facility data, and ELD verification.

Step 3 — Claims are filed automatically and tracked through resolution. The claim is submitted to the broker, follow-ups happen at standard intervals, and payment is recorded when it arrives. Your ops team sees the status in their TMS or in a recovery dashboard — without touching the process.

No driver workflow change. No dispatch workflow change. The data your fleet already generates does the work.

What to look for in a detention recovery integration

• API-first architecture — the integration should consume standard TMS data formats (REST/JSON, webhooks). Avoid solutions that require manual file uploads or portal access.
• No carrier behavior change — if drivers or dispatchers need to learn a new system, adoption will be low. The best integrations are invisible to the field.
• Commission-only pricing — if the recovery service charges a subscription regardless of results, you pay even when nothing is recovered. Commission-only aligns incentives.
• White-label option — some fleets and TMS vendors want detention recovery to appear as a native platform feature, not a third-party tool.
• Facility intelligence — does the integration surface data on which facilities cause the most detention? This is valuable for lane planning and rate negotiation.
• Transparent reporting — you should see every claim, its status, and the outcome. No black boxes.

ROI of automated vs manual detention recovery

At fleet scale, the math is clear: a 200-truck fleet with $3 million in annual detention exposure that recovers even 30% through automation adds $900,000 to the bottom line — with zero incremental headcount.

For TMS vendors — the integration opportunity

Detention recovery is becoming a standard expectation for fleet TMS platforms. Carriers are asking for it, and the vendors who offer it first will have a retention and differentiation advantage.

FreightClaims signed a TMS channel deal in November 2025. The category is forming. Embedding detention recovery as a native feature increases carrier retention and creates a new revenue stream through revenue share on recoveries.

API-first recovery platforms like Bastion are designed to be embedded as white-label features — your brand, your carriers, your revenue share. The integration surfaces detention recovery inside your existing UI, so carriers never leave your platform.

If you are a TMS vendor interested in adding detention recovery as a native feature, see our partnership options.

For more on building a systematic recovery process across your fleet, see our guide to recovering detention pay at scale. For FMCSA regulations governing detention, see FMCSA detention time rules. To calculate your fleet's specific exposure, see calculating fleet detention costs. For a ready-to-use detention policy, see our detention pay policy template.