Multi-Division Carrier TMS: Automated Inter-Company Settlement Solvers
Motor carriers operating multiple divisions under separate legal entities face unique transportation accounting challenges. When dry-van, refrigerated, flatbed, and brokerage operations exist under distinct DOT and MC authorities yet share driver pools, tractor fleets, and customer relationships, the resulting inter-company transactions create significant month-end reconciliation burdens.
Strong Tower Consulting has worked with numerous multi-entity motor carrier groups to design and implement TMS architectures that automate inter-company freight billing, revenue proration, and elimination journal entries. This technical guide details the operational realities, database design patterns, workflow automation, and integration best practices required to eliminate weeks of manual accounting work.
The Multi-Entity Motor Carrier Operating Model
Many established motor carriers evolve into multi-division organizations. A single parent operating authority may spawn secondary entities for specialized equipment types or market segments. Common configurations include:
- Dry van division under MC-123456
- Refrigerated division under separate MC-789012
- Flatbed or specialized division with its own authority
- Affiliated freight brokerage operating under distinct MC authority
These entities frequently share physical assets. A company driver employed by the dry van entity may pull a refrigerated trailer assigned to the reefer division for a dedicated customer. A load initially tendered to the brokerage may be interlined to the asset-based carrier division after the first 400 miles. Tractor pools are often dynamically assigned across divisions based on maintenance schedules, driver availability, and customer requirements.
Without proper system support, these shared-resource movements generate tangled inter-company accounts receivable and payable. At month end, accounting teams must manually identify every interlined load, calculate mileage-based or revenue-based splits, create inter-company invoices, and then prepare consolidated elimination entries to remove the internal transactions from the group's financial statements. This process routinely consumes 2-4 weeks of senior accounting resources.
Modern Multi-Entity TMS Architecture
Contemporary transportation management systems designed for multi-division carriers implement a unified operational database while maintaining strict legal entity separation for regulatory, tax, and liability purposes. Strong Tower Consulting recommends the following core schema patterns when implementing or upgrading such systems.
Core Database Schema Components
LegalEntity (LegalEntityID, Name, DOT, MC, EIN, Address...)
Division (DivisionID, LegalEntityID, Name, OperatingAuthorityRef, Mode...)
Order (OrderID, DivisionID, CustomerID, RevenueAmount, Status...)
OrderLeg (LegID, OrderID, Sequence, Origin, Destination, Miles, EquipmentType, ResponsibleCarrierID, ActualCarrierID...)
InterCompanyTariff (TariffID, SourceLegalEntityID, TargetLegalEntityID, RateType, RateValue, EffectiveDate, ExpirationDate...)
InterCompanyInvoice (InvoiceID, SourceLegalEntityID, TargetLegalEntityID, OrderLegID, Amount, InvoiceDate, ReferenceLegID...)
JournalTemplate (TemplateID, LegalEntityID, AccountType, DebitCredit, EliminationFlag...)
The critical innovation is the OrderLeg table with both ResponsibleCarrierID (the division that contracted with the customer) and ActualCarrierID (the division that physically performed the move). When these differ, the system automatically triggers inter-company settlement logic.
InterCompanyTariff records establish the contractual rates between affiliated entities. These may be mileage-based, flat-rate per load, or percentage-of-revenue. Because Strong Tower Consulting and Exspeedite LLC are separately organized sister companies under common ownership (separate EINs; liability firewall), we treat inter-company tariffs with the same rigor as external arm's-length agreements.
The Automated Inter-Company Settlement Solver
The settlement solver is a rules engine that activates whenever an OrderLeg is marked as "Delivered" or "Invoiced." The process follows these steps:
- Identify all OrderLeg records where ResponsibleCarrierID differs from ActualCarrierID.
- Retrieve the applicable InterCompanyTariff based on the two LegalEntity values, equipment type, and movement date.
- Calculate the inter-company payable amount using the tariff logic (mileage proration, stop-count, or revenue percentage).
- Generate a mirrored pair of inter-company invoices:
- Debit entity invoices Credit entity for the calculated amount
- Credit entity invoices Debit entity for the identical amount (reciprocal reference)
- Create corresponding accounts-receivable and accounts-payable ledger entries within each entity's sub-ledger.
- Generate elimination journal entries that net to zero at the consolidated group level.
This entire process executes in near real-time as loads are completed, eliminating the traditional month-end backlog. The solver maintains complete audit history with immutable records of every tariff applied, mileage calculation, and journal entry generated.
Dynamic Revenue Proration Algorithms
Accurate revenue splits require sophisticated proration logic. The most common methods we implement for clients include:
Mileage-Based Proration
When a load moves across multiple divisions, revenue is split according to the actual dispatched miles each entity performed. The TMS must maintain a precise geo-coded mileage record for each Leg segment. We integrate with PC Miler or similar engines through the ELD and EDI integration layer to capture verified distances.
Event-Based Splits
Certain dedicated fleets use stop-count or event-based splits. The first division that performs pickup and the first two delivery stops receives 65% of revenue; the secondary division that completes the remaining route receives 35%. These rules are stored in configurable business rules tables rather than hard-coded logic.
Interline Percentage Agreements
Some multi-entity carriers maintain standing interline agreements that assign fixed percentages regardless of mileage. The settlement solver respects these contractual overrides when present in the InterCompanyTariff record.
Consolidated Elimination Journal Entries
The final and most critical component is the automatic generation of elimination entries that flow directly into the enterprise accounting system. When two affiliated entities record offsetting revenue and expense, the consolidated financial statements must remove both sides of the internal transaction.
Our recommended integration pattern with transportation accounting integration uses a standardized elimination journal template. For every inter-company invoice pair, the system generates four balanced journal entries:
- Debit AR - Division A / Credit Revenue - Division A (elimination)
- Debit Expense - Division B / Credit AP - Division B (elimination)
- Offsetting entries in Division B's books
- Consolidation-level elimination entries that net to zero
These entries are posted through API or file-based integration to the primary ERP or accounting platform. Because the TMS maintains legal entity context on every transaction, the resulting trial balance at both the division and consolidated level is accurate on day one of the close process.
Implementation Best Practices
Strong Tower Consulting follows a structured methodology when implementing multi-division TMS solutions. Key practices include:
- Comprehensive legal entity and division configuration workshops before any software configuration begins.
- Creation of inter-company tariff schedules with involvement from both operations and finance leadership.
- Parallel testing of the settlement solver against 6-12 months of historical transactions to validate accuracy.
- Integration testing with the accounting platform to confirm elimination entries post correctly and eliminate cleanly on consolidation.
- Role-based security ensuring users only see data for divisions they are authorized to access.
These projects typically combine elements of TMS implementation, business process optimization, and advanced reporting to deliver both operational visibility and financial accuracy.
For carriers also operating brokerage or 3PL services, we extend the same framework to handle brokerage operations. Similar patterns apply to intermodal drayage and truckload operations that cross corporate boundaries.
Conclusion: From Weeks of Reconciliation to Real-Time Accuracy
The combination of a properly designed multi-entity TMS, dynamic inter-company tariff management, automated settlement solving, and direct accounting integration transforms what was once a painful month-end process into a fully automated, auditable workflow. Carriers gain accurate divisional profitability reporting, reduced accounting labor costs, and stronger internal controls.
If your motor carrier group operates multiple divisions under separate authorities and struggles with inter-company billing complexity, Strong Tower Consulting can assess your current processes and recommend a targeted modernization path.
Enterprise Systems Advisory
Ready to modernize your transportation management software, eliminate manual spreadsheets, or optimize telematics and recruiting workflows? Contact Strong Tower Consulting for direct architect guidance.