Demurrage vs detention is one of the most common points of confusion in ocean freight. The words are often used together, but they usually refer to two different delay clocks. One is tied to a container sitting too long at a marine terminal. The other is tied to equipment being kept too long outside the terminal. Per diem adds another layer because it is often used as a daily equipment-use charge.
For import, drayage, and logistics teams, this is not just vocabulary. It affects pickup planning, document readiness, customer communication, finance review, and freight exception management. The Federal Maritime Commission says detention is charged for extended use of intermodal equipment, while demurrage accrues when a container exceeds free time on a marine terminal. [1]
The scale of the issue is also large. FMC data says nine ocean carriers collected roughly $15.4 billion in detention and demurrage charges between April 1, 2020, and March 31, 2025. [1] That does not mean every charge is avoidable. It does mean import teams need better operational context before small document problems turn into bigger delays.
Why Demurrage, Detention, and Per Diem Get Confusing
Demurrage, detention, and per diem are confusing because all three can appear near the same shipment, involve the same container, and be triggered by missed free time. The key difference is usually where the container or equipment is when the clock runs past the allowed time.
The FMC’s current regulatory wording treats demurrage or detention as charges, including per diem charges, related to the use of marine terminal space or shipping containers, excluding freight charges. [2] In plain English, these fees usually relate to space, equipment, or both.
Import teams often run into confusion when a shipment has several moving parts at once:
| Event | Possible Risk |
|---|---|
| Container arrives at terminal | Demurrage clock may start after free time |
| Customs clearance is delayed | Pickup readiness may be blocked |
| Delivery order is missing | Drayage provider may not be able to pick up |
| Container is picked up | Detention or per diem clock may start |
| Empty container is not returned on time | Equipment-use charges may accrue |
The problem gets harder when documents sit across inboxes, shared drives, PDFs, portal screenshots, and forwarded email threads. McKinsey notes that documentation for a single shipment can require up to 50 sheets of paper exchanged with up to 30 stakeholders. [3] That is exactly why a searchable shipment file and connected shipment record matter.
What Is Demurrage?
Demurrage is generally tied to a container staying too long at a terminal after the allowed free time. For an import shipment, this often means the container is discharged, becomes available, and then remains at the terminal beyond the free time window.
Demurrage can happen for many reasons. The cargo may not be customs cleared. The delivery order may not be released. Freight charges may not be paid. A terminal appointment may not be available. The drayage carrier may be waiting on pickup instructions. In each case, the container may still be sitting at the terminal while time keeps moving.
How Demurrage Usually Starts
Demurrage risk often starts before anyone sees a bill. A shipment blocker may be hiding in the document trail. For example, the arrival notice may be buried in email, the delivery order may be missing, or the customs release may not be visible to the person scheduling drayage.
A strong import workflow should connect terminal status, document readiness, and pickup readiness. That means the team should know:
| Question | Why It Matters |
|---|---|
| Is the container available? | Confirms whether pickup can happen |
| Is customs cleared? | Blocks release if incomplete |
| Is the delivery order available? | Needed by drayage teams |
| Is the last free day known? | Shows urgency |
| Is an appointment booked? | Converts readiness into action |
| Is any hold active? | Explains why pickup is blocked |
This is where shipment document intelligence helps. It does not need to make bold promises. It helps teams organize documents, identify missing information, understand blockers, and act earlier.
What Is Detention?
Detention usually applies when equipment is kept outside the terminal beyond the free time allowed by the carrier or contract. In an import move, detention can begin after a full container is picked up and continue until the empty container is returned.
Think of demurrage as a terminal-space problem and detention as an equipment-use problem. That simple mental model helps teams avoid mixing up the two clocks.
Why Detention Is Often Called Per Diem
Per diem means “per day.” In container shipping, it is often used to describe a daily charge for keeping equipment beyond allowed free time. The federal definition of demurrage or detention includes per diem charges related to marine terminal space or shipping containers. [2]
For import teams, the practical lesson is clear: do not stop tracking after pickup. Pickup may end one risk, but it can start another. Once the container leaves the terminal, teams still need to monitor delivery, unloading, empty return instructions, return appointments, and empty return confirmation.
Demurrage vs Detention vs Per Diem: Quick Comparison
| Term | Simple Meaning | Common Import Trigger | Operational Focus |
|---|---|---|---|
| Demurrage | Container stays too long at terminal | Container not picked up before free time ends | Pickup readiness |
| Detention | Equipment kept too long outside terminal | Empty container not returned on time | Empty return readiness |
| Per diem | Daily equipment-use charge | Often tied to detention-style billing | Equipment clock tracking |
This is the easiest way to explain demurrage vs detention to a new import coordinator: demurrage is usually before pickup, detention is usually after pickup, and per diem is often the daily charge tied to equipment use.
Why Import Teams Should Track LFD and Return Deadlines Separately
Last Free Day, or LFD, is important, but it is not the only deadline. Import teams should track at least two clocks:
| Clock | What It Tracks |
|---|---|
| Terminal free time | How long the container can remain at the terminal |
| Equipment free time | How long the container can be outside before return charges apply |
A team that only tracks terminal LFD may avoid demurrage but still run into detention or per diem because the empty return was late. A team that only tracks return deadlines may miss the fact that the container is not ready for pickup in the first place.
The FMC’s 2024 final rule on detention and demurrage billing practices requires minimum invoice information and addresses timing and billing practices. [4] A later court decision set aside one section, 46 CFR 541.4, about who may receive an invoice, but the FMC says the rest of the rule remains in effect. [5] This article is operational, not legal advice, so teams should confirm billing questions with qualified counsel or compliance experts.
Last Free Day Is Not the Whole Story
LFD is a deadline. It does not explain whether the shipment is actually ready. A container may be inside free time but still blocked. Common shipment blockers include:
- missing delivery order
- customs hold
- exam hold
- unpaid freight or terminal charges
- no appointment slot
- missing pickup number
- chassis issue
- unclear empty return location
- mismatched container number on a document

