Detention charge disputes across TMS, Outlook and AP: a system map of records and linking keys

Short answer

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.

Visual briefFull-size diagram
Five system nodes in a row, TMS stops, ELD feed, Outlook, carrier pay and rate confirmations, with linking keys (load number, truck number, load number in the email subject, invoice number, MC number) traveling into one rebuilt detention claim; the Outlook link is highlighted as the weakest join.
Illustrative: the keys that join one fictional detention claim. The mailbox link breaks most often.

This system map is part of the detention charge disputes guide. The hub covers what to inventory before a TMS replacement, and the worked hard case 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.

SystemRecord it holdsLinking key it sharesUsual owner
TMS stop recordsAppointment field, arrival and departure events, stop statusLoad or order number, stop sequenceTMS administrator, operations
ELD or tracking feedLocation pings and duty status changes, if shared through an integrationLoad number in the tracking request, truck or trailer numberCarrier, shared to the broker by integration
Outlook mailboxesAppointment confirmations, reschedules, dispute threadsLoad number in the subject line, carrier email domainIndividual staff unless a shared mailbox is used
TMS carrier pay and APCarrier invoice image, original and revised pay lines, approval, paymentLoad number, carrier invoice number, carrier IDController or AP manager
Rate confirmationsDetention terms: free time, hourly rate, when the clock startsLoad number, carrier IDCarrier 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.

KeyTMS sideOther sideJoin qualityWhat to ask
Load numberPrimary key on every stop and pay lineEmail subject or body; invoice referenceGood in AP, fair in emailWere staff required to put the load number in the subject?
Carrier identifierCarrier record with MC or SCAC codeSender domain in email; remit-to on the invoiceFairDo dispatch and accounting share one carrier record?
Appointment timeStop appointment field, if dispatch entered itThe confirmation email itselfGood when both existIs a reschedule logged in the TMS or only in email?
Arrival and departureStop events from check calls, tracking or ELDDriver or carrier emailsGoodWhich source wins when feeds disagree?
Invoice numberCarrier pay line referenceInvoice PDF in the AP inboxGood if revisions keptDoes a revised invoice overwrite the original line?
ApproverUser ID on the approvalReply in the dispute threadFairWas 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.

StepSystemRecordKey carried forward
1TMS stop recordsLoad 58213, pickup stop: appointment June 12, 13:00Load 58213
2Outlook shared mailboxShipper 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
3ELD or tracking feedTruck arrives 12:50, departs 18:40Load 58213, truck number
4TMS carrier payCarrier invoice 7714: 3 hours 40 minutes detention billed from 13:00Load 58213, invoice 7714, MC number
5Outlook shared mailboxDispute: free time runs from 15:00 per the forwarded rescheduleLoad 58213 in the subject
6TMS carrier payRevised invoice 7714-A approved: 1 hour 40 minutes; original line keptInvoice 7714, approver user ID
7Rate confirmationsLoad 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 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 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.

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. 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, check the broker on who qualifies and read the program terms before making the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can the ELD feed replace the TMS arrival time?

It can corroborate it, but the ELD record belongs to the carrier's driver and system, and the broker usually holds only what was shared through a tracking integration. Note which source the TMS stop event came from rather than assuming.

What if the load number never appears in the emails?

Then the email join falls back to carrier domain plus date, which works for a few cases and fails at volume. Record that as a gap; a history with clean TMS keys and loose email is still worth describing accurately.

Sources

  1. learn.microsoft.com/en-us/exchange/recipients-in-exchange-online…
  2. learn.microsoft.com/en-us/microsoft-365/admin/email/convert-user…
  3. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment