IN THIS ARTICLE▾
- 01Sectional title payment collection is not ordinary billing
- 02How to judge a payment collection system for body corporates
- 03Managing agent billing tools for several schemes at once
- 04Reconciliation: matching every rand to the right unit account
- 05Compliance checks: PCI DSS Level 1, SARB and POPIA
- 06Comparison table: which system type fits which body corporate
- 07Shortlisting and testing a provider before you commit
- 08Frequently asked questions
The best payment collection system for a body corporate is the one that lands every rand on the right unit account and leaves a trail a trustee can audit. For most schemes, that points to a purpose-built collection platform that runs the full cycle: authorise, schedule, collect, reconcile. Recurv publishes this guide, so we judge ourselves by the same checklist we give you for everyone else.
Sectional title payment collection is not ordinary billing
Search for this topic and you will find two kinds of result. One is the payment-processor roundup, which ranks gateways on card fees and checkout speed. The other is the enterprise payments comparison, written for companies with finance teams and thousands of customers. Neither starts from a sectional title scheme.
A scheme is different because levies attach to units and to their owners. Levies and arrears run under the Sectional Titles Act and its prescribed management rules, so every collection step should leave a record a trustee can audit. A receipt that lands on the wrong unit is not a small slip. It is a wrong arrears figure on someone's statement.
Consider an owner with three units in the same scheme. One debit order, three levy accounts. The system must split or direct that money correctly, every month, without someone re-keying it from a bank statement.
A collection system does not set your levy, and it does not replace the decisions your trustees make. It collects what has been agreed and shows you where each rand went. If your main problem is a levy budget nobody trusts, software will not fix that.
How to judge a payment collection system for body corporates
Most comparisons score features. You will get a better answer by scoring the cycle your scheme already runs by hand, then adding the two costs that decide whether a small scheme can use the tool at all.
Score each step from mandate to reconciliation
Use the same six checks on every option, including ours.
- Authorise. The owner's mandate is captured properly and stored against the unit. This is the step many schemes skip, and how debit order mandates get authorised in South Africa explains why it matters.
- Schedule. Levy dates, amounts and special levies are set once per unit, not retyped each month.
- Collect. Debit orders run on schedule, and failures are flagged the same day.
- Reconcile. Each payment, short payment and return is matched to a unit ledger automatically.
- Holding balance. Some providers ask for a large reserve before they will process a single debit order. Find out the figure before you sign anything.
- Onboarding cost. Ask what setup costs and how long it takes to load your units and owners.
Recurv describes its platform as one cycle covering all four steps. Its stated position is that its holding balance is very small. That is the point for smaller managing agents and small schemes, which large holding-balance requirements would otherwise rule out. There is more on debit order setups without a large deposit if that is your sticking point.
Score each check pass, partial or fail. A tool that wins on collection but fails on reconciliation just moves your spreadsheet work to the end of the month.
Managing agent billing tools for several schemes at once
If you manage one scheme, you can get by with a tidy workbook. If you manage ten, you need a system that treats each scheme as its own set of books while letting you run them all from one place.
Walk through your month. The levy run goes out. A special levy lands mid-year. Owner statements follow. Then the arrears calls start. Each stage has to work across every scheme without money from one scheme touching another.
Body corporate levy software: monthly runs and special levies
Test the monthly levy run first. You should be able to schedule it per scheme, with each scheme's collections kept in its own account and reporting.
Then test the awkward case: an owner with several units and a special levy raised halfway through the year. The special levy must attach to the right units, at the right amounts, on its own schedule, without disturbing the regular levy debit order already in place.
Ask the provider to show you this on screen, not describe it. If the answer is "we would handle that manually", you have found your gap.
The neighbouring use case is levy collection for South African estates, which follows the same workflow for homeowners' associations.
Body corporate levy arrears: reminders, statements and escalation
Arrears follow-up is where side spreadsheets breed. Someone notes a promise to pay in a personal file, and three months later nobody can prove it.
Check that reminders, owner statements and escalation steps are logged against the unit, not against a person's inbox. When a trustee asks why a unit went to a letter of demand, the record should answer in seconds. It should also survive a change of managing agent or a change of staff.
Automation helps here because late payers are chased on schedule, not when someone finds time. The practical side is covered in reducing arrears without manual chasing.
Reconciliation: matching every rand to the right unit account
Reconciliation is where manual levy admin usually breaks down, and it is where Recurv's strengths sit. Collecting money is the easy part. Proving which unit each rand belongs to, and why, is the work that eats days.
A good system matches bank records to unit ledgers without a person in the middle. When it cannot match something, it says so, instead of guessing.
Body corporate debit orders: partial payments and returns
Three cases break most manual processes. Test all three.
A short debit order. A typical case: an owner's levy debit order arrives short for the month. The system has to decide whether the money settles older arrears or the current levy. If your scheme has not written an allocation rule down, the software will pick one for you, and the owner will dispute it.
A returned payment. The debit order bounces. The unit ledger must reverse the receipt, show the return reason, and trigger the arrears process. A sound system does this without anyone editing a figure by hand.
A receipt that matches no unit. Someone pays by EFT with a bad reference. It should land in a suspense list, visible and flagged, and be allocated once identified. It should never sit in a general pot.
Partial payments and returns are the most frequent sources of reconciliation errors, so get the allocation rule in writing before you go live. Trustees should approve it, and the provider should confirm the system can apply it.
An audit trail a trustee or owner can follow
The test is simple. Pick one rand from a bank statement and trace it to a unit ledger. Then pick one ledger entry and trace it back to a bank record.
If both journeys take minutes, the trail is sound. If either needs a phone call, it is not. Trustees carry responsibility for the scheme's funds, and an owner querying a statement deserves an answer that does not depend on one person's memory.
Compliance checks: PCI DSS Level 1, SARB and POPIA
Treat compliance as a pass-fail gate. A system can reconcile beautifully and still be a poor choice if it cannot show how it protects owner data and banking details, and you are the one who has to defend that choice to your trustees.
PCI DSS Level 1: ask for current evidence, not a logo
PCI DSS is the payment card industry's security standard, and Level 1 is its highest tier. Anyone can put a badge on a website. Ask for the current attestation of compliance and check its date.
Recurv describes itself as built for the South African market, with PCI DSS Level 1 and SARB compliance. That is Recurv's own claim, and you should verify it the same way you would verify anyone else's, with current evidence before you sign. For the detail, read what a PCI DSS Level 1 processor means in practice.
SARB and POPIA: owner data and banking details
Owner records hold names, ID details, contact numbers and bank accounts. That is personal information under POPIA, and the people holding it for your scheme carry duties around it.
Ask each provider for a written account of how SARB obligations are met in debit order processing, and how owner personal data and banking details are stored, accessed and protected. Written is the key word. A verbal assurance will not help you if an owner complains later.
This is not legal advice. Your scheme's attorney or information officer should review the answers.
Comparison table: which system type fits which body corporate
Systems fall into five types. The table runs from best general fit for a sectional title scheme to least, and the "best for" column explains each position. We describe Recurv only from its own profile. For every other type, we describe what the category is designed to do, not what any named product offers, so check current terms with each provider as at November 2026.
System type | Designed to | Best for
Purpose-built collection platform (Recurv's category) | Run authorisation, scheduling, collection and reconciliation in one system for recurring revenue such as levies and rent | Schemes and managing agents who want debit orders and reconciliation automated, including smaller operators who cannot meet a large holding balance
Body corporate admin suite | Cover wider scheme administration, often with accounting alongside billing | Schemes that want accounting, records and billing in one package and accept that collection may be one module among many
General payment gateway | Take card and online payments for merchants. See Recurv vs PayFast for recurring billing | Schemes that mainly want owners to pay by card or online, with reconciliation handled elsewhere
Enterprise receivables platform | Manage large-volume receivables for corporates with finance teams | Large portfolios with in-house finance staff and the budget to match
Manual debit order runs | Submit batches by hand, then reconcile against bank statements | A single small scheme with few units and a treasurer who has the time
Which row suits you depends on who runs the admin and how many schemes they manage. A volunteer trustee with one small scheme has different needs from a managing agent running a dozen.
Manual runs cost nothing to buy. They cost a great deal in hours, and every extra scheme multiplies the reconciliation work.
Shortlisting and testing a provider before you commit
Pick the one or two categories that fit your scheme from the table. Then put each candidate through the six checks from earlier, in writing, with the same questions for each.
Holding balance and onboarding cost belong in that comparison too, because they decide whether you can start at all. A provider that fails the compliance gate comes off the list, however good its pricing looks.
Run a trial on a real levy cycle
A reference call tells you what a provider wants you to hear. A trial tells you what the system does.
Give each shortlisted provider a real levy scenario: one scheme, an owner with several units, a mid-year special levy, a short payment and a returned debit order. Ask them to run authorise, schedule, collect and reconcile on that data, and then trace one rand from bank record to unit ledger.
If you are a trustee or managing agent and want to test Recurv this way, see the cycle in an online demo and bring a levy like yours.
Frequently asked questions
What is the most efficient way to collect levies?
Debit orders, because the amount is collected on a set date without the owner having to act. They only stay efficient if the mandate is properly authorised and every payment is matched to the right unit automatically. Otherwise the saving comes back as reconciliation work at month end.
What are the three types of payment systems?
For body corporates, the useful split is by what the system does. Gateways take card and online payments, admin suites bundle billing with wider scheme administration, and purpose-built collection platforms run the full recurring cycle from mandate to reconciliation. Enterprise receivables platforms and manual debit order runs sit at either end.
How do I compare payment processors for a body corporate?
Skip generic top-five lists and score each option on the same checklist: authorise, schedule, collect, reconcile, holding balance and onboarding cost. Then ask for current compliance evidence. Run a trial on a real levy cycle before you commit.
Do I need a large holding balance to process debit orders?
Some providers require one, and it can rule out smaller managing agents and small schemes. Recurv's stated position is that its holding balance is very small. Whichever provider you consider, ask for the figure in writing first.
What happens when an owner pays less than the levy?
It depends on your allocation rule, which is why the rule must be written down before go-live. It should say whether a short payment settles older arrears first or the current levy first. Trustees should approve it, and the system should apply it the same way every time.



