Export earliest return dates and rolled bookings: disputing detention you could not avoid

The export side of D&D

Most D&D discussion is about imports, but exporters carry the same clocks in reverse. Detention starts when the trucker picks up the empty, runs while the box is loaded at the shipper's facility, and stops when the loaded container ingates at the terminal. If free time runs out before the terminal will take the box, detention accrues on days the exporter could do nothing about.

The exposure is sharpest for agricultural and forest products exporters, who load to harvest and mill schedules, work with thin per-container margins, and often book space weeks ahead. A single roll can push a full set of loaded boxes past free time while they wait at a warehouse or on the street for a terminal that will not receive them yet.

What the ERD element requires

The earliest return date (ERD) is the first day a terminal will accept a loaded export container for a given vessel. It is set by the vessel schedule and the terminal's receiving rules, and it moves when the schedule moves.

Part 541 makes the ERD part of the invoice. 46 CFR § 541.6(b)(7) requires every export demurrage or detention invoice to state the earliest return date, alongside the allowed free time, the free time start and end dates, and the specific dates charged. An export invoice without an ERD fails the element check, and under § 541.5 that failure eliminates the billed party's obligation to pay.

When the ERD is present, it gives you the comparison that matters: did free time end before the terminal would accept the box? If it did, the invoice itself shows that detention ran while return was impossible.

How rolls and ERD changes create charges

Three patterns account for most export disputes we prepare. In the first, the vessel is delayed or a sailing is cancelled and the ERD moves later after the empty has already been picked up and loaded. In the second, the booking is rolled to a later vessel, so the box that was on time for the original ERD is now early for the new one. In the third, the loaded box was already ingated when the roll happened, and it sits at the terminal past export free time, generating demurrage instead of detention.

In every case, the question under 46 CFR § 545.5 is whether the charge served its purpose as an incentive for cargo and equipment fluidity. An exporter cannot return a loaded box earlier than the terminal will receive it, and cannot make a rolled vessel arrive sooner. The empty-return paragraph, § 545.5(c)(2)(ii), says that absent extenuating circumstances, detention that does not serve its incentive purpose, such as when containers cannot be returned, is likely to be found unreasonable.

• Vessel delay or blank sailing moves the ERD after empty pickup
• Booking rolled to a later vessel, resetting the ERD
• Loaded box ingated, then rolled, accruing export demurrage at the terminal

The certification question

Every Part 541 invoice must certify, under § 541.6(e)(2), that the billing party's performance did not cause or contribute to the underlying charges. When the ocean carrier that rolled the booking then bills detention for the days the roll created, that certification deserves a hard look.

This is a factual argument, not an automatic one. Rolls happen for many reasons, including late documentation or a missed cutoff on the exporter's side. Before citing the certification, confirm from the booking history that your documents, VGM and cargo were on time for the original vessel. If they were, the roll was the carrier's, and the charge flows from it.

Worked example: six containers and a rolled booking

Sierra Basin Walnut Growers, an agricultural exporter, books six 40-foot containers on a vessel with an ERD of July 14, 2025. Its trucker picks up the empties on July 8. The carrier's export detention free time is 7 days, counting the pickup day, so free time covers July 8 through July 14. The boxes are loaded and ready for ingate on July 14.

On July 11 the carrier rolls the booking to the next sailing and issues a revised confirmation with an ERD of July 21. The terminal will not receive the loaded boxes before then. Sierra Basin's trucker is busy on July 21 and 22 and ingates all six on July 23. The detention invoice bills July 15 through July 23: 9 days at $175 per container, for 6 x 9 x $175 = $9,450.

The dispute separates the days. July 15 through July 20 (6 days) the terminal would not accept the boxes because of the carrier's roll, so Sierra Basin disputes 6 x 6 x $175 = $6,300. July 21 through 23 (3 days) the terminal was receiving and the delay was Sierra Basin's own, so it accepts 6 x 3 x $175 = $3,150. The check: $6,300 + $3,150 = $9,450. The packet attaches the original and revised booking confirmations with timestamps, the documentation cutoff receipts showing Sierra Basin was on time, the invoice's printed ERD, and the gate receipts.

Writing the export request

Lead with the dates, because export disputes are date disputes. The first lines of the request should show, per container: empty pickup, free time end as printed, the original ERD, the revised ERD and when it was issued, and the loaded ingate. A reviewer who sees the revised ERD fall after the printed free time end understands the dispute before reading the argument.

Then show the split between blocked days and the exporter's own days, with the arithmetic, and the basis: § 545.5(c)(2)(ii) for detention while the terminal would not receive the box, and the § 541.6(e)(2) certification where the carrier's roll caused the charge. If the invoice has no ERD, or an ERD that matches neither booking version, put the § 541.5 point at the top.

Accepting the days that were yours is not a concession of the argument. It is what makes the rest of the request credible, and it narrows what the billing party has to resolve inside its 30-day window.

Evidence specific to exports

Export disputes depend on a paper trail that most import teams never keep. Save every booking confirmation and amendment, not just the final one, because the original ERD is the anchor for the argument. Save the carrier's roll notice and its timestamp. Save documentation cutoff and VGM submission receipts, which show whether the exporter caused the roll. Save the terminal's receiving schedule for the vessel, captured on the days the box was waiting.

Then match those to the equipment events: empty outgate, loaded ingate, and, for boxes rolled after ingate, the load or departure event. Carrier EDI 315 messages or API milestones carry most of these. If the invoice's ERD does not match the ERD on the latest booking confirmation, that discrepancy goes first in the request.

Building the habit

The exporters who recover the most are the ones whose operations teams treat each booking amendment as a document to keep, not an email to skim. Milestone & Gate Tracking stores booking versions and ERD changes per container, and the OSRA Audit Engine compares the invoice's ERD and free time dates to the booking history automatically. Our /solutions/agricultural-exporters page covers how this works for harvest-season volumes.

Send the request inside the § 541.8(a) window, which gives at least 30 calendar days from invoice issuance, and track the billing party's 30-day resolution window under § 541.8(b). ATAHSKIA prepares the analysis and the packet; the exporter decides what to send.