A working guide to demurrage claim tracking

Laytime runs, a vessel waits, and a claim becomes payable. Whether it is recoverable depends on documents gathered in the days after the event, not on the rate in the charter.

What is demurrage and how is a claim tracked?

Demurrage is the liquidated amount payable when a vessel is detained at berth or anchorage beyond the laytime allowed in the charterparty or sale contract. Tracking a claim means holding four things together: the laytime allowance and exceptions as written in the governing terms, the timeline of events evidenced by the notice of readiness, statement of facts and pumping logs, the calculation applying the contractual conventions to that timeline, and the notification and documentation deadlines, commonly ninety days, after which the claim is time barred regardless of merit.

Last updated: September 25, 2026 · Reviewed by the Aavenir Oil, Gas & Mining practice

Key takeaways

  • ✓Time bars extinguish valid claims. The deadline is a contract obligation, not an administrative preference.
  • ✓Laytime exceptions do most of the work in a dispute. Extract them per contract rather than assuming a standard.
  • ✓Evidence quality at load and discharge decides outcomes. Collect it while the vessel is still there.
  • ✓Track claims by cargo movement, not by invoice, so the calculation and the documents stay attached.

Demurrage sits in an awkward place organizationally. It is a commercial exposure created by operational events, calculated by chartering or shipping specialists, invoiced through finance, and governed by terms that were negotiated by a trading desk under time pressure. Every function touches part of it and no single function owns the whole claim.

The financial consequence is easy to underestimate because it arrives in many small pieces rather than one large one. A handful of hours at a congested terminal, repeated across a year of liftings, accumulates into a material number. Industry practice has long treated a portion of demurrage as unrecoverable leakage, and the causes are usually procedural: the statement of facts was signed with a protest that nobody followed up, the pumping log was never obtained, or the claim was submitted three days after the documentary deadline in the charter.

The useful framing is that demurrage is an obligation management problem wearing shipping clothes. There is a deadline, an evidence requirement, a calculation with contractual conventions, and a counterparty who will decline anything incomplete. Organizations that treat it that way recover materially more than those that treat it as a dispute to be argued after the fact.

Why recoverable demurrage goes unrecovered

The recurring causes are documentary and procedural. Very few claims are lost on the substance of the laytime calculation itself.

  • Time bar missed, most charters and sale contracts require notice and full supporting documents within a fixed window, and a late claim fails regardless of how strong it is.
  • Incomplete document set, the counterparty rejects the claim because one item is missing, the clock keeps running, and the resubmission arrives after the bar.
  • Unchallenged statement of facts, the master or terminal records a version of events that starts laytime earlier than it should, and no letter of protest is issued at the time.
  • Wrong conventions applied, the calculation uses a standard practice rather than the exceptions actually written into that contract, and the difference is argued away.
  • No single owner per movement, chartering, operations, trading and finance each hold part of the file, and nobody is accountable for the claim as a whole.

These are all controllable. What they require is that the deadline and the document list be extracted from each contract at the point of fixture and attached to the specific cargo movement, so the operational team knows what to collect before the vessel sails. This is the same extraction discipline that keeps rate schedule compliance from drifting.

The time bar is the control that matters most

Read the notification clause carefully, because the variations matter. Some contracts require notice of a claim within one period and full documentation within another. Some specify which documents constitute a complete claim. Some start the clock at completion of discharge and others at the date of the bill of lading. Capture the trigger event, the notice period and the documentation period as three separate fields per contract, and drive reminders from the trigger rather than from the invoice date.

The control set for demurrage exposure

Five controls, applied per cargo movement rather than per counterparty, cover the majority of recoverable value.

  • Terms extracted at fixture. Laytime allowance, rate, exceptions, notice of readiness requirements, time bar triggers and the required document list, captured as fields against the movement.
  • Event evidence collected at the port. Notice of readiness with tender time, statement of facts, timesheets, pumping logs, ullage reports and any letters of protest, gathered before the vessel departs.
  • Protest discipline. A standing instruction that any disputed entry in the statement of facts triggers a written protest at the time, since a protest issued later carries far less weight.
  • Calculation against the governing terms. The laytime computation applies that contract exceptions and conventions, with the version of terms used recorded alongside the result.
  • Deadline monitoring per movement. Notice and documentation deadlines held as dated obligations with an owner, escalating before expiry rather than reporting after it.

A five-step roadmap for tightening demurrage control

Step 1, Extract laytime and time bar terms at fixture

Do not wait for a claim to read the clause. At fixture, capture allowance, rate, exceptions, notice of readiness conditions, time bar triggers and the document list as structured fields attached to the movement, so the requirement is known before the vessel arrives.

Step 2, Standardize the port document pack

