Rental management software: a South African buyer’s guide

Start with trust accounting — it is the dealbreaker

For any managing or rental agent handling client money, trust accounting is the first thing to evaluate and the easiest place for a system to fail you. Client funds — rent collected, deposits held, supplier floats — must be kept separate from your operating money, and every cent must reconcile. The Property Practitioners Act 22 of 2019 (generally referenced around section 54 for trust account obligations) sets the framework agents work within, and your software should be designed to support those obligations rather than leave you to bridge gaps in a spreadsheet.

Practically, look for a system where each receipt and payment posts to a ledger automatically, where the trust position is always visible, and where bank reconciliation is a built-in workflow — not a manual export. A genuine general-ledger posting engine, with idempotent journals tied to the source receipt or invoice, is what lets you trust the numbers under audit. Ask to see how the software handles a deposit held on behalf of a landlord versus rent due to that same landlord — the two must never blur.

• Separate trust and operating ledgers with a live trust position
• Automated journal posting from receipts, invoices and payments
• Built-in bank reconciliation, not a manual spreadsheet step
• An audit trail you can hand to an auditor without re-keying

Tenant screening: insist on TPN or equivalent

Placing a tenant without screening is the single most expensive mistake in rental management. South African agents typically screen through TPN, which aggregates payment-behaviour and credit data specific to the rental market. Your software should let you initiate a screen from inside the applicant workflow and attach the result to the lease record — not send you off to a separate portal and back.

When you evaluate screening, check whether consent capture is handled properly (this intersects with POPIA), whether results are stored against the applicant with the right retention controls, and whether the workflow nudges you to screen before a lease is signed rather than after. Screening is only useful if it sits at the decision point.

Collections: DebiCheck-ready, not EFT-by-hand

Rent collection is where cash flow lives or dies. The strongest setups use authenticated debit-order collection — DebiCheck — so that mandates are verified up front and disputes are reduced. When assessing a system, ask how it handles mandate setup, collection runs, failed collections and the arrears that follow. Manual EFT reconciliation, where you match bank statements to tenants by hand, is the workflow you are trying to leave behind.

Tie this to arrears management. Good software turns a failed collection into a tracked arrears case with reminders, escalation steps and a clear paper trail — useful if a matter ever heads toward the Rental Housing Tribunal under the Rental Housing Act 50 of 1999. The goal is fewer manual follow-ups and a defensible record of every contact.

• Authenticated mandate setup and verified collection runs
• Automatic handling of failed collections into arrears
• Reminder and escalation sequences with a logged history
• Reconciliation of incoming payments back to the tenant ledger

Lease management and the documents around it

A lease is more than a PDF. Strong rental software models the lease as structured data: parties, term, escalation, deposit held, renewal and expiry dates — with derived status that flags leases as expiring or expired based on the dates, not just the stored state. That lets the system warn you ahead of renewals and deposit refunds instead of leaving you to diary them manually.

Check how documents attach to the lease, how renewals and escalations are handled, and whether deposit accounting flows correctly into the trust ledger. Deposits are client money; the lease record and the trust account must agree on the held amount at all times.

POPIA and data handling are buyer requirements

POPIA makes data protection a procurement question, not an afterthought. You are processing tenant identity documents, credit results, banking details and contact information — all personal information. Ask where the data is hosted (data residency in South Africa is a reasonable expectation for POPIA-aligned operations), how access is controlled by role, what the retention and deletion policy is, and how a data subject access or deletion request is handled.

A serious vendor will have answers in writing: role-based access, encryption of sensitive fields such as banking details, audit logging of who accessed what, and a defined breach-handling process. If consent for screening or marketing is involved, confirm the system captures and stores that consent against the record.

Portals: give tenants, landlords and trustees their own view

Portals reduce the phone calls and emails that eat an agent's day. A tenant portal lets renters view their statement, lodge maintenance requests and upload proof of payment. A landlord portal gives owners visibility of their statements and payouts without a monthly call. For agents who also manage community schemes, a trustee portal serves the same purpose for body corporate or HOA oversight.

When you compare portals, look past the screenshots: does the data shown match the ledger exactly, can a tenant actually submit proof of payment that lands in your workflow, and is access scoped so each party sees only their own information? A portal that shows stale or wrong figures creates more support load than it removes.

The migration is where buyers get hurt

Most disappointment with new rental software is really a botched migration, not a bad product. The riskiest data is the money: opening balances per tenant and landlord, deposits currently held, and outstanding arrears. These must transfer accurately and then reconcile against your trust bank position before you go live. If they do not balance on day one, every report after that is wrong.

Insist on a packet-based, checkpointed migration rather than a single all-or-nothing import — so one bad row never sinks the whole run — and on a reconciliation sign-off step. Column mapping from your existing exports (with sensible synonyms so fields line up) saves days of manual cleanup. Run a trial import, reconcile the trust position to the cent, and only then cut over.

• Migrate opening balances, deposits held and arrears first and verify them
• Reconcile the trust position to the bank before go-live, not after
• Prefer packet-based imports with a dead-letter list for bad rows
• Keep your old system read-only for one cycle as a fallback

Questions to ask every vendor

A vendor-neutral checklist keeps demos honest. Ask each provider the same questions and compare the answers, not the marketing. The strongest signal is a vendor who answers the hard ones — reconciliation, migration, POPIA — without deflecting.

• Show me a full bank reconciliation in the live system, end to end.
• How do you keep trust and operating funds separate, and where is the audit trail?
• How does tenant screening work and how is consent captured and stored?
• What does the migration plan look like, and how do you reconcile opening balances and deposits?
• Where is our data hosted, who can access it, and how do you handle a POPIA deletion request?
• What happens to a failed debit-order collection — walk me through the arrears flow.