# Detention dispute records: a system map | SourceX

Canonical: https://refer.sourcex.si/guides/detention-charge-disputes-records-across-systems
Last updated: 2026-11-04

To reconstruct a detention dispute across systems you need four keys to line up: the load number, the carrier identifier, the appointment time and the invoice number. The TMS holds the load, the stop times and the carrier pay lines; Outlook holds the appointment confirmation and the argument; AP holds the invoice image and the payment. The case can be rebuilt only where each system recorded the same identifier at the time. The mailbox join is the most fragile, and it carries the reasoning.

This system map is part of the [detention charge disputes guide](/guides/workflow-detention-charge-disputes). The hub covers what to inventory before a TMS replacement, and the [worked hard case](/guides/detention-charge-disputes-exception-examples) follows one early arrival decision by decision. This page answers a different question: which system holds each piece, and what holds the pieces together.

## Five places one detention claim is recorded

A mid-sized broker usually spreads one detention claim across five places. The table is the map: one row per system, the record it holds, the key it can share and the team that administers it.

| System | Record it holds | Linking key it shares | Usual owner |
|---|---|---|---|
| TMS stop records | Appointment field, arrival and departure events, stop status | Load or order number, stop sequence | TMS administrator, operations |
| ELD or tracking feed | Location pings and duty status changes, if shared through an integration | Load number in the tracking request, truck or trailer number | Carrier, shared to the broker by integration |
| Outlook mailboxes | Appointment confirmations, reschedules, dispute threads | Load number in the subject line, carrier email domain | Individual staff unless a shared mailbox is used |
| TMS carrier pay and AP | Carrier invoice image, original and revised pay lines, approval, payment | Load number, carrier invoice number, carrier ID | Controller or AP manager |
| Rate confirmations | Detention terms: free time, hourly rate, when the clock starts | Load number, carrier ID | Carrier sales or operations |

The TMS is the spine because the load number is its primary key on every stop and pay line. Which tables, fields and revision histories a given TMS can hand over differs by product and by how the company configured it, so that answer comes from the company's administrator, never from a partner's assumption.

## The linking keys, and how reliable each one is

Each join works only if both sides recorded the same value. The reliability column is where the history usually gets thin.

| Key | TMS side | Other side | Join quality | What to ask |
|---|---|---|---|---|
| Load number | Primary key on every stop and pay line | Email subject or body; invoice reference | Good in AP, fair in email | Were staff required to put the load number in the subject? |
| Carrier identifier | Carrier record with MC or SCAC code | Sender domain in email; remit-to on the invoice | Fair | Do dispatch and accounting share one carrier record? |
| Appointment time | Stop appointment field, if dispatch entered it | The confirmation email itself | Good when both exist | Is a reschedule logged in the TMS or only in email? |
| Arrival and departure | Stop events from check calls, tracking or ELD | Driver or carrier emails | Good | Which source wins when feeds disagree? |
| Invoice number | Carrier pay line reference | Invoice PDF in the AP inbox | Good if revisions kept | Does a revised invoice overwrite the original line? |
| Approver | User ID on the approval | Reply in the dispute thread | Fair | Was approval given in the TMS or by email? |

Arrival and departure stamps are the strongest keys when they come from devices rather than typed check calls. The catch is ownership: the duty log belongs to the carrier, so the broker usually keeps only the times its tracking integration captured, and those are what the map should count. The appointment time is weaker than it looks: a receiver's reschedule often reaches the broker by email and never updates the TMS appointment field, so the two sides disagree about the slot unless someone reconciles them.

## One fully joined claim (Illustrative)

A fictional 340-person temperature-controlled freight broker pays detention at a shipper whose loading slot was moved the night before. Every identifier is invented to show the shape of a joined case.

