The jump from one property to several is not a volume problem, it is a structure problem. Three things that were implicit become explicit: where the money for each property sits, who is allowed to see and do what on each, and whether a consolidated figure can be traced back to its parts. A product that handles one property well can fail all three without any feature appearing to be missing.
Money has to be attributable per property
Whether or not each property has its own bank account, every transaction must be attributable to exactly one property, and a report per property must reconcile to something. Where properties are owned by different entities or with different partners, separate accounts are usually not optional. The commonest structural mistake is a single account and a spreadsheet allocation, which works until somebody asks for a property's figures for a past year.
Permissions by property, not just by role
A caretaker at one site, an agent managing two, an owner who sees their own and nothing else. The permission model has to be property-scoped, not merely role-based, or people will see things they should not and you will end up not giving access to anyone. Test this with a real third party during evaluation, because a demo account is always an administrator.
Consolidation that traces back
A portfolio total is only useful if you can click into it and arrive at the transactions. Products that compute consolidated figures separately from the per-property ledgers produce numbers that disagree in the third month and cannot be reconciled without a rebuild. Ask to see a portfolio figure decomposed to its properties and then to its transactions.
Where the per-unit pricing turns
Multi-property operators are exactly the customers per-unit pricing is designed for, and the bill grows linearly while the work does not. This is the point at which negotiating a band, or pricing an alternative, becomes worth an afternoon. It is also the point where an export you can actually use becomes a commercial lever rather than a technical detail.
Questions people ask about multi property management software
Does each property need its own bank account?
Where ownership differs it is usually necessary and always simpler. Where it is one owner, separate ledgers with a clean allocation can be enough.
What is the most common reporting failure?
A consolidated figure that cannot be traced to per-property transactions, which means one of the two is wrong and nobody knows which.
When should permissions be set up?
Before the first outside person is given access, which in practice means at setup rather than when the first contractor asks.