# Detention charge disputes before a TMS change | SourceX

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

Before a TMS replacement, inventory the three records that explain each detention dispute: the arrival timestamp (gate check-in or ELD event), the appointment email that set the booked slot, and the invoice as finally accepted. Note which system holds each, how many years exist, who owns them and the date old-system access ends. Then introduce the executive who can authorize a data discussion; whether the records can be licensed depends on rights and qualification.

## What does a detention charge dispute involve?

Detention is the charge a carrier bills when its truck waits at a shipper or receiver beyond the free time in the rate agreement. A dispute starts when the payer, usually a freight broker or shipper, thinks the clock started too early, ran too long or should not have run at all. The DOT Inspector General found there is [no reliable industrywide detention data](https://www.oig.dot.gov/library-item/36237), partly because most stakeholders only track time beyond contract limits, often 2 hours. That gap is why a company's own dispute history is unusual: it records the clock, the argument and the settled amount load by load.

The same report estimated that a 15-minute increase in average dwell time raises the expected crash rate by 6.2 percent, and FMCSA is running a [follow-up study](https://www.fmcsa.dot.gov/research-and-analysis/research/impact-driver-detention-times-safety-and-operations-phase-ii) using electronic logging device data. Detention is not a minor billing line, and its safety cost is why regulators study it. For how detention fits among other accessorial checks, see [freight audit exceptions](/data-types/freight-audit-exceptions).

## What should be inventoried before TMS replacement affects detention charge disputes history?

Inventory record classes, time coverage, system owners and the real access deadline, at metadata level only. A transportation software consultant on the replacement project is often the first to know which history will not migrate, because most cutovers move open loads and master data, not years of settled carrier pay.

Questions for the inventory, answered by the company's own team:

- [ ] **Record classes:** stop events, appointment records, carrier invoices (original and revised), dispute threads, approval logs, rate agreements with detention terms.
- [ ] **Time coverage:** how many years of settled loads sit in the old TMS, and how many years of the dispute mailbox survive.
- [ ] **Volume:** roughly how many loads a year carried a detention line, and roughly how many were disputed.
- [ ] **System owners:** who administers the TMS, the mailboxes and AP, and who signs off on decommissioning.
- [ ] **Access deadline:** the date the old TMS license, hosting or read-only access ends, taken from the contract rather than the project plan.
- [ ] **Migration scope:** whether closed loads, revised pay lines and attachments are in scope for the new system.

What a partner does not do: collect exports, screenshots or logins, or advise the company to retain data beyond its own policy or authority. If the company is mid-sale, retention decisions may also sit with the deal team; the guide to [earnouts](/questions/what-is-an-earnout) explains why post-closing records matter to both sides. The same inventory logic applies to back-office systems in [an ERP replacement](/guides/an-erp-replacement).

## Which detention records survive the cutover, and which do not?

Run each record class through the same three-way test. Is it in the new system's migration scope? If not, will the company export it, under its own decision, before old-system access ends? If neither, it is lost at cutover. The table shows how the answers often fall; it is Illustrative, and the company's project plan decides the real ones.

| Record class | Typical migration scope | If out of scope | Question for the project team |
|---|---|---|---|
| Open loads, customers, carriers, rates | In scope | Not applicable | None for this inventory |
| Settled loads with stop events | Often out of scope beyond a cutoff year | Archive or report export, if the company chooses | What is the cutoff, and what happens to older loads? |
| Revised carrier pay lines | Often only the final amount moves | Original line and revision history may be lost | Does the original billed amount survive, or only the paid one? |
| Load attachments (invoices, proofs of delivery) | Varies | Document store export | Are attachments in scope, and in what format? |
| Appointment and dispute emails | Not a TMS record | Mailbox retention applies | Whose mailboxes, and how far back? |
| Rate agreements with detention terms | Current ones only | Contract files | Are superseded agreements kept? |

Mailboxes deserve their own line because the appointment email is often the key fact in a dispute. Microsoft notes that classic Outlook exports a mailbox to a .pst file one account at a time, and that in Cached Exchange Mode only cached items, by default the past 12 months, are exported. If someone assumes a quick export captured the full dispute history, the inventory should say whether that was checked. On the TMS side, some vendors publish APIs to their database, as [McLeod does](/systems/mcleod-software-data-export); whether that reaches settled history is a question for the company's administrator, not a claim to make on their behalf.

## Does the company qualify?

The introduced company needs 50+ full-time employees at peak (contractors excluded; owner-operators under contract do not count), 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.

Unknown until SourceX reviews it with the company: how carrier and customer agreements affect rights in shared records, what must be de-identified, whether there is dataset demand, and any offer. Partners sign the Channel Partner Agreement before submitting, and the first valid introduction within the 90-day window is credited when the company submits a verified application. The [logistics exceptions guide](/guides/how-to-identify-logistics-exceptions-and-their-documented-resolutions) and the [industries hub](/industries) cover related record types.

## Go deeper on detention charge disputes

- [Detention charge disputes referral brief template](/resources/detention-charge-disputes-referral-brief-template): a fill-in template for the introduction note.
- [Detention charge disputes exception examples](/guides/detention-charge-disputes-exception-examples): worked disputes, such as a carrier that arrives before the booked slot, record by record.
- [Detention charge disputes records across systems](/guides/detention-charge-disputes-records-across-systems): a map of the keys joining TMS, mailbox and AP records.
- [Who can license detention charge disputes records](/questions/who-can-license-detention-charge-disputes-records): a short answer on which decision-maker to introduce.

## 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 a client's TMS cutover date is set and years of settled detention disputes will not migrate, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you send the handoff.

## Sources

- https://www.oig.dot.gov/library-item/36237
- https://www.fmcsa.dot.gov/research-and-analysis/research/impact-driver-detention-times-safety-and-operations-phase-ii
- https://support.microsoft.com/en-us/outlook/export-emails-contacts-and-calendar-items-to-outlook-using-a-pst-file
- https://innovationhub.mcleodsoftware.com/apis
- https://refer.sourcex.si/terms
