Intermodal Drayage Chassis Splits: Automated Cost Allocation & Dispute Engines
Marine container drayage operations at U.S. ports routinely encounter chassis splits: situations in which the ocean container and the chassis used to move it originate from or must be returned to different physical facilities. These events generate complex billing interactions among steamship lines, merchant haulage operators, intermodal equipment providers (IEP), terminal operators, and the drayage motor carrier.
Without automated tracking and allocation logic inside the transportation management system (TMS), the resulting per diem, accessorial, and split-run invoices create persistent reconciliation friction, disputed charges, and cash-flow leakage. This technical guide details the operational mechanics of chassis splits, the database and workflow structures required to manage them, and the engineering patterns that enable fully automated cost allocation and dispute resolution.
The Operational and Billing Chaos of Chassis Splits
Definition and Common Scenarios
A chassis split occurs whenever the pickup or drop-off location of the container and the pickup or drop-off location of the chassis differ. Typical triggers include:
- Container retrieved from a marine terminal while the chassis is pulled from an off-terminal IEP pool depot.
- Empty container returned to a steamship line yard while the chassis is dropped at a separate maintenance or storage facility.
- Merchant haulage versus ocean carrier haulage transitions that require chassis swaps at different gates.
Each split generates at least two distinct geofence events. Terminal operators, IEPs, and steamship lines each record these events independently, often on different calendars and with different per-diem rules. The resulting invoices arrive weeks later in varying formats (EDI 210, CSV, PDF, API payloads), frequently containing overlapping or contradictory charges.
IEP Per Diem and Split-Run Billing Mechanics
Intermodal Equipment Providers operate chassis pools under standardized agreements. When a chassis is not returned to the same facility from which it was taken, IEP systems flag a split-run. This typically triggers:
- Additional daily per-diem rates for the “split” portion of the equipment cycle.
- Accessorial charges for repositioning or “street turn” penalties.
- Allocation of responsibility between the steamship line (if under ocean carrier haulage) and the merchant (if under merchant haulage).
Disputes commonly arise over which party caused the split, the exact timestamp when possession transferred, and whether the motor carrier followed the prescribed routing. Manual reconciliation of these disputes consumes significant administrative labor and often results in partial payment or write-offs.
Engineering an Automated Chassis Split Engine in the TMS
A purpose-built intermodal TMS engine must treat chassis splits as first-class domain objects. The following architectural components have proven effective across multiple drayage fleets and 3PL brokerages.
1. Dual-Geofence Event Model
Replace the traditional single “location” field with a composite event structure that records both container facility and chassis facility. A simplified relational schema fragment includes:
CREATE TABLE chassis_split_events (
event_id UUID PRIMARY KEY,
move_id UUID NOT NULL REFERENCES shipment_moves(move_id),
container_number VARCHAR(20),
chassis_number VARCHAR(20),
container_facility_id VARCHAR(50),
chassis_facility_id VARCHAR(50),
event_type ENUM('PICKUP','DROPOFF','SWAP'),
event_timestamp TIMESTAMPTZ NOT NULL,
geofence_source VARCHAR(30),
latitude NUMERIC(9,6),
longitude NUMERIC(9,6),
created_by_system VARCHAR(30),
raw_payload JSONB,
hash_value CHAR(64)
);A deterministic hash of the core fields (container, chassis, timestamps, facilities) creates an immutable audit key that can be shared with counterparties to prove event provenance.
2. Automatic Accessorial Calculation Rules
Business rules evaluate each split event against carrier rate matrices, steamship line contracts, and IEP tariff schedules. Rules are stored in a decision-table format that can be maintained by operations analysts without code changes. Example decision dimensions:
- Haulage type (ocean carrier vs merchant)
- Facility pair distance and allowed street-turn windows
- Responsible party per master service agreement
- Time-of-day and weekend/holiday multipliers
When a split is detected, the engine posts the calculated accessorial to the shipment’s billing line items with full lineage back to the source geofence events. This linkage is critical for dispute defense.
3. IEP Electronic Invoice Reconciliation
The TMS ingests IEP invoices via API or EDI 210. A reconciliation service matches incoming line items against previously recorded chassis split events using the immutable hash values. Matches are auto-cleared; variances are routed to an exception queue with attached evidence packets containing:
- Timestamped geofence records from both terminal and chassis provider
- Calculated versus billed amounts
- Contractual rule citations
- Digital signatures of the audit trail
Accepted variances update the carrier’s cost ledger; disputed items generate structured dispute files that can be transmitted back to the IEP through their web portal or EDI 214/210 response loop.
Regulatory and Audit Considerations
Automated chassis split engines must preserve chain-of-custody for FMCSA, CBP, and state weight-and-measure compliance. All geofence events should be recorded with source system identity, GPS precision, and tamper-evident hashes. When merchant haulage and ocean carrier haulage overlap on the same container move, the system must maintain separate cost and revenue ledgers until final allocation is confirmed by the steamship line’s demurrage and per-diem portal.
Integration with ELD systems (via the practices described in our ELD and EDI Integration practice) ensures driver-captured timestamps align with terminal gate transactions, further strengthening the audit trail.
Integration Best Practices for Production Deployments
Successful chassis split automation requires mature integration across several domains. Strong Tower Consulting recommends the following prioritized workstreams:
- TMS Implementation - Extend the core move object model to support composite container/chassis events.
- Transportation Accounting Integration - Post split accessorials directly to the correct GL accounts and customer invoices with proper cost center allocation.
- Carrier Rate Matrix Optimization - Maintain dynamic rate tables that reflect current IEP, terminal, and steamship line accessorial tariffs.
- Business Process Optimization - Redesign dispatch, yard, and billing workflows to treat split detection as a real-time rather than after-the-fact activity.
- Advanced Reporting - Deliver executive dashboards showing split frequency by facility pair, average dispute resolution time, and recovered revenue.
For organizations operating in both brokerage and asset-based intermodal drayage, the same engine serves both 3PL brokerage and intermodal drayage business units, while truckload operations benefit from the unified accounting and ELD data foundation.
Eliminate Chassis Split Leakage in Your Operation
If your organization still reconciles intermodal chassis invoices manually or writes off frequent disputes, an automated split tracking and dispute resolution engine can materially improve margins and reduce administrative burden. Strong Tower Consulting, LLC has helped numerous motor carriers and freight brokerages design, implement, and optimize these capabilities inside both commercial and custom TMS platforms.
Begin with an objective assessment of your current intermodal billing and exception processes. Contact us to schedule a no-obligation technical review.
Frequently Asked Questions
- What is a chassis split in intermodal drayage?
- A chassis split occurs when the ocean container and the intermodal chassis are fetched from or returned to different terminal or depot facilities, creating dual geofence events and separate billing responsibilities.
- How does an automated chassis split engine resolve IEP billing disputes?
- The engine logs precise timestamped geofence events at each facility, automatically allocates per diem and accessorial charges to the responsible party, generates immutable audit trails, and reconciles against electronic IEP invoices.
- What integration points are required for chassis split automation in a TMS?
- Key integrations include EDI 214 status messages, terminal API geofence events, IEP billing web services, steamship line merchant haulage feeds, and accounting system cost allocation endpoints.