Two flats still fit a spreadsheet, five do not: where is the line
An owner of two flats who tracks everything in a spreadsheet usually has no trouble with it. A column for rent, a column for the payment date, meter readings somewhere off to the side. That works as long as everything still fits in your head. The trouble comes later, and it almost never looks like a breakdown. It starts with one missed deadline. Then with a tenant question you cannot answer without opening three files. At tenanto we work with owners who have already been down this road, and we see a recurring pattern: the line does not run where they expect it to.
Why a spreadsheet works for one or two rentals
At a small scale there are so few events in a month that they fit in your memory: one transfer, one meter reading, the occasional conversation with a tenant. A spreadsheet needs no rollout and no learning. You remember the context of every entry without describing it in a system. You know why the payment was lower in March, because you agreed to it yourself.
A mistake in a file like that is visible at a glance, because the whole rental history fits on one screen. No filtering, no sorting, no searching. Just look at it. And that is a real advantage, not a temporary crutch.
Let us be honest about it: not everyone needs an app from day one. Pushing the owner of a single flat to roll out a tool would be disingenuous, and we would rather someone came to tenanto at the point where they actually gain something from it.
What changes between the second and the fifth flat
What grows is not the number of flats but the number of combinations. Agreements end in different months, service charge rates differ between housing associations, indexation dates drift away from signing dates. And the deposits? Each one at a different stage of settlement: one paid in full, another in instalments, a third partly deducted after the previous tenant.
On top of that come the events that are rare but expensive. A notice of termination, arrears dragging on for months, a utilities settlement after the tenancy has ended. Each of them calls for reconstructing the whole chain of arrangements, not just the last amount.
The growth is not linear. Each new flat adds not one row but another thread to run in parallel with the rest. Working with tenanto users brings out something characteristic: people rarely move to an app after counting their flats. They move after a specific slip-up.
Signs that the spreadsheet has run out
Instead of a fixed numerical threshold, a checklist. The more points that fit, the closer you are to the line:
- You check a tenant’s balance by opening your banking app and scrolling through the transfer history, because you do not trust the last update in the file.
- You have more than one version of the spreadsheet, and the file names contain dates or the word “final”.
- You cannot say off the top of your head when the agreement for a particular flat ends, or how much of the deposit is left to return.
- You remember an indexation date after it has passed, not before.
- Settling utilities takes a whole evening and ends with adding yet another column.
- Someone else - a co-owner, a partner, an accountant - needs access, and the only way is to email the file.
None of these signs settles the matter on its own. Three at once mean that your memory is propping up the system, rather than the other way round. Keeping a record of tenant payments that is immune to gaps like these is the first place where the difference shows.
Four things a spreadsheet will not do for you
A spreadsheet is passive. It will not remind you about a deadline, because you only open it once you have reminded yourself. Which means you are the calendar, not the file.
Nor will it build a history of events. An overwritten cell wipes out the previous state for good, and in a dispute with a tenant it is precisely the sequence of events that counts: what was agreed, when, and in response to what. The last value in a cell proves nothing.
It will not generate a document. A payment demand, an annex or a handover protocol are created outside the file and start a life of their own across folders. Usually in several versions. All of this belongs to the features of a rental system .
It will not protect you from data loss. A file on a local drive has no versioning, and one in the cloud without an agreed structure can be overwritten by a co-owner acting in good faith.
Tip: before you judge whether you need an app, try reconstructing the full history of one tenancy from a year ago out of your spreadsheet. It is the fastest sufficiency test we know.
Tax and paperwork: where a spreadsheet turns into a risk
Settling rental income rests on documented receipts assigned to a specific agreement and period, not on the total of a single column. With several flats the risk grows that a payment lands in the wrong month or against the wrong agreement - the transfer came in with no clear reference, the tenant paid for two periods in one go, and that is that.
Utility re-invoicing and advances towards costs have to be tracked separately, so they are not treated as rental income. A deposit has a different character again from rent, and dropping it into the same column clouds the picture for a long time. Especially when part of it has been deducted.
A practical rule: how the settlement is structured and how individual receipts are classified is a matter for an accountant or a tax adviser. The app puts the data in order and shows what belongs to what. It will not replace professional advice.
What the move from spreadsheet to system looks like
You do not have to move the whole history. The opening balance is enough: current agreements, balances, deposits and the latest meter readings. The rest stays where it was.
- Start with one flat - the one with the messiest tenancy, not the simplest. If the system handles that one, it will handle the rest.
- Enter the opening balance and, for a month, run that tenancy only in the new place.
- Only then add the next flats, one at a time.
- Keep the old spreadsheet as an archive you can look back at. Do not delete it on migration day.
The free tenanto plan covers one flat with no time limit, so you can run that test on real data rather than sample data. What the other plans include is set out in the plan comparison. By the time you get to settling utilities with tenants, the difference from a spreadsheet will already be obvious.
Tip: move your data in a month with no utilities settlement due. You will avoid running two sources of truth at once.
The question owners ask most often
With three flats, is it already worth changing tools?
The line does not run through the number of flats but through the number of parallel deadlines and the number of people who need access to the same data. Three flats with one long-term tenant each can be easier to run than two with turnover every six months - in the first case there are a handful of events a year, in the second a dozen or more. The practical marker is simpler than arithmetic: if at any point in the past month you had to reconstruct from memory what you agreed with a tenant, the spreadsheet is no longer enough. We write more about tools for flat owners in our pieces on technology in rentals.
In short: the line runs through the number of events, not flats
A spreadsheet stops working not when there is a lot of data, but when that data starts changing over time and calling for a response by a deadline. A static table describes a state well. It handles a process badly.
The five-flat threshold is a mental shortcut - handy in conversation, misleading in practice. The real threshold is the moment when the owner’s memory becomes part of the system. Because from then on, every forgotten detail costs money or a relationship with a tenant.
A sensible first step is a small one: move one tenancy, the most troublesome one, and check after a month whether you are getting your evenings back at settlement time. All you need to do is set up an account and enter the opening balance. The answer to that question tells you more than the number of flats in your spreadsheet.
