Laytime and Demurrage: Why the Cost Is Decided After the Ship Has Gone

Summary

Demurrage is usually described as the cost of a delay. That description leaves out the part that decides the money. A delay is an event. Demurrage is a claim — assembled after the fact, out of documents your company did not write, under contract wording that decides which hours are allowed to count, and against a deadline that can extinguish an entirely correct claim.

This article sets out where laytime is bought, where it is spent, who writes the record that prices it, and why the same delay can leave you owing the vessel while unable to recover anything from your buyer. It is meant to let you tell an operational problem from a contractual one before the invoice arrives, and to see which of the two your own company actually has.

Read it if you lift or deliver physical cargo and your laytime calculations live in a spreadsheet while the evidence for them lives in an inbox. Start with the next section — everything after it follows from the distinction it makes.

The delay is an event; the money is a claim

A vessel waits. That is a fact about the world, and it happened whether or not anybody was watching.

What follows from it is not a cost. It is a sequence of acts: somebody obtains the port documents, somebody prepares a calculation, somebody presents it to a counterparty with supporting papers attached, and the counterparty either agrees, disputes the hours, or rejects the presentation for a reason that has nothing to do with the hours at all. Only at the end of that sequence does money move.

Demurrage is not a cost you incur; it is a claim somebody makes — and a claim that is never made, or made after the contractual deadline, is worth nothing however correct the underlying facts are.

This is the property that makes demurrage behave unlike almost anything else in the trade lifecycle. A price move marks your book whether you look at it or not. A quality deduction shows up in the invoice by itself. A demurrage entitlement does neither. It sits inert until somebody assembles it, and it can expire while it is inert.

The direction matters here, and it cuts both ways. Where you are the claimant, an unassembled claim is revenue that quietly does not exist. Where you are the payer, an unexamined claim is somebody else's arithmetic arriving as an invoice, and the practical question is whether anybody in your company is in a position to check it before it is paid.

The clock is started and stopped by documents you do not write

Laytime is an allowance of time. What consumes it is decided by a small set of records, and the notable thing about that set is who produces it.

Five records; four different authors; not one of them inside your company, and none of them keyed to your trade.

Your entitlement is computed from a record your company neither produces nor controls, and it arrives after the only people who witnessed the events have moved on to the next vessel.

This is why demurrage work does not resemble the reconciliation disciplines around it. Reconciling an invoice is a comparison of two numbers with a difference in the middle. Reconciling a laytime claim is a comparison of a narrative against a contract clause, where the narrative was written by a third party for a different purpose and the clause was agreed by somebody who is not in the conversation. There is no difference to compute until you have decided what the words mean.

Laytime is bought when the trade is priced and spent when the vessel berths

The allowance and the demurrage rate are commercial terms. They are agreed at the point of the deal, by the person doing the deal, as part of a package that also contains the price, the delivery window and the quality specification. In that moment they are a trade-off like any other: a tighter allowance in exchange for something else.

Then weeks pass, and the hours are actually spent — by a terminal working at its own pace, by a berth that is occupied, by weather, by an inspection that took longer than expected. Nobody in that second scene has any visibility of what an hour is worth, and in most operations they have no reason to.

The price of an hour is set by one person and the hours are spent by another, and in most companies the two facts never appear in the same document.

The consequence is not that people behave carelessly. It is that a decision with a known price is being made by people who have not been told the price. An operations desk choosing between two berthing options, or deciding whether to press a terminal, is making a commercial choice; whether it is visible as one depends entirely on whether the rate travelled with the cargo.

The argument is about which hours count, not about the arithmetic

Two parties can agree on every event in the statement of facts and still be far apart on the money. The gap is produced by the contract, not by the calendar.

Nearly all of the following are negotiated terms rather than industry constants, and each of them moves the total without anybody disputing a single recorded time:

• When the clock starts. A notice of readiness has to be validly tendered, often accepted, and a stated period may run before laytime commences at all.
• Whether waiting for a berth is your problem or the vessel's. This turns on how the contract defines the point of arrival, and it is one of the largest single swings in the total.
• Which hours are excluded. Weather, holidays and non-working periods may or may not be excepted, and the exceptions are drafted, not standard.
• What happens once the allowance is exhausted. Many standard forms carry the principle that exceptions which would have interrupted laytime no longer interrupt time on demurrage — but that is a matter of what your contract says, not a universal rule.
• How a part cargo is treated. Where a vessel serves several parcels, the allowance has to be apportioned, and the basis of apportionment is a term.

