Container charges: reconstruct demurrage and detention clocks
A container invoice compresses several clocks into one amount. Cargo can be available at a terminal while equipment later remains outside it, and a return appointment or port closure can affect the evidence for particular charged days. Research needs a daily event ledger before it can explain how a charge arose or why part of it is disputed.
This guide concerns US ocean-shipping evidence within the stated FMC context. Its rates, days and events are fictional contract assumptions. It reconstructs billing arithmetic and documented objections; it does not declare a real invoice payable, unenforceable or automatically refundable.
Locate the charge and case boundaries
The FMC Detention and Demurrage page, under its data section, distinguishes extended use of equipment from container time beyond free time on a marine terminal. Use that distinction to identify the physical clock, then read the actual tariff or contract for start, end, free time and rate details.
The FMC’s July 8, 2026 account of the court decision concerns detention during a three-day closure and the trucker’s lack of a practical earlier return opportunity. It explains the freight-fluidity purpose applied to those facts. It is not a blanket rule that every weekend, holiday or closure makes every container charge invalid.
Rebuild the four-day equipment invoice
Assume a specific agreement grants equipment free time through Friday at 23:59 local terminal time. It expressly charges one hundred per calendar day thereafter, including the actual return day, with no tier changes in this example. Equipment is accepted back at 10:00 Tuesday, so the invoice counts Saturday, Sunday, Monday and Tuesday: four days, four hundred.
The supplied evidence also says the assigned return facility was closed Saturday through Monday. The cargo owner did not release the emptied equipment until Friday at 20:00, after that facility’s 17:00 closing, and no authorised alternative was available. These are explicit hypothetical facts to investigate, not assumptions that every closure necessarily satisfies.
| Charged day | Contract arithmetic | Supplied availability evidence |
|---|---|---|
| Saturday | 100 | Assigned return facility closed |
| Sunday | 100 | Assigned return facility closed |
| Monday | 100 | Assigned return facility closed |
| Tuesday | 100 | Actual return accepted at 10:00 |
| Total | 400 | Four days under the stated agreement |
The closure-related objection identifies three days and three hundred of the four-hundred invoice. It does not by arithmetic alone establish a three-hundred credit. Tuesday’s one hundred is outside this particular closure argument, but that does not establish its ultimate legal treatment either. Keep invoiced amount, argued adjustment and final disposition as separate fields.
Test the practical earlier-return boundary
Change one mechanism: suppose equipment was actually empty and released Thursday morning, and an authorised return location had available appointments on Thursday and Friday. The same Saturday–Monday closure now has a different surrounding fact pattern. Preserve the earlier opportunity rather than copy the first case’s conclusion merely because the closure lasted three days.
Conversely, a facility marked open on a website does not prove the specific equipment could be returned. Match the carrier’s return instruction, accepted equipment type, appointment availability, restrictions and actual attempted return. An unusable appointment for a different container class is not evidence of a practical return path for this container.
Record what was known at the relevant time. A later gate schedule cannot by itself show which appointments were offered on Friday. Save contemporaneous instructions, booking attempts, rejection messages and time zones. Where those records are absent, describe the gap rather than invent a failed attempt or assume that a general opening time proves actual acceptance.
Keep terminal and equipment clocks distinct
For a separate example, assume cargo is available Monday, terminal free time covers Monday and Tuesday, and gate-out occurs Wednesday. A stated contract charging eighty for every post-free-time calendar day through gate-out produces one terminal day, eighty. This is a terminal-time calculation under supplied assumptions.
Now assume the equipment agreement grants Wednesday through Friday free after that gate-out, and the equipment is returned the following Monday. Under an explicitly assumed calendar-day rule including return day, equipment days are Saturday, Sunday and Monday, at one hundred each: three hundred. With no other adjustments, the two distinct assumed charges total 380.
Do not start equipment detention from vessel arrival merely because the terminal clock began earlier. Do not continue terminal time after the container has left under a contract that stops it at gate-out. Different counterparties may use different labels, so store the contract’s own wording alongside the physical location and event boundary.
Check rate tiers and day-count rules
The four-day main case assumes a flat calendar rate. A different contract could count working days, exclude a specified day, stop before the accepted-return day or change rates after a threshold. Those are inputs requiring evidence, not optional settings chosen to reproduce an invoice.
For an independent tier check, assume the first two chargeable days cost one hundred each and the next two 150 each. Four days then cost five hundred, not four hundred. A correct day count with a wrong rate table still gives a wrong bill. Preserve rate effective date, currency, equipment size and the exact free-time provision used.
If events cross midnight, retain local timestamps and the contractual day definition. A 00:05 return can fall on another chargeable day under one agreement, but the worksheet should not round it backward to fit a more favourable amount. An invoice date is a separate clock from physical storage or equipment use.
Separate billing, collection and dispute outcomes
For a separate financial illustration, four hundred is billed, fifty waived, 350 paid and twenty later refunded. Net cash retained from this invoice is 330. That is not the originally billed four hundred or the 350 collected before refund. A company-level collection ratio must specify whether it uses gross bills, adjusted bills or final net receipts.
A dispute submitted is not a credit received. Keep the submission date, invoice reference, amount contested, response and any actual adjustment or refund. If a company records a receivable allowance, connect that accounting evidence separately; a disputed operational charge does not by itself establish the final accounting loss.
Quarterly carrier totals on the FMC overview are aggregate data with their own coverage. They cannot validate the eligibility or cash outcome of an individual invoice. Likewise, a refund received this quarter can concern a much older container, so monthly cash receipts and newly billed days need not belong to the same cohort.
Use the daily container verification sheet
| Field | Obtain | Check |
|---|---|---|
| Identity | Container, invoice and contractual parties | Same equipment and charge type |
| Free time | Applicable contract or tariff version | Start, end and day convention |
| Events | Availability, gate-out and accepted return | Actual timestamp and local zone |
| Return path | Instructions, gate hours and appointments | Practical authorised acceptance |
| Amount | Daily tiers, currency and invoice lines | Reproduce each charged day |
| Outcome | Objection, credit, payment and refund | Claimed adjustment distinct from actual cash |
Start with the invoice and reconstruct the physical timeline independently. Obtain the applicable documents before asserting billing deadlines or procedural rights; the two general sources cited here do not supply a universal deadline for every invoice. Preserve contractual and regulatory version information for the actual question being reviewed.
When carrier, terminal and haulier records conflict, compare the event each timestamp represents. Appointment booked, truck arriving and gate accepting equipment are different events. Keep the unresolved interval and request the specific acceptance or rejection record rather than select whichever timestamp generates the preferred charge.
New gate logs, corrected return instructions, tariff versions, dispute decisions or settlement movements trigger updates. Preserve the original invoice and identify each adjustment. The resulting conclusion should explain days, rates, practical availability and final cash separately, with the exact unresolved facts that could change the result.
Reconcile invoice lines before adding container totals
An invoice may identify more than one equipment object or separate charge lines. Match each line to its own container or chassis reference, rate basis and interval before aggregating. A second line is not automatically a duplicate, while the same container and charge repeated across a revised invoice should not be counted as another physical use period.
Keep original, cancelled and replacement invoices linked. If a revised bill replaces four hundred with three hundred, the open billed amount is not seven hundred unless evidence establishes two independent obligations. This document relationship check is separate from the daily arithmetic and can explain a reconciliation failure even when every line’s day count is correct.
FAQ
Does a closed terminal automatically remove every charge during closure?
No. The applicable rule, actual return options and surrounding facts must be established.
Is a dispute submission the same as a refund?
No. Record the objection and the actual financial outcome separately.