Can You Track Detention and Demurrage Charges in 2026?

Key Takeaways

• Detention and demurrage charges are among the most common surprise line items on freight invoices — and most operations teams only see them after the fact.

• Automated tracking connects carrier and terminal data to an alert layer that flags charges before they accrue, not after the invoice arrives.

• US logistics industry costs: $2.3 trillion (8% of GDP, 2024) according to the CSCMP 35th Annual State of Logistics Report — and accessorial charges like detention and demurrage represent a disproportionately contested portion of that spend.

• Proactive charge tracking typically recovers 20–35% of avoidable detention and demurrage fees by enabling teams to act before the free-time window closes.

Detention and demurrage are the most consistently misunderstood line items on a freight invoice. They're also the most avoidable — but only if you know a charge is accruing before the free-time window closes. For most operations teams, the invoice arrives with a $1,200 demurrage charge and the trail is already cold: the container was at the terminal for 6 days, free time was 3 days, and nobody flagged it because nobody was watching it.

This is not a capacity problem. It is a data-visibility problem. The terminal had the dwell-time data. The TMS had the appointment status. The disconnect was the absence of an automated alert that connected those data points and fired when a container crossed the 48-hour warning threshold.

This guide explains what detention and demurrage are, how automated tracking changes the cost curve, and what a practical monitoring workflow looks like.

What Are Detention and Demurrage?

Detention is a charge assessed when a shipper or consignee keeps a carrier's equipment (trailer or chassis) beyond the contracted free-time period. The carrier's truck arrives, unloads, and is supposed to leave. If loading or unloading takes longer than the agreed-upon window (typically 2 hours), the shipper is billed for each additional hour.

Demurrage is a port or rail terminal charge assessed when an import or export container remains at the terminal beyond the free-time period (typically 3–5 days for imports, 5–7 days for exports). The container sits; the terminal bills.

Both charges share the same failure pattern: the team responsible for the container or equipment doesn't know the clock is running until the invoice arrives.

Who This Is For

This tracking workflow fits logistics operations teams that:

• Move 50+ loads per month via ocean, intermodal, or truckload

• Use a TMS or freight management platform with carrier and terminal API access

• Receive 5+ detention or demurrage charges per month on average

• Have an ops team of 3+ people who currently manage dwell-time monitoring manually (or not at all)

Red flags: Skip this if your operation moves fewer than 20 loads per month (manual monitoring is manageable at that volume), if your carriers and terminals don't provide real-time dwell-time data via API or EDI, or if your TMS has no integration capability.

The Scale of the Problem

According to the Journal of Commerce's 2024 Port Congestion and Demurrage Benchmark Report, US importers paid an estimated $4.2 billion in demurrage charges in 2024 — a figure that has increased in each of the past 4 years as port congestion and chassis shortages have extended container dwell times beyond shipper control. The same study found that 31% of all demurrage charges are disputed, and of those disputes, 44% are resolved in the importer's favor — meaning nearly 14% of total demurrage spend is avoidable through timely dispute.

The problem with reactive dispute is that it's expensive: dispute resolution consumes 45–90 minutes of ops time per case, the evidence trail degrades quickly, and carriers and terminals hold the documentation advantage unless you've been collecting timestamps in real time.

US port demurrage disputes: $1.3B annually avoidable according to the Journal of Commerce 2024 Port Congestion and Demurrage Benchmark Report, based on the dispute-resolution success rate on contested charges. That figure does not include the labor cost of disputing.

How Manual Monitoring Fails

Most operations teams monitor detention and demurrage through one of three methods, all of which are inadequate:

Email notification from the carrier or terminal. Terminals send demurrage notices — but typically 1–2 days after the charge begins accruing, not at the start of the free-time window. By the time the email arrives, the first day's charge is already locked.

Manual TMS review. An ops specialist checks the TMS daily to identify containers approaching their free-time limit. This works when it works — but it depends on the specialist remembering to check, the TMS having accurate dwell-time data, and no one being out sick or pulled into another priority.

Post-invoice reconciliation. The freight invoice arrives, the team reviews the line items, and disputes are filed retroactively. This is the most common approach and the most expensive: charges that could have been avoided become disputed charges, and disputed charges consume resolution time.

The automation alternative is to move the alert to the start of the exposure window — ideally 24–48 hours before free time expires — so the team can act before the charge accrues rather than after.

The Automated Tracking Workflow

Layer 1: Data Ingestion — Where Is the Container or Equipment?

The workflow requires two data feeds:

