The 30-day issuance rule: how to spot and dispute late D&D invoices

What § 541.7 actually requires

Before Part 541, a D&D invoice could arrive months after the container moved, when nobody on the import team still remembered why a box sat at the terminal. The FMC's billing rule closed that gap. Under 46 CFR § 541.7(a), a billing party must issue a demurrage or detention invoice within 30 calendar days from the date on which the charge was last incurred. If it does not, the billed party is not required to pay the charge.

That sentence has three moving parts: who the billing party is (an ocean common carrier, including an NVOCC, or a marine terminal operator), what "issue" means (when the invoice was sent or made available to you), and what "last incurred" means (the final day the charge accrued). Get any of the three wrong and you either dispute a timely invoice, which wastes credibility, or pay a late one, which wastes money.

The rule took effect May 28, 2024 with the rest of Part 541 (89 Fed. Reg. 14330, February 26, 2024). It sits alongside the § 541.6 content requirements, so a timely invoice can still fail on missing elements, and a complete invoice can still fail on timing.

Finding the last-incurred date

For import demurrage, the charge stops accruing when the full container leaves the terminal, so the last-incurred date is normally the outgate date. For import detention (or per diem), the charge stops when the empty is returned, so the last-incurred date is normally the empty ingate at the return location. For exports, detention runs from empty pickup to the loaded ingate, and export demurrage, where charged, runs until the box is loaded or otherwise leaves the terminal's custody.

The invoice itself should tell you. Element (b)(8) of § 541.6 requires the specific dates for which demurrage or detention was charged, so the last charged date is printed on the invoice. Check it against the gate record anyway. Gate transactions come from the terminal's TOS and appear as outgate and ingate events in the carrier's EDI 315 feed, and they are the date you will rely on if the billing party disputes your count.

A practical note on counting: Part 541 speaks in calendar days, so weekends and holidays count. Count day 1 as the day after the last-incurred date. If a charge was last incurred on February 10, day 30 is March 12.

Proving the issuance date

The invoice date printed on the document is evidence of issuance, but it is not always the same as the day the invoice reached you. Some billing parties post invoices to a portal without notification; some email PDFs in batches; some generate the invoice in their system days before sending it.

Keep the record that shows when the invoice actually arrived: the email header timestamp, the portal posting date, or the EDI receipt log. If the printed date is inside the window but the invoice reached you outside it, you have a factual argument about issuance, and the timestamp is what supports it. If the printed date is already outside the window, the invoice concedes the point on its face.

This is also why your intake process matters. Invoices that sit in a shared mailbox for two weeks do not change the issuance date, but they do eat into your own § 541.8 request window, which runs from issuance.

Worked example: one late, one on time

Brookfield Kitchenware, a 1,800 TEU importer, receives two invoices for the same container in March 2026.

The first is an MTO demurrage invoice. The container was billed 7 days at $250 per day, so $1,750, and outgated on February 10, 2026. Thirty calendar days from February 10 is March 12 (18 days to February 28, plus 12 days into March). The invoice is dated March 19 and arrived by email the same day. That is 37 days after the charge was last incurred, so under § 541.7(a) Brookfield is not required to pay the $1,750. The dispute is two sentences long: the gate record, the invoice date, and the citation.

The second is a carrier detention invoice. The empty was returned February 20, 2026, and the invoice bills 9 days at $160 per day, $1,440. Thirty days from February 20 is March 22. The invoice is dated March 20 and arrived March 20, which is day 28. It is timely. If Brookfield disputes it, the argument has to be on content under § 541.6 or on the merits under § 545.5, not on timing.

Together the two invoices total $3,190. A team that treats both as late wastes a request on the detention invoice; a team that pays both pays $1,750 it did not owe.

NVOCC timing and wrong-party reissues

Two provisions modify the basic clock. Section 541.7(b) covers NVOCCs acting as billing parties. An NVOCC usually cannot invoice its customer until the ocean carrier or terminal invoices it, so its 30 days run from the issuance date of the invoice the NVOCC received, not from the last-incurred date. If the NVOCC misses that window, its own billed party need not pay.

Section 541.7(d) covers invoices sent to the wrong party. A billing party that invoiced an incorrect person may invoice the correct billed party, but only within 30 calendar days of when the charge was last incurred. A reissue does not restart the clock. If the original went to your customs broker on day 20 and the corrected invoice reaches you on day 41, the corrected invoice is late.

Section 541.7(c) adds a rule for NVOCCs that are both billed and billing party: when the NVOCC's customer disputes, the NVOCC can notify its own billing party and gets an additional 30 calendar days from that notice to dispute upstream. We cover that pass-through mechanic in detail at /resources/blog/nvocc-pass-through-disputes.

What a late-invoice dispute should say

A timing dispute does not need an argument about fairness, operations or rates. It needs three facts and a citation. State the last-incurred date and the record that proves it (the outgate or empty ingate event, with the gate receipt or EDI 315 message attached). State the issuance date and the record that proves it (the printed invoice date, plus your receipt timestamp). State the day count. Then cite § 541.7(a), or § 541.7(b) for an NVOCC invoice, and note that the billed party is not required to pay.

Send it inside the § 541.8 request window even though the invoice is unenforceable on its face. Silence can be read as acceptance by a billing desk, and a late invoice left unanswered has a way of reappearing on a statement of account three months later. A short, documented request closes the file.

Keep the tone flat. The goal is a credit memo, not a debate, and billing teams handle precise requests faster than angry ones.

Automating the clock

Timing checks fail in practice for one reason: the gate date and the invoice live in different systems. The invoice arrives in accounts payable; the outgate sits in a visibility tool or the terminal's website. Nobody puts them side by side until the invoice is already paid.

The OSRA Audit Engine pulls the last charged date from the invoice, the last gate event from Milestone & Gate Tracking, and the issuance timestamp from intake, then computes the day count automatically. Late invoices go straight to the Automated Disputes queue with the citation and evidence attached. The free /osra-dispute-calculator runs the same arithmetic for a single invoice.

ATAHSKIA prepares the analysis and the dispute packet; the billed party decides whether and how to send it. For contract-specific questions, consult maritime counsel.