A demurrage dispute is almost never an arithmetic dispute; it is a dispute about which hours the contract permits you to count.

That is worth stating plainly because it decides where the work belongs. If the problem were arithmetic, a better calculator would solve it. It is not. The calculation is the easy part, and it is the part everybody already does.

A back-to-back cargo is not a back-to-back clock

A trader who buys afloat and sells on is exposed on both sides of the same delay, under two separate contracts that were negotiated with different counterparties at different times.

The two columns describe the same waiting vessel. Nothing requires them to reach the same number, and nothing requires the deadlines to fall in a convenient order — you can be obliged to settle upstream before you have established anything downstream.

Two contracts covering one delay do not have to agree about it, and the gap between them is yours to fund.

Where terms are genuinely mirrored the exposure is small and the work is administrative. Where they are not, the difference is a real position that nobody opened deliberately, and it is created at contract drafting rather than at the berth.

A claim is documentary before it is financial

Claims are commonly required to be presented within a contractual period, and commonly required to be presented with the supporting documents rather than merely notified. The documents are the ones from the table above — produced by other parties, at ports, in whatever form those parties use.

This gives the whole exercise a shape that is easy to underestimate.

A demurrage claim can fail on a missing attachment while every hour in it is correct.

It is a well-recognised outcome, and it is not a filing accident. The evidence has to be requested from parties who have no particular incentive to hurry, sorted against a contract that specifies what counts as proof, and assembled into a presentation before a date that started running at a moment nobody announced. Each of those steps is somebody's task; whether they add up to a claim in time is usually nobody's.

The same shape works against you when you are the payer. A claim arrives with documents attached, and the window in which you can sensibly challenge it is bounded by how quickly you can reconstruct what happened from records you also did not write.

Between the delay and the settlement, nobody carries the number

There is a period — often a long one — during which a demurrage exposure is real, material and recorded nowhere.

The vessel has waited. The claim has not been presented, or it has been presented and disputed. The trade has been invoiced. The position has been closed. From the outside, the deal looks finished, and its margin has been reported as though it were.

Demurrage is a margin item that is managed as an administrative one, and the handover between those two descriptions is where it stops being anybody's number.

Look at where it sits organisationally and this stops being surprising. The entitlement is created by a commercial term, consumed by an operational event, evidenced by a third party, quantified by a claims function, and settled as a payable or receivable in finance. Five functions, none of which owns it end to end, and a deal P&L that in many companies was signed off before the question was asked.

Three checks you can run this week

None of these needs a study. They can be answered from inside your own company in an afternoon.

First: find your oldest open demurrage claim, in either direction, and ask what is holding it up. If the answer is "waiting for documents from the port", the constraint is the evidence chain, not the counterparty relationship, and it will hold up the next one identically.

Second: take one voyage where the vessel waited and ask who knew the clock was running while it was still running. Not who received the statement of facts afterwards — who could have acted. If the honest answer is nobody, then every demurrage decision in your company is being taken retrospectively, and retrospective decisions are only ever about who pays.

Third: ask whether last year's demurrage, paid and received, can be put next to the trades that generated it. Not the total in the ledger — the split by deal. If the two cannot be joined, then your realised margins are known to be wrong by an amount nobody has measured, and the deals that consistently produce demurrage are indistinguishable from the ones that never do.

If all three land uncomfortably, the constraint is not the laytime calculation. It is that the entitlement, the evidence and the deal are held in three different places, and only people are joining them.

Questions people ask about this

Is demurrage not just a cost of doing business?

Partly, and the part that is genuinely unavoidable is worth accepting without drama. But two things sit inside that description that do not belong there: claims you were entitled to make and did not, and claims you paid without being in a position to check. Neither is a cost of doing business; both are outcomes of not having the evidence in time. The test is whether your demurrage total would change if the assembly work were faster. If it would, that portion was never a cost of doing business.

We have a laytime spreadsheet that works. What does it not cover?

The calculation, generally, is not where things go wrong — a spreadsheet computes hours perfectly well. What a spreadsheet does not do is tell you that a statement of facts has not arrived, that a claim is approaching its contractual deadline, that the sale contract and the charter treat waiting time differently, or that this counterparty has now disputed the same clause three times. Those are all questions about the state of a population of claims, not about one calculation. The spreadsheet is the right tool for the job it is doing; the gap is that nothing is doing the other job.