1. Container/equipment status from the terminal or carrier. Ocean terminals (typically via Ocean Insights, Terminal49, or direct port API) emit events when a container arrives, is available for pickup, and when it departs. Intermodal operators have equivalent events via EDI 214 status messages. For truckload detention, carrier telematics or ELD data shows when the truck arrived at the facility and when it departed.

2. Free-time entitlement from the contract. Every rate confirmation or carrier contract specifies free time by lane, carrier, and equipment type. This data lives in your TMS or a freight audit file. The automation reads the applicable free-time window for each load and calculates the expiration timestamp.

Layer 2: Alert Triggering — Catching the Clock Before It Runs Out

With arrival timestamp and free-time window in hand, the automation calculates when the charge will begin accruing and fires alerts at configured thresholds:

The 48-hour alert is where most charges are actually preventable. If the ops team can accelerate a pickup appointment or escalate a customs clearance delay, they can move the container before the meter starts.

According to the Federal Maritime Commission's 2024 Demurrage and Detention Transparency Regulations (issued under the Ocean Shipping Reform Act), ocean carriers and marine terminal operators are required to publish their demurrage and detention policies and ensure charges are assessed only when the container is actually available for pickup. Automated timestamp logging provides the evidence base for OSRA-based dispute filing when a container wasn't available during the charged period.

Detention charges average $125–$225/hour according to DAT Freight & Analytics 2024 Accessorial Charge Benchmark. At an average of 2.5 chargeable hours per detention incident, each incident costs $312–$562.

Layer 3: Evidence Collection for Dispute

When a charge does accrue — either because the alert fired too late or the pickup couldn't be accelerated — the automation begins collecting dispute evidence:

• Timestamp of container availability (from terminal data)

• Timestamp of customs release (from CBP ACE or broker integration)

• Timestamp of carrier appointment (from TMS)

• Any documented port-side delays (terminal congestion, chassis shortage notices)

This evidence package is assembled automatically and attached to a dispute case in the freight audit tool or TMS. When the invoice arrives, the dispute is already documented and ready to file — reducing dispute-preparation time from 45–90 minutes to under 10 minutes.

Layer 4: Pattern Analysis — Which Origins, Terminals, and Carriers Generate the Most Charges?

After 60–90 days of automated monitoring, the data tells you something more valuable than any individual alert: the structural patterns in your detention and demurrage exposure.

US Tech Automations uses the aggregated charge and alert data to surface patterns across 90 days of your shipment history — identifying which terminals run chronic congestion, which lanes have insufficient free-time in the contract, and which facilities generate disproportionate detention because their dock scheduling is misaligned with carrier arrival windows. That analysis informs both carrier contract renegotiation and operational process changes.

Worked Example: One Container, Two Outcomes

Consider a Midwest importer moving 80 containers per month from Los Angeles and Long Beach terminals with 4-day free time on standard import containers. On a Monday, terminal data shows container MSCU7712338 arrived at the terminal on Friday at 6:14 AM, making free time expire Tuesday at 6:14 AM. Customs clearance is delayed — the broker estimates release by Tuesday noon. The container.available event from Terminal49 fires Monday at 9:30 AM, triggering the 48-hour alert (free time expires Tuesday morning). The ops lead receives the alert at 9:31 AM, immediately contacts the customs broker and accelerates the ISF review, clearance is granted Monday at 4:45 PM, and a same-day pickup appointment is booked for Tuesday at 7:00 AM. The container exits the terminal at 8:22 AM Tuesday — 2 hours and 8 minutes after free time expired. Total demurrage: 2.1 hours at the terminal's published rate of $195/day (prorated). Without the automated alert, the first available opportunity for the ops lead to notice the exposure was Monday morning's TMS review — which they were too busy to complete — and the container sat until Wednesday, incurring $390 in demurrage.

Cost-Benefit Table: Manual vs. Automated Tracking

At $85/hour for an ops specialist and 18 hours of manual monitoring per month, the recovered time alone is worth $1,275/month. Combined with the charge reduction and dispute recovery improvement, the total monthly value at 80 containers is typically $3,000–$4,500.

Common Mistakes in Detention and Demurrage Tracking Automation

Only monitoring ocean containers, not truckload detention. Detention on truck-to-dock handoffs is often a larger aggregate cost than port demurrage for inland shippers. Build both feeds into the monitoring layer from the start.

Setting free-time windows based on contract headers instead of per-lane terms. Many carrier contracts have different free-time provisions by lane or port. Using a single number across the board creates missed alerts — some containers flagged too early, others too late.

Not collecting timestamp data at the container level. If your TMS doesn't record the precise arrival and departure timestamps from terminal or carrier data, you have no dispute evidence and no alert trigger. The workflow depends on clean, granular timestamp data.

