What managing agents should look for in property software

Start with the managing-agent model, not generic property tools

A managing agent is not a single landlord managing a single building. You act on behalf of many clients at once — multiple landlords with rental stock, and multiple bodies corporate, homeowners' associations or sectional-title schemes with their own funds, trustees and members. Generic property tools are often built for one owner's view, and they tend to strain the moment you need to keep dozens of separate client ledgers, trust balances and reporting lines apart.

When you evaluate software, frame every demo around your real structure: multiple clients, each with their own money and records, all administered by your firm. Ask to see how a single login moves between a rental landlord's portfolio and a scheme's levy book without the data bleeding together. The architecture that supports this cleanly is generally very different from a tool designed for an individual owner.

Per-client trust accounting is the non-negotiable core

Managing agents hold and administer money that belongs to clients, so trust accounting is the heart of the evaluation. The Property Practitioners Act 22 of 2019 (notably section 54) deals with trust account obligations for property practitioners, and community schemes carry their own financial duties under the STSMA (Act 8 of 2011) and the CSOS Act (Act 9 of 2011). Your software should be designed to support keeping client funds clearly separated, reconciled and reportable per client — not pooled into one undifferentiated ledger.

Test the basics hard. Can the system maintain a distinct trust position per landlord and per scheme? Does it reconcile receipts (rent, levies, special levies) against expected amounts and flag shortfalls? Can it produce a per-client trust statement on demand that an auditor or trustee would accept? Does every movement of money carry a traceable source and authorising user? Trust accounting that looks tidy in a sales deck but cannot survive a year-end audit is a liability, so insist on seeing real reconciliation and statement output.

• Separate trust position maintained per landlord and per scheme
• Receipt reconciliation for rent, levies and special levies with shortfall flags
• Per-client trust statements suitable for audit and trustee review
• Every transaction traceable to a source document and an authorising user

Audit trails and reporting that withstand scrutiny

Because you answer to landlords, trustees, auditors and ultimately the regulator, an immutable, queryable audit trail is generally as important as the accounting itself. Look for a system that records who did what, when, and to which client record — including financial postings, changes to leases or levy rolls, document uploads and approvals. The value of an audit trail is in its completeness: if any sensitive action can happen off the record, the trail is weakened.

Reporting should be available per client and across your whole book. Trustees typically want scheme-level financials, a current levy roll and arrears positions; landlords want their own statements and arrears; and you want a firm-wide view to manage your business. Confirm that reports can be generated per scheme, per landlord and in aggregate without manual spreadsheet assembly, since hand-built reporting is where errors and disputes usually originate.

Role-based access and approval workflows

A managing-agent firm has many hands on the system — portfolio administrators, accounts staff, directors, and sometimes client-side trustees or landlords with limited views. Role-based access control lets you grant each person only what their job requires, which protects client data and reduces the risk of unauthorised or accidental changes. Ask how granular the roles are and whether you can scope access to specific clients or portfolios.

Structured approval workflows matter just as much. Payments out of a trust account, supplier invoices, levy adjustments and similar sensitive actions should generally require an explicit, recorded authorisation before they take effect. A system designed to support multi-step approvals — request, review, approve, with each step logged — gives you internal control and gives clients confidence that nothing material happens without sign-off.

One platform for mixed rental and scheme books

Many South African managing agents run both rental portfolios and community schemes. Splitting these across two systems generally fragments your trust accounting, duplicates client and contact data, and forces staff to reconcile across tools. A platform that natively handles both rental management and community-scheme management — leases and rent collection on one side, levy rolls and scheme governance on the other — typically reduces error, training overhead and reconciliation effort.

When assessing this, look beyond a feature checklist. Check that a single client record, contact and document store serves both sides, that trust accounting spans rental and levy money under one consistent model, and that reporting can cut across the whole book. Regalis is built to administer mixed rental and community-scheme portfolios from one platform, with per-client trust accounting and scheme-level governance handled in the same system rather than as separate products.

Fee invoicing, levy and rent collection, and arrears

Your firm earns management fees, and those fees must be invoiced accurately and traceably against the correct client. Look for native fee invoicing that can apply your fee structure per client, raise invoices, and tie collection back into the trust ledger so your income is never confused with client funds. Manual fee invoicing outside the accounting system is a common source of leakage and disputes.

On the collection side, the software should handle recurring rent and levy billing, record receipts, and surface arrears clearly. For scheme work, an accurate, current levy roll is central; for rentals, rent collection and arrears tracking under the Rental Housing Act 50 of 1999 framework matter. Confirm the system can age arrears, support follow-up, and report outstanding balances per client and per unit, because arrears visibility is often where good administration is won or lost.

POPIA, data residency and client confidentiality

You hold personal information for tenants, owners, trustees and suppliers, which brings POPIA obligations into play. Software for managing agents should be designed to support lawful processing — controlled access, the ability to honour data-subject requests, retention controls, and clear separation of each client's data. Ask the vendor how access is restricted, how data is secured, and whether South African data residency is offered, since residency is increasingly relevant for compliance comfort.

Confidentiality between clients is part of this. Because you administer competing landlords and unrelated schemes on one platform, the system must keep each client's information walled off from the others by design, exposing it only to authorised users. Treat data protection as a first-class evaluation criterion, not a tick-box at the end.

A practical evaluation checklist

Before committing, run a structured comparison of approaches rather than a beauty parade of brands. Use a consistent set of questions across every system so you compare like with like, and insist on seeing your own scenarios — a real reconciliation, a real trust statement, a real approval — rather than canned demos.

• Per-client and per-scheme trust accounting with audit-ready statements
• Complete, immutable audit trail across money, records and approvals
• Granular role-based access, scoped to clients or portfolios
• Recorded multi-step approvals for payments and sensitive changes
• Native fee invoicing tied correctly to each client
• Recurring rent and levy billing, receipting and arrears reporting
• Single platform for mixed rental and community-scheme books
• POPIA-aligned data controls and South African data residency