Detention charge disputes, a worked hard case: when a carrier arrives before the booked slot

Short answer

Three records explain most detention exceptions: the arrival timestamp, the appointment email that set the booked slot, and the invoice as finally accepted. In the hard case below, which is Illustrative, a carrier arrives 80 minutes early and bills detention from arrival; the broker disputes from the appointment time and settles at $75 instead of $155. Each decision left a record in a named system. That sequence is what makes a dispute history useful evidence, and it is what a partner should listen for at a client.

Visual briefFull-size diagram
A case timeline for one load that branches at the early arrival: the carrier's path counts from 06:40 and bills $155, the broker's path counts from the 08:00 appointment and settles at $75, with each decision's record appearing in sequence.
Illustrative case: a fictional 260-person freight broker, two hours of free time and $60 per hour after it.

This worked case is part of the detention charge disputes guide, which covers what to inventory before a TMS replacement. Here the job is narrower: follow one exception from the first email to the approved payment, and name who made each call.

The case at a glance (Illustrative)

A fictional 260-person freight broker books a dry van load into a receiver's distribution center. The rate confirmation gives the carrier two hours of free time and $60 per hour of detention after that. It does not say in writing whether free time starts at arrival or at the appointment, which is the gap the whole dispute turns on.

  • Booked slot: dock 4, Tuesday 08:00, confirmed by email on Monday afternoon.
  • What happened: the truck checked in at the gate at 06:40, loading started at 08:20 and the truck left at 11:15.
  • The carrier's view: 4 hours 35 minutes on site, minus 2 hours free, is 2 hours 35 minutes of detention, or $155.
  • The broker's view: the clock starts at 08:00, so 3 hours 15 minutes on site, minus 2 hours free, is 1 hour 15 minutes, or $75.
  • Settled: $75, approved by the AP manager on Friday.

Neither side is lying. They applied different start rules to the same timestamps. A record set is valuable when it shows which rule the company applied, who applied it and whether the other side accepted it.

Step by step: what went wrong and who decided what

  1. Monday 15:12. The appointment is confirmed. The broker's carrier sales rep emails the carrier dispatcher with the receiver's slot, load number in the subject. Decision: accept the 08:00 slot.
  2. Tuesday 06:40. The driver arrives early. The gate check-in, 80 minutes ahead of the slot, is copied into the stop record. No one at the broker decides anything yet.
  3. Tuesday 08:20 to 11:15. Loading and departure. Loading starts 20 minutes after the slot; departure is confirmed by the driver's logging-device status change.
  4. Wednesday 09:30. The carrier bills from arrival. The carrier's billing clerk bills 2 hours 35 minutes at $60 per hour: $155, keyed into the carrier pay module.
  5. Thursday 10:00. The exception is flagged. The AP specialist sees that arrival precedes the appointment and holds the invoice, with a note naming the reason.
  6. Thursday 14:05. The broker disputes. The carrier relations manager replies in the same thread, attaching the Monday confirmation and stating the broker's rule: free time starts at the booked slot when a truck arrives early. Decision: offer 1 hour 15 minutes.
  7. Friday 10:40. The revised invoice is accepted. The carrier sends a revised invoice for $75, and the AP manager approves it, keeping the original $155 line beside it.

The hard part of this case is step 6. The rate confirmation was silent, so the outcome depended on a rule that lived in the broker's practice, not its contract. Only the email thread shows that rule being stated and accepted.

The record chain behind each decision

The table is the evidence asset for this page. Each row pairs one decision with the record that proves it was made, and the system that holds it.

