Modern motor carriers lose millions annually to unbilled or disputed detention, layover, and facility dwell accessorials. The root cause is almost always the same: lack of an immutable, GPS-derived audit trail that both carrier and shipper can trust. Strong Tower Consulting has spent more than 16 years engineering solutions that close this gap using polygon geofencing, driver push-button synchronization, automated threshold alerts, and touchless invoice generation.
Whether your fleet runs Truckmate, McLeod, TMW, or another SQL-based TMS, this guide provides the exact architecture, data model patterns, and integration points required to turn telematics data into defensible accessorial revenue.
The Business Impact of Unbilled Dwell Time
Industry data consistently shows that 18-27% of eligible detention and layover events go unbilled. When billed, nearly 40% are disputed because of conflicting arrival and departure times between the carrier, driver, and facility. A robust geofenced dwell engine typically recovers 12-19% of total accessorial revenue within the first full year of operation.
Core Architecture: Polygon Geofencing & Event Engine
The foundation is a facility polygon geofence library. Unlike simple radius-based geofences, polygons accurately represent complex terminal and distribution center footprints. Each facility record contains:
- Unique Facility ID
- Polygon coordinate array (lat/long vertices)
- Standard free time rules by accessorial type (detention, layover, demurrage)
- Customer billing party mapping
- EDI transmission rules
Telematics platforms (including those integrated via ELD APIs) stream GPS pings into a dedicated event processor. When a truck enters a defined polygon, an "Arrival" event is generated. When it exits, a "Departure" event is recorded. Driver confirmation via mobile app push-button synchronizes the system record with the driver's log, creating a three-way match between GPS, driver, and TMS.
| Accessorial Type | Free Time | Charge Increment | Typical Rate | Trigger Condition |
|---|---|---|---|---|
| Customer Detention (Loading) | 2 hours | 15 minutes | $85-$125/hr | Arrival to Loaded departure |
| Customer Detention (Unloading) | 2 hours | 15 minutes | $85-$125/hr | Arrival to Empty departure |
| Layover | 0 hours | Per occurrence | $450-$750 | Driver forced to stay overnight |
| Facility Dwell (Drop & Hook) | 4 hours | 30 minutes | $65-$95/hr | Trailer drop to trailer retrieval |
Integration Points with Major TMS Platforms
The billing engine writes directly into the carrier's existing TMS via SQL stored procedures or API endpoints. In McLeod and TMW environments, new records are inserted into the accessorial billing tables (commonly ACC_BILLING or ORDER_ACCESSORIAL) with source code "TELEMATIC" and immutable GPS audit fields. Truckmate implementations typically leverage the custom event and billing modules.
EDI 204 inbound load tenders are enriched with facility geofence IDs. EDI 214 status messages transmit the precise arrival and departure timestamps with qualifying codes (e.g., "X1 - Arrived at Consignee", "X2 - Departed Consignee"). The final EDI 210 invoice includes the accessorial line items with reference to the supporting 214 events.
Automated Alerts and Driver Settlement Integration
When dwell time approaches the free-time threshold, the system sends automated alerts to dispatch, the driver, and the customer. This proactive notification often prevents the charge altogether by prompting faster turnaround. When charges are incurred, the same event record flows into the driver settlement engine so that drivers are compensated for their time without manual pay code entry.
Fuel surcharge calculations remain independent. The accessorial engine references the same rate matrix used by the carrier's primary rating system, ensuring consistency across fuel, detention, and other accessorial charges.
Independent by Design
Independent by design. Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership (separate EINs; liability firewall). You never have to buy our software. Carriers engage us for architecture, SQL schema development, process engineering, and TMS configuration services while retaining complete freedom to use any technology stack.
Implementation Roadmap
- Facility polygon library development (typically 800-2500 locations)
- Telematics API integration and GPS ping normalization
- Driver mobile application configuration for arrival confirmation
- TMS data model extensions and stored procedure development
- Automated EDI 214/210 generation rules
- Driver settlement and accounting integration testing
- Go-live with parallel manual validation for first 90 days
Strong Tower's transportation accounting integration practice ensures these new revenue streams are properly reflected in your financial statements and IFTA fuel tax calculations.
Conclusion
A properly engineered geofenced dwell and accessorial billing system transforms a chronic revenue leakage problem into a reliable profit center. The combination of immutable GPS evidence, automated threshold monitoring, and seamless TMS integration delivers both immediate revenue recovery and long-term operational discipline.
Carriers serious about accessorial revenue engineering should begin with a formal assessment of their current telematics, TMS, and billing workflows.
Call 763-244-1373 to speak with our transportation technology team.