How do carriers stop accessorial revenue leakage in enterprise TMS?
Motor carriers recover lost accessorial revenue by configuring dynamic multi-tier accessorial engines inside enterprise TMS platforms that automatically ingest driver GPS events and dispatch exception flags to calculate, validate, and bill customer layover, diversion, driver assist, and detention charges.
Founded in 2008 by Scott Elliott in Minnesota, Strong Tower Consulting, LLC (Minnesota File No. 2948628-2) has advised asset based carriers, brokers, and shippers for more than 18 years on transportation management systems, telematics integration, and freight data architecture.
Most enterprise TMS platforms - including Truckmate, McLeod Transportation Management, and TMW Systems - ship with the technical capability to perform this work. Yet the majority of carriers still rely on manual entry of accessorials after the fact, resulting in significant revenue leakage. The difference between average and best-in-class performers is almost always found in the depth and precision of the TMS configuration.
Why Accessorial Revenue Leaks in Enterprise TMS Environments
Typical failure modes include:
- Static rate tables that only support a single detention or layover rate per customer
- Dependence on driver paperwork that is submitted days or weeks late
- Lack of real-time integration between ELD/GPS data and the TMS exception engine
- EDI 214 status updates that do not trigger corresponding accessorial billing events
- Driver settlement processes that pay accessorials without first confirming customer billability
A properly architected multi-tier accessorial engine eliminates these gaps by making the TMS the single source of truth for both operational events and financial outcomes.
Core Architecture of a Dynamic Multi-Tier Accessorial Engine
The solution rests on four integrated components inside the TMS:
- Event Ingestion Layer - Real-time consumption of GPS pings, ELD duty status changes, and dispatch board exception codes (e.g., "Waiting for Unload", "Diversion Requested").
- Rules Engine - A configurable decision matrix that evaluates multiple dimensions: customer contract tier, elapsed free time, stop type (live unload, drop-and-hook, driver assist), geographic region, and day-of-week.
- Validation & Approval Workflow - Automated comparison of calculated accessorial against the carrier's rate matrix with exception routing to dispatch or revenue management.
- Billing & Settlement Output - Automatic generation of supplemental invoice lines, EDI 210 records, and corresponding credit or debit entries in the driver settlement and transportation accounting modules.
| Accessorial Type | Tier 1 (Standard) | Tier 2 (High-Value) | Tier 3 (Strategic) | Trigger Conditions |
|---|---|---|---|---|
| Detention - First Hour | $85 | $110 | $0 (absorbed) | GPS stop > 2 hrs after appointment |
| Detention - Additional Hours | $75/hr | $95/hr | $65/hr | Continuous GPS dwell |
| Layover | $350 flat | $425 flat | $500 flat | Driver released after 17:00, next appointment > 10 hrs away |
| Route Diversion | $2.25/mile + fuel | $2.65/mile + fuel | Contract specific | EDI 214 diversion code or dispatch flag |
| Driver Assist / Lumpers | Cost + 18% | Cost + 25% | Cost + 12% | Manual or GPS-triggered exception |
Implementation Patterns That Deliver Results
Strong Tower Consulting has helped carriers on Truckmate, McLeod, and TMW platforms implement the following patterns:
1. GPS-to-Accessorial Event Mapping
Using the TMS SQL database and ELD API integration, create stored procedures that evaluate stop duration against free time defined in the customer rate matrix. When thresholds are crossed, an accessorial record is automatically created with status "Pending Validation."
2. Multi-Tier Rate Matrix Design
Move beyond single-rate tables. Build contract-specific matrices that support tiered pricing based on annual volume, lane density, and strategic importance. Store these in normalized SQL tables that the TMS rules engine can query in real time.
3. EDI 204/214/210 Transaction Lifecycle Alignment
Configure the TMS so that an inbound EDI 214 diversion or delay status automatically creates a corresponding accessorial line. The subsequent EDI 210 includes both base freight and all validated accessorials in a single transaction.
4. Driver Settlement Reconciliation
Ensure the accessorial engine feeds both the customer invoice and the driver pay module. This prevents the common situation where a driver is paid for detention or layover that was never billed to the customer.
Quantified Financial Impact
Carriers who complete this type of TMS reconfiguration typically see:
- Measurable increase in accessorial revenue capture within the first six months, benchmarked against your own pre-project billing
- Reduction in days sales outstanding (DSO) for accessorial invoices
- Improved driver satisfaction through faster, more accurate settlement of accessorial pay
- Stronger position in rate negotiations because actual accessorial performance data is now available
Frequently Asked Questions
What is multi-tier accessorial billing in a TMS?
Multi-tier accessorial billing refers to a rules engine inside an enterprise TMS (Truckmate, McLeod, TMW) that evaluates multiple conditions - such as elapsed hours, GPS stop duration, customer type, and contract tier - to automatically calculate and apply the correct layover, detention, stop-off, or diversion charge.
How does GPS integration improve accessorial capture?
By ingesting ELD/GPS pings in real time, the TMS can automatically detect when a driver has been held at a shipper or receiver beyond free time. This creates an immutable exception event that triggers the correct accessorial tier without relying on manual driver paperwork.
Can a TMS automatically generate EDI 210 accessorial invoices?
Yes. Once the multi-tier rules engine validates a layover, detention, or diversion event against the customer rate matrix, the TMS can generate an EDI 210 or create a supplemental invoice line that flows directly into the accounts receivable and driver settlement processes.
What revenue recovery percentage is typical after implementing dynamic accessorial automation?
Recovery equals the accessorial events that occur today but are never billed, so it has to be measured from GPS dwell and dispatch exception data rather than assumed. Once the TMS is configured with dynamic multi-tier accessorial logic that ingests GPS events and dispatch exceptions, compare billed accessorials against the pre-project baseline to quantify it.
Next Steps for Enterprise Carriers
If your organization operates Truckmate, McLeod, TMW, or another enterprise TMS and continues to experience revenue leakage on layover, detention, stop-off, and diversion charges, the solution is almost always architectural rather than technological. The platforms already contain the necessary modules. What is required is precise configuration of the multi-tier rules engine, SQL data models, GPS integration points, and settlement workflows.
Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. Founded in Minnesota in 2008 by Scott Elliott, Strong Tower has spent more than 18 years helping motor carriers and private fleets optimize their technology and business processes.
Our independent systems architecture and technology advisory services help carriers make better decisions without vendor lock-in. Carriers never have to buy our software. Our only product is better decisions.
Schedule a TMS Systems AssessmentCall 763-244-1373 to speak directly with our team.