NVOCC pass-through disputes: using the extra 30 days in § 541.7(c)

Stuck in the middle

An NVOCC sits on both sides of every D&D charge. The ocean carrier or terminal bills the NVOCC as the party on its bill of lading. The NVOCC bills its shipper or consignee on its own house bill. When the shipper disputes, the NVOCC either wins the same dispute upstream or absorbs the difference. For a 20-person forwarder running on thin margins, a few months of absorbed detention can erase the profit on an account.

Part 541 recognises this position directly. Section 541.7 has two NVOCC provisions, and § 541.6 applies to the NVOCC's own invoices just as it applies to the carrier's. Used together, they let an intermediary keep the dispute moving in both directions instead of being the place where charges stop.

Rule one: your own 30-day clock

Under 46 CFR § 541.7(b), an NVOCC acting as a billing party must issue its D&D invoice within 30 calendar days from the date of issuance of the invoice it received. If it misses that window, its billed party is not required to pay.

That is a different trigger from the carrier's clock. The carrier's 30 days in § 541.7(a) run from when the charge was last incurred. The NVOCC's 30 days run from when the carrier's or terminal's invoice was issued to it. The practical risk is internal: carrier invoices land in an operations inbox, wait for someone to match them to a house bill, and only then reach billing. A two-week internal delay turns a recoverable charge into one the NVOCC cannot pass on.

Rule two: the pass-through extension

Section 541.7(c) addresses the case where the NVOCC is both billed party and billing party for the same charge. If the NVOCC's own billed party disputes the charge, the NVOCC may notify its billing party (the carrier or terminal) of that dispute. The billing party must then allow the NVOCC an additional 30 calendar days from the notice to dispute the charge.

This matters because the NVOCC's own request window under § 541.8(a) runs from the date the upstream invoice was issued, and the customer's dispute may arrive late in that window. Without the extension, an NVOCC would have to dispute every upstream invoice defensively, before knowing whether its customer will object. With it, the NVOCC can wait for the customer, then notify upstream and build the dispute with the customer's evidence.

The notice itself should be clear and dated. Identify the upstream invoice, the containers, the fact that your billed party has disputed, and that you are invoking § 541.7(c). Keep the sent timestamp; the additional 30 days run from it.

Rule three: your invoice has to be compliant too

An NVOCC that forwards the carrier's PDF with a cover note is issuing a D&D invoice, and Part 541 applies to it. The NVOCC's invoice must carry all 20 elements in § 541.6: identifying, timing, rate, dispute and certification information. That includes its own contact details and public URL for requests, its own defined timeframes, and its own certification that the charges comply with the FMC's D&D rules and that its performance did not cause or contribute to them.

Element (a)(4), the basis for why the billed party is liable, deserves attention. The original rule's § 541.4 limited who could be billed; the D.C. Circuit vacated that section in World Shipping Council v. FMC on September 23, 2025, and the FMC removed it from the CFR in December 2025. The basis requirement in § 541.6(a)(4) remains. For most NVOCCs, the answer is the house bill and the customer agreement, and the invoice should say so.

Worked example: a Houston NVOCC and three containers

Bayou Gate Logistics, a 22-person NVOCC in Houston, receives a carrier demurrage invoice issued January 5, 2026 for three 40-foot containers moving for its customer Prairie Hollow Auto Parts. Each container is billed 9 days at $240 per day, so the invoice totals 3 x 9 x $240 = $6,480.

Bayou Gate's own deadline to invoice Prairie Hollow under § 541.7(b) is 30 days from January 5, which is February 4 (26 days to January 31, plus 4 into February). It issues a compliant invoice on January 9. On January 30, Prairie Hollow disputes 4 of the 9 days per container, with timestamped captures showing the terminal had no import appointments for those days. Bayou Gate sends a § 541.7(c) notice to the carrier on February 2. The carrier must allow 30 more days from that notice, so Bayou Gate has until March 4 to dispute upstream (26 days to February 28, plus 4 into March).

The upstream dispute uses Prairie Hollow's evidence and cites § 545.5(c)(2)(i). The disputed amount is 3 x 4 x $240 = $2,880; the accepted amount is 3 x 5 x $240 = $3,600. Bayou Gate holds the $2,880 in dispute with Prairie Hollow until the carrier responds, and passes the outcome through. Without the notice, Bayou Gate's own request window under § 541.8(a) could have closed as early as February 4, five days after the customer's dispute reached it.

Turning the customer's dispute into the upstream dispute

The extension only helps if the NVOCC uses the time to build a better file than the customer sent. A shipper's dispute is often an email with a screenshot. The upstream dispute needs the full structure a carrier billing desk expects: the carrier's invoice number and issuance date, the master bill and container numbers (not the house bill the customer knows), the timeline per container, the recalculated days, and the citation.

Three steps make that conversion routine. First, map the house bill to the master bill and the upstream invoice the day the customer's dispute arrives, so the § 541.7(c) notice can go out immediately. Second, ask the customer for its source evidence (appointment captures, trucker logs, gate tickets) rather than its summary of it. Third, add what only the NVOCC has: the carrier's arrival notice and release timing, the NVOCC's own freight payment records and any carrier advisories it received.

Then hold the customer's disputed amount open in your own receivables until the upstream answer comes back. Collecting from the customer while disputing upstream invites a second dispute; crediting the customer before the carrier credits you is how NVOCCs end up absorbing charges.

When a charge complaint involves an NVOCC

If a dispute ends in a charge complaint under 46 U.S.C. § 41310 against an NVOCC, § 41310(e) directs the FMC to consider whether the NVOCC is responsible for the charge in whole or in part, and whether another party is ultimately responsible. An NVOCC that passed a carrier charge through unchanged, notified upstream under § 541.7(c) and disputed in good faith has a clean record to show. One that sat on the customer's dispute does not.

Running it per client

The NVOCC / Forwarder plan is $3,500 per month with a tiered per-client pass-through, so the cost follows the clients who benefit. Upstream invoices are matched to house bills automatically through CargoWise or Magaya, the OSRA Audit Engine checks both the carrier's invoice and the NVOCC's outgoing invoice against § 541.6, and the clocks for § 541.7(b), § 541.7(c) and § 541.8 are tracked per container.

See /solutions/nvocc-forwarders for how multi-client workspaces are set up. ATAHSKIA prepares notices and dispute packets; the NVOCC decides what to send.