IN THIS ARTICLE▾
Seeing occupancy revenue and ancillary revenue together in one view lets a self-storage operator catch a defaulting tenant early, often before the lien and auction process becomes necessary.
Self-storage has a remedy most other recurring-billing businesses don't: if a tenant stops paying and stays unresponsive long enough, the facility can eventually invoke a lien over the contents and, ultimately, auction them. It's a real legal remedy, and it exists for good reason, but it's slow, it's operationally unpleasant, and it's the outcome every operator wants to avoid reaching in the first place. The entire game, for most operations managers, is catching a defaulting tenant early enough that the lien and auction process never becomes necessary.
Catching a default early depends on knowing about it early, and that's where most facilities' monthly billing cycle quietly works against them.
Where the visibility gap comes from
A typical month runs like this. The rental (and any add-ons, insurance, late fees) gets submitted as a debit-order batch. The result comes back from the bank some time later: which debits succeeded, which failed, and why. Someone then has to match that result against the tenant ledger to update who's behind and by how much, often by hand, in a spreadsheet, alongside everything else the operations team is doing that week.
By the time that matching is done, a tenant who defaulted on the 1st might not show up as a flagged arrears case until well into the month, and the standard follow-up sequence (a call, a reminder, a formal notice) hasn't even started yet. Every day of delay in spotting the default is a day closer to needing the lien remedy instead of a simple phone call.
Why "occupancy revenue vs ancillary revenue" is the wrong two numbers to conflate
Most facilities track occupancy, how many units are filled, as their primary operating metric, and that's reasonable; it's the core of the business. But occupancy revenue (the rental) and ancillary revenue (insurance, late fees, access-fee upgrades, size-change adjustments) often get reported and reconciled separately, if ancillary revenue gets reconciled with any rigour at all. An owner reviewing month-end numbers may see the occupancy figure clearly and have only a rough sense of what the ancillary lines actually collected.
This matters because ancillary revenue, at scale, isn't trivial, insurance premiums and late fees across a few hundred tenants add up to a meaningful monthly figure, and if it isn't reconciled with the same rigour as rental, leakage happens quietly.
What single-pane recon changes
When rental and every ancillary charge run through the same billing system with automated recon behind them, the matching step between the bank's result and the tenant ledger happens as part of the collection process itself. A failed debit, whether it's the rental or an add-on, is tagged with the bank-returned reason and reflected against that tenant's account immediately, visible in the same view as every tenant who paid successfully.
For the operations manager, this means the arrears list is current on the day it's viewed, not reconstructed from a spreadsheet a week or two after the cycle ran. A default that would have surfaced mid-month in a manual process surfaces the same day the debit fails, which is the difference between a phone call on day 3 and a formal notice on day 25.
What this means for the lien-and-auction pathway
The lien and auction remedy doesn't disappear as an option, it remains available for tenants who genuinely go unresponsive. What changes is how often it needs to be reached at all. A tenant caught in arrears within days, followed up promptly, resolves the situation far more often than one who isn't flagged until weeks have passed and multiple cycles have failed. Faster visibility doesn't replace the legal remedy; it reduces how frequently the facility needs it.
What this means for reporting to ownership
An owner or multi-site finance lead reviewing month-end performance benefits from seeing occupancy revenue and ancillary revenue reconciled with the same rigour, in the same view, rather than a clean rental number and a vaguer sense of what insurance and fees actually brought in. That single view also makes it easier to compare performance across multiple sites on a like-for-like basis, since every site's recon follows the same structure.
What this isn't
It isn't a replacement for the operations team's judgment about when to escalate a specific case. Whether to call, send a formal notice, or eventually invoke the lien remains an operational decision, made with the facility's own policies and the specifics of the tenant relationship in view.
It isn't a claim that better recon eliminates defaults entirely. Tenants will still fall behind for their own reasons. What changes is how quickly the facility knows about it and how much runway there is to resolve it before the lien becomes the only option left.
It also isn't specific to rental alone, insurance, late fees, and any other ancillary charge reconcile through the same view, which is part of why the ancillary-revenue leakage problem shrinks alongside the arrears-visibility problem.
Related reading
See how Recurv handles recurring billing for long-term storage.
View Long-term Storage use case →