A property-software requirements checklist (South Africa)

How to use this checklist

Start by writing your own context at the top: portfolio mix (sectional title schemes, HOAs, rental stock), number of units, who the daily users are, and which functions are dealbreakers versus desirable. A 12-unit single-scheme trustee has very different needs from a managing agent running mixed residential and community-scheme portfolios.

Then turn each line below into a scored question. A simple approach is to mark each requirement as Must-have, Should-have or Nice-to-have, and rate every shortlisted vendor out of five against it. Ask vendors to demonstrate the capability live on their own data, not describe it. Where a feature is claimed, ask to see it configured for a South African workflow — a levy run, a trust reconciliation, an arrears letter — rather than a generic example.

Keep the same scorecard across all vendors. The discipline of identical questions is what makes your final recommendation defensible to trustees, owners or a board.

Core functional must-haves

These are the day-to-day capabilities most portfolios need regardless of provider. Confirm each one exists, works on your data, and is included in the quoted price rather than a paid add-on.

• Property, unit and owner/tenant records with a clear single source of truth
• Lease management: capture, renewals, escalations and document storage
• Levy and rent invoicing with batch (mass) billing and statements
• Receipting and allocation, including handling of part-payments and credits
• Arrears tracking with ageing and configurable reminder and letter workflows
• Maintenance and inspection logging, work orders and contractor records
• Meeting support for AGMs and trustee/committee meetings, including notices and minutes
• A document repository with permissioned access for owners, tenants and trustees
• Role-based portals so owners, tenants and trustees see only what they should
• Audit trails on financial and record changes

South African rails and regulation

This is where global software typically falls short and where you should weight your scoring most heavily. South African property management sits on top of specific statutes and money rails, and the software either supports them properly or creates manual workarounds that erode the value of buying software at all.

For community schemes, confirm the system is designed to support the framework around the Sectional Titles Schemes Management Act (STSMA, Act 8 of 2011) and the Community Schemes Ombud Service Act (CSOS Act, Act 9 of 2011) — for example managing a levy roll, distinguishing administrative and reserve funds, and producing the records bodies corporate and HOAs are generally expected to keep. Ask how the system supports CSOS-related reporting and levy obligations rather than assuming it does.

For trust accounting, the Property Practitioners Act (Act 22 of 2019) places obligations on practitioners who handle clients' money, including trust account requirements (commonly referenced around section 54). Your software should be designed to support segregated trust handling, reconciliation and the kind of audit-ready records a practitioner needs. Treat trust accounting integrity as a top-tier requirement, not a reporting nicety.

For rentals, the Rental Housing Act (Act 50 of 1999) shapes lease, deposit and receipt practices, so check the system handles deposits, statements and the documentation a landlord or rental agent is generally expected to maintain.

• Levy roll and dual-fund (administrative and reserve) accounting for schemes
• Trust accounting designed to support practitioner obligations and reconciliation
• Support for South African payment rails and bank statement import/reconciliation
• Tenant vetting/credit-check workflow integration (e.g. a recognised tenant data source)
• VAT handling and South African statement and invoice formats
• ZAR currency handling and local date/number formats throughout

Data security and POPIA

Property systems hold large volumes of personal information — ID numbers, contact details, financial records and banking data — which makes the Protection of Personal Information Act (POPIA) directly relevant. Your vendor is generally a processor of personal information on your behalf, so the security and contractual terms matter as much as the features.

Ask where data is hosted and whether it stays in South Africa or is transferred cross-border, since data residency affects your POPIA position. Where data is processed outside the country, you should understand the safeguards in place. Confirm encryption in transit and at rest, role-based access controls, and meaningful audit logging of who accessed or changed what.

• A written processing/operator agreement covering POPIA obligations
• Clarity on data hosting location and any cross-border transfer safeguards
• Encryption of data in transit and at rest
• Granular, role-based permissions and enforced access controls
• Audit logs for sensitive financial and personal-data actions
• Backup, retention and a stated recovery approach
• A clear data-breach notification process
• Your right to export and delete data, supporting data-subject requests

Integrations and money flow

Software that cannot move money and data cleanly creates manual re-keying, which is where errors and reconciliation pain come from. Map your existing tools — banking, accounting, payment collection, communications — and confirm how the new system connects to each.

Pay particular attention to how bank statements come in and how payments are matched. Automated or assisted reconciliation against imported bank data is one of the highest-value capabilities for a managing agent, so test it on a real statement during evaluation.

• Bank statement import and assisted/automated reconciliation
• Payment collection rails appropriate to your levy and rent flows
• Accounting system export or integration if you keep a separate ledger
• Email and SMS/communications for notices, statements and reminders
• Document generation (statements, letters, certificates) and bulk send
• An API or supported export if you need to connect other tools later
• Bulk data import for onboarding existing portfolios

Reporting and oversight

Trustees, owners, landlords and auditors all need to see the numbers. Beyond standard statements, check the system produces the financial and operational reports your stakeholders expect, and that owners and trustees can self-serve much of this through their portals to reduce ad-hoc requests on your team.

Ask to see real reports generated live: an income and expenditure view, a balance position, arrears ageing, a levy roll, and a trust reconciliation. Confirm reports export cleanly to PDF and a spreadsheet format for further analysis or audit packs.

• Income and expenditure, and a balance/financial position view
• Arrears ageing and collection-status reporting
• Levy roll and reserve-fund reporting for schemes
• Trust reconciliation and audit-ready financial records
• Owner, trustee and landlord self-service dashboards
• Clean export to PDF and spreadsheet formats

Support, onboarding and migration

The best feature set fails if onboarding stalls or support is unreachable. Ask exactly how your existing data is migrated, who does the work, how long it takes, and what it costs. Request a written migration plan and a defined go-live checkpoint.

Confirm support channels, hours and response expectations, and whether support is South Africa-based and familiar with local compliance. Ask about training for your team and the portals you will roll out to owners and tenants.

• A documented data-migration process with responsibilities and timeline
• Bulk import of existing properties, owners, tenants, leases and balances
• Training for staff and rollout guidance for owner/tenant portals
• Stated support channels, hours and response expectations
• Local support familiar with SA compliance and money rails
• A named onboarding contact and a defined go-live milestone

Commercial terms and exit

Finally, scrutinise the contract as carefully as the software. Pricing models vary — per unit, per portfolio, tiered, or by module — so calculate total cost against your actual unit count and the modules you genuinely need, not a headline rate. Watch for features that appear in the demo but sit behind paid tiers.

Most importantly, confirm your exit rights before you sign. You should be able to export your full data set in a usable format if you ever leave, with no hostage situation over your own records. Clarify contract term, notice period, price-increase mechanics and what happens to data on termination.

• A transparent pricing model mapped to your real unit count and modules
• Clarity on what is included versus paid add-ons
• Contract term, notice period and price-escalation terms
• Full data export rights on exit, in a usable format
• What happens to your data after termination
• Any setup, migration or training fees stated upfront