Publish one list of documents to be collected at load and discharge, and make collection a completion condition for the operational file. Documents obtained while the vessel is alongside are straightforward. The same documents requested six weeks later often do not arrive.

Step 3, Make protests automatic, not discretionary

Any statement of facts entry that conflicts with your own record should trigger a written protest before departure. Teams that treat protest as an escalation rather than a routine step lose the argument about when laytime commenced.

Step 4, Calculate against the contract, not the habit

Apply the exceptions written into the governing terms rather than a house standard. Where a term is ambiguous, record the interpretation used and the reasoning, so a later challenge is answered from a documented position.

Step 5, Run a claims aging and leakage review

Report claims by movement showing days to submission, document completeness and outcome. Patterns appear quickly: particular terminals, particular counterparties and particular contract forms account for most of the leakage, and each has a specific fix.

See claim deadlines tracked per cargo movement

Time bars, document lists and laytime terms extracted from the governing contract and monitored against each lifting.

Book a demo

Owning demurrage across functions

The organizational fix is usually more valuable than any single process change. Demurrage claims fail at handoffs: operations holds the port documents, chartering holds the fixture terms, trading holds the sale contract, and finance holds the invoice. A claim needs all four, and in most organizations no role is accountable for assembling them. Naming a single owner per movement, with visibility of the extracted terms, the document pack and the deadline, closes that gap without reorganizing anyone. The second-order benefit is negotiation intelligence. Once claims are tracked by contract form and counterparty, it becomes clear which laytime exceptions consistently cost money and which time bar periods are too short to be operationally achievable. That evidence belongs in the next negotiation, and it is the same argument made for obligation management in energy and mining more broadly.

Evidence and deadline mapping

The table shows what a monitorable demurrage file holds for each stage of a cargo movement.

StageTerms to applyEvidence to collectDeadline to track
FixtureAllowance, rate, exceptionsCharterparty and recapTerms extraction complete
ArrivalNotice of readiness conditionsTendered notice with timeValidity of tender confirmed
Load or dischargeLaytime counting rulesStatement of facts, timesheetsProtest issued before sailing
CompletionPumping and ullage conventionsPumping log, ullage reportsClaim notice period start
ClaimCalculation conventionsFull document packDocumentation deadline

Demurrage recovery is a documentation discipline with a hard deadline attached. The teams that do it well extract the laytime terms and the time bar at fixture rather than at claim, collect a standard document pack while the vessel is still alongside, treat protests as routine, calculate against the specific contract rather than a house convention, and monitor notice and documentation deadlines as dated obligations with a named owner per movement. None of that changes the commercial terms. It changes how much of what the contract already allows you actually collect, and it produces the evidence to negotiate better terms next time.

For related guidance, see Contractor prequalification and MSA control for operators, The land manager’s guide to mining royalty obligations and Lost in hole equipment charges, a controls datasheet.

FAQ

Demurrage and laytime questions

What is the difference between laytime and demurrage? +
Laytime is the period the charterparty or sale contract allows for loading or discharging without additional charge. Demurrage is the liquidated sum payable for detention beyond that period. Laytime is an allowance, demurrage is the agreed consequence of exceeding it, which is why the exceptions that pause laytime are so heavily contested.
Why do demurrage claims become time barred? +
Because most charters and sale contracts require notice of the claim, and often full supporting documentation, within a defined window after completion of discharge or the bill of lading date. Miss either deadline and the claim is extinguished on procedure, so the merits are never examined.
Which documents are needed to support a demurrage claim? +
Typically the notice of readiness with tender time, the statement of facts signed at each port, timesheets, pumping logs and ullage reports, any letters of protest, and the laytime calculation itself. Some contracts specify the list, and where they do, an incomplete submission can fail even inside the deadline.
Why does a letter of protest matter? +
Because the statement of facts is the primary record of when laytime commenced and how it ran. If it contains an entry you dispute and you sign without protest, you are arguing later against a document you accepted. A protest issued at the time, before sailing, preserves the position.
Who should own demurrage claims inside an organization? +
One named owner per cargo movement, with access to the fixture terms, the port document pack and the claim deadline. The common failure is distributed ownership across chartering, operations, trading and finance, where each function holds part of the file and none is accountable for the claim.
How can contract data reduce demurrage leakage? +
By extracting laytime allowance, exceptions, notice of readiness conditions, time bar triggers and required documents as structured fields at fixture, then attaching them to the specific movement. The operational team then knows what to collect and by when, and deadlines can be monitored rather than remembered.

Stop losing recoverable demurrage to deadlines

Aavenir extracts laytime terms, document requirements and time bars from charterparties and sale contracts, then monitors them as dated obligations against each cargo movement.

  • ✓Time bars and document lists tracked per movement
  • ✓Laytime terms extracted from the governing contract
  • ✓Standalone or native on ServiceNow