By Scott Elliott, Principal Transportation Systems Architect at Strong Tower Consulting
Strong Tower Consulting, LLC was founded in Minnesota in 2008. In business for more than 18 years, we serve motor carriers, freight brokerages, and private fleets with enterprise-grade transportation technology solutions. Phone: 763-244-1373.
Motor carriers operate in a highly competitive labor market for qualified CDL drivers. A well-engineered compensation system within the Transportation Management System (TMS) serves dual purposes: accurate payroll generation and transparent visibility for prospective drivers during the recruitment process. Strong Tower Consulting has implemented these architectures for numerous truckload, intermodal drayage, and brokerage-affiliated carrier operations since 2008.
This technical guide examines the database schemas, business logic, and integration patterns required to build dynamic CPM matrices, accessorial pay engines, and recruitment-facing transparency portals. All patterns described reflect real-world enterprise TMS implementations using relational databases, rules engines, and secure API layers.
A normalized relational design is essential for maintainability and audit compliance. The primary entities include:
Foreign key relationships enforce referential integrity while allowing a single driver to be assigned to different matrices based on equipment type, tenure, or union status. Indexes on effective date ranges and driver classification columns ensure sub-second lookup performance during dispatch and payroll cycles.
Industry-standard practice separates compensation for revenue-generating (loaded) miles from non-revenue (empty, deadhead) miles. Within the TMS, the dispatch module evaluates each leg of a driver's tour against the active matrix.
The calculation engine follows this decision flow:
Many carriers implement banded matrices where the CPM rate steps down after certain cumulative mileage thresholds within a pay period. This requires the TMS to maintain running totals per driver per pay cycle, typically stored in a DriverPayPeriodSummary table that is updated transactionally after each load settlement.
| Tier | Min Miles | Max Miles | Loaded CPM | Empty CPM |
|---|---|---|---|---|
| 1 | 0 | 500 | 0.65 | 0.28 |
| 2 | 501 | 1200 | 0.58 | 0.25 |
| 3 | 1201 | null | 0.52 | 0.22 |
This table structure is stored relationally and exposed through configuration UIs for carrier operations teams. Strong Tower Consulting frequently optimizes these matrices as part of our carrier rate matrix optimization practice.
Accessorial compensation represents a significant portion of driver earnings. Modern TMS platforms encode these rules in a declarative rules engine rather than hard-coded logic. Common elements include:
All accessorial calculations write to a PayLineItem table with foreign keys to the source event (stop, detention record, etc.), the applied rate record, and the resulting monetary amount. This granular lineage supports both payroll and dispute resolution.
Integration with ELD systems is critical for automated capture of detention and layover events. Our ELD and EDI integration practice ensures real-time, compliant data flows between electronic logging devices and the central TMS compensation engine.
Forward-thinking carriers expose a read-only version of their active compensation architecture to prospective drivers through a secure recruitment portal. This "pay transparency engine" typically includes:
The transparency engine is architected as a separate microservice or carefully permissioned module within the TMS. It queries the same normalized rate tables used by payroll but returns only public-facing, redacted views. No individual driver payroll data is ever exposed.
During the application workflow, the portal can pre-populate expected earnings based on the applicant's indicated home terminal and preferred equipment type. This approach has become a competitive differentiator in CDL driver recruitment.
Once calculated, driver earnings must flow to payroll and general ledger systems with full auditability. Strong Tower Consulting recommends using NACHA-compliant file formats for direct deposit transmission and standardized CSV or XML manifests for accounting integration.
The settlement process typically follows these steps:
Version-controlled rate tables ensure that historical payroll runs can be reproduced exactly as originally calculated, satisfying both internal controls and regulatory requirements.
Successful deployment of advanced driver compensation architecture requires more than software configuration. Our business process optimization methodology includes:
Carriers operating in the truckload, intermodal drayage, or brokerage/3PL segments each require tailored matrix designs. The flexibility of a normalized, date-effective schema allows carriers to support multiple operating divisions within a unified payroll and recruiting platform.
Strong Tower Consulting, LLC and affiliated sister company Exspeedite LLC are separately organized under common ownership (separate EINs; liability firewall). Scott Elliott is founder and principal transportation systems architect of both organizations.
Contact Scott Elliott at 763-244-1373 to architect a dynamic driver compensation matrix integrated with your dispatch, settlement, and recruiting systems.