Why do our demurrage claims get rejected when the calculation is right?

Usually for one of two reasons, and they need different fixes. Either the presentation was incomplete or late against what the contract requires — a documentary failure, fixable by process — or the counterparty is reading a clause differently, which is a commercial disagreement and will recur on every voyage under that contract until somebody resolves it at the contract level. Treating the second as though it were the first produces a great deal of correspondence and no change in outcome.

Should demurrage sit with operations, with claims, or with the trading desk?

Ownership of the work can sit reasonably in any of them, and arguing about it tends to be less productive than answering a narrower question: who is accountable for the number, and against which deal? The work is operational. The exposure is commercial. Wherever the desk sits, the outcome has to arrive back at the trade that created it, or the company is measuring margins it knows to be incomplete.

We buy and sell the same cargo. Do the two demurrage positions not cancel out?

Only if the terms mirror each other exactly, which is a drafting outcome rather than a natural one. The allowance, the rate, the exception clauses, the proof requirements and the presentation deadlines are all separately negotiated, and each mismatch is a residual you carry. It is worth checking on your own contracts rather than assuming either way — the answer is knowable, and it is knowable before the vessel sails rather than after.

How is this different from managing our scheduling and laycan exposure?

Scheduling exposure is about the decisions that determine whether a vessel waits: the nomination, the window, the berth. Demurrage exposure begins once waiting has happened and is about whether the resulting entitlement can be established, evidenced and collected — or challenged, when it is presented to you. The two are adjacent, and they fail differently. Better scheduling reduces the number of events; better claims handling changes what each event is worth. A company can be good at one and poor at the other, and most are.

What breaks first as we do more voyages?

Not the calculating. What fails first is the tracking of state across a population: which claims are open, which are missing which document, which are near their deadline, and which counterparty owes a response. A handful of voyages can be held in one experienced person's memory, and it works better than it should. That memory does not degrade gradually — it holds until that person is on leave when a deadline falls, and the failure is invisible until the entitlement is already gone.

Where this lands in a trading system

The argument above is about physical trading operations in general. This section is narrower: what a system can settle here, and what it cannot.

Three of the conclusions above correspond to capabilities the trading and risk system you already run should be expected to cover. That the entitlement has to end up back on the deal is the reason physical trade, financial hedging, risk control and settlement sitting in one platform matters for this topic specifically — a demurrage figure that cannot be joined to a trade is a figure that cannot correct a margin. The consumption of laytime happens inside the movement, which is a matter of end-to-end logistics coordination and execution management rather than a separate discipline. And a claim eventually becomes a payable or a receivable like any other, which is where automated financial settlement and payment processing applies.

The fourth conclusion — that the evidence is written by other parties and arrives as attachments and spreadsheets — maps onto something different. X-Ray is a non-invasive data processing and analysis platform, and the component that matters here is XDK: non-invasive automated data collection from databases, Excel files, and web interfaces, designed to collect data without disrupting existing systems or workflows. Where the laytime calculation genuinely does live in a spreadsheet, that is a way to read it where it is rather than insisting it move first. X-Eagle provides real-time risk alerts and monitoring for trade finance field warnings; whether that shape — a watched field, a date, a notification before it passes — is pointed at a claim deadline is a configuration question rather than something a platform decides for you, though a deadline on a field is an ordinary shape and not an exotic one.

None of this reads your statement of facts, and none of it decides which hours count. There is no clause interpretation here, no reading of charter wording, no judgement about whether a notice of readiness was validly tendered. Those are contractual questions answered by people with the authority to answer them, and they will stay that way. What a system settles is narrower and duller: where the entitlement is recorded, whether the deadline is visible before it passes, and whether the money — in either direction — arrives back at the trade that produced it.

See the products → · Talk to us about physical operations →

A note on the evidence in this article

This article contains no statistics, and that is a deliberate choice rather than an oversight.

The material we hold on how these processes run in practice — where the manual effort concentrates, which steps depend on spreadsheets and mail — comes from research we are not in a position to publish as a citable source. Publishing a figure we cannot point you to would be worse than publishing none: it would look like evidence and could not be checked.

So the argument here runs on structure instead. Every claim above is meant to be testable against your own operation rather than accepted on our authority: the documents really are written by other parties, the allowance really is agreed before the hours are spent, and the two contracts covering one delay really can disagree. Where that does not describe your business, the conclusions should not carry weight with you.