| Step | System | Record | Key carried forward |
|---|---|---|---|
| 1 | TMS stop records | Load 58213, pickup stop: appointment June 12, 13:00 | Load 58213 |
| 2 | Outlook shared mailbox | Shipper reschedules to 15:00 on the evening of June 11; account manager forwards to carrier, subject "58213 new pickup 15:00" | Load 58213, carrier domain |
| 3 | ELD or tracking feed | Truck arrives 12:50, departs 18:40 | Load 58213, truck number |
| 4 | TMS carrier pay | Carrier invoice 7714: 3 hours 40 minutes detention billed from 13:00 | Load 58213, invoice 7714, MC number |
| 5 | Outlook shared mailbox | Dispute: free time runs from 15:00 per the forwarded reschedule | Load 58213 in the subject |
| 6 | TMS carrier pay | Revised invoice 7714-A approved: 1 hour 40 minutes; original line kept | Invoice 7714, approver user ID |
| 7 | Rate confirmations | Load 58213 confirmation: 2 hours free from the "scheduled appointment" | Load 58213 |

The load number runs through every step, so the claim rebuilds cleanly. Step 2 is the hinge: the reschedule lives only in email. If the account manager had phoned the carrier instead, the TMS would show a 13:00 appointment, the carrier would look right, and the approved revision in step 6 would look like the broker short-paying without a reason.

## Where the joins break before anyone exports anything

Most brokers have strong TMS keys and weaker ones everywhere else. Naming the breaks lets the company describe its history accurately.

- **Email in personal mailboxes.** Appointment changes and dispute threads in staff members' own mailboxes leave with the person. Microsoft documents that when an Exchange Online license is removed, mailbox data has a default 30-day grace period, extendable by a further 30 days with Delicensing Resiliency, after which it is deleted. Microsoft also documents the usual fix: a departing user's mailbox under 50 GB can be converted to a shared mailbox and its license removed, provided the user account is kept as an anchor. Whether that was done for past dispute staff is a question for IT. The guide to [shared mailbox retention](/guides/shared-mailbox-retention) covers the policy side.
- **Subject lines without the load number.** A thread titled "Re: Thursday pickup" can only be matched by carrier domain and date, which works for a handful of claims and fails across thousands.
- **Overwritten pay lines.** If the TMS replaces the billed amount with the paid amount, the dispute disappears from the ledger.
- **Tracking data held by the carrier.** The broker may hold only what the integration shared. The page on [telematics data monetization](/questions/telematics-data-monetization) covers who owns device data.
- **Dispatch tools outside the TMS.** Where loads are tendered through a separate tool, the appointment may live there; see [AI dispatching](/guides/ai-dispatching).

## Questions to map coverage with the operations director

The operations director can usually answer these from memory or a TMS report, without opening a load:

1. Which systems hold appointments, arrival times, carrier pay revisions and dispute email, and since which year?
2. Do dispute emails cite the load number in the subject, and do they sit in a shared mailbox?
3. Are reschedules logged in the TMS, or only in email?
4. Does a revised carrier invoice create a new line or overwrite the original?
5. Roughly how many loads a year carry a detention line, and roughly how many are disputed?
6. Who administers the TMS, the mail system and AP?

The answers feed the [detention referral brief template](/resources/detention-charge-disputes-referral-brief-template). The introduced company needs 50+ full-time employees at peak (contractors excluded), 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 70% of the data is in English. Partners sign the Channel Partner Agreement before submitting introductions and never handle loads, emails or exports. Whether the joined records can be licensed after carrier and shipper terms are checked, and whether any buyer wants them, stays unknown until SourceX reviews it with the company's authorized contact.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the operations director confirms that the load number reaches the dispute emails and revised pay lines are kept, [register as a partner](/register), check the broker on [who qualifies](/who-qualifies) and read the [program terms](/terms) before making the introduction.

## Sources

- https://learn.microsoft.com/en-us/exchange/recipients-in-exchange-online/manage-user-mailboxes/exchange-online-delicensing-resiliency
- https://learn.microsoft.com/en-us/microsoft-365/admin/email/convert-user-mailbox-to-shared-mailbox?view=o365-worldwide
- https://refer.sourcex.si/terms
