IN THIS ARTICLE▾
CSOS and the STSMA both expect an SA community scheme's levy collection process to produce a clean, auditable paper trail, not a spreadsheet rebuilt from memory.
Every South African body corporate and HOA operates under a layer of regulation most other recurring-billing contexts don't have to think about: the Sectional Titles Schemes Management Act (STSMA) for body corporates, and CSOS oversight, the Community Schemes Ombud Service, across both body corporates and HOAs. Neither piece of legislation was written with debit-order software in mind specifically, but both create real expectations about how a scheme records, justifies, and can account for its levy collection when a dispute or an audit puts that record under scrutiny.
This piece looks at what those expectations actually mean in practice for the collection trail a scheme keeps, and what an audit-ready version of that trail looks like.
What CSOS and the STSMA actually require
CSOS exists as a statutory dispute-resolution body for community schemes, and its 2025 Practice Directive tightened expectations around governance and record-keeping. In practice, this means a scheme needs to be able to show, clearly, what was billed, when, to whom, and what happened when a debit failed, not just a general sense that "most people pay."
The STSMA governs body corporates specifically, including section 3(2), which allows a body corporate to levy interest on arrear contributions. Using that provision defensibly requires being able to show precisely when an owner fell into arrears and for how long, which depends on the underlying collection record being accurate and current, not reconstructed after the fact from a stale spreadsheet.
Neither piece of legislation mandates a specific software system. What they create is a standard the scheme's record-keeping needs to meet if a dispute, an interest charge, or a hand-over to attorneys is ever challenged.
Where manual recon creates compliance risk
A monthly age analysis rebuilt by hand from a bank result file is only as reliable as the person building it and the time they had to do it carefully. If an owner disputes a CSOS-referred arrears matter and the scheme's own record shows an inconsistency, a payment matched to the wrong month, an interest calculation based on an incorrect arrears start date, that inconsistency becomes the owner's argument, not the scheme's.
This isn't a hypothetical. CSOS adjudications turn on exactly this kind of record. A scheme whose collection trail is accurate, timestamped, and generated automatically as part of the collection process, rather than reconstructed by hand after the fact, is in a materially stronger position if a dispute ever needs to go to adjudication.
What an audit-ready trail actually contains
A defensible levy-collection record, at minimum, shows: what was billed to each owner and when, what was actually collected and on what date, the specific reason for any failed collection (as returned by the bank), when an owner's account moved into arrears and by how much, and any interest calculated under STSMA section 3(2) with the dates and figures that calculation depends on.
When this record is generated automatically as part of the collection cycle itself, rather than assembled after the fact from a result file and a spreadsheet, the trail is both more accurate and more readily produced if CSOS, a trustee, or an attorney needs to see it.
What this means for the trustees' own exposure
Trustees carry personal liability considerations under the STSMA and the scheme's governing documents, and a poorly-documented collection process is, in a small but real way, part of that exposure. Being able to show CSOS or an owner exactly how and when a levy was billed, collected, or escalated is a governance safeguard for the trustees themselves, not just an operational convenience for the managing agent.
What this means for POPIA
Owner banking details and payment records are personal information under POPIA, and a scheme's collection system needs to handle that data with appropriate security regardless of which rail it runs on. This isn't a differentiator specific to any one provider, it's a baseline every scheme's collection process needs to meet, and worth confirming explicitly with any rail a scheme is considering, including the one it already uses.
What this isn't
It isn't legal advice, and it isn't a substitute for the scheme's own attorney or managing agent's compliance guidance on a specific dispute or interpretation of the STSMA or CSOS's practice directives. This piece describes what a well-kept collection record looks like structurally; it doesn't replace professional advice on a scheme's specific legal position.
It isn't a claim that better software eliminates disputes. Owners will still dispute charges, sometimes legitimately. What a clean, automated collection trail changes is the scheme's ability to respond to that dispute with an accurate, contemporaneous record rather than a reconstruction built under time pressure after the fact.
It also isn't unique to any one provider as a regulatory matter, every scheme, on every rail, operates under CSOS and the STSMA. The differentiator is whether the collection system generates the audit trail as a natural byproduct of running the cycle, or whether that trail has to be assembled separately, by hand, only when it's needed.
Related reading
See how Recurv handles recurring billing for hoas & estates.
View HOAs & Estates use case →