Demurrage and Detention Invoices Need a 30-Day Evidence Clock

Demurrage and detention disputes are often lost before anyone reviews the invoice. The decisive evidence—container availability, free-time terms, appointment attempts, terminal holds, gate transactions, and equipment return records—may be scattered across carrier portals, emails, drayage systems, and spreadsheets. By the time freight audit assembles the file, the dispute window may already be closing.

That is why ocean freight teams need more than invoice workflow. They need a 30-day evidence clock that begins with operational events and keeps running through billing, validation, dispute, and resolution.

The Federal Maritime Commission's billing framework makes timing concrete. Ocean carriers and marine terminal operators generally must issue demurrage and detention invoices within 30 calendar days after charges stop accruing. A billed party must receive at least 30 calendar days to submit a mitigation, refund, or waiver request. Once a timely request is made, the billing party must attempt to resolve it within 30 days unless the parties agree to more time.

The deadline is short, but the exposure is large

These are not edge-case charges. Supply Chain Dive reported that ocean carriers collected about $6.9 billion in detention and demurrage costs from 2020 through 2022. FreightWaves, citing the FMC rule's preamble and a different carrier population, reported approximately $8.9 billion charged by nine of the largest carriers serving U.S. container trades over that period. The definitions differ, but both figures show why evidence management belongs in the core transportation process.

The 30-day framework also has an important NVOCC layer. FreightWaves reported the FMC's clarification that an NVOCC has an additional 30 calendar days to issue its customer invoice, beginning on the date the invoice received by the NVOCC was issued. When the NVOCC's customer disputes a charge, the rule also provides a mechanism for additional time in the upstream dispute with the vessel-operating carrier.

That extra link is useful, but it creates another handoff where time and evidence can disappear. A source invoice sitting in an inbox for ten days does not stop any clock.

Build the evidence packet before the invoice arrives

A defensible charge starts with the free-time record. Store the allowed days, start and end dates, tariff or contract source, and any extensions. Do not replace the original terms when a carrier grants more time; preserve the baseline and the amendment with its timestamp and approving party.

For import demurrage, capture discharge, customs and government holds, freight release, container availability, terminal closure periods, appointment inventory, appointment attempts, and pickup gate-out. For detention, add empty-return instructions, return-location changes, dual-transaction requirements, rejected return attempts, terminal capacity constraints, and final gate-in.

Each event should contain a source, timestamp, time zone, container number, shipment reference, and responsible party. Screenshots and emails matter, but structured milestones make the record searchable and allow the system to detect missing evidence before it becomes urgent.

Invoice data must be equally precise. The FMC framework calls for information including the invoice and due dates, free time allowed, free-time start and end dates, the import availability date or export earliest-return date, and the specific dates charged. FreightWaves notes that omission of required invoice information eliminates the billed party's obligation to pay the applicable charge. A TMS should compare these fields with the operational record automatically rather than asking an auditor to reconstruct the move line by line.

Turn 30 days into controlled checkpoints

The evidence clock should create deadlines from the invoice receipt date and the applicable contract or rule, then work backward:

• Day 0: Ingest the invoice, source document, charge dates, amount, container, and billing party. Calculate the response deadline and assign an owner.
• Days 1–3: Match the invoice to the shipment, free-time terms, availability event, gate moves, holds, and appointment history. Flag missing or inconsistent fields.
• Days 4–10: Request missing evidence from operations, drayage providers, terminals, customers, or carriers. Escalate unanswered requests instead of leaving them in email.
• Days 11–20: Complete charge validation, determine responsibility, and prepare the dispute narrative with attachments and a quantified requested adjustment.
• Days 21–25: Obtain internal approval and submit through the required carrier portal or channel. Preserve confirmation numbers and submission timestamps.
• Days 26–30: Escalate any unsubmitted case, verify acknowledgment, and monitor the billing party's response clock.

This schedule deliberately avoids treating day 30 as the target. Portal failure, missing credentials, weekends, and disputes over the invoice receipt date are predictable operational risks. A five-day internal buffer is cheap insurance.

Automate exceptions, not judgment

A useful TMS can calculate chargeable days, compare them with invoiced days, and generate exception reasons. It can detect charges during a customs hold, dates when no return appointments were available, duplicate invoices, mismatched containers, or billing sent to the wrong party. It can also alert managers when evidence is missing or an owner has not acted.

The system should not blindly approve or reject a charge. Contract language, terminal facts, and responsibility still require judgment. Automation's job is to put a complete, chronological case in front of that decision-maker early enough to act.

Track performance at the process level: invoices received, dollars reviewed, percentage automatically matched, disputes filed within the internal target, recoveries, average resolution time, and root causes by port, carrier, terminal, customer, and drayage provider. Those measures turn freight audit from a reactive recovery function into an operating-control system.

Make every container dispute-ready

The strongest dispute is assembled while the container is moving, not weeks after it returns. When a TMS connects free-time rules, operational milestones, documents, invoices, owners, and deadlines, teams can distinguish valid cost from preventable leakage quickly—and support the decision with evidence.

CXTMS gives freight forwarders a shared operational record for ocean milestones, documents, costs, and exception workflows. Request a CXTMS demo to build deadline-driven demurrage and detention control into every shipment.