Cylinder Deposit & Demurrage Management, Explained

Deposits and demurrage sit at the intersection of finance and operations, and that intersection is exactly why they leak. Cylinders move physically — onto trucks, into customer warehouses, back onto trucks again — while the money attached to those movements moves on a completely separate paper or spreadsheet trail. The two are supposed to reconcile perfectly at all times, but in practice they drift apart almost immediately, and the drift compounds every single day the two systems stay disconnected. This guide explains what a proper deposit and demurrage process looks like, where the money actually leaks, and how to run both cleanly using the same data that already exists in your dispatch and delivery records.

Why deposits and demurrage are different problems that get treated as one

It is worth separating these two concepts clearly, because most operators conflate them and end up managing both badly.

A deposit is a refundable security amount tied to the physical cylinder itself — the customer pays it when they take possession of a cylinder and gets it back (in full or in part) when the cylinder is returned. It is a balance-sheet item, not revenue.

Demurrage, sometimes called a holding charge or rental fee, is the cost of a customer keeping a cylinder longer than an agreed free period. It is a revenue item, billed periodically, and it depends entirely on accurately knowing how long a cylinder has been away from your yard.

Because both revolve around "how many cylinders does this customer currently have, and since when," they are naturally linked — but they need separate ledgers, separate calculation logic, and in most systems, separate line items on the customer statement. Treating them as a single fuzzy "customer cylinder balance" is where a lot of the confusion, and therefore the leakage, begins.

What a deposit ledger must track

A robust deposit ledger records, per customer, the following fields at minimum: cylinders issued (by serial number, not just quantity), cylinders returned, net cylinders currently held, the deposit rate applicable per cylinder type, and the resulting deposit balance outstanding. Crucially, every one of these values must be derived automatically from the same scan events that drive your dispatch and returns process — never entered separately by a clerk reading a paper challan after the fact.

The moment a deposit ledger is populated by manual re-entry rather than by the underlying movement data, you have created two independent sources of truth that are guaranteed to diverge over time, simply through ordinary human transcription error compounding month after month. A customer portal that shows the customer their own real-time deposit and holding position is one of the most effective ways to keep this ledger honest — customers who can see the number themselves will flag a discrepancy far faster than your own back office typically will.

Setting free days and demurrage rates

Demurrage applies once a customer holds a cylinder beyond an agreed number of free days from delivery. A clear, enforceable policy needs three explicit components, and ambiguity in any one of them is where disputes are born:

• The free-day window — commonly somewhere between 7 and 30 days depending on industry and customer type, but the number matters far less than that it is written down, agreed, and applied identically to every customer in that tier.
• The daily (or weekly) demurrage rate — usually a small percentage of the deposit value or a flat per-cylinder-per-day charge, structured so that long-term holding is clearly and increasingly more expensive than simply returning the cylinder promptly.
• An escalation structure for long-idle assets — many operators apply a higher rate after 60 or 90 days, and treat cylinders idle beyond a defined threshold (say 120 days) as presumptively lost, triggering a formal recovery or write-off process rather than letting demurrage accrue indefinitely on an asset that may never come back.

Different customer segments often warrant different terms. A large industrial account with predictable, high-volume cylinder turnover might reasonably get more generous free days than an occasional small retail customer, precisely because the industrial account's cylinders circulate reliably and rarely sit idle for long.

Where the money actually leaks

In our experience auditing manual gas distribution operations, deposit and demurrage leakage concentrates in a handful of very specific, very fixable failure points:

• Returns credited to the wrong customer ledger. When cylinders are physically identical or poorly tagged, a returns clerk processing a busy morning batch will often credit a return against whichever customer's paperwork happens to be on top of the pile, not the customer who actually returned that specific cylinder.
• Free days counted manually, and counted generously. A staff member calculating holding days by hand, under time pressure, and often with an informal instinct to "give the customer the benefit of the doubt," will systematically under-count overdue days — every single time, in the same direction, which compounds into a large and entirely one-sided annual loss.
• No visibility of which cylinders are overdue at any given moment. Without a live dashboard, overdue cylinders are typically only discovered during a periodic manual review — often quarterly, sometimes only annually — by which point months of billable demurrage have already gone unbilled and unbillable in retrospect, because the customer will reasonably dispute a large lump-sum backdated charge.
• Deposits never reconciled against physical stock. A deposit ledger can show a healthy, growing balance for months while the actual cylinders backing that balance have already gone missing, because nobody cross-checks the ledger total against a physical or system stock count on any regular cadence.
• Partial returns not handled cleanly. A customer who returns 8 of the 10 cylinders they hold often gets processed as a full reconciliation event by a rushed clerk, silently writing off the two outstanding cylinders from active tracking.
• Deposit refunds processed without verifying condition or completeness. Refunding a deposit is sometimes treated as a purely financial transaction disconnected from confirming the actual cylinder has, in fact, been returned in serviceable condition.

