Carrier detention and consignee dwell represent one of the largest sources of uncollected revenue in trucking operations. Traditional manual processes relying on driver paperwork, phone calls, and after-the-fact rate entry routinely leave 40-60% of eligible detention revenue on the table. Strong Tower Consulting designs and implements automated detention accrual engines that eliminate human latency and deliver touchless accessorial invoicing through geofence-triggered logic, real-time timestamp validation, and native integration with Truckmate, McLeod, TMW, and other major TMS platforms.
The Business Case for Automated Detention Recovery
Most carriers bill detention only when a driver explicitly reports it via paper logs or manual entry into the TMS. This creates multiple failure points: drivers forget to record detention, dispatchers fail to enter it, and billing teams lack verifiable proof of arrival and departure times. The result is systematic revenue leakage that compounds across thousands of loads each month.
Our geofence-driven architecture solves this by automatically calculating detention based on GPS-verified facility entry and exit events. When a power unit crosses a predefined polygon boundary at a shipper or consignee, the system records a precise timestamp. Upon exit, the engine computes total dwell time against the contractually allowed free time and immediately determines the appropriate accessorial charge.
| Metric | Manual Process | Automated Engine | Improvement |
|---|---|---|---|
| Detention Events Captured | 312 | 1,847 | +492% |
| Average Recovery Rate | 38% | 94% | +147% |
| Monthly Revenue Recovered | $18,400 | $107,200 | +$88,800 |
| Administrative Hours per Month | 94 | 11 | -88% |
Core Architecture Components
The detention recovery engine is built as a modular, event-driven microservice that operates independently of the primary TMS while maintaining two-way synchronization. Key components include:
- GPS Geofence Polygon Service: Maintains facility-specific polygons (typically 300-800 ft radius) with entry/exit rules that account for parking lots, staging areas, and scale houses. Polygons are version-controlled and can be updated by operations without code changes.
- Real-Time Timestamp Validator: Cross-references ELD pings, telematics API data, and EDI 214 status reports to establish irrefutable arrival and departure times. When discrepancies exist, the system applies configurable business rules to determine the authoritative timestamp.
- Contract Free-Time Threshold Engine: Stores shipper- and consignee-specific free time rules (including variations by day of week, commodity type, and appointment status) in a normalized SQL schema. Rules support both flat hours and complex tiered calculations.
- Accessorial Calculation & EDI 210 Generator: Computes charges using carrier-specific rate matrices (including fuel surcharge interaction logic) and automatically generates EDI 210 invoices with supporting 214 reference data. The engine also supports PDF generation for non-EDI customers.
- Driver Settlement Integration: Automatically allocates recovered detention revenue to driver pay according to each carrier's unique settlement rules, preventing disputes and ensuring accurate per-stop compensation.
Integration with Major TMS Platforms
The solution is deliberately TMS-agnostic. We have successfully deployed the engine with:
- Truckmate (SQL Server stored procedures and API hooks)
- McLeod (both Transportation Management and LoadMaster editions via database triggers and web services)
- TMW Suite / Trimble (through the TMW XML Interface and custom .NET listeners)
- Legacy systems via flat-file exchange or direct SQL Server Integration Services (SSIS) packages
EDI transaction lifecycles (204 tender, 214 status, 210 invoice) are fully orchestrated. When a 214 is received showing an "arrived" status, the engine can reconcile it against geofence data and flag discrepancies for immediate review.
Operational Data Flow
1. Asset crosses geofence boundary → event published to message queue.
2. Timestamp service validates against ELD/telematics and EDI 214.
3. Dwell calculator retrieves applicable free-time rule from the contract matrix.
4. If detention is accrued, rate engine calculates charge (including any fuel surcharge interaction).
5. EDI 210 is generated and queued for transmission.
6. Settlement engine updates driver pay records in real time.
7. All events are logged to an audit table for dispute resolution and carrier compliance.
Implementation Considerations
Successful deployment requires clean facility master data, accurate GPS telematics feeds, and clearly documented accessorial tariff language. Strong Tower Consulting performs a comprehensive systems assessment before implementation to identify data gaps and process exceptions. Typical projects include initial polygon mapping for the carrier's top 150 facilities, configuration of rate matrices, and integration testing with existing EDI workflows.
Frequently Asked Questions
How accurate are geofence-triggered timestamps compared to manual entry?
Geofence events combined with ELD data typically achieve greater than 98% accuracy when polygons are properly configured. Manual entry accuracy often falls below 65% due to driver workload and memory factors. The system also maintains an exception queue for rare cases where GPS drift or signal loss occurs.
Will this system work with our existing Truckmate installation?
Yes. The engine reads directly from Truckmate's SQL Server database and writes calculated detention records back into the appropriate accessorial and settlement tables. No core TMS modifications are required. We maintain compatibility with all current Truckmate versions.
How does the engine handle fuel surcharge interaction with detention charges?
The rate matrix supports both additive and multiplicative fuel surcharge logic. Many carriers apply a reduced fuel surcharge percentage to detention revenue. The engine stores these rules per customer and automatically calculates the correct total invoice amount for each EDI 210.
What is the typical ROI timeline for automated detention recovery?
Most carriers see positive cash flow within the first 45 days. Full payback on the project usually occurs between 3 and 5 months depending on fleet size and average detention frequency. Recovered revenue continues as pure margin thereafter.
Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. Founded in Minnesota in 2008 by Scott Elliott, we have spent more than 18 years helping motor carriers and private fleets optimize their technology and operational processes. Our only product is better decisions.