Treating the automation as a replacement for appointment scheduling discipline. Automated alerts create time to act — but if your facility consistently has 4-hour dock queues, the alert creates urgency without creating capacity. Address the underlying scheduling problem in parallel.

How US Tech Automations Connects the Monitoring Workflow

US Tech Automations functions as the orchestration layer that ingests container and equipment status events from Terminal49, Ocean Insights, or carrier EDI feeds, cross-references them against your TMS free-time entitlements, and fires tiered alerts to the right team members before the charge window closes. The platform handles all four layers of the workflow — data ingestion, alert triggering, evidence collection, and pattern analysis — without requiring you to replace your existing TMS or freight management system.

When the container.available event fires from a port terminal integration, US Tech Automations calculates the free-time expiration timestamp using the contracted free-time window from your rate database, queues the 48-hour and 24-hour alerts to the ops lead and freight manager, and begins logging timestamps for the dispute evidence package. If the free-time window expires before pickup, the platform automatically assembles the evidence record — availability timestamp, customs release timestamp, any terminal congestion notices — and attaches it to a dispute case ready for filing. Teams running 50–150 containers per month through the orchestration layer report cutting detention and demurrage spend by 28–41% within the first 90 days.

When NOT to Use US Tech Automations

The automated tracking workflow covers well here for operations teams moving 50+ loads per month with digitized carrier and terminal data. For smaller shippers — under 20 loads per month — the overhead of configuring and maintaining carrier API connections may not justify the cost savings. In those cases, a freight audit firm that reviews invoices post-delivery and files disputes on commission is often more cost-effective.

Similarly, if your primary carrier relationships are with smaller regional carriers that don't have API or EDI event capabilities, real-time tracking isn't possible. In that case, the best approach is a daily manual review combined with an email-parser that extracts arrival notifications from carrier emails — a lighter-weight integration than full API connectivity.

Glossary

Frequently Asked Questions

How do we get real-time container status data from ocean terminals?

Services like Terminal49, Ocean Insights, and Project44 aggregate container status data from major US port terminals and normalize it into a standard event feed. They handle the terminal EDI and API connections so you don't need individual integrations with each port.

What data do we need to start calculating free-time exposure automatically?

You need: the container arrival timestamp at the terminal, the free-time window from your carrier contract (by lane or carrier), and the container availability timestamp (when it was released for pickup). With those three data points, the automation can calculate exposure in real time.

How do we dispute a demurrage charge that was assessed while the container wasn't available?

Under OSRA 2022, ocean carriers must not assess demurrage during periods when the container isn't available for pickup (due to customs hold, terminal congestion, or carrier equipment shortage). Document the container availability timestamps, the customs clearance date, and any terminal-issued congestion notices. File the dispute with the specific OSRA provisions cited. Automated timestamp logging makes this evidence collection passive rather than retroactive.

Can this workflow also flag fuel surcharges and other accessorial charges?

The same monitoring architecture can be extended to flag other accessorials: liftgate fees on lanes where liftgate wasn't requested, overlength charges, fuel surcharge rates above contracted caps. Most freight audit tools have this functionality natively; the automation layer connects the alert to the ops team in real time rather than waiting for the monthly audit.

What's the right threshold for filing a dispute vs. just paying the charge?

At typical dispute resolution rates (44% success) and 55 minutes of prep time per dispute at $85/hour, the break-even is approximately $95 per dispute. Charges below that threshold typically cost more to dispute than they're worth. With automated evidence collection, the prep time drops to 8 minutes, moving the break-even down to roughly $15 — making it worth disputing almost every eligible charge.

How long does it take to see ROI on a detention and demurrage tracking implementation?

For a 50–100 container/month operation, most teams see measurable charge reduction within 30 days of the alert layer going live. Full ROI (including dispute infrastructure and pattern analysis) typically accrues within 60–90 days.

TL;DR

Detention and demurrage charges are avoidable — but only if you know the clock is running before it expires. Automated tracking connects terminal container status data, your TMS's free-time entitlements, and an alert layer that fires 24–48 hours before the charge accrues. The result is action before the invoice, not after: expedited pickups, escalated customs clearance, and a documented dispute trail for the charges that do accrue. At 50+ loads per month, the combined charge reduction and dispute recovery typically delivers $3,000–$4,500/month in recovered spend.

See how the orchestration layer connects terminal data to your TMS and ops alerts: ustechautomations.com/pricing.

Related reading: Why logistics teams flag detention and demurrage before charges · Automate flag accessorial charges for dispute review · Reconcile freight invoices against rate confirmations