How software closes these gaps

A proper tracking platform ties every deposit and demurrage ledger entry directly to a scanned cylinder movement — dispatch, delivery confirmation, and return — so there is no manual re-entry step for either the deposit balance or the holding-period clock to drift away from reality. Holding periods are calculated automatically from the actual scan timestamps rather than from a clerk's memory or a paper challan date that may itself have been filled in late. Overdue cylinders surface automatically on a dashboard the moment they cross the free-day threshold, rather than waiting to be discovered during an infrequent manual review.

This has a compounding effect across the whole deposit-and-demurrage cycle: because returns are tied to serial numbers rather than quantities, misattribution to the wrong customer becomes structurally impossible rather than merely discouraged. Because demurrage is calculated automatically, "generous rounding" by staff disappears entirely — the system charges exactly what the policy says, every time, for every customer, without exception or favouritism. And because deposit balances are derived from live stock movement rather than parallel manual entry, a monthly reconciliation against physical count becomes a quick confirmation exercise rather than a multi-day forensic investigation.

Comparing manual and automated deposit/demurrage management

Implementing a clean deposit and demurrage process

1. Define your policy in writing first. Before touching any software, agree free-day windows, demurrage rates and escalation thresholds across customer segments, and get sign-off from both sales and finance so the policy does not get quietly overridden later by a sales team worried about upsetting a large customer.
2. Tag every cylinder with a unique, scannable identity. Deposit and demurrage tracking by serial number is only possible once every cylinder in circulation has a durable, unique identity — see our cylinder loss reduction checklist for the specifics of getting this foundation right.
3. Route every delivery and return through a scan event, using a driver mobile app so the timestamp and location are captured at the actual moment of handoff rather than reconstructed later from memory.
4. Migrate the deposit ledger to derive automatically from scan data, running it in parallel with your existing manual ledger for one full billing cycle to validate accuracy before fully retiring the old process.
5. Turn on automatic demurrage calculation and billing, starting with a grace-period communication to customers explaining the new, consistent policy before the first automated invoices go out, to pre-empt disputes.
6. Give customers visibility into their own balance through a customer portal, which both reduces inbound query volume and makes customers active participants in keeping the ledger accurate.
7. Reconcile monthly against physical stock, treating any variance as a trigger for investigation rather than a routine adjustment to the ledger.

Frequently asked questions

Should demurrage rates be the same across all customer segments? Not necessarily. Many operators tier rates by customer type or contract value, provided the policy is documented, consistent within each tier, and communicated clearly upfront — inconsistency applied ad hoc, rather than tiering itself, is what generates disputes.

How do we handle demurrage disputes from customers who claim they returned cylinders on time? This is precisely the problem a scan-based system solves — a dispute becomes a simple lookup of the actual delivery and return scan timestamps rather than a he-said-she-said argument based on paper records that may have been filled in after the fact.

What happens to the deposit if a cylinder is never returned? Policy varies, but a common structure is to retain the full deposit after a defined idle threshold (say 120–180 days) and formally reclassify the cylinder as lost, removing it from active circulation tracking while keeping a permanent record for audit purposes.

Can this be managed for a multi-depot operation with cylinders moving between locations? Yes, though it requires that inter-depot transfers are also scan-tracked, so that a customer's deposit and demurrage record correctly reflects which depot currently holds responsibility, rather than getting lost in a transfer that only one of the two depots recorded.

Getting deposits and demurrage under control

Deposits and demurrage are two of the highest-leverage numbers in a cylinder rental business precisely because they are so commonly mismanaged — which means the upside from fixing them is unusually large relative to the effort involved. Explore the Cylinder Rental Software module or the broader Cylinder Rental & Deposit solution to see how deposit and demurrage tracking is automated end-to-end on top of the same scan data that already drives your dispatch and delivery process. For the related loss angle, read our cylinder loss reduction checklist, or book a demo to see your own deposit and demurrage numbers modelled against your current customer base.