Demurrage and detention are two clocks.

They start on different events, they stop on different events, and they are owed to two different companies. A screen that keeps one free-time number per container has to be wrong about one of them.

Demurrage runs while the box is still on the terminal. Detention runs while the box is held off it. The board counts both against the same container, names the counterparty on each row, and audits the carrier’s own invoice when it arrives.

2
Clocks per container
Two start events, two stop events, two counterparties, two rates. One field cannot hold both.
20
Items on a D&D invoice
46 CFR §541.6 lists what a demurrage or detention invoice must carry. The audit checks the carrier’s invoice against every one.
What it does

Every row says which clock, and who is on the other end.

This is not a list of containers with a number of days beside them. Each row names the clock, the event that started it, the day free time ran out, and the company the money is owed to — because those four things differ between the two, and the phone call differs with them.

Fig. 1 — Two clocks, not one column.46 CFR §541.6 · lib/dd.ts
Discharged Last free day Out the gate Returned Demurrage — the box is in the terminal Charged by the terminal. Stops the moment it is released. Detention Charged by the carrier, until the box comes back.
They are two clocks because they answer to two different counterparties; merged into one column, the dispute gets argued with the wrong company.
Free time — 02 September 3 accruing
Free time — containers past their last free day
ContainerClockStartedLast free day OverAccrued
MSKU701235440HC · USLAX DemurrageTerminal Discharged 08/0808/13 19USD 185/day3,515.00
TCNU441906340HC · USLAX DemurrageTerminal Discharged 08/1108/16 3Stopped — released 08/19555.00
TCNU4419063the same box DetentionCarrier — HMM Out-gated 08/1908/23 9USD 125/day1,125.00
MSDU228051440HC · export DetentionCarrier — Maersk Out-gated 08/2108/25 7ERD 09/04 — cannot be returned yet875.00
Still running — 3 of the 4 clocksUSD 5,515.00
The row no arrival board will ever show
MSDU2280514 is an export. It was pulled on 21 August for a vessel whose earliest return date is 4 September, so detention has been running for seven days on a box that has nowhere to go back to — and it appears on no arrival list anywhere, because it has not arrived. It has not sailed.

Different events, different people.

Demurrage runs while the container is on the terminal. It starts when discharge begins, it stops when the box goes out of the gate, and it is owed to the terminal. Detention runs while the box is held outside. It starts at that same out-gate, it stops when the equipment is handed back, and it is owed to the carrier.

One event ends the first clock and begins the second, which is exactly why they cannot be one running total. TCNU4419063 appears twice above for that reason: three days of demurrage that have stopped, and nine days of detention that have not.

There is therefore no column here called free time. There is a clock, an event, a date and a counterparty, and the row is legible without anyone remembering which kind of box this was.

Drayage and dispatch →

And when the invoice arrives

The carrier’s invoice is checked against the rule that governs it.

A demurrage or detention invoice has to carry certain information: twenty items of it, set out in 46 CFR §541.6. The audit reads the invoice against all twenty, counts the days in §541.7 as dates, and writes the letter if items are missing.

D&D invoice — HDMU-DD-040175 · HMM Failed 8
ContainerHDMU1950988 · 40HC · import
ChargeDemurrage 26 Apr → 05 May 2026 — 10 days
AmountUSD 1,470.00 — 10 × USD 147.00
Checked against46 CFR §541.6 — 20 required items
8 of the required items are not on this invoice§541.6
Date the container was made available · start date of free time · end date of free time · allowed free time in days · the rule the daily rate is based on · contact for a request to mitigate · the statement that the charges comply with the Commission’s rules · the statement that the billing party’s own performance did not cause the charge.
Last day charged05 May 2026
Invoice issued17 Jun 2026 — 43 days later
§541.7 — issue within 30 daysDue 04 Jun 2026 — 13 days late
Window to request mitigation17 Jun → 17 Jul 2026 — closed 47 days ago
What the audit produces
A dispute letter to HMM, filled in with these dates, these eight items and the clause each one comes from, ready for the forwarder to read and send. AMC does not send it.

It reads the direction first.

The twenty items are not all required on every invoice. An import invoice has to carry the port of discharge. An export invoice has to carry the earliest return date and is not asked for a port of discharge at all. Checking every item against every invoice manufactures failures that are not failures, and one of those inside a letter is worse than sending no letter.

The thirty days are counted, not remembered.

