Intermodal Drayage Chassis Billing Reconciliation: Co-Op Pool Invoices & Daily Usage Auditing
Intermodal drayage operators face one of the most complex equipment-cost reconciliation challenges in transportation. Each month, drayage carriers receive thousands of per-diem billing lines from interoperable chassis pool providers (IEP, OCEMA, and regional co-ops). These invoices routinely contain systemic errors: incorrect off-hire dates, chassis split mismatches between pool operators, duplicate daily charges, and equipment billed to the wrong motor carrier.
A purpose-built TMS chassis reconciliation engine addresses this complexity through automated daily ingestion, deterministic matching, exception flagging, dispute packet generation, and precise customer cost pass-through. This technical guide details the engineering patterns, database schemas, integration points, and operational workflows required to achieve near-real-time chassis billing accuracy.
The Financial Complexity of Intermodal Chassis Management
Interoperable chassis pools were created to reduce empty repositioning and improve equipment utilization across competing ocean carriers and motor carriers. While the operational model succeeds at the physical layer, the financial layer remains fractured. A single 20-foot container move in the Southern California basin may involve chassis supplied by three different pool participants, each sending separate per-diem invoices on different billing cycles with different rules for free days, weekend charges, and holiday adjustments.
Typical monthly invoice volumes for a mid-sized drayage fleet exceed 15,000 line items. Manual reconciliation against dispatch records, gate logs, and TIR documents becomes unsustainable. Errors compound when chassis splits are not correctly allocated across multiple loads or when the off-hire timestamp recorded by the pool does not match the actual return recorded in the TMS.
Without automation, these discrepancies create three direct financial impacts: overpayment to chassis providers, delayed or inaccurate customer pass-through billing, and material accrual errors in monthly financial statements.
TMS Chassis Reconciliation Engine Architecture
The reconciliation engine is implemented as a dedicated microservice within the broader TMS platform. It follows an event-driven architecture with the following core components:
- Daily invoice ingestion pipeline (EDI 810, CSV, or API)
- Chassis master reference database with pool participant splits
- Normalized movement and TIR event store
- Deterministic matching engine using composite business keys
- Rules engine for per-diem logic and exception classification
- Dispute document generator and EDI 812 outbound service
- Customer allocation and pass-through billing module
The system is designed to run a full daily reconciliation cycle by 6:00 AM local time, providing operations and accounting teams with validated chassis costs before daily dispatch planning begins.
Data Ingestion and Normalization
Invoice data arrives through multiple channels. The preferred method is EDI 810 Invoice transactions transmitted via AS2 or VAN. Where EDI is not available, pool operators provide daily CSV extracts through secure FTP. Each inbound file is parsed, validated against schema, and loaded into a staging schema that preserves the original source data for audit purposes.
Normalization is critical. Chassis identifiers must be standardized (removing leading zeros, standardizing prefix/suffix formats). Pool participant codes are mapped to a canonical equipment provider master. Timestamps are converted to UTC with source timezone preserved for dispute documentation.
Simultaneously, the TMS maintains a high-fidelity event store of all chassis-related movements. Terminal Interchange Reports (TIR), gate transactions, and driver mobile events are captured with chassis number, container number, load reference, and precise timestamps. This creates the source-of-truth dataset against which invoices are matched.
Chassis Split Matching and Daily Per-Diem Reconciliation
The core matching algorithm uses a composite key consisting of:
- Normalized chassis identifier
- Pool participant code
- Load or booking reference (when available)
- Gate-in or interchange timestamp within a configurable tolerance window (typically +/- 4 hours)
When a match is confirmed, the engine calculates the exact number of billable days based on the TMS-recorded on-hire and off-hire events, applying the specific free-day rules and rate tables for that pool participant and equipment type. Any variance between the billed amount and the calculated amount is flagged according to configurable tolerance thresholds.
Chassis splits present additional complexity. When a single load uses chassis from multiple providers, the system allocates per-diem responsibility based on the actual days each chassis was in the carrier's possession. This allocation is stored at the line-item level and flows directly into accounts payable and customer invoice modules.
Unmatched or discrepant lines are routed to an exception queue with supporting documentation automatically attached: copies of the TIR, gate photos if available, and calculated versus billed day counts. These exception packets are formatted for EDI 812 dispute transmission or PDF export for manual submission.
Customer Pass-Through Billing and Accounting Integration
Validated chassis costs must be accurately passed to the customer freight invoice. The reconciliation engine writes allocated cost records to a dedicated chassis_cost_allocations table. This table maintains foreign keys to the original invoice line, the matched TMS load, the customer shipment, and the general ledger account.
Integration with transportation accounting systems occurs through both real-time webhooks and nightly batch files. When Strong Tower Consulting implements these solutions, we map the validated chassis costs directly into the carrier's chart of accounts and subledger structure, ensuring accurate per-load contribution margin reporting.
This same allocation dataset powers customer invoices. Depending on contract terms, chassis costs may be billed as a separate accessorial, embedded in a fuel surcharge line, or included in a flat all-in rate. The TMS rate matrix and billing rules engine determines the correct presentation on the freight invoice.
Learn more about transportation accounting system integrationRegulatory Compliance and Audit Readiness
Accurate chassis billing directly affects fuel tax reporting, IFTA allocations, and state mileage tax calculations. Because chassis per-diem is treated as equipment rental rather than linehaul revenue in most jurisdictions, proper segregation in the general ledger is required. The reconciliation engine maintains complete audit trails from original pool invoice through matching logic to final accounting entry.
Daily reconciliation also supports Sarbanes-Oxley and SOC 2 control objectives by moving from monthly sample-based review to 100% automated validation with exception-based human review.
Implementation Best Practices for Drayage Operators
Successful deployment of an automated chassis reconciliation engine requires mature foundational data. Strong Tower Consulting recommends the following prerequisites:
- Complete digitization of all terminal gate transactions and TIR documents
- Standardized chassis numbering conventions across all dispatch systems
- Real-time or near-real-time EDI 214 and 210 processing for load status
- Centralized equipment master with pool participant relationships
- Documented per-diem rules by pool, region, and equipment type
Our TMS implementation methodology includes a dedicated 8-week chassis data quality sprint prior to activating the reconciliation engine. This ensures the matching logic operates with greater than 94% first-pass automation rates based on historical client data.
Additional relevant practices include ELD and EDI integration, business process optimization, and enterprise reporting.
Applicable Market Segments
This technical pattern is most relevant for operators in the following segments:
- Intermodal drayage specialists
- Asset-light 3PLs and freight brokerages that manage drayage subcontractors
- Regional truckload carriers with growing intermodal divisions
Conclusion: From Monthly Pain to Daily Control
The transition from monthly manual chassis invoice reconciliation to daily automated matching represents one of the highest-ROI technology investments available to intermodal drayage operators. By ingesting pool invoices daily, matching against authoritative TIR and dispatch records, systematically flagging exceptions, and automatically allocating validated costs, carriers eliminate overpayments, accelerate cash flow through accurate customer billing, and produce auditable financial records.
Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership (separate EINs; liability firewall). Scott Elliott is founder and transportation systems architect of both organizations. For more than 18 years we have helped motor carriers and freight brokerages replace manual reconciliation processes with engineered, auditable systems.
Ready to eliminate chassis billing leakage and automate your intermodal cost reconciliation?
Start a Systems Assessment Speak with Scott Elliott at 763-244-1373