WhenDecisionWho decidedRecord that captured itSystem
Mon 15:12Accept the 08:00 slot at dock 4Carrier sales repAppointment confirmation emailRep's mailbox
Tue 06:40None; the truck arrives 80 minutes earlyNot applicableGate check-in eventReceiver yard log, copied to the stop record
Tue 11:15None; departure after 4 hours 35 minutesNot applicableDeparture event and logging-device status changeStop record, logging device
Wed 09:30Bill 2 hours 35 minutes, $155Carrier billing clerkCarrier invoiceAP inbox, carrier pay module
Thu 10:00Hold the invoice for reviewAP specialistHold status and reason noteCarrier pay module
Thu 14:05Count from the slot; offer 1 hour 15 minutesCarrier relations managerDispute email citing the confirmationEmail thread
Fri 10:40Approve revised invoice, $75AP managerApproved revised pay line, original keptCarrier pay module

Remove any one row and the case stops explaining itself. Without the confirmation email, the early arrival looks like a long wait the broker refused to pay. Without the hold note, nobody can tell whether the exception was caught by a person or slipped through. Without the revised line kept beside the original, the history shows a $75 payment and no argument at all.

Why this sequence is useful evidence

A complete exception record has four parts: a starting state, a rule applied, an action and a checked result. This case has all four, each tied to a timestamp and a named role. Most payment histories keep only the last part, the amount that cleared, which tells a reader what was paid but not why.

The waiting itself is not trivial for the people involved. GAO found that about 80 percent of drivers who had experienced detention said it reduced their available driving time under federal hours-of-service rules. That is one reason the arrival and departure stamps get argued over, and why a broker that kept them alongside its decisions holds something unusual.

There is also a timing asymmetry worth noticing. FMCSA requires motor carriers to keep records of duty status and supporting documents for six months from receipt. The carrier's own duty-status trail can therefore be gone long before anyone looks back, while the broker's TMS stop events, hold notes and revised pay lines may survive for years. In a dispute history, the broker's copy is often the only one left.

A routine detention line, billed and paid as is, shows a charge, not a judgment. How the records join across the TMS, mailbox and AP is mapped in detention charge disputes records across systems.

How to recognize similar cases at a client

A transportation software consultant rarely sees the records themselves, and should not ask to. The signs come up in ordinary conversation about the TMS, the AP process or a coming system change:

  • The AP team talks about "holding" carrier invoices for review, not just paying or rejecting them.
  • Someone mentions an unwritten rule, such as "free time starts at the appointment if they show up early".
  • Revised carrier invoices are kept as new lines, not overwrites of the original.
  • Dispute emails go to a shared mailbox or reference the load number in the subject.
  • Rate confirmations changed over the years, so the rule may have been written down later.

Questions for the operations director, answered at metadata level only: roughly how many loads a year carry a detention line, roughly how many are disputed, which systems hold arrival times and pay revisions, how many years of dispute email survive, and who owns each system. The broader pattern of logistics exceptions is in identifying logistics exceptions and their documented resolutions, and detention sits alongside other accessorial checks on the freight audit exceptions page.

What the partner can confirm, and what stays open

The partner can learn which record classes exist, where they sit, who owns them and which executive can authorize a licensing discussion; who can license detention charge disputes records walks through that decision. 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. Unknown until SourceX reviews it with the company: how carrier and shipper 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 never collect exports, invoices or emails. Freight audit firms see the same pattern from the payer side; see freight audit and payment companies.

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 team can describe disputes like this one and confirms that holds, revisions and dispute emails were kept, register as a partner, check the company on who qualifies and read the program terms before you introduce the decision-maker.

  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

Is an early-arrival dispute rarer than an ordinary long wait?

Nobody publishes a reliable rate, so treat it as a pattern to ask about rather than a statistic. What matters is whether the company's records let a reader see the rule it applied each time, not how often the case occurred.

What if the carrier never accepted the revised invoice?

Then the case ends in a write-off, a short payment or a continuing argument, and each of those outcomes is still a recorded decision. Note the outcome type when you describe the history; an unresolved case is weaker evidence than a settled one but not worthless.

Sources

  1. gao.gov/products/gao-11-198
  2. fmcsa.dot.gov/hours-service/elds/how-long-must-motor-carri…
  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