When a freight charge is disputed, a reliable assessment can connect the invoice with cargo availability, notices, appointments, holds, equipment movements, contractual roles, calculation inputs and dispute steps. The invoice is one record in a longer event, not the whole event.
The chronology is most useful while systems and people still retain the underlying records, before each side’s position becomes the only surviving narrative.
Fact: the issue in 30 seconds
The Federal Maritime Commission’s final rule, Demurrage and Detention Billing Requirements, 89 FR 14330, addressed the permitted billing relationship, invoice timing and contents, and the minimum period and process for fee-mitigation, refund or waiver requests. The published rule stated an effective date of 28 May 2024 while initially delaying two provisions. The FMC then confirmed that the complete rule would take effect on 28 May 2024 after the required information-collection approval.
The current source record contains a material rule-and-court split. In No. 24-1088, the D.C. Circuit’s 23 September 2025 opinion severed and set aside 46 CFR 541.4. The FMC’s November 2025 case update identifies that provision as the affected billing-party restriction. The FMC’s FY2027 testimony describes the other rule provisions as remaining in effect while the Commission revisited the billing issue. The Ocean Shipping Reform Act implementation page collects related rulemaking, advisories and complaint information. The federal rule sources, court opinion, FMC case update and FY2027 testimony were accessible and checked on 23 August 2026.
This does not mean the legal position is static. Later rulemaking, case activity or guidance may change the split. The sources are US federal maritime materials and do not govern every shipment, charge, port, inland movement, contract or jurisdiction. Current case posture beyond the official sources reviewed, and the outcome of any individual charge dispute, are NOT_ASSESSED.
Signal: the parties have invoices but not the same timeline
Investigate when:
- The invoice date, charge period and cargo or equipment events cannot be linked.
- “Available” means vessel arrival in one system and actual pickup availability in another.
- A hold, inspection, terminal condition, appointment failure or release problem is recorded in only one party’s system.
- Notices were sent to an old contact, portal account or intermediary with no confirmed delivery path.
- The billed party, contracting party, consignee, shipper, trucker and account holder are treated as if they were one entity.
- Free-time rules, tariffs, service contracts and quoted commercial terms are mixed without hierarchy or date.
- Screenshots show a portal state but omit timestamp, timezone, shipment identity or later correction.
- A dispute is submitted without preserving the information the carrier, terminal or regulator says it needs.
Counter-signals include synchronized identifiers, system exports, dated notices, appointment records, gate events, stated calculation rules and a clear map of contractual roles. They do not prove that a charge is valid or invalid.
Action checklist: questions for one event table
The following questions can structure one row per material event while keeping the underlying records connected.
- Identity map. Can shipment, bill of lading, booking, container or equipment, voyage, terminal, invoice and purchase-order identifiers be connected while keeping the carrier, intermediary, shipper, consignee, terminal, trucker and billed-party roles distinct?
- Contract and rule layer. Are the service contract, tariff, bill terms, quotation, applicable rule, effective dates and later amendments preserved, with a source for each calculation assumption?
- Operational chronology. Are arrival, discharge, holds, release, actual availability, free-time start and end, appointment attempts, gate events, pickup, return and closure tied to source-system timestamps and timezones?
- Notice record. What was sent, to whom, through which channel and when? Can delivery or portal availability be shown separately from an automated message?
- Exception and control. Which weather, congestion, outage, equipment, terminal, government-hold or appointment events appear in the record, who controlled the condition and what mitigation was available without turning an allegation into a finding?
- Calculation bridge. Can each invoice line be reproduced from the stated period, rate, free time, exclusions, credits and tax, with unresolved differences left visible?
- Dispute path. Are the deadline, required content, submission receipt, response, escalation and current status recorded against the current official process rather than only a historical summary?
A shared event table becomes more testable when each correction identifies its participant and source. The objective is a testable record, not an artificially unanimous story.
Limitations: what this does not prove
Contract interpretation, tariffs, statutes, agency rules, court decisions, jurisdiction, causation, mitigation and procedural deadlines may change the analysis. Maritime movements can involve several legal regimes and inland segments. Source systems can be incomplete or use different time conventions.
The FMC source is time-sensitive and includes material later history. Any conclusion for a particular charge depends on current official rule and case status, contractual deadlines, complete facts and applicable professional analysis. This guide is general information, not maritime, customs, logistics or legal advice.
Owner Q&A
Did the court invalidate the entire FMC rule?
The official source record does not support that statement. It records that the D.C. Circuit set aside the billing-party restriction associated with 46 CFR 541.4, while the FMC later said the other provisions remained in effect and the issue was being revisited.
Does a complete event table show that a fee is invalid?
No. It makes the timeline, roles, calculation and contrary records testable. Contract terms, tariffs, rules, later legal developments and the facts determine what follows.
Which date should control the record?
No single date controls in the abstract. Each system’s event label, timestamp and timezone can be compared with the event used by the applicable contract or rule.
Next verification
Recheck the federal rule sources, FMC rulemaking and implementation pages, the D.C. Circuit docket and later action affecting 46 CFR Part 541 when the legal posture changes. Revisit the analysis if a shipment’s contract, tariff, route, roles, event record or dispute process differs from the source context.
Sources and limitations
- FMC final-rule publication, 89 FR 14330 and FMC effective-date notice — official rule sources.
- D.C. Circuit opinion in No. 24-1088 and FMC case update — official court and regulator sources for the affected billing-party provision.
- FMC FY2027 testimony — official regulator status context accessible and checked on 2026-08-23; describes the provisions other than 46 CFR 541.4 as remaining in effect at that check.
- Later case posture, later rulemaking and any individual charge outcome are NOT_ASSESSED.