Logistics & supply chain / Finance

Separate demurrage, detention and terminal storage before checking a bill

By Vikasraj YadavPublished 6 min read

For import-export operations and logistics finance teams · Understand the problem

TL;DR — what you’ll learn

  • Identify the issuer, agreement and charging period behind each container-related invoice line.
  • Demurrage, detention and terminal storage can use different clocks; do not infer the rule from the label alone.
  • Check start/end events, inclusive dates, calendars, equipment and movement scope before counting chargeable days.
  • Preserve disputed event evidence and approved free-time changes alongside the calculation.

Topics: demurrage and detention · container detention charges · port storage charges · container free time India

Grade-A 3PL distribution centre dispatch bay and freight verification desk with pallet racking, barcode scanner, parcel weighing scale and loading dock doors in natural daylight

Illustrative 3PL warehouse dispatch and freight verification desk; not a client facility.

All quantities, amounts, product codes and events are illustrative teaching examples.

The import file contains a carrier charge and a terminal storage bill. Both refer to the same container and several of the same dates. Finance suspects duplicate billing, while the operations team says the charges measure different things.

Start by identifying what each agreement charges for and which events start and stop its clock. Similar dates do not prove a duplicate, and different labels do not prove that both lines are valid. Reproduce each line under the applicable terms before deciding what to approve or challenge.

Treat the labels as questions to investigate

Container demurrage and detention commonly distinguish periods associated with equipment at a terminal and equipment outside it, but carriers can define separate or combined arrangements. Terminal storage concerns the relevant terminal's occupancy/service terms. The actual tariff, booking agreement and movement determine the calculation.

OOCL's India page illustrates why labels are insufficient: its import section starts the listed detention clock at terminal discharge for local cargo, while the export section uses different event boundaries. It also distinguishes terminal storage terms. These are carrier-specific definitions, not universal rules. OOCL India — Demurrage and detention free time and charges.

For every line, record the issuer, customer/booking agreement, import or export direction, port/ICD or terminal, equipment type, validity period and charge basis. Establish whether free time is separate, combined or amended for the shipment.

Rebuild the journey from evidence

Keep discharge or availability, terminal gate events, pickup, delivery and empty-return evidence as distinct milestones. A planned event is not the same as a confirmed event. A truck's GPS position near a depot may support an investigation without proving that the depot accepted the empty container.

Scroll horizontally to see all columns.

Evidence Question it helps answer Limitation to resolve
Carrier/terminal event What event was recorded and when? Confirm event meaning, actual/planned status and timezone
Gate receipt Was equipment received or released at the named facility? Match container, movement and timestamp
Empty-return acknowledgement Did the authorised return location accept the equipment? Check rejection, redirection or later correction
Booking/free-time agreement Which rule applies? Confirm version, scope and authorised amendments
Invoice detail Which dates and rate bands were charged? Reproduce the count rather than accept a total

If records disagree, preserve both and obtain an explanation from the responsible party. Replacing one timestamp with another solely because it reduces the charge destroys the evidence needed for a credible dispute.

Work through three fictional clocks

The following illustrative import example uses invented separate-clock terms. It does not represent OOCL's India import tariff described above. All dates use the agreed local calendar; the example rules include their start and end dates.

The container's defined start event is 10 June. It gates out on 16 June and its empty return is accepted on 21 June.

Scroll horizontally to see all columns.

Example charge Fictional free-time rule Last free date Chargeable dates under that rule
Carrier demurrage Five days from 10 June through gate-out 14 June 15–16 June: two days
Terminal storage Three days from 10 June through gate-out 12 June 13–16 June: four days
Carrier detention Four days from gate-out on 16 June through empty return 19 June 20–21 June: two days

These counts are valid only under the stated fictional inclusive rules. The table demonstrates why one container can have several deadlines and why the gate-out date can participate in more than one defined clock. It does not establish that such overlapping charges are payable under any real agreement.

A combined free-time arrangement would need a different calculation. Do not add the separate allowances above and assume the combined entitlement is equivalent.

Separate the count from the commercial resolution

First reproduce the billed dates and applicable rate bands. For a further fictional storage calculation, charge the first two chargeable days at ₹600 per day and the next two at ₹900. The four storage days above cost (2 × ₹600) + (2 × ₹900) = ₹3,000 before applicable tax. Charging every day at the final ₹900 band would give ₹3,600, a ₹600 difference.

This example indexes bands from the first chargeable day. An actual tariff may define its bands differently, so retain that basis as well as the daily rates. Then assess missing evidence, disputed applicability, approved extensions, waivers and contractual claims. An operations delay may explain what happened without automatically creating an entitlement to extra free time.

The carrier or terminal account owner should obtain the governing terms and clarify disputed events. Operations supplies the journey evidence. Finance reviews the resulting bill or adjustment. Qualified commercial/legal review is appropriate where entitlement remains contested.

A useful dispute record identifies the exact line, the carrier's calculation, the alternative supported calculation and the source of the difference. “Container delayed by customs” is context, not a complete explanation of which contractual clock should change.

Keep the review sequence explicit

Review flow: classify the charge and issuer → confirm applicable terms → assemble actual event evidence → calculate free and chargeable dates → compare rate bands and invoice → route disputed applicability or evidence. Where the start event is uncertain, show a provisional calculation and an owner rather than a definitive payable amount.

A controlled worksheet can be adequate for a small population. An alert or billing system becomes useful when many containers require repeated event updates and deadline changes. In either case, store the rule version and calculation inputs so the result can be reproduced later.

Measure charges with complete evidence, disputed value by cause and time to resolve the underlying case. Avoid presenting all avoided or reduced charges as savings unless the counterfactual and actual settlement support that conclusion.

Explain each clock before approving the bill

Container-charge review depends on the relationship between an agreement and an evidenced journey. Keeping those relationships separate allows finance to recognise legitimate differences between charges and identify unsupported ones without relying on labels.

Next actions

  1. Select one container with carrier and terminal charges.
  2. Obtain the applicable agreements and their effective scope.
  3. Reconstruct the actual event timeline and record any conflicting evidence.
  4. Reproduce each clock independently, including its counting convention.
  5. Route the remaining commercial difference to the authorised owner before settlement.

Discuss this workflow

Describe your current systems, the recurring exception and the outcome you need. Keep shipment, customer and financial records out of the initial message.

Draft an assessment email

References

Sources checked 15 October 2026. Vendor documentation supports platform facts; the worked examples and diagrams are original.

About the author

Vikasraj Yadav writes about operational decisions, software and automation for NextEdge Labs.