§541.7 gives the billing party thirty days from the last day a charge was incurred to issue the invoice. This one charged up to 5 May and was issued on 17 June, which is forty-three days later and thirteen past the deadline. The same section gives the billed party thirty days from the invoice to ask for mitigation — a window that opened on 17 June and closed on 17 July. Today is 2 September, so the screen says the window is closed rather than leaving it to be worked out from an invoice date.

Why the letter is worth writing

§541.5 is direct about what a missing item does: failure to include the required information “eliminates any obligation … to pay.” That is the sentence the letter rests on, and it is the reason the eight items are listed by name with their clause beside them instead of being summarised as a score.

Recording — 15 s, silent, loops R-09 · not yet shot
What it shows Two clocks running on the same box, and the audit turning a late carrier invoice into a letter that is ready to send.
Where to shoot it Free time — 02 September, then D&D invoice — HDMU-DD-040175, demo company
The take
  1. Open the free time board. Three rows accruing, running total USD 5,515.00.
  2. Point at TCNU4419063 on both of its rows: demurrage stopped, detention still running.
  3. Open the D&D invoice and run the audit, then stop on the eight missing items with their clauses beside them.
Why here Two clocks and twenty CFR items is the densest prose on the site. Fifteen seconds shows both without asking anyone to hold §541.6 in their head while they read.
One rule

The two clocks never share a field.

It would be simpler to keep one free-time number per container and let the screen work out which kind it is. AMC did not, because there is no direction that single field can point in that is right.

With the field pointed at demurrage

The box already pulled goes quiet. Detention began at the out-gate, it is owed to the carrier rather than the terminal, and it is running at a different rate — but the number on the screen stopped moving on the day the second cost started. The screen goes calm at the moment the exposure begins.

With the field pointed at detention

The box still sitting on the terminal is then counted against the wrong company at the wrong rate, and the demurrage in fact accruing has no line at all. Whichever way the single field is pointed, one of the two clocks disappears — and it disappears quietly, which is the part that costs money.

Demurrage stops at the out-gate. Detention starts there.
One event ends the first clock and begins the second, so a container can carry a closed demurrage total and an open detention total at the same time. Both are kept against the box and both are shown, rather than being added into a single figure that answers neither question.
The counterparty is part of the charge
Demurrage belongs to the terminal, detention to the carrier. Two rates, two invoices, two companies to write to. The board names who is on the other end of each row, because that is the first thing needed before anything can be done about it.
A box pulled before its earliest return date is counted
An export container out-gated ahead of the ERD is holding a carrier’s equipment while there is nowhere to return it to. Detention runs from the out-gate all the same. No arrival board shows the box, because it has not arrived anywhere and it has not sailed — which is why these are counted separately instead of being left to a screen that only knows about imports.

And one clause the audit does not cite.

The audit compares an invoice against twenty items in §541.6, and not one of the twenty comes from §541.4. That is deliberate, and the reason is worth knowing before the letter is relied on.

§541.4 was vacated

On 23 September 2025 the Court of Appeals for the D.C. Circuit vacated 46 CFR §541.4. It is not in force. An argument built on it is an argument a carrier can dismiss in a single line, and software that still checks against it is quietly producing findings that cannot be defended.

The letter therefore never relies on it

The twenty items and the thirty days sit in §541.6 and §541.7, which stand. A dispute letter that cites a vacated clause tells the person reading it that nobody checked, and the rest of the letter is then read in that light. The clause on each row exists so that the rule can be read at source, which only helps if the rule is still there.

What it does not do

Stated plainly, before the demonstration.

It does not file the dispute on the forwarder’s behalf
The letter is written, dated, and filled in with the missing items, the clauses and the two deadlines. Sending it to the carrier, and everything that follows, remains the forwarder’s responsibility. AMC does not act for the forwarder in front of a carrier or the Commission.
It is not legal advice
It is a comparison between an invoice and a published rule, with the clause printed on each row so that the rule can be read at source. What the company does about the answer is its own decision, and a lawyer’s if the amount is worth one.
It will not cite a vacated rule
§541.4 was vacated on 23 September 2025 and appears nowhere in the audit or the letter.
It does not go and look at the box
Milestones arrive through container tracking in the Connect extension, or from whoever keys them. Containers counts clocks off the events it is given; it does not fetch them.
No money moves here
A demurrage invoice and any credit that follows it are ordinary supplier bills against the shipment’s cost lines, and they reach QuickBooks with the rest. There is no general ledger in this system and no payment run.
Get a demo

A D&D invoice already paid, audited on the call.

The invoice is run against the twenty items of §541.6 during the call, the thirty days of §541.7 are counted from the last day charged, and the letter is printed with the clauses on it. If the invoice is clean, the demonstration says so.