Intermodal Chassis Pool Cooperatives: Defending Against Erroneous IEP Split Invoices in TMS

The interoperable chassis pool model was intended to streamline equipment utilization for intermodal motor carriers. In practice, it has created one of the most complex and error-prone billing ecosystems in freight transportation. Drayage operators moving containers for major railroads routinely receive thousands of line-item invoices each month from Consolidated Chassis Management (CCM), DCLI, TRAC, and Flexi-Van. Industry data consistently shows error rates exceeding 28 percent on these invoices.

These errors translate into millions of dollars in phantom per-diem, bad-order dwell, and unauthorized split charges that flow directly to the bottom line of asset-light and private fleet drayage operations. Strong Tower Consulting helps carriers build repeatable audit and dispute workflows that integrate directly with their existing TMS platforms.

The Chaotic Billing Maze of Interoperable Chassis Pools

When a drayage driver pulls a chassis from a cooperative pool at a rail terminal, the transaction is governed by the Uniform Intermodal Interchange and Facilities Access Agreement (UIIA). The chassis pool provider bills the motor carrier for per-diem days, yet the billing responsibility often shifts between the motor carrier, the steamship line, and the beneficial cargo owner through complex split arrangements.

Daily invoice files arrive via EDI 210 or CSV from multiple pool operators. Each file can contain hundreds of records referencing the same chassis across different equipment providers. Without automated reconciliation, accounts payable teams spend days manually matching these records against gate receipts, driver logs, and GPS telemetry. The result is both financial leakage and operational distraction from core lane management activities.

Common Chassis Pool Billing Traps

Four error categories dominate chassis pool disputes for drayage carriers:

• Bad-order chassis staged in terminal maintenance tracks that continue to accrue per-diem after being reported out of service
• Incorrect on-hire dates that begin the clock before the driver actually received the unit at the gate
• Phantom days billed after the chassis has been returned and gate-out confirmed via TIR records
• Unauthorized pool split charges where the IEP attempts to rebill the motor carrier for equipment responsibility that belongs to the ocean carrier under the UIIA

These issues are particularly acute when operating across multiple chassis pools in the same market. A single power unit may pull a CCM chassis in the morning and a TRAC unit in the afternoon, generating separate daily invoice streams that must be reconciled against the same driver settlement and fuel surcharge records.

Engineering Automated Chassis Invoice Reconciliation in TMS

Modern drayage technology stacks running Truckmate, McLeod, or TMW can ingest chassis pool EDI 210 files and CSV billing extracts through native import routines or custom SQL staging tables. The reconciliation engine performs a three-way match against:

1. Terminal Interchange Receipts (TIR) captured at gate-in and gate-out
2. GPS dwell telemetry from the tractor or chassis-mounted units
3. Driver logs and pre-trip/post-trip DVIR records stored in the TMS

When discrepancies are detected, the system flags the invoice line item and automatically assembles a dispute package. SQL queries that join the EDI 214 status messages, fuel surcharge tables, and driver settlement records provide the necessary audit trail. This automation reduces manual review time by more than 80 percent while increasing dispute accuracy.

Overturning Erroneous Invoices Through UIIA Section E Arbitration

The UIIA provides a structured arbitration path under Section E for chassis billing disputes. Successful motor carriers treat this process as a repeatable operational discipline rather than an occasional administrative task. The key is maintaining timestamped evidence at the point of interchange.

Gate photos taken with mobile applications, electronic DVIRs with precise timestamps, and GPS breadcrumb data have proven decisive in arbitration. Carriers that batch-file disputes weekly through their TMS recover an average of $18,000 to $47,000 per month in misbilled chassis fees, depending on fleet size and geographic density.

Independent Advisory Perspective

Strong Tower Consulting, LLC maintains strict separation from any TMS, ELD, or chassis management software vendor. Our role is to design technology-agnostic reconciliation architectures that work inside your current Truckmate, McLeod, or TMW environment. Exspeedite LLC, our sister company under common ownership, can provide optional implementation support when carriers elect to build these capabilities internally.

Whether you operate 15 power units or 250, the discipline of daily chassis invoice auditing delivers measurable margin protection in an environment where fuel surcharges, detention, and accessorial recovery remain under constant pressure.

Frequently Asked Questions

How do I identify unauthorized split charges from an IEP in my TMS?

Compare the equipment provider listed on the original EDI 204 load tender against the billing party on the chassis invoice. When the IEP attempts to rebill for equipment responsibility assigned to the ocean carrier under the UIIA, the dispute package should reference the specific contract of carriage and booking number. Most TMS platforms can be configured to flag these mismatches automatically during the 210 import process.

What evidence is most effective when disputing bad-order chassis dwell days?

Timestamped pre-trip DVIR records combined with terminal gate photographs showing the out-of-service tag remain the gold standard. When possible, include GPS telemetry proving the chassis remained in the maintenance area after the defect was reported. Arbitration panels consistently accept this combination of driver-generated and system-generated records.

Can chassis pool reconciliation be fully automated inside McLeod or Truckmate?

Yes. Both platforms support custom SQL staging tables and EDI 210 import routines that allow automated three-way matching against TIR records and GPS data. The key is building exception workflows that route only disputed items to the accounts payable team while automatically approving clean matches. Strong Tower has helped multiple drayage carriers implement these engines without replacing their core TMS.