Maersk’s Container Charge Settlement Turns Detention and Demurrage Into a Documentation Problem

Container detention and demurrage used to sit in a frustrating gray zone: expensive enough to hurt, common enough to normalize, and messy enough that many shippers treated disputes as an after-the-fact billing fight. Maersk’s latest settlement with the Federal Maritime Commission makes that approach look obsolete.

According to Logistics Management, A.P. Moller Maersk agreed to pay $1.9 million and provide refunds and waivers to certain customers to resolve FMC allegations tied to container-related detention charges. The agency said the carrier assessed charges against third parties that had not agreed to be bound by the relevant shipping contracts, bills of lading, or tariffs. The article also notes the broader context: detention fees became a major flashpoint during pandemic congestion, when containers sat at ports and terminals longer than expected and cost exposure piled up quickly.

That is not just a carrier compliance story. It is a shipper operating model story. The practical lesson is blunt: detention and demurrage are no longer just “costs of doing business.” They are auditable events that require clean evidence.

The charge is only the end of the workflow

A detention invoice usually appears at the end of a long chain of operational facts. When was the container made available? When did free time start? Was the terminal appointment obtainable? Was the container on hold? Did the consignee, trucker, forwarder, or carrier create the delay? Was the party being billed actually bound by the document the carrier relied on?

Those questions sound legal, but they are mostly operational. The answer lives in milestone data, dispatch notes, appointment records, customs status, emails, carrier messages, EDI feeds, terminal updates, and exception timestamps. If those records are scattered across inboxes and spreadsheets, the shipper’s dispute position is weak before the invoice even arrives.

The Maersk settlement shows why the billing file matters as much as the freight file. A shipment record should not stop at estimated arrival and delivery confirmation. For ocean freight, it needs a charge-defense trail:

• vessel arrival, discharge, availability, last free day, pickup, outgate, return, and empty received timestamps;
• party responsibility for each milestone and handoff;
• documentation of holds, appointment shortages, terminal closures, equipment shortages, and carrier instructions;
• signed or accepted contract, tariff, booking, and bill of lading references;
• dispute owner, deadline, amount at risk, and refund status.

That is exactly where money leaks.

Free-time clocks need owners, not reminders

Detention and demurrage exposure often starts because no one owns the clock. Operations sees a container. Finance sees an invoice. Procurement sees the carrier relationship. Customer service sees the exception after the customer is already angry. By then, the organization is arguing internally instead of controlling the event.

The better model is to assign ownership before the container lands. For every import container, teams should know the first available date, the last free day, the planned pickup window, and the escalation trigger if a milestone slips. If the clock is visible only after the fee posts, the workflow has already failed.

This is where transportation management discipline matters. A TMS should not merely store rates and bookings. It should translate ocean milestones into work queues: containers approaching free-time expiration, containers missing appointment confirmation, containers with unresolved holds, and invoices that do not match the operational timeline. The system needs to preserve facts fast enough for people to act.

Ocean procurement now depends on billing governance

The settlement also changes how shippers should think about ocean procurement. A low base rate is less valuable if the carrier relationship creates opaque charge exposure. Procurement teams need to compare not only freight rates, transit times, and service strings, but also billing behavior, dispute responsiveness, tariff clarity, documentation quality, and refund history.

That is especially important because container cost volatility has not disappeared. In a separate Logistics Management report, U.S. prosecutors alleged that four major Chinese container manufacturers and seven executives participated in a price-fixing conspiracy from as early as November 2019 through at least January 2024. The article says the named companies represented roughly 95% of global standard dry container production, highlighting how concentrated equipment economics can become during stress periods.

Shippers do not control carrier settlements or container manufacturing markets. They do control whether their own records are strong enough to manage cost risk when the market turns messy.

Refund readiness is a process, not a scramble

The weakest demurrage programs wait for a painful invoice and then hunt for evidence. The strongest ones build refund readiness into the shipment lifecycle.

That means standardizing exception codes, capturing carrier communications in the shipment record, linking invoices back to shipment events and contract terms, and creating a dispute calendar. Charge challenges often fail when teams miss deadlines rather than when they lack a valid argument.

It also means separating three questions that companies often blend together:

1. Was the operational delay real?
2. Who caused or controlled the delay?
3. Is this party contractually responsible for the charge being assessed?

A detention invoice may be mathematically accurate and still disputed because the responsible party is wrong. Or the charge may be contractually valid but preventable next time through better appointment planning. Without structured documentation, teams cannot tell the difference.

What shippers should do now

Ocean shippers, forwarders, and importers should treat the Maersk settlement as a reason to tighten the operating system around container charges. Start with four practical moves.

First, map every detention and demurrage trigger in the import workflow. If no one can explain exactly when free time starts and ends for each lane, terminal, and carrier agreement, the process is exposed.

Second, make exception notes mandatory. “Container delayed” is not enough. Teams need to know whether the cause was customs, terminal appointment availability, carrier release delay, drayage capacity, consignee refusal, documentation error, or weather.

Third, connect freight audit to operations. Finance should not review accessorial invoices in isolation. The invoice should be checked against the shipment timeline, contract references, and exception log.

Fourth, measure recovery. Track charges prevented, charges disputed, dollars refunded or waived, average dispute cycle time, and repeat causes by carrier, port, consignee, and lane. If the same exception keeps appearing, it is not an exception anymore. It is a process defect.

The new standard: prove it or pay it

Container charge governance is becoming more evidence-driven. Regulators are watching billing practices. Carriers are refining tariff language. Shippers are under pressure to defend margins without slowing freight. The winners will not be the teams with the loudest disputes. They will be the teams with the cleanest records.

CXTMS helps freight teams turn those records into operating control: milestone visibility, exception tracking, document discipline, invoice review, and audit-ready workflows in one transportation management environment. If detention and demurrage are eating into your ocean freight budget, schedule a CXTMS demo and see how better execution data can protect the next container before the next invoice arrives.

Sources

• Maersk agrees to settlement in regards to container charges, Logistics Management
• Chinese Container Makers are indicted by U.S. in price-fixing case, Logistics Management