Every quarter the same scramble. Numbers pulled by hand from the loan book, the GL, the CRM. A finance lead reconciling six spreadsheets at 11pm, signing off on figures they don't fully trust. The auditor asks where a number came from and nobody can answer for ninety minutes. The cost of one wrong submission isn't paperwork. It's a SARB penalty, a R10M POPIA fine, or a donor walking back next year's grant.
Compliance & Regulatory Reporting Engine
The submissions regulators, auditors, donors, and boards expect — assembled from the data you already generate, no quarter-end scramble.
- Industry
- Banks, NGOs, regulated operators, finance teams
- Best for
- Teams whose quarter-end is a fortnight of spreadsheets, late nights, and "where did this number come from?"
We sit with your business. We find the operational problem costing you the most. We build the system that fixes it.
A reporting engine that knows which systems each submission draws from and pulls the data itself. Validations run live against the regulator's rule pack. Exceptions surface with a one-line cause and a human action. The same engine produces a banking return, an NGO donor report, a POPIA filing, or a tax submission. Every figure traces back to its source row.
Quarter-end stopped being a fortnight of late nights. The same engine, repointed at different sources and rule packs, now produces four kinds of submission. Auditors ask where a figure came from. They get an answer in seconds — the system already knew.
One example — a South African bank, NGO and finance team in scope. Yours would point at the submissions your team actually files, with the rule packs your regulators publish.
One engine. Four submissions. Every figure traceable.
Pick a report. Watch the engine pull from the source systems, validate against the regulator's rule pack, and assemble the submission. Then change the quarter and watch it run again.
Source systems
4 feedingThe engine pulls from these systems on schedule. Inactive sources are skipped for this report.
- Loan Book pullingCore banking · 1.2M rows
- General Ledger pullingNetSuite · 412k entries
- Transactions pullingReal-time stream · 8.4M/day
- Customer Master pullingKYC store · 92k subjects
- Donor CRMSalesforce NPSP · 4.8k records
- M&E DatabaseProgramme outcomes · 28k records
Validations
3 pass · 1 failEach rule from the regulator's rule pack runs against the pulled data. Cite, status, evidence — all retained.
- Completeness · passAll 137 BA200 line items populatedBA200 §schedule-1
- Consistency · passTier 1 capital = paid-up + reserves + R/ESARB Directive D7/2024
- Threshold · passCapital adequacy ratio ≥ 8.0%Basel III §CAR
- Threshold · failLiquidity coverage ratio ≥ 100%Basel III §LCR
Observed 96.4% · below regulatory floor
Output preview
XBRL- Capital adequacy ratio14.2%
- Tier 1 capitalR 2.84B
- Risk-weighted assetsR 20.00B
- Liquidity coverage ratio96.4%
- Non-performing loans3.1%
Click any figure to unroll its lineage — source system, source rows, applicable rule and the exact calculation.
30-day stressed outflow modelled R 142M higher than HQLA stock at quarter close.
Want one built for your business? The first conversation is free.
Book a discovery callOne engine. Any regulator. Every figure traceable.
The engine pulls from every source system on a schedule. It applies the rule pack for the chosen report and assembles the final submission. XBRL, PDF, or Excel — without anyone keying a number.
Every figure carries its lineage: which source system, which row, which rule applied. Click any cell of the output and the audit trail unrolls. Submissions stand up to a regulator months later.
Completeness, consistency, threshold, and reporting checks run as data lands. Variances surface before submission, not after. The finance team sees what the regulator will see — and acts on it first.
Not the primary focus for this system.
Want one built for your business?
The first conversation is free. And useful either way.