Compliance controls that follow the loan.

Compliance is part of the workflow, not a spreadsheet beside it

When compliance lives in a parallel set of files, the hardest question a regulator can ask is simply: show me the evidence that this check happened before the decision was made. Ustawi answers that by making each control a step in the loan's own timeline — every action leaves evidence, every decision leaves an audit trail, and the figures feed the reports.

From a side spreadsheet to evidence on the loan

Drag the slider: the same checks, kept in a spreadsheet versus recorded on the loan in Ustawi.

A compliance timeline that follows the loan

Every loan passes through the same governed stages — and each stage carries its own control. The timeline is the spine this whole page hangs on: the check that belongs at each point, done there, and kept there. Follow loan #1956 through it.

Every control, and the evidence it leaves

A control is what you require before a decision; evidence is what remains afterwards. Ustawi pairs the two, so the record is not just that a decision was made, but that the check behind it was done.

An audit trail that keeps the evidence behind every decision

Every material compliance action is captured with a timestamp, the user, the action, the entity it touched, and what changed. When an examiner asks who did what and when, the trail is on one screen — recorded as the work happened.

One borrower, one compliance history

Because each control lives on the loan, a borrower's whole compliance history reads as one story — KYC, CRB, affordability, approval, disclosure, complaints and recovery, in order, each with its evidence.

One control center for compliance across the book

Above every loan sits a single view of the compliance work that is open, due, or overdue — the required actions, the deadlines that are running, and the decisions still missing their evidence. Compliance stops being a separate set of files and becomes a worklist tied to the loans themselves.

Compliance at a glance — institution and branch

Above the individual controls sits a management view: completion of affordability and CRB checks, open complaints, overdue controls, missing evidence and pending recovery — for the institution as a whole, and broken down by branch.

Regulatory reporting from the same loan data

The figures on a supported regulatory report are built from the loans, repayments and classification the platform already holds — aggregated, reviewed, and exported. Because the numbers come from the ledger, a report is traceable back to the events behind it rather than reassembled by hand.

Controls depend on your institution type and framework

There is no single generic configuration that fits every lender. Tanzania regulates non-deposit-taking MFIs, SACCOS and community microfinance groups under separate instruments, and Zanzibar has its own. Which controls apply, which reports are supported and which deadlines are tracked follow from your institution type and the applicable framework — the cards below show the concept; they are not a compliance determination.

Connected across the Ustawi platform

Compliance & Regulatory is not a bolt-on. It is the control and evidence layer over the apps around it — reading and writing against the same loan record they do.

How we get you live

A structured rollout, from mapping your applicable framework to running controls on live lending.

1. 01Discover

   Map your institution type, applicable framework and current controls.

2. 02Configure

   Set the controls, thresholds, deadlines and reports that apply to you.

3. 03Migrate

   Bring existing loans and their compliance records onto the platform.

4. 04Test

   Validate controls, deadlines and reports against known cases.

5. 05Train

   Bring compliance, credit and branch staff up to speed on the workflow.

6. 06Go live

   Run controls on live lending, with support on hand.