Every rental program has a leak, and it rarely shows up as a single missing container or an obvious billing error. For industrial gas, chemical, and LPG distributors managing fleets of cylinders, totes, and tanks, leakage accumulates quietly across hundreds of assets sitting at customer sites and depot yards, building up unbilled days while your billing system assumes normal cycling. The gap between what your ERP records and what is physically happening on the ground is where rental revenue disappears.
The root cause is visibility; for operations running thousands of returnable containers, the financial exposure that follows from its absence is material, and it tends to compound long before anyone notices it on a report.
The leakage happens in two places: at the customer site and at your facility. A cylinder leaves your facility, gets delivered to a customer, and sits. The customer’s operations don’t require it immediately, so it gets set aside in a corner of their yard, where it stays for weeks or months without a return event ever being logged. Your system has no record of return, and no record of the asset still sitting at the customer site accumulating a billable day.
Your facility creates the same problem from the other direction. Cylinders returned without proper scanning fall into inventory in an indeterminate state: physically present but not re-entered into the rental billing cycle, neither generating a charge nor triggering a return credit. They accumulate in a gray zone, invisible to finance and operations alike.
Standard billing cycles are built around events: a delivery triggers the start of a rental period; a return triggers the end. When those events aren’t captured accurately, the billing logic breaks down, because you can’t invoice for what you can’t verify, and without container-level tracking, verification isn’t possible.
ERP systems are transaction engines: they record what is entered (orders, invoices, deposits) but don’t track where a physical asset is between those transactions. If a cylinder is delivered and the next event entered into your ERP is a new order to the same account, the system has no way of knowing the original container never came back. It processes the next order and creates the next invoice, because that’s all it was built to do.
This distinction sits at the core of the problem. ERP records financial activity; it doesn’t track physical asset state. A cylinder sitting in a customer’s yard for 90 days won’t generate a line item unless something forces the event, and in most operations, nothing does.
Billing teams working from ERP data are working from an incomplete picture, billing against what the system recorded rather than what is occurring in the field. The delta between those two views is where revenue leakage lives.
Consider a mid-size industrial gas distributor with 5,000 cylinders in active circulation. If 10% of those cylinders are idle at customer sites at any given time (a conservative estimate for operations without container-level visibility), that’s 500 assets sitting outside the billing cycle at any moment.
At a daily rental rate of $0.50 per cylinder, those 500 idle assets represent $250 per day in uncollected revenue; over a 90-day period, that’s $22,500. Annualized, across a fleet that shifts and turns constantly, the exposure compounds at a rate that most finance teams would find difficult to explain away.
None of those numbers require exceptional circumstances. They require only what already exists in most operations without container-level tracking: assets that move without being individually scanned, return events that go unlogged, and billing cycles that run on transaction records rather than physical reality.
The instinct is to look at billing process: tighten the invoicing cycle, add reconciliation steps, push for faster closes. But process improvements can only work with the data that already exists, and if the underlying data doesn’t capture where an asset is or when it goes idle, no amount of workflow refinement closes the gap.
The fix must happen upstream, at the point of movement. Every handoff (delivery, pickup, return, transfer) needs to be captured as a timestamped event tied to a specific, serialized container, because that event data is what drives accurate billing. Without it, the billing system works from assumptions; with it, every idle day becomes visible, and every billable day becomes collectable.
This is why asset visibility functions as a revenue protection tool, not just an operational convenience. When you can see exactly which containers are at which customer sites, how long they’ve been there, and which rental charges have or haven’t been applied, your billing team stops estimating and starts executing against a precise, defensible record.
Container-level tracking, via barcode or RFID scan at each handoff, creates the event record that billing requires. Mobile capture at delivery, voice-enabled scanning at pickup, and facility reconciliation at return together produce a continuous chain of custody; when that chain is intact, idle time becomes visible. The system knows which container is at which customer site, when the rental period started, and which accounts have exceeded normal dwell times.
Rental analytics built on that data can surface under-billed accounts, identify rate discrepancies, and flag containers that have been sitting long enough to warrant a pickup call. The result is margin recovery at scale. TrackAbout customers have recovered 6% or more in rental revenue after implementing event-level tracking, precisely because container-level visibility closes the gaps that billing systems, working from transaction records alone, simply cannot see.
The revenue was always there. Visibility is what makes it collectable.
What causes rental revenue leakage from idle cylinders?
Revenue leakage occurs when cylinders sit idle at customer sites or in your facility without triggering billing events, accumulating unbilled days while your ERP system assumes normal cycling. Without container-level tracking, these assets remain invisible to billing systems, creating gaps between physical reality and what gets invoiced.
How much revenue can idle cylinders cost a distributor?
A mid-size distributor with 5,000 cylinders in circulation can lose $22,500 over 90 days if just 10% of assets sit idle at $0.50 per day rental rates. This assumes only conservative idle rates in operations without container-level visibility, and the exposure compounds annually.
Why can't my ERP system track idle cylinders?
ERP systems record financial transactions like orders and invoices, but they don't track physical asset location between those events. If a cylinder is delivered and never scanned upon return, the ERP has no way of knowing it's still sitting at a customer site accumulating billable days.
Will improving my invoicing process fix rental revenue leakage?
No, because process improvements only work with existing data. If the underlying data doesn't capture where an asset is or when it goes idle, no amount of workflow refinement closes the gap—the fix must happen upstream at the point of movement.
How does container-level tracking prevent revenue leakage?
Barcode or RFID scanning at every handoff creates timestamped event records tied to specific containers, producing a continuous chain of custody. This visibility allows billing teams to see exactly which containers are at which sites, how long they've been there, and which rental charges haven't been applied.
What kind of revenue recovery is possible with event-level tracking?
TrackAbout customers have recovered 6% or more in rental revenue after implementing event-level tracking, because container-level visibility closes the gaps that billing systems working from transaction records alone cannot see.
Where do cylinders typically go idle in a rental operation?
Cylinders go idle in two places: at customer sites where they get set aside without return events being logged, and at your own facility where returned cylinders aren't properly scanned back into inventory, leaving them in an indeterminate state outside the billing cycle.
Small Asset Losses Are a Data Integrity Problem: How missing containers corrupt utilization, forecasting, and billing accuracy across the operation.
Datacor's asset tracking software, TrackAbout, gives industrial gas, chemical, and LPG distributors the event-level asset data that billing systems require to close these gaps. If you’re running a rental program without container-level tracking, the leakage is already there. Contact us to see how TrackAbout makes it visible and collectable.