IN THIS ARTICLE▾
A self-storage facility can bill unit rental, insurance, late fees, and size upgrades all through one variable-amount mandate, instead of separate manual processes for each.
A self-storage tenant almost never pays exactly one amount for the life of their tenancy. The monthly unit rental is the baseline, but on top of it sit the things that change: contents insurance, a late fee if a debit fails and gets recovered, an access-fee upgrade, a size change when the tenant needs more or less space, a packing-supplies purchase at move-in. Each of these is a different amount, billed at a different time, to a different subset of tenants.
Most SA storage facilities end up running these as separate processes: the rental on the debit-order or billing system, insurance tracked in a spreadsheet or billed by the insurer directly, late fees added manually to the next invoice, size-upgrade changes requiring a fresh mandate or a manual adjustment. Each fee, individually, is manageable. Together, they're the part of the billing operation that eats the most admin time and produces the most reconciliation gaps.
This piece is about what changes when every one of those charges runs against the same mandate as the monthly rental.
Why the standard rental mandate doesn't stretch
A conventional fixed-amount debit-order mandate authorises one number, on one date, recurring. That works cleanly for the core rental as long as the rental itself doesn't change. It breaks down the moment a tenant adds insurance, incurs a late fee, or moves into a different-sized unit, because each of those changes the amount, and a fixed mandate doesn't flex to a new number without a fresh authorisation.
The practical result at most facilities: the rental is automated, and everything else is a manual add-on, a separate invoice, a phone call, an adjustment made by hand at month-end when someone remembers to capture it.
What a variable-amount mandate changes
A variable-amount mandate, signed once at move-in, authorises the facility to debit the amount it raises, with appropriate notification to the tenant, rather than locking in a single fixed figure. It runs on the same underlying EFT rail as a standard mandate; the difference is the amount field isn't fixed.
Once that mandate is in place, the rental, the insurance premium, the late fee, and the size-upgrade adjustment all run through the same authorisation. There's no second signature required when a tenant adds insurance three months into their tenancy, no separate manual process for a late fee, no re-papering when a tenant upgrades from a small unit to a larger one.
What this means for the insurance line
Many facilities offer tenant contents insurance as an upsell, but billing it cleanly is often the sticking point, it's a different amount than the rental, sometimes billed by the insurer separately, sometimes tracked manually against the tenant's account. On a variable-amount mandate, the insurance premium is simply an additional line raised against the same authorisation the tenant already signed for their rental, itemised on their statement, collected on the same cycle.
What this means for late fees
A late fee only makes sense to charge if it can actually be billed without a separate manual chase, otherwise the fee exists in policy but not in practice. On a variable-amount mandate, a late fee triggered by a failed rental collection can be raised against the same mandate and collected on the next cycle, rather than requiring a standalone invoice the tenant has to be separately reminded about.
What this means for size upgrades and downgrades
A tenant moving from a small unit to a larger one, or the reverse, changes their monthly rental amount. On a fixed mandate, this technically requires a new authorisation for the new figure. On a variable-amount mandate, the new rental amount is simply raised against the existing mandate from the next cycle onward, with the tenant notified of the change, and no re-signing required at the desk.
What changes operationally
Three things shift for the operations team. Insurance, once sold, is a line item, not a separate billing process. Late fees, once triggered, collect automatically rather than requiring a manual invoice. Size changes update the billed amount without a fresh mandate, the tenant's authorisation already covers it.
The end-of-cycle recon view reflects all of this in one place: rental, insurance, late fees, and adjustments, reconciled together rather than requiring the operations team to check multiple sources to understand a single tenant's account.
What this isn't
It isn't a way to bill a tenant for something they haven't agreed to. The mandate authorises debits raised by the facility in line with the tenant's rental agreement and any add-ons they've opted into; it doesn't grant the facility authority to invent charges.
It isn't a replacement for the facility management software many operators already run for unit allocation, gate codes, and occupancy tracking. The variable-amount mandate is the billing and collection layer underneath, it sits alongside the FMS, not in competition with it.
It also isn't specific to insurance, late fees, or size changes alone, any variable, ad-hoc, or once-off charge a facility needs to bill a tenant can run through the same mandate, which is part of why the operational saving compounds across the whole billing workload.
Related reading
See how Recurv handles recurring billing for long-term storage.
View Long-term Storage use case →