Intermodal Drayage Chassis Pools: Automated Interchange Billing & Dispute Solvers

The Persistent Reconciliation Gap in Intermodal Drayage

Motor carriers engaged in intermodal drayage face daily friction when reconciling chassis pool usage invoices against actual terminal interchange records. Chassis pool operators - including DCLI, TRAC, and Flexi-Van - generate high-volume daily per-diem invoices under the Uniform Intermodal Interchange and Facilities Access Agreement (UIIA). These invoices frequently contain discrepancies that require labor-intensive manual review.

The core problem stems from the asynchronous nature of data flows between three primary parties: the motor carrier, the chassis pool provider, and the marine or rail terminal operator. Gate transactions recorded at the terminal (typically via optical character recognition or RFID) often fail to synchronize in real time with the chassis pool's billing systems. As a result, carriers are routinely billed for equipment they no longer control.

Prevalent Billing Errors in Chassis Pool Invoicing

Four categories of billing errors dominate intermodal drayage operations:

1. Post-Gate-In Per-Diem Continuation: Chassis pool operators continue assessing daily per-diem charges after the equipment has been gated into a marine terminal, even though the motor carrier's responsibility has ended.
2. Incorrect Equipment Interchange Receipts (TIR / EDI 422): Mismatched or missing EDI 422 transaction sets result in incorrect start and stop dates for per-diem calculations.
3. Uncredited Bad-Order Out-of-Service Time: Mechanically defective chassis that are placed out-of-service at the terminal are often not credited for the days they were unavailable, despite explicit UIIA provisions requiring such credits.
4. Mismatching Ocean Carrier Split-Billing Terms: Complex contractual splits between ocean carriers and chassis pools are frequently misinterpreted, leading to incorrect allocation of per-diem responsibility to the motor carrier.

These errors compound rapidly at scale. A mid-sized intermodal drayage carrier moving 250 containers per day can easily accumulate thousands of line items monthly across multiple chassis providers and terminal locations.

Technical Architecture of Automated Chassis Billing Reconciliation

Modern intermodal TMS platforms address these challenges through structured automation layers. The solution begins with standardized data ingestion pipelines that consume multiple source formats:

• EDI 422 transaction sets from chassis pool operators
• IANA UIIA daily invoice files (typically CSV or XML)
• Terminal gate transaction logs (TIRs) delivered via API, SFTP, or VAN
• Internal TMS move records containing appointment, dispatch, and status timestamps

A robust reconciliation engine maintains a normalized database schema that captures the complete lifecycle of each chassis instance. Key tables include:

chassis_interchange_events (
    event_id UUID PRIMARY KEY,
    chassis_number VARCHAR(11) NOT NULL,
    pool_operator VARCHAR(20) NOT NULL, -- DCLI, TRAC, FLEXIVAN
    event_type ENUM('GATE_OUT', 'GATE_IN', 'BAD_ORDER', 'REPAIR_COMPLETE'),
    event_timestamp TIMESTAMPTZ NOT NULL,
    terminal_location VARCHAR(20),
    tir_document_id VARCHAR(50),
    edi_422_reference VARCHAR(50),
    per_diem_start_date DATE,
    per_diem_end_date DATE,
    dispute_status ENUM('OPEN', 'SUBMITTED', 'RESOLVED', 'REJECTED')
);

This schema supports temporal joins between terminal gate events and invoice line items. The matching logic uses a deterministic windowing algorithm that aligns timestamps within a configurable tolerance (typically +/- 4 hours) while respecting business rules for weekend and holiday per-diem exceptions.

Automated Dispute Package Generation and Credit Recovery

Once discrepancies are identified, the TMS generates structured dispute packages containing:

• Chassis number and pool operator reference
• Disputed per-diem days with exact dollar amounts
• Timestamped terminal interchange records (TIRs)
• Corresponding EDI 422 transaction excerpts
• Bad-order documentation when applicable (photos, mechanic sign-off, terminal rejection codes)
• UIIA clause citations supporting the dispute

These packages are transmitted to chassis pool operators through preferred channels - most commonly EDI 214 or web portal file upload. The system tracks dispute status through a state machine that automatically follows up on aging disputes according to carrier-specific escalation rules.

Integration with accounting systems ensures that approved credits are automatically applied against future invoices, maintaining clean accounts payable ledgers. This closed-loop process eliminates the spreadsheet-based reconciliation that has historically consumed significant administrative resources in intermodal drayage operations.

Integration Best Practices with Enterprise TMS and Accounting Systems

Successful chassis billing automation requires tight integration across several practice areas. Strong Tower Consulting recommends the following technical approach:

• Real-time or near-real-time ingestion of terminal gate events through API connectors or scheduled EDI 214/322 processing.
• Event-driven architecture using message queues to trigger reconciliation immediately upon receipt of new gate or invoice data.
• Master data management layer that maintains accurate mappings between chassis pool equipment numbers, ocean carrier contracts, and customer billing entities.
• Exception workflow engine that routes complex disputes (those exceeding dollar or day thresholds) to human analysts with complete supporting context.

These capabilities align directly with broader TMS implementation and transportation accounting integration strategies. Carriers should evaluate their current systems against these requirements when planning technology roadmaps.

Regulatory and Standards Compliance Considerations

All automated reconciliation logic must remain strictly compliant with the UIIA, which remains the governing document for equipment interchange. The IANA maintains interpretive guidance on acceptable evidence for disputes, particularly regarding bad-order chassis and terminal gate timestamps.

Carriers should maintain audit-ready records of all dispute submissions and resolutions. This includes preserving original source documents with cryptographic timestamps where possible. Integration with ELD and EDI systems further strengthens the compliance posture by creating an unbroken chain of custody from driver activity through terminal interchange to final billing resolution.

Implementation Roadmap for Intermodal Drayage Carriers

Organizations seeking to implement automated chassis pool interchange billing and dispute resolution should follow a phased approach:

1. Current-state assessment of existing manual reconciliation processes and error rates.
2. Gap analysis against target data sources (terminal APIs, EDI 422 feeds, UIIA contract terms).
3. Selection or enhancement of TMS capabilities for automated matching and dispute generation.
4. Integration with accounting platforms to automate credit application and reporting.
5. Establishment of key performance indicators around dispute recovery rates and administrative time savings.

Strong Tower Consulting works with motor carriers and 3PLs to execute these implementations through disciplined project governance and deep domain expertise in both intermodal drayage operations and enterprise system architecture.