That is why document readiness and pickup readiness should be managed together. A container-level document view helps the team see what is present, what is missing, and what action is needed next.
Common Shipment Blockers That Create D&D Exposure
Many D&D problems begin as basic information problems. The container is not necessarily ignored. The team may simply not know that something is missing until the clock is already tight.
Operations teams commonly report recurring issues such as surprise charges, poor communication, limited visibility near LFD, appointment issues, customs holds, chassis shortages, and paperwork delays. Forwarders often deal with cases where a missing document, late payment, customs delay, or terminal issue causes the container to sit and accumulate charges.
Missing Document Detection Before Pickup
Missing document detection is one of the most practical ways to reduce confusion. It should answer simple questions:
| Document or Signal | Why It Matters |
|---|---|
| Bill of lading | Confirms shipment identity and cargo movement |
| Arrival notice | Shows arrival and release instructions |
| Delivery order | Supports pickup authorization |
| Commercial invoice | Supports customs and finance review |
| Packing list | Supports cargo details and customs review |
| Appointment confirmation | Confirms pickup plan |
| Customs release | Confirms clearance status |
| Empty return instructions | Supports return planning after delivery |
A team does not need a magic button. It needs a dependable way to see missing information earlier.
How Scattered Shipment Documents Create Operational Risk
Freight delays often start as document problems. An arrival notice sits in one inbox. A delivery order is attached to a forwarded email. A customs release is in a broker portal. A terminal screenshot is saved locally. A drayage appointment is in a text thread.
When that happens, a shipment manager may have visibility in theory but not operational context in practice. The file exists somewhere, but the team cannot quickly answer, “Is this container ready to pick up?”
The core problem is clear: operations depend on BOLs, delivery orders, invoices, arrival notices, and vendor paperwork, but those files are often scattered across inboxes, shared drives, and forwarded email chains, leading to missed LFDs, delayed pickups, slow clearance, reconciliation work, and payment timing issues.
That is where an AI document hub can help. It creates a central place for shipment document intelligence, document-to-container matching, and a searchable shipment file.
How an AI Document Hub Supports Freight Exception Management
An AI document hub should not promise to eliminate demurrage or fully automate freight operations. A safer and more useful promise is this: it helps teams organize documents, identify missing information, understand blockers, and act earlier.
For import teams, that means turning scattered documents into a connected shipment record. Each shipment record should show the containers, documents, dates, status signals, owners, and blockers that matter.
Connected Shipment Record
A connected shipment record brings the shipment file together in one place. Instead of asking five people for updates, the team can open one record and see the latest operational context.
A good connected shipment record may include:
| Field | Example |
|---|---|
| Shipment reference | Booking, house bill, master bill |
| Container number | ABCD1234567 |
| Carrier | Ocean carrier or NVOCC |
| Terminal | Arrival terminal |
| LFD | Last free day |
| Pickup appointment | Confirmed or missing |
| Required documents | Present, missing, or mismatched |
| Shipment blocker | Customs hold, missing DO, no appointment |
| Next action | Request release, book pickup, confirm return location |
DCSA’s Track & Trace standards show why common data models matter in container shipping: they support cross-carrier shipment tracking and more unified digital communication among supply chain participants. [6]
Container-Level Document View
A container-level document view helps users avoid one of the most common operational traps: assuming a document applies to a container when it does not. If a shipment has multiple containers, the team needs to know which delivery order, pickup number, appointment, release, and return instruction belongs to which container.
Document-to-Container Matching
Document-to-container matching helps the team connect PDFs, emails, and extracted fields to the right container. That matters when one shipment includes multiple containers with different availability dates, holds, or appointments.
Searchable Shipment File
A searchable shipment file lets a coordinator search by container number, bill of lading, customer, carrier, reference number, or document type. This is simple, but powerful. It reduces the time spent digging through old emails and helps the team answer urgent questions faster.
Practical Workflow for Better Document Readiness
Here is a practical daily workflow for import teams:
| Step | Action | Goal |
|---|---|---|
| 1 | Review arrivals for the next 7 days | Catch document gaps early |
| 2 | Check each connected shipment record | Confirm documents and milestones |
| 3 | Flag missing documents | Create a clear owner and next action |
| 4 | Review container-level document view | Match each document to the right container |
| 5 | Confirm customs and release status | Improve pickup readiness |
| 6 | Check appointment status | Move from “ready” to “scheduled” |
| 7 | Watch empty return instructions | Reduce post-delivery confusion |
| 8 | Log shipment blockers | Build operational context for the team |
| 9 | Escalate urgent exceptions | Act before delays grow |
This kind of freight exception management does not guarantee that every fee will be avoided. It does help teams work from cleaner information, spot blockers sooner, and make better decisions under time pressure.
FAQs About Demurrage, Detention, and Per Diem
What is the main difference between demurrage and detention?
Demurrage usually applies when a container remains at the terminal beyond free time. Detention usually applies when equipment is kept outside the terminal beyond free time. The FMC summarizes it this way: detention is for extended use of intermodal equipment, while demurrage accrues when a container exceeds free time on a marine terminal. [1]
Is per diem the same as detention?
Per diem is often used as a daily equipment-use charge, so it is commonly connected to detention-style charges. Under federal wording, demurrage or detention can include per diem charges related to marine terminal space or shipping containers. [2]
Why do import teams confuse demurrage vs detention?
Teams confuse demurrage vs detention because both relate to free time, delays, and containers. The simplest way to separate them is location: demurrage is usually tied to the terminal, while detention is usually tied to equipment outside the terminal.
Can better documents help reduce D&D risk?
Better document organization can help teams act earlier, but it should not be framed as a guarantee. An AI document hub can support document readiness, missing document detection, pickup readiness, and shipment blocker visibility.
What documents are most important for pickup readiness?
The most important documents often include the bill of lading, arrival notice, delivery order, customs release, payment confirmation, pickup appointment, and terminal release information. The exact list depends on the carrier, terminal, broker, customer, and shipment type.
What should a team do when a container is blocked?
The team should identify the blocker, assign an owner, confirm the deadline, and decide the next action. For example, if the delivery order is missing, the next action may be to contact the forwarder or carrier. If customs is not cleared, the next action may be to contact the broker.
Does Zettel AI automate D&D disputes?
No. The safer product promise is operational: Zettel AI helps teams organize documents, identify missing information, understand blockers, and act earlier. It can support a clearer shipment record and better evidence organization, but it should not be described as automatically filing or resolving D&D disputes.
Conclusion
Demurrage, detention, and per diem are easier to manage when teams understand the different clocks. Demurrage is usually about terminal time. Detention is usually about equipment time. Per diem is often the daily equipment-use charge that appears when free time is exceeded.
The bigger lesson is operational. Delays often begin with scattered documents, unclear ownership, and missing information. When import and drayage teams work from a connected shipment record, container-level document view, and searchable shipment file, they can see what is missing, what is blocked, and what needs action next.
That is the practical value of shipment document intelligence. It does not need to make unrealistic promises. It helps logistics teams organize the work, understand the operational context, and act before small document gaps become larger freight exceptions.
Sources
- [1] Federal Maritime Commission
- [2] eCFR
- [3] McKinsey & Company
- [4] Federal Register
- [5] Federal Maritime Commission
- [6] DCSA



