What should carrier acquisition technology due diligence cover?
Review the target carrier's TMS data integrity, telematics feeds, EDI interfaces, settlement rules, software contracts, and recovery controls. Test representative records and reconcile financial outputs so the buyer can distinguish documented capabilities from migration costs and unresolved risks.
Founded in 2008 by Scott Elliott, Strong Tower Consulting, LLC brings 18+ years of freight transportation technology consulting experience. The firm was founded in Minnesota on July 29, 2008 (File No. 2948628-2); see our company history.
Private equity sponsors and strategic carriers acquiring motor carriers in 2025 face unprecedented technology risk. A single overlooked licensing shortfall, corrupted telematics archive, or non-compliant EDI 204/214/210 transaction history can destroy projected synergies and create material contingent liabilities. This checklist delivers the exact audit framework used by Strong Tower Consulting during carrier acquisition technology due diligence engagements.
Five Critical Audit Vectors
- Core TMS Relational Schema Health - Foreign-key integrity, indexing strategy, and historical data volume in Truckmate, McLeod, TMW, and legacy platforms.
- J1939 Telematics & ELD Data Streams - Completeness of engine ECM, GPS, and Hours-of-Service archives required for IFTA, CSA, and litigation defense.
- EDI Transaction Compliance & Audit Trail - 204 tender acceptance, 214 status, 210 freight invoice, and 990 load tender response integrity.
- Driver Settlement & Escrow Accounting Accuracy - Correct calculation of fuel surcharges, detention, accessorials, and per diem in settlement engine.
- Software Licensing & Subscription Liabilities - True-up exposure on McLeod, Truckmate, Samsara, Motive, and third-party EDI VAN contracts.
Database Schema Audit Checklist
Begin every carrier acquisition review with a read-only replica of the production TMS database. Strong Tower Consulting recommends the following minimum queries and validation steps:
| Object | Validation Target | Red Flag Threshold | Typical TMS |
|---|---|---|---|
| Order & Shipment Tables | Foreign-key integrity between OrderHeader, OrderStop, Shipment, and Carrier tables | >0.8% orphaned records | Truckmate, McLeod, TMW |
| EDI 214/210 Log Tables | Complete inbound/outbound transaction history with timestamps and ACK status | Missing >3% of expected 214s for loads moved in last 24 months | McLeod, TMW |
| DriverSettlement Table | Accurate fuel surcharge, detention, and accessorial pass-through to driver pay | >1.2% variance in sampled settlements vs. actual customer invoices | Truckmate, legacy AS/400 |
| Telematics Event Log | J1939 PID 190 (Engine Speed), PID 84 (Vehicle Speed), and HOS duty status records | >18% of active power units with >30-day gaps in 90-day history | Samsara, Motive, Geotab |
| IFTA & Fuel Tax Tables | State-by-state mileage by jurisdiction with GPS corroboration | Unreconciled mileage >4% of total reported miles | Multiple integrated systems |
Telematics & ELD Data Integrity Review
J1939 data streams have become the single largest source of post-acquisition write-downs. Acquirers must validate:
- Continuous recording of engine hours, odometer, and GPS coordinates for every power unit over the trailing 36 months.
- Absence of systematic "GPS drift" or "engine-off coasting" events that would invalidate IFTA returns.
- Complete HOS logs that match driver settlement records and CSA BASIC scores.
- API availability and historical data export capability from Samsara, Motive, or Geotab platforms.
EDI Transaction Lifecycle Audit
Review the complete lifecycle of EDI 204 tender, 990 acceptance, 214 status updates, and 210 freight invoices. Confirm that the target carrier has maintained functional acknowledgments (997/999) and that exception handling for rejected loads is fully documented. Missing 214 status messages on 8% or more of loads typically indicates systemic integration failure that will require post-close remediation costing $175,000-$425,000.
Driver Settlement Engine Validation
Sample at least 200 driver settlements across multiple pay periods. Verify that fuel surcharge revenue is correctly allocated, detention and accessorials flow through at the contracted percentage, and escrow accounts reconcile to the general ledger. Discrepancies here frequently reveal both underpayment to drivers (creating labor risk) and overstated earnings (inflating EBITDA).
Software Licensing Liability Checklist
- Obtain true-up reports for all McLeod, Truckmate, and TMW licenses.
- Review Samsara, Motive, and other telematics subscription agreements for minimum committed units.
- Validate EDI VAN contracts (Kleinschmidt, T-Connect, etc.) for volume-based pricing tiers.
- Identify any "perpetual" license agreements that actually contain hidden support renewal obligations.
Post-Acquisition Integration Risk Matrix
Strong Tower Consulting maintains a proprietary scoring model that weights each of the five vectors above. Carriers scoring below 72/100 on the combined technology diligence scorecard typically require 9-14 months and $1.2M-$3.8M in incremental investment before full integration can be achieved.
Frequently Asked Questions
What are the five critical vectors that must be audited in trucking M&A technology due diligence?
Technical due diligence for commercial motor carrier acquisitions must audit five critical vectors: core TMS relational schema health, J1939 telematics data streams, EDI transaction compliance, driver settlement accuracy, and unrecorded software licensing liabilities.
Which TMS platforms require the deepest schema scrutiny during carrier acquisition due diligence?
Truckmate, McLeod, TMW, and legacy AS/400 systems require the deepest schema scrutiny. Auditors must examine foreign-key integrity between Order, Shipment, Stop, DriverSettlement, and FuelSurcharge tables, along with indexing strategies on high-volume EDI 214 and 210 transaction logs.
Why is J1939 telematics data integrity critical in M&A due diligence for fleets?
J1939 streams from ELDs and engine ECMs directly impact Hours-of-Service compliance, IFTA fuel-tax reporting, and CSA SMS scoring. Incomplete or corrupted historical streams can create millions in contingent liabilities for the acquiring entity.
How long does a comprehensive carrier technology due diligence engagement typically require?
A full-scope technical due diligence engagement performed by Strong Tower Consulting normally requires 18-25 business days, including on-site data center or colocation visits, database analysis, API testing, and final risk report with integration cost estimates.
Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. Carriers never have to buy our software. Our only product is better decisions.
Call Scott Elliott directly at 763-244-1373 to schedule an independent systems assessment before your next carrier acquisition.