Running a scheme is not difficult because people are dishonest. It is difficult because life is busy.
Money comes in at different times. Someone forgets a reference. A member needs help early. A big decision is discussed in a WhatsApp thread and then disappears.
Most schemes do not fail because the idea was bad. They fail because the rules were unclear, the records were thin, and people stopped trusting the process.
This guide is for every scheme type we support on Zeturi:
- Stokvels
- Burial societies
- Investment clubs
- Property syndicates
The goal is simple: keep money safe and keep relationships intact.
Rule 1: Write The Rules Down (Before The First Contribution)
A verbal agreement works until it doesn’t.
At minimum, your written rules should answer:
- How much is the contribution?
- When is it due?
- What happens if someone is late?
- Who approves payments and changes?
- How do members leave (and what do they get back, if anything)?
If you cannot write the rule clearly, you probably don’t agree on it yet.
Rule 2: Separate “Policies” From “People”
A healthy scheme does not rely on a single person’s memory or goodwill.
Instead of:
- “Ask Thandi, she knows what we decided.”
Aim for:
- “It’s in the scheme rules and it applies to everyone.”
This protects the admin and it protects the members.
Rule 3: Decide Your Contribution Mode Upfront
Every scheme has a contribution rhythm. Confusion starts when the rhythm changes without a clear process.
Choose one:
- Fixed amount per member (simple and fair)
- Variable amount (flexible, but needs better records)
- Per-unit contribution (useful for unitised schemes)
If your scheme allows variable contributions, make sure your reporting can still explain:
- who paid
- how much
- when
- what it was for
Rule 4: Make Late Payments Boring And Predictable
Late payments are normal. The damage comes from inconsistency.
Pick one approach and document it:
- Grace period (e.g. 3 days)
- Small penalty (be clear and humane)
- Loss of benefits until caught up
- Formal “lapsed” status after a threshold
Avoid rules that are impossible to enforce. If it cannot be applied consistently, it will create conflict.
Rule 5: Use One Reference Format For All Payments
Most “missing payment” problems are not fraud. They are identification problems.
Use a consistent reference like:
SCHEME_CODE-MEMBER_NUMBER(e.g.ZET-001)
This makes reconciliation easier and reduces the number of awkward messages in the group.
Rule 6: Have A Plan For Unknown Money (Suspense)
Sometimes money hits the account and you cannot identify it.
You need a rule that protects everyone:
- Record it as unallocated
- Do not treat it as income you can spend
- Allocate it only when you can match it confidently
A simple suspense process prevents accidental overspending and later disputes.
Rule 7: Use A Simple Approval Rule For Money Going Out
Money out is where trust gets tested.
At minimum:
- Define who can approve an outgoing payment
- Require a second person for large amounts
- Keep a short note explaining why it was paid
Even if you trust each other, approvals reduce mistakes.
Rule 8: Keep Decisions Traceable
If you cannot prove what was decided, you will end up debating the past.
A “traceable decision” has:
- a proposal (what is being decided)
- a vote or agreement record
- a date
- who supported it
- the final outcome
This matters even more when leadership changes.
Rule 9: Use Thresholds For Big Changes
Not every decision needs a full vote. But big changes should.
Examples of “big changes”:
- changing contribution amounts
- admitting new members
- approving a large payout
- taking on debt (property syndicates)
- changing claim rules (burial societies)
Set a threshold (quorum + approval percentage) so decisions stay legitimate.
Rule 10: Reconcile Monthly (10 Minutes, Every Month)
A monthly reconciliation habit is more powerful than a yearly cleanup.
Once a month:
- compare the bank balance to recorded contributions and payments
- list any unknown payments
- confirm any outstanding obligations
Small, regular checks prevent big, emotional arguments later.
Rule 11: Protect Member Data (POPIA Basics)
Schemes handle personal information, even when they don’t think they do.
Treat the following as sensitive:
- phone numbers
- ID numbers
- bank details
- beneficiary and dependant information
Practical rules:
- collect only what you need
- do not share full lists in public groups
- restrict access by role
- mask sensitive details where possible
If you want trust, protect people.
Rule 12: Plan For Succession
A scheme that depends on one person is fragile.
At minimum:
- define how roles change
- keep shared access to records
- document handover steps
Succession planning is not pessimism. It is maturity.
Scheme-Type Notes (Quick Guides)
Stokvels
- If you rotate payouts, publish the rotation order and stick to it.
- Agree on what happens if someone wants to swap months.
Burial Societies
- Define waiting periods clearly.
- Document claim requirements and timelines in plain language.
Investment Clubs
- Decide whether you run “equal shares” or units.
- If you track units, keep the unit price logic consistent.
Property Syndicates
- Define how capital calls work.
- Agree on a distribution order (what gets paid first, and why).
Closing Thought
A scheme is a financial system, but it is also a relationship system.
If you design it for clarity, fairness, and routine, you protect both.