How to dispute chassis invoices.

Understanding chassis pool billing mechanics and interchange events

Chassis pool billing can quickly erode operating margins if invoices go unchecked. Across North American intermodal transport, equipment providers such as DCLI, TRAC Intermodal, Flexi-Van, and regional cooperative pools supply the chassis that move ocean and domestic containers. Whether your fleet operates out of marine terminals, rail ramps, or off-dock depots, billing runs on a standard mechanism: daily rental fees tied directly to gate interchange events.

The billing cycle begins when a driver out-gates a chassis. The facility records the move and issues an Equipment Interchange Receipt (EIR) or gate slip capturing the equipment number, carrier Standard Carrier Alpha Code (SCAC), date, and timestamp. That out-gate event signals to the pool provider that your company has assumed custody and financial responsibility.

Billing accrues daily until the chassis is formally in-gated back into an approved facility. While straightforward in concept, pools process millions of transactions monthly across hundreds of facilities using optical cameras, barcode scanners, and manual entries. When that tracking chain fails, billing engines default to charging the motor carrier. Daily rates and billing rules vary across providers and pools, so carriers should check the current rule in their equipment contract and pool tariff schedule.

Chassis statements can arrive weeks after return. Without systematic verification against gate slips, GPS logs, and dispatch manifests, carriers pay for equipment usage they never incurred.

The most common billing errors on chassis invoices

Chassis statements frequently contain clerical and systemic errors. Automated billing engines rely on terminal gate feeds where missed scans or keypunch mistakes create invalid line items:

• Days billed after return: The most frequent drayage error. A driver returns an empty chassis, but the facility fails to record the in-gate scan. The pool continues billing your account until the chassis is scanned again or pulled by another carrier.
• Chassis billed to the wrong account or SCAC: Clerks can mistype a SCAC at the kiosk, or cameras misread cab lettering, billing your account for moves made by an unrelated carrier. Lingering booking references from prior moves can also attach historical rental days to your invoice.
• Overlapping days and duplicate line items: System glitches or re-bills can create two separate line items covering the same chassis on identical dates, doubling your daily equipment expense.
• Chassis never in your possession: Transposed digits during gate recording generate phantom billings. If a clerk enters an incorrect serial number, the pool bills your SCAC for equipment your drivers never moved.
• Weekend and holiday counting discrepancies: Pool contracts differ on whether non-working days accrue charges. Some agreements exclude weekends and holidays under specific ocean carrier programs, while others charge for every calendar day.
• Missing drop-off records for bare chassis returns: Off-dock drop lots often process bare returns slower than main gates. A chassis dropped Friday may sit unrecorded until Monday, adding unearned billing days to your statement.

Building a line-by-line invoice verification checklist

Challenging incorrect charges requires verifiable operating records. Equipment pools handle heavy dispute volumes and reject unsubstantiated claims. A structured audit workflow ensures every disputed line item is supported by concrete documentation.

The cornerstone of invoice auditing is the Equipment Interchange Receipt. Every time a driver enters or leaves a facility, an electronic or paper EIR is generated. Paper slips left in cabs are easily lost, so drivers should capture clear digital photos at the gate using a mobile web app. Drivers should also photograph chassis and container numbers to provide visual proof if a pool claims equipment was returned to the wrong yard.

Your audit checklist should cross-reference each invoice line against five core operational fields:

• Equipment identifier: Confirm the chassis prefix and serial number match your dispatch manifest.
• Start date and timestamp: Verify that the billed out-gate aligns with the pickup time on your driver gate slip.
• End date and timestamp: Ensure the billed termination date matches your return receipt rather than a delayed scan days later.
• Location codes: Verify that the billed facilities match the actual yards your driver visited.
• Vehicle tracking confirmation: Match gate timestamps against GPS geofence breadcrumbs. A GPS record showing your tractor entering a yard and departing bobtail proves the chassis was left on site at that specific time.

If any field fails to match your operating records, flag the line item for dispute immediately. Always check the dispute window defined in your pool agreement, as late claims are routinely denied.

Worked example: auditing and disputing an incorrect chassis statement

The following scenario is a completely made-up illustration using invented, round numbers to show how a carrier calculates overcharges, gathers proof, and structures a financial dispute.

An independent carrier receives a weekly statement from a hypothetical chassis pool provider covering five equipment units. The contract establishes an illustrative daily usage fee of $30.00 CAD per calendar day.

During the audit, dispatch identifies irregular charges on chassis unit ABCZ-100200 and an unfamiliar unit. According to the pool invoice:

• ABCZ-100200 was billed from Monday, October 5 through Thursday, October 15, totaling 11 billable days ($330.00 CAD).
• ABCZ-100200 had a duplicate line item for October 7 through October 8, totaling 2 billable days ($60.00 CAD).
• Unit ABCZ-999888 was billed for 3 days between October 10 and October 12, totaling 3 billable days ($90.00 CAD) against the carrier SCAC.
• Total invoice amount under review: $480.00 CAD.

The dispatcher audits these charges against operating logs:

• For ABCZ-100200, the manifest confirms the driver pulled the chassis on Monday, October 5 at 08:30 from a terminal for an import delivery.
• The driver returned the bare chassis to a designated rail yard depot on Thursday, October 8 at 16:00.
• The driver obtained an in-gate EIR stamped October 8 at 16:02 and uploaded a photo to the driver web app.
• Fleet GPS confirms the truck entered the rail terminal geofence at 15:45 on October 8 and exited bobtail at 16:15.
• The true custody period was 4 calendar days (October 5, 6, 7, and 8). The correct charge is 4 days at $30.00 CAD, equaling $120.00 CAD.
• The pool recorded the in-gate scan on October 15, creating 7 excess days billed after return ($210.00 CAD overcharge).
• The duplicate line for October 7 and 8 represents an erroneous double charge of $60.00 CAD already covered under the primary movement.
• For ABCZ-999888, dispatch has zero record of the unit. Manifests, GPS logs, and appointment records confirm the carrier never moved this equipment. The $90.00 CAD charge represents an incorrect SCAC assignment.

Summary of the dispute calculation:

• Total billed by pool: $480.00 CAD.
• Legitimate carrier liability: $120.00 CAD (4 days on ABCZ-100200).
• Total overcharge to be credited: $360.00 CAD ($210.00 for days after return, $60.00 for duplicate billing, and $90.00 for the incorrect chassis).

Supported by gate receipts and GPS breadcrumbs, the carrier submits a formal dispute claim requesting a credit of $360.00 CAD.

Drafting an effective dispute submission packet

Submitting an effective dispute requires an organized, self-contained packet. Pool billing departments handle vast transaction volumes, and claims submitted without clear documentation face rejection or lengthy delays.

Begin with a concise cover letter or summary containing your basic business details:

• Carrier legal name and SCAC.
• Pool account number.
• Invoice number and invoice date.
• Total billed amount, total disputed value, and undisputed balance being remitted.
• An itemized list summarizing disputed chassis numbers, specific reason codes, and requested adjustments.

Attach primary source records for each disputed unit in chronological order:

• Out-gate interchange receipt: Proves when carrier custody and billing began.
• In-gate interchange receipt: Proves the date, timestamp, and location where the chassis was returned.
• Driver mobile app photos: Visual verification of gate slips, chassis numbers, or equipment staged in return lanes.
• GPS geofence breadcrumbs: Satellite tracking records showing yard entry, dwell time, and bobtail departure.
• Dispatch manifest: Operating schedules showing that an unfamiliar unit was never assigned to your fleet.

Many providers take disputes through a web portal or a template with reason codes such as incorrect termination date, duplicate billing or invalid interchange. Ask your provider how it wants them submitted.

Maintain permanent records of every submission, including copies of dispute letters, original invoices, documentation packets, and pool confirmations. Track claims systematically to ensure credit memos appear on future statements.

Frequently asked questions

How long do motor carriers have to dispute an incorrect chassis pool charge?

Dispute windows vary by pool provider and contract terms. Some agreements require dispute submissions within a few weeks of the invoice date, while others allow a longer timeframe under standard rules. Missing this deadline forfeits your right to contest the charge, so check the current rule in your pool agreement or tariff schedule and audit incoming statements promptly.

What should a carrier do if a marine terminal or rail ramp fails to issue an equipment interchange receipt?

If a gate kiosk or clerk fails to print a slip, the driver should photograph the gate exit screen showing transaction approval. Dispatch should log the gate time and preserve tractor GPS breadcrumbs showing entry, dwell time, and bobtail departure. These location records and dispatch manifests provide credible secondary evidence if the pool fails to record the return.

Can a chassis pool bill a motor carrier if the chassis was returned bare rather than mounted?

Yes, daily rental fees apply to the chassis asset itself, whether mounted or bare. Billing errors occur frequently on bare returns because off-dock depots often experience delays entering bare equipment into inventory systems. Drivers must always obtain an explicit bare-chassis in-gate receipt to prove the unit has officially cleared company custody.

Why do chassis invoices show duplicate days for the same chassis unit?

Duplicate line items usually happen when billing engines process two electronic records for the same movement. This occurs when a gate event is manually edited after an automated scan or when ocean carrier data conflicts with direct pool feeds. When an audit reveals overlapping dates, dispute the redundant line item using the master interchange receipt.

Does an ocean carrier's merchant haulage agreement cover chassis pool charges?

Under merchant haulage, the motor carrier or cargo owner is responsible for securing and paying for the chassis directly with the pool. In carrier haulage moves, the ocean carrier may provide or absorb the chassis under their bill of lading, but terms vary by line and facility. Review the booking confirmation and pool agreement to confirm whether charges belong to the shipping line or the trucker.

Where Dispatch Board fits

Dispatch Board's chassis bill checker takes DCLI, TRAC and Flexi-Van invoices and checks each line against when your loads actually had the chassis, then produces a dispute letter and a CSV. The driver app puts photos, signed PODs and documents on the load, even when a terminal has no signal, and the waiting-time audit keeps GPS pings in the geofence as evidence.

That means the records you need for a dispute are already attached to the load when the invoice arrives. Try it free for 14 days with your own invoice.

This guide is general information from the Dispatch Board team, not legal, tax or accounting advice. Rules and rates change: confirm against the official source linked in the text before you rely on them.