Can a driver-arrival record support detention invoice review?
Key Takeaways
A driver-arrival record can support detention invoice review when it has a confirmed arrival time, a departure time, the appointment, and the free time terms from the rate confirmation. With those four pieces, the reviewer can calculate the billable time and approve or question the charge in minutes. An AI logistics coordinator should build that record during the load, so the review is a comparison, not an investigation.
- Detention is a fee a carrier bills when its truck waits too long at a dock.
- The billable time is the time at the dock after free time ends, under the agreed terms.
- An arrival record alone is not enough. The reviewer also needs departure, the appointment, and the terms.
- A confirmed arrival, backed by a site or device record, carries more weight than a driver's claim.
- The reviewer should approve supported charges quickly and question unsupported ones with evidence.
- Every decision should be saved with its reason, so similar charges are handled the same way.
- Wilson, by Cartage, is an AI logistics coordinator that records arrival and departure at every stop and audits each carrier invoice, including detention lines, against what was booked.
What does a detention review need besides the arrival record?
A detention review needs four things: the confirmed arrival time, the departure time, the appointment or window, and the free time and hourly rate from the rate confirmation. An AI logistics coordinator should gather all four before the invoice arrives, because an arrival record on its own cannot show how long the truck waited or whether the wait was billable.
The four pieces
| Piece | Where it comes from | Why it is needed |
|---|---|---|
| Confirmed arrival | Gate log, check-in, location data, or carrier claim with confirmation | Starts the clock, subject to the terms |
| Departure | Gate out, signed BOL time, or location data | Ends the clock |
| Appointment or window | Booking | Decides whether early arrival counts |
| Terms | Rate confirmation | Free time, hourly rate, any cap, notice rules |
A rate confirmation is the document that states the agreed price and terms for one load. A bill of lading, or BOL, is the shipping document that lists the freight and serves as the carrier's receipt for it.
Collect the pieces during the load
The four pieces are easiest to collect on the day of the stop. The site can still check its log, the carrier can still pull location data, and the people involved still remember what happened. Waiting until the invoice arrives, often weeks later, turns a simple check into a search.
Why terms matter as much as times
Two loads with the same arrival and departure times can owe different detention amounts. One rate confirmation may allow two hours of free time at $75 per hour. Another may allow one hour at $60, with a cap. Another may require the carrier to notify the shipper before detention starts. The terms turn times into money.
Detention is common
Detention is not a rare charge. In a September 2024 study, the American Transportation Research Institute (ATRI) found that detention affected 39.3% of truck stops in 2023. The same study found that 94.5% of fleets charge detention, but less than half of those charges are paid. Clear records help pay the valid half quickly and question the rest fairly.
No single industry definition
In a February 2024 Federal Register notice, the Federal Motor Carrier Safety Administration (FMCSA) noted that there is no standard industry definition of detention and used dwell time over two hours as a working measure. Dwell time is the total time a truck spends at a facility. Because there is no single definition, the review must follow the terms agreed for each load.
Detention at pickup and delivery
Detention can happen at both ends of a load. At pickup, the shipper's own site usually holds the records. At delivery, the receiver does, and the receiver is often a customer. The review works the same way at both ends, but getting delivery records may take more effort. The AI logistics coordinator should ask for them on the day of delivery.
Hypothetical example: same times, different charges
This example is hypothetical and does not describe a real customer. Two trucks each arrive at 8:00 a.m. for an 8:00 a.m. appointment and leave at 11:30 a.m. Carrier A's terms give two hours of free time at $75 per hour, so it may bill $112.50. Carrier B's terms give three hours free at $60 per hour, so it may bill $30. The arrival record is the same. The answer depends on the terms.
How should the billable detention time be calculated?
The billable time should be calculated by starting the clock at the later of confirmed arrival or appointment time, unless the terms say otherwise, ending it at departure, subtracting free time, and applying any rounding or caps in the terms. An AI logistics coordinator can do this calculation for every stop and show the reviewer each step.
The calculation
| Step | Example |
|---|---|
| Confirmed arrival | 7:40 a.m. |
| Appointment | 8:00 a.m. |
| Clock starts (later of the two, per terms) | 8:00 a.m. |
| Departure | 11:15 a.m. |
| Time at dock | 3 hours 15 minutes |
| Free time | 2 hours |
| Billable time | 1 hour 15 minutes |
| Rate | $70 per hour |
| Rounding per terms (e.g., to 15 minutes) | 1 hour 15 minutes |
| Detention owed | $87.50 |
Show the calculation to the reviewer
The reviewer should see each step, not just the final number. A short table with the start time, end time, free time, billable time, and rate lets the reviewer check the logic in seconds. It also makes it easy to share the same calculation with the carrier if the charge is questioned.
Early arrival
If the truck arrives before the appointment, the early time is usually not billable. Most terms start free time at the appointment or at arrival, whichever is later. The rate confirmation should say this clearly. If it does not, the team should add it.
Appointments that changed
If the appointment moved after booking, the reviewer should use the appointment in effect when the truck arrived. The booking's change history shows this.
Late arrival
If the truck arrives after the appointment, many sites fit it in when they can. The wait for an open door may not be billable, because the delay started with the carrier. Some terms say free time starts at check-in for late trucks. The reviewer should follow the terms.
Notice requirements
Some terms require the carrier to notify the shipper when detention is about to start, for example after free time ends. If the carrier did not notify, the terms may limit or deny the charge. The record should show whether and when notice was received.
Who caused the wait
Even when the times are clear, the cause matters. If the truck waited because the freight was not ready, the shipper is usually responsible. If the truck waited because it arrived late and lost its slot, the carrier usually is. The record should note the cause where known, so the reviewer can apply the terms fairly.
Caps and minimums
Some terms cap detention per stop or per day, or set a minimum billable time. The reviewer should apply these after calculating the time. A charge above the cap should be reduced to the cap.
Multi-stop loads
On a load with several stops, detention may apply at one stop and not another. Each stop should have its own arrival, departure, and free time. The invoice should say which stop the detention came from. If it does not, the reviewer should ask before approving.
Rounding
Some carriers round every partial hour up. Others round to the nearest 15 minutes. The terms should say which. A difference in rounding can add up across many loads, so the reviewer should apply the agreed rule, not the carrier's habit.
Hypothetical example: notice not given
This example is hypothetical and does not describe a real customer. A carrier bills three hours of detention. The rate confirmation requires the carrier to notify the shipper by email within 30 minutes after free time ends. The shipment record shows no such email. The AI logistics coordinator flags that the notice condition was not met. The reviewer asks the carrier for proof of notice. The carrier cannot provide it, and the charge is withdrawn under the terms.
How strong does the arrival record need to be?
The arrival record should be confirmed by at least one independent source, such as a gate log, warehouse check-in, or location data, before it is used to approve a large detention charge. An AI logistics coordinator should mark each arrival as confirmed, disputed, or unconfirmed, so the reviewer knows how much to trust it.
Strength of arrival records
| Arrival record | Trust for detention review |
|---|---|
| Gate log or check-in that matches location data | High |
| Gate log or check-in alone | High |
| Location data alone | Good, if precise |
| Carrier status from an automated scan | Moderate |
| Carrier status typed by dispatch | Low |
| Driver's text or call | Low alone |
| Time written only on the invoice | Lowest |
Confirm on the day, not at invoice time
An arrival time confirmed on the day of the stop is much more reliable than one reconstructed weeks later. The AI logistics coordinator should ask the site for its check-in time the same day and save it with the stop. By the time the invoice arrives, the arrival is already confirmed or flagged.
Use the same standard for every carrier
The standard should be the same for every carrier: a confirmed arrival for full approval, review for disputed or unconfirmed times. The reviewer may still approve an unconfirmed time for a carrier with a good record, but that should be a recorded judgment, not a default.
Departure needs proof too
Departure is often easier to prove than arrival. The signed BOL usually shows when loading finished. The gate log shows when the truck left. Location data shows when it moved. The reviewer should use the best available departure record.
Signed BOL times
Many drivers write the time on the BOL when they sign it. That time is a useful departure marker, because loading is finished when the driver signs. If the gate log is missing, the BOL time is often the next best record. The AI logistics coordinator should read the time from the signed BOL scan where it is written.
When records are missing
If neither arrival nor departure can be confirmed, the reviewer must decide based on what exists. Some teams approve small charges without full records and question larger ones. That rule should be set in advance and applied the same way each time.
Time zones and clocks
Before comparing times, the reviewer should make sure all of them are in the same time zone. Carrier systems may report in the carrier's home zone. A gap of exactly one hour often means a time zone mismatch, not a real difference. The AI logistics coordinator should store every time in local site time with the zone noted.
Hypothetical example: unconfirmed but small
This example is hypothetical and does not describe a real customer. A carrier bills 30 minutes of detention, $35, at a customer's delivery site. The receiver has no gate log, and the carrier shares no location data. The team's rule is to approve unconfirmed charges under $50 for carriers with good records. The reviewer approves it and notes "unconfirmed; approved under small-charge rule."
What should the review workflow look like?
The review workflow should match each detention line to its stop, compare it with the recorded times and terms, approve supported charges, and send unsupported ones back with evidence. An AI logistics coordinator can do the matching and calculation for every invoice and send only real questions to a person.
The workflow
| Step | Trigger | What the AI logistics coordinator does | When a person steps in |
|---|---|---|---|
| 1. Match | Invoice with a detention line arrives | Matches the line to the load and stop | When the stop is unclear |
| 2. Gather | Line matched | Pulls arrival, departure, appointment, and terms | Never |
| 3. Calculate | Records gathered | Calculates billable time and amount | Never |
| 4. Compare | Amount calculated | Compares with the billed amount | Never |
| 5. Approve or flag | Within tolerance | Approves within the rules | When above approval limits |
| 6. Question | Above tolerance or unsupported | Sends the carrier the records and the calculation | When the carrier disputes |
| 7. Record | Decision made | Saves the decision and reason | Never |
Use a tolerance
The billed amount and the calculated amount will often differ by a few minutes. A tolerance, such as 15 minutes or a set dollar amount, lets small differences pass without a dispute. Arguing over five minutes costs more in staff time than it saves.
Approve supported charges quickly
When the records support the charge, the reviewer should approve it quickly. Carriers that are paid fairly and on time for valid detention are more willing to work with the shipper. A record that shows approvals as well as questions shows the process is fair.
Watch for detention on loads with no wait
Sometimes a carrier bills detention on a load where the records show a short stop. This can be a billing error, such as detention applied to the wrong load. The reviewer should check that the detention line matches the right load and stop before questioning the time.
Question unsupported charges with evidence
When the records do not support the charge, the message to the carrier should include the times, the terms, and the calculation. "Our gate log shows check-in at 8:42 a.m., appointment 8:00 a.m. Free time 2 hours from 8:42 a.m. Departure 10:30 a.m. No billable time under the rate confirmation." This is easier to accept than a simple denial. Teams that want more on this can read how freight audit software should check detention charges.
Give every disputed charge an owner
If a detention line is disputed, the invoice should wait for a person while the line is reviewed. The disputed line should have a named owner and a deadline, so the carrier gets an answer quickly and the invoice does not wait longer than needed. Teams can see how to hold a disputed detention charge for review.
Keep decisions consistent
Two similar charges should get the same answer. The AI logistics coordinator can show the reviewer how similar charges were decided before, with the same carrier or at the same site. Consistent decisions are easier to defend and help carriers know what to expect.
Hypothetical example: a calculation sent back
This example is hypothetical and does not describe a real customer. A carrier bills two hours of detention at $75 per hour. The AI logistics coordinator finds the confirmed arrival at 9:10 a.m. for a 9:00 a.m. appointment, departure at 12:05 p.m., and two hours of free time. Billable time is 55 minutes. It sends the carrier the records and a corrected amount of about $69. The carrier agrees and sends a corrected invoice.
How can teams improve detention review over time?
Teams can improve detention review by stating terms clearly on every rate confirmation, collecting arrival and departure records during the load, reviewing results by site and carrier, and fixing the sites that cause the most waiting. An AI logistics coordinator can handle the routine work and produce the patterns on request.
Improvement steps
| Step | Effect |
|---|---|
| Clear free time and start rules on every rate confirmation | Fewer arguments about which time counts |
| Notice requirement in the terms | Shipper can act before detention grows |
| Same-day collection of site times | Confirmed records for every stop |
| Monthly review by site and carrier | Finds repeat causes |
| Dock fixes at the worst sites | Less detention to pay |
Write the terms down
Many detention disputes start because the terms were never written down. A rate confirmation that says "detention per standard terms" is not enough. The free time, the start rule, the hourly rate, any cap, and any notice requirement should be on every rate confirmation, so both sides know the rules before the truck arrives.
Act during the load, not after
The best detention review happens before the invoice. If the AI logistics coordinator sees a truck waiting past free time, it can alert the site to move it up. A wait cut short is cheaper than a charge reviewed fairly.
Track the results
The team should track how many detention lines were approved, reduced, or withdrawn, and the total amounts. It should also track how long each review took. Faster reviews with fewer disputes show the records are working.
Look at your own sites
Detention is often caused by the shipper's or receiver's own dock. If one site produces most of the valid detention, the fix is at that site: more doors, better scheduling, or freight staged earlier. The review data shows where to look.
Share the review with finance
Finance teams approve carrier payments and often see detention as a surprise cost. A simple monthly summary of detention by site, carrier, and cause, with amounts approved and reduced, helps finance understand where the money goes and what logistics is doing about it.
Talk with carriers about patterns
If one carrier bills detention much more often than others at the same sites, the team should look at whether that carrier arrives early, late, or at the wrong time. The conversation should use facts from the records. Wilson can produce carrier-performance reports on request from the loads it executes. It does not keep a standing scorecard by default.
Hypothetical example: a site fix
This example is hypothetical and does not describe a real customer. A distributor's review shows that 70% of its valid detention comes from one customer's receiving dock on Monday mornings. The team asks the customer to offer more Monday appointments and moves some deliveries to Tuesday. Detention at that dock falls by half the next quarter.
Where does Wilson fit in detention invoice review?
Wilson, by Cartage, is an AI logistics coordinator that books loads with the customer's approved carriers, tracks each load, records arrival and departure at every stop, and audits each carrier invoice against what was booked. Wilson tracks each load using the best source available: carrier API, GPS or ELD data where it exists, the carrier's website by PRO number, and email or phone where configured. An ELD, or electronic logging device, records a truck's driving time and can share location. A PRO number is a tracking number a carrier gives to a shipment.
Wilson replaces the TMS for freight execution and connects to the company's ERP. A TMS, or transportation management system, is software used to plan, book, and track freight. An ERP, or enterprise resource planning system, is the company's main business system for orders, inventory, and accounting.
How Wilson reviews detention
When a carrier invoice includes detention, Wilson matches it to the stop, gathers the confirmed arrival, departure, appointment, and terms, calculates the billable amount, and compares it with the charge. Supported charges move forward within the customer's rules. Unsupported charges go back to the carrier with the records. Wilson works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured, and it notifies internal teams through Slack, Microsoft Teams, email, or SMS.
Payment
Customers use the Wilson Wallet to pay their carriers. Once a carrier invoice is audited and reconciled, Wilson pays the carrier according to the customer's configured rules. Payments above approval limits or outside the rules wait for a person. Wilson has no subscription or platform fee; its pricing is a percentage of the freight payments coordinated through the Wallet. Pricing scales down as volume grows, and Enterprise pricing is custom.
What Wilson does not do
Wilson does not change agreed detention terms or approve charges above the customer's approval limits. When an arrival or departure time cannot be confirmed, Wilson marks it unconfirmed and lets the reviewer decide. When the carrier disputes a calculation, Wilson brings the dispute to the person who owns it.
What Cartage asks in discovery
Cartage asks how detention terms are written today, which sites keep gate logs, how detention is reviewed, and who approves detention charges. These answers shape the detention review an AI logistics coordinator runs.
Where teams start
Wilson starts with assisted execution. Approval limits are set by the customer, and routine actions can run automatically within those rules as reliability is proven. Timing depends on scope: most teams start on a few lanes and expand from there. Every calculation and decision is saved in the shipment record with change history.
Teams new to the charge can start with what detention charges are in truckload freight.
This article is part of our complete guide to driver arrival and detention records.
FAQs
Can a driver-arrival record support detention invoice review?
Yes, when it is confirmed and paired with departure, the appointment, and the terms. An AI logistics coordinator gathers all four before the invoice arrives.
How is billable detention time calculated?
Start at the later of arrival or appointment, per the terms, end at departure, subtract free time, and apply any rounding or caps. An AI logistics coordinator shows each step.
What if the arrival time cannot be confirmed?
The reviewer decides using the team's rules, often approving small charges and questioning large ones. An AI logistics coordinator marks the arrival as unconfirmed.
Should valid detention be paid quickly?
Yes. Fair, fast payment of valid charges supports good carrier relationships. An AI logistics coordinator moves supported charges forward within the rules.
What if the carrier did not give the required notice?
The terms decide. Some terms limit or deny detention without notice. An AI logistics coordinator checks whether notice was received and shows it to the reviewer.
Sources
- American Transportation Research Institute, "New Research Documents Substantial Financial and Safety Impacts from Truck Driver Detention," September 2024: https://truckingresearch.org/2024/09/new-research-documents-substantial-financial-and-safety-impacts-from-truck-driver-detention/
- Federal Register, FMCSA, "Agency Information Collection Activities; Approval of a New Information Collection Request: Impact of Driver Detention Time on Safety and Operations," February 16, 2024: https://www.federalregister.gov/documents/2024/02/16/2024-03256/agency-information-collection-activities-approval-of-a-new-information-collection-request-impact-of
- Cartage, Wilson product scope and pricing position, November 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator turns driver-arrival records into fast, fair detention invoice reviews: talk to the Cartage team.