What a back-office system owes its members
A back-office system is a promise to the people whose records it holds. Here's how we design for that obligation, not just the workflow.
By The Khumalo Group
Every administration system carries a quiet obligation. Behind each row in the database is a person who expects their contributions counted, their balance correct, and their statement to mean what it says. The workflow is the easy part. The obligation is the hard part.
Records are promises
When a member cannot see how their balance was reached, trust erodes — and trust is the whole product. We design ledgers to be legible: every movement traceable, every adjustment attributable, every statement reproducible from first principles.
Month-end is the test
A system that works on a quiet Tuesday but stumbles at month-end has not been built; it has been demonstrated. We build to the busy day, not the calm one — the close, the audit, the regulator query.
The unglamorous parts
Data migration, reconciliation, the first audit — this is where systems earn their keep, and where the team that runs it decides whether to rely on it or keep a spreadsheet open on the side, just in case. Getting them to close that spreadsheet is the actual job.
- systems
- building-in-africa
- Pensions & Retirement Funds