Mkondo Report
The regulated intake for licensee returns to RURA. Preparers file, approvers release, and every submission lands in an immutable audit trail with its deadline tracked. This is the foundation the rest of the rail stands on — and the reason we built it first.
Filing that a regulator can trust and an operator can actually meet.
Two hands on every return
A Report Preparer drafts and files; a Report Approver reviews and releases to RURA. Nothing reaches the regulator on one person's say-so (BR-012).
Never miss a filing window
Every reporting obligation is tracked with its due date and status — on time, due, or in breach — so operators see what RURA sees, before RURA sees it.
Provable after the fact
Filings, releases, edits, and logins are written append-only with actor and source. The record is the evidence.
Your data stays yours
Row-level security isolates every licensee in the database itself. The regulator reads across; operators never see each other.
One OpenAPI standard
Returns flow through a single published contract, so integrations and the regulator's expectations line up from day one.
Eight roles, one console
Licensee admin, station manager, preparer, approver — plus RURA and platform roles — each see exactly what their mandate allows.
Report is layer one of the rail.
Compliance came first because it is what the mandate enforces first — and because the registry and clearing layers above it inherit its audit trail and isolation rather than reinventing them.
Report
Licensee returns to RURA.
Registry
Battery identity & custody. Explore →
Clearing
Rider & battery settlement. Explore →
Put your Q3 returns on the rail.
We'll map Report to your licence class and show the maker-checker flow end to end.