Which interchange exception resolution records help a company explain how exceptions were handled?
The records that explain a resolved exception show the gap, the evidence used to close it, the decision made and the money that moved. Here is one case end to end.
Worked example: the out-gate that never posted
Illustrative. A 260-person intermodal drayage company, with employee drivers, picks up a container on a chassis at a rail ramp. The equipment provider's record shows the container available on day 1 and returned on day 10, but no out-gate event. Its invoice treats the container as out from day 1 and bills 9 days. (Days are simplified here and ignore free time.)
- The gap. The billing analyst spots the missing out-gate and opens a dispute with the provider.
- The delay decision. A dispatch email from day 2 records why pickup waited: no chassis was available at the ramp, so the dispatcher held the move.
- The handover message. On day 6 the driver replies "picked up" with the container number; the asset tracker shows the chassis leaving the ramp geofence the same morning.
- The submission. The analyst sends the provider the tracker exit time and the dispatch thread, arguing for 4 days, from day 6 to day 10.
- The outcome. The provider accepts and credits 5 of the 9 days. The credit memo is filed against the dispute.
The labeled parts are what make the case useful: an initial problem (missing event), an authorized action (dispute with stated evidence) and a checked result (credit accepted). When providers and carriers cannot settle, UIIA binding arbitration covers per diem, maintenance and repair, and equipment use charges once the dispute steps under the agreement and the provider's addendum are exhausted, and an arbitration decision adds a formal outcome label. The broader case for this kind of record is laid out in why AI agents need work data and exception handling data for AI agents.
The record map: what each record proves
Each record in the worked example answers a different question. The case is only explainable when the company holds enough of them to cover the gap, the action and the result.
| Record | Usually held by | What it proves | Common weakness |
|---|---|---|---|
| Equipment Interchange Receipt or electronic equivalent | Equipment provider, copy with carrier | That an interchange took place, and the equipment's condition | Missing when the gate event never posted |
| Provider billing timeline | Equipment provider | What the provider believes happened, and the days billed | Built from the same missing event |
| Asset tracker events | Carrier | Where the chassis actually was, and when | Geofence exits need interpretation |
| Dispatch email and driver replies | Carrier | Why the move waited, and when pickup happened | Kept in personal mailboxes |
| Dispute file and credit memo | Carrier billing team | The argument made and the accepted outcome | Outcome not linked back to the dispute |
The UIIA explains why the first row carries weight. Under UIIA Section D.2.a, the parties execute an Equipment Interchange Receipt or an electronic equivalent at interchange, and the equipment's physical condition may be described on it or captured in recorded images. When that receipt is missing or wrong, the carrier's own tracker and email records are what fill the gap, which is why they matter to an exception history even though they look routine.
Which interchange exceptions are worth asking about
The missing out-gate is one kind. When talking to an operations director, a partner can ask which of these the company has disputed and kept files for, without asking to see any:
- Missing or late gate events that inflate per diem days.
- Damage claims where the condition at interchange is in question.
- Wrong equipment numbers keyed at the gate, which attach charges to the wrong move.
- Chassis shortages that force a delay decision the provider later bills for.
- Disputes escalated under the UIIA process, where a formal decision exists.
The volume of each, the years covered and whether outcomes are recorded tell SourceX more than any single file.
Does the company qualify?
The company needs 50+ full-time employees at peak, with contractors excluded; many drayage fleets run on owner-operators, so check how owner-operators are counted first. It also needs a documented operating history, rights to license the records and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English.
What stays unknown until SourceX reviews it: SourceX's current data needs for interchange disputes, how provider and tracker-vendor contracts affect rights, how much preparation the set needs, and any offer. Sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application. Related transport workflows sit under the industries hub.
Go deeper on interchange exception resolution
- Reconstructing interchange exceptions across systems: a system map of the equipment numbers, references and timestamps that join tracker, email and billing records.
- Who can license interchange exception records: a short answer on which operations and executive roles to introduce.
- Preserving interchange history before a platform upgrade: an inventory checklist for the months before an upgrade.
- Interchange exception referral brief template: a fill-in template for the one-page introduction.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a drayage or ramp client keeps dispute files that still tie tracker events and dispatch emails to the credit that settled them, register as a partner, confirm the company against who qualifies, and read the program terms before you send the handoff.