Guide ยท Carrier
Getting paid for detention
We're a fleet. How do we actually get paid for detention?
Detention is under-billing, not under-charging. Drivers are detained at a large share of stops and fleets collect on fewer than half the invoices they send, so the fix is proof: ELD timestamps into the TMS, the invoice generated from them, and the dispute handled before the customer forgets.
ASSUMEDWe assumed an asset carrier with an ELD provider and a dispatch system that don't talk to each other.
Your stack, as you described it
Where people are the glue
- Dispatch keys detention from driver texts
- Billing invoices detention a week later, if at all
Three ways through
- Use what you haveOften enough
Your ELD already has geofenced arrival and departure. Turn the report on and attach it to the invoice; that alone moves the collection rate.
- ConnectWhat we'd do
ELD events into the TMS, detention invoices generated automatically with the proof attached, and an exception queue for disputes. Often paid for out of what it recovers.
- BuildOnly if it's your edge
A customer-facing detention portal if you run dedicated fleets for a few shippers and the dock is the relationship.
What happens next
- We start with your last 90 days of detention invoices and ELD data.
- A prototype of the automated invoice in weeks.
- Run keeps it working when the ELD vendor changes an API.
Have a different stack? Ask the guide.
Ask a follow-up