Bulk operations software for South African schemes
Run 200 schemes in one click.
Multi-scheme bulk operations built for Mafadi-class scale. One-click bulk levy run dispatching the month across every scheme in parallel; supplier-payment batches with ACB EFT file export OR Stitch payouts dispatch on a six-stage approval workflow; and portfolio bank reconciliation import with drag-and-drop CSV parsers for FNB, Standard Bank, Nedbank, ABSA and Capitec. Per-scheme isolation means one failure never blocks the other 199.
- Multi-scheme levy run
- ACB EFT or Stitch payouts
- 5 SA bank CSV parsers
- 6-stage approval
- Per-scheme isolation
Schemes run in parallel, tunable to your firm's throughput. Live progress dashboard with per-scheme completion and failure surfacing.
FNB, Standard Bank, Nedbank, ABSA, Capitec — the bank is identified automatically on upload, and reconciliation runs across every trust account in scope.
Drafted, reviewed, approved, executed — each stage has its own role gate and a full audit trail to support audit preparation.
The difference between a 50-scheme MA and a 200-scheme MA is not a bigger team. It is bulk operations.
A South African managing agent firm running 50 community schemes can absorb the per-scheme manual click-overhead of legacy platforms. The first-of-the-month levy run takes a morning. Supplier payments take an afternoon. Bank reconciliation takes another afternoon. It is grumpy work but it is survivable.
A firm running 200 schemes cannot. The same per-scheme overhead multiplies into a week-long ordeal, and the team starts dropping balls — levy runs happen late, reconciliations get behind, supplier payments stack up. The firm hits a glass ceiling not because of headcount or capability but because the software was not built for that scale.
Regalis was built with bulk operations as a first-class workflow, not an afterthought. The multi-scheme levy run is one click. The supplier batch payment workflow handles dozens of payments at once with a structured approval pipeline. The portfolio bank reconciliation accepts five bank formats and runs the trust-reconciliation engine across every trust account. The managing-agent firm grows the book without growing the back-office headcount proportionally.
What the 200-scheme glass ceiling looks like
- The 1st of the month is a full-team event — every PM logs in to fire each of their schemes' levy runs individually. The 2nd is spent on the same task because not everyone finished.
- Supplier payments stack up because each batch requires manual EFT file creation, manual approval routing in Slack, and manual import into business banking. Vendors complain about slow payment.
- Bank reconciliation lives in Excel — bookkeeper exports the bank CSV, the platform CSV, runs them through formulas to spot the deltas. By month-end the deltas have compounded into a multi-day investigation.
- When a single scheme fails mid-month — a missing budget, a misconfigured chart of accounts, a participation-quota mismatch — there is no isolation, so half the firm's schemes end up needing a rerun, and trust account balances temporarily drift.
- When a class of bug exists in the legacy platform — for example, two schemes' levy runs overwriting each other's invoices — the firm finds out at year-end audit when the balances do not tie out.
- The firm cannot grow past ~150 schemes without doubling headcount on the back office. The unit economics stop working.
What Regalis ships out of the box
- One-click multi-scheme bulk levy run, parallel execution, live progress dashboard. 200 schemes in ~5 minutes.
- Supplier-payment batches with structured six-stage approval workflow and ACB EFT file export or Stitch payouts dispatch — choose per batch.
- Drag-and-drop bank CSV reconciliation for FNB, Standard, Nedbank, ABSA and Capitec — the platform identifies the bank, parses the rows, fires the recon engine.
- Per-scheme transaction isolation — one scheme failure never blocks the other 199, and successful runs are not rolled back. Failed schemes surface on the dashboard for individual rerun.
- We caught a class of bug in our own platform (two schemes' levy runs silently overwriting each other's invoices), fixed it, and added an automated test. Legacy systems may still carry similar bugs unaddressed.
- The 200-scheme firm runs first-of-the-month in roughly the time a 30-scheme firm used to. Headcount grows with revenue, not with click-count.
From first-of-the-month to mid-month reconciliation.
Multi-scheme bulk levy run
On the 1st of the month (or whenever your firm runs levies), open the bulk levy run page, select the period, confirm the scope (defaults to every active scheme in the portfolio), and fire. Each scheme runs in its own transaction in parallel. The dashboard shows live progress, completion count, and any failures with the specific scheme + reason. Failed schemes can be rerun individually after fixing the cause.
- One-click dispatch across all schemes
- Parallel execution, tunable to your throughput
- Live progress dashboard
- Per-scheme failure surfacing with reasons
Bank reconciliation across the portfolio
Mid-month or end-month, your bookkeeper exports the bank CSV (or multiple CSVs across multiple banks) and drags them onto the portfolio reconciliation page. The platform identifies the bank automatically (FNB, Standard, Nedbank, ABSA, Capitec), reads the rows, and runs the trust-reconciliation engine across every trust account in scope. Matches surface for review; exceptions surface for investigation.
- Drag-and-drop CSV upload
- 5 SA bank parsers built in
- Trust recon across all trust accounts
- Match + exception surfacing
Supplier-payment batch
When supplier invoices are ready for payment, the bookkeeper builds the payment batch — selecting the invoices, the source trust accounts, the priority. The batch enters the six-stage approval workflow: drafted, ready for review, reviewed, approved, executing, then executed. Each stage carries the right role gate and captures who acted, when, and why.
- Batch builder with multi-invoice selection
- 6-stage approval pipeline
- Per-stage role gates
- Audit trail with actor + reason
Dispatch via ACB EFT or Stitch payouts
Once approved, the batch is dispatched. If your bank uses ACB EFT files, the platform generates the file in your bank's import format. If you have Stitch payouts enabled, the batch dispatches via Stitch directly. The batch moves to executing and then to executed (or failed) as the bank confirms. The evidence pack — invoice list, payment file, bank confirmation — attaches to the batch record.
- ACB EFT file export per bank format
- OR Stitch payouts dispatch
- Status updates from bank confirmation
- Evidence pack on the batch record
A toolkit built for the firm that wants to grow past 200 schemes.
Multi-scheme levy run
One-click dispatch across every active scheme in the portfolio. Per-scheme transaction isolation. Live progress dashboard with completion + failure surfacing. Failed schemes rerunnable individually.
Parallel execution
Schemes run in parallel, with the number running at once tunable so larger firms can tune throughput. A 200-scheme portfolio typically runs in ~5 minutes.
Per-scheme isolation
One scheme failure never blocks the other 199. Successful runs are not rolled back. Failed schemes surface with the specific cause for targeted intervention.
Silent-overwrite bug fix
We caught and fixed a class of bug where a second scheme's levy run silently overwrote a first scheme's owner invoices. An automated test was added to prevent recurrence; legacy platforms may carry similar bugs unaddressed.
Supplier payment batches
Multi-invoice batch builder with source trust account selection, priority ordering and per-supplier grouping. Built for the firm paying dozens of vendors per month.
Six-stage approval workflow
Drafted, ready for review, reviewed, approved, executing, then executed. Each stage has its own role gate and captures who acted, when, and why, with a full audit trail.
ACB EFT file export
Automated Clearing Bureau EFT files in your bank's import format. Per-bank formatting (FNB, Standard, Nedbank, ABSA Business). Drop into business banking for execution.
Stitch payouts dispatch
Alternative to ACB EFT: dispatch the batch via Stitch payouts directly. Same six-stage workflow, same audit trail, same evidence pack — different rail. Choose per batch.
Portfolio bank reconciliation
Drag-and-drop bank CSV upload on the portfolio reconciliation page. Multiple files, multiple banks, one session. Runs the trust-reconciliation engine across every trust account.
FNB CSV parser
Native parser for First National Bank business banking exports. Identifies the format automatically; no manual mapping.
Standard Bank CSV parser
Native parser for Standard Bank business banking exports. Handles both balance-style and entry-style CSV formats.
Nedbank CSV parser
Native parser for Nedbank business banking exports. Identifies the format automatically; handles multi-statement files.
ABSA CSV parser
Native parser for ABSA Business Online exports. Identifies the format automatically; handles the ABSA-specific row layout.
Capitec CSV parser
Native parser for Capitec Business exports — particularly useful for smaller schemes using Capitec rather than the legacy big four.
Match + exception surfacing
Auto-matches against the right invoice via reference rules + tolerance band for partial payments. Exceptions surface for investigation with the candidate matches shown.
Trust account integrity
Bulk operations carry the same trust-account safeguards individual operations do — an immutable ledger, retries that never double-post, and post-run reconciliation against the bank-side balance.
Run history + replay
Every bulk run is logged with the operator, the scope, the outcome and a per-scheme breakdown. Re-runs of failed schemes are tied to the original run for audit.
Live progress dashboard
Bulk run progress is visible in real time — per-scheme status, overall completion, time-elapsed, estimated time-remaining. The operator stays informed; the team can plan around it.
When two scheme levy runs in the same month silently destroy each other's invoices, you have not noticed the bug because the symptom is invisible.
Some bugs in financial software are loud — a stack trace, a crashed page, an obvious failure. Some are silent. The silent ones are the dangerous ones, because the damage compounds for weeks before anyone notices the balances do not tie out at year-end audit.
We caught one of those in our own platform recently. In a multi-scheme scenario where two schemes' levy runs fired in the same period, owner invoices were not correctly scoped to the owning scheme. A second scheme's run could silently overwrite owner invoices from a scheme that had already run. The owners never knew. The trustees never knew. The managing agent never knew — until the balances stopped tying out. We traced it, fixed the scoping, added an automated test, and shipped the fix.
The story matters because legacy South African community-scheme platforms may carry a similar class of bug. When the historical design assumption was one-scheme-at-a-time, the rules that keep each scheme's records separate can be brittle. When you run two scheme levies in the same month — which is normal for a managing agent with 200 schemes — you do not want one quietly overwriting the other. Regalis tested for this explicitly, and the test runs on every release.
Continue exploring how Regalis handles the rest of the rental operation.
Levy collection
Structured levy arrears recovery — DebiCheck retries, 4-bucket age analysis, CSOS-grade evidence pack. The collection side of the same engine.
Read moreManaging agent software
Multi-landlord oversight, view-as principal, approvals workflow, MA fee invoicing — built for SA managing-agent firms.
Read moreCommunity schemes overview
The integrated community-schemes mode covering HOA, body corporate, sectional title and share block on one platform.
Read moreCommon questions about bulk operations.
Can I run levies for all schemes at once?+
Yes. The multi-scheme bulk levy run dispatches the monthly levy run across every scheme in your portfolio in one click. Each scheme runs in its own transaction with its own participation quotas, its own budget and its own chart of accounts — but you fire it from one screen with one click and watch progress on a live dashboard. A 200-scheme portfolio that used to take half a day of clicking now takes the time it takes to make a coffee.
Do you export ACB EFT files?+
Yes. The bulk supplier-payment batch produces an Automated Clearing Bureau (ACB) EFT file in the format your bank expects for import into business banking. The same batch can dispatch via Stitch payouts where you have the integration enabled — same six-stage approval workflow, same audit trail, same evidence pack. The choice is per batch, not per platform.
Which banks are supported for CSV import?+
Five major South African banks ship with native CSV parsers: FNB, Standard Bank, Nedbank, ABSA and Capitec. Drag the bank-export CSV onto the portfolio reconciliation page and the platform identifies the bank automatically, reads the rows, and runs the trust-reconciliation engine across every trust account in scope. Multiple files for multiple banks can be uploaded in the same session.
What happens if a single scheme fails in a bulk run?+
Per-scheme isolation. Each scheme runs in its own transaction. If one scheme fails (a missing budget, a misconfigured chart of accounts, a participation-quota mismatch), it fails alone — the other 199 still complete. The failure is surfaced on the bulk-run dashboard with the specific scheme and the error reason, and the operator can re-run the failed schemes individually after fixing the cause. The successful runs are not rolled back.
How does the six-stage approval workflow work?+
Supplier payment batches move through six stages: drafted, ready for review, reviewed, approved, executing, then executed (or failed). Each stage carries the right role gate — typically the bookkeeper drafts, the property manager reviews, the manager approves, and the bookkeeper executes. Each stage transition captures who acted, when, and why. The records are structured to support an audit trail, so trustees can see exactly who approved what and when.
Did you really fix a silent-overwrite bug in legacy systems?+
We fixed it in our own platform: in a multi-scheme scenario, a second scheme's levy run could silently overwrite owner invoices from a scheme that had already run in the same period. We caught it in production, traced it to invoices not being correctly scoped to the owning scheme, fixed it, and added an automated test so it cannot recur. The story matters because legacy South African scheme platforms can carry a similar class of bug — when you run two scheme levies in the same month, you do not want one quietly overwriting the other. We test for it explicitly; ours does not.
Are the bulk operations safe for trust accounts?+
Yes. Trust account integrity is the highest priority. Every bulk operation carries the same trust-account safeguards individual operations do: each scheme runs in isolation, ledger entries are immutable, retries are handled safely without double-posting, and every run is reconciled against the bank-side balance afterwards. The bulk operation is designed so it cannot put the trust ledger out of balance; if anything would, the run stops and reverses cleanly. These workflows are built to support South African property-practitioner trust-accounting requirements.
How long does a 200-scheme levy run take?+
A 200-scheme bulk levy run completes in roughly 4-6 minutes. Schemes run in parallel, with the number running at once tunable to your firm's needs. The live dashboard shows progress per scheme, completion count and failure count. For comparison: doing the same work scheme-by-scheme on a legacy platform takes 30-60 seconds per scheme of attention even when the system itself is fast — call it 100-200 minutes of operator time, easily a half-day.
See everything built for you — explore the property managers hub
Run 200 schemes in one click.
Not 200 clicks.
Walk through the multi-scheme bulk levy run, the six-stage supplier-payment workflow and the portfolio bank reconciliation with someone from the team.