CBSRM · Microfinance Risk Layer for laghubitta institutions
Request a pilot

Risk layer for microfinance institutions

Branch risk monitor, early warning and stress testingbeside your Core Banking System.

CBSRM reads an authorised CSV export from the institution's existing CBS or MIS and turns it into a month-end view of portfolio risk: PAR, a trend and early-warning alerts against agreed thresholds for every branch, overdue migration and concentration across the portfolio, and stress tests for rate, farm income, monsoon, regional disaster and funding shocks. It is read-only. It posts nothing back and changes no account, so the CBS stays the ledger of record.

Open the app View sample dashboard
  • Read-only no posting to the CBS
  • In the browser the file is not uploaded
  • SHA-256 of every input file

01How it connects

CBS versus CBSRM

The CBS keeps the books. CBSRM reads them and tells you where the risk is.

Existing CBS / MIS (CSV export)
CBSRM risk layer
Management and board reports (board summary, alerts CSV)

Direct API connection is pilot work, not built yet.

CBSRM does not replace the Core Banking System. It analyses authorised data from it.

  • Role CBS / MISRecords transactions, accounts and repayments. It is the ledger of record. CBSRMReads an authorised export of that ledger. It keeps no ledger of its own.
  • Work CBS / MISPosts disbursements, collections and interest, day to day. CBSRMComputes portfolio risk, stress results and early-warning alerts by branch.
  • Access CBS / MISRead and write, inside the institution's own systems. CBSRMRead-only. No posting, no write-back, no change to any account.

02What a pilot looks like

three steps, repeated each month-end

Export, calibrate, review.

  1. 1

    Export

    The institution exports an anonymised or centre-level aggregated portfolio file from its CBS/MIS in the template format (laghubitta_template.csv).

    no customer names or IDs
  2. 2

    Calibrate

    Thresholds, provisioning rates and scenarios are set together with the institution's risk team against current NRB directives.

    set with the risk team
  3. 3

    Review

    Management and board receive the branch risk monitor, alerts, stress results and a board summary each month-end.

    every month-end

03What the institution provides

Three things, none of them customer-identifying.

  • 01

    An anonymised or aggregated portfolio export

    From the CBS/MIS, in the template format. Centre-level aggregates are enough. No customer names or IDs are needed.

  • 02

    A balance-sheet summary

    The handful of figures needed for capital, liquidity and funding stress.

    capitalRWAliquid assets90 day inflows90 day outflowsborrowings
  • 03

    A contact in risk or MIS

    One person who knows the export and can sit in on calibration.

04Privacy

processed in the browser

The app processes the file in the browser. Nothing is uploaded.

Where it runsIn the browser tab, on the computer that opens the file.
UploadNone. The file is read locally and is not sent to a server.
What it needsNo customer names or IDs. An anonymised or centre-level aggregated file is enough for the pilot.
What it recordsA SHA-256 of the input file and the parameter set used, so a figure can be traced back to the exact file and settings that produced it. The hash-chained record of every computed block is produced by the open-source library for the sample dataset and shown on the sample dashboard.

05What it gets

try them in the app or see the sample dashboard

Five outputs, every month-end.

Monitor

Branch risk monitor

PAR and a 24 month trend for every branch, filterable by province and district, with overdue migration and concentration across the portfolio.

Alerts

Early-warning alerts

Rules flag branches that cross agreed thresholds, ranked by severity, each with the value and the threshold that triggered it.

highmedium
Stress

Stress tests

Each scenario recomputes PAR, provisions, capital and the 90 day liquidity gap.

ratefarm incomemonsoonregional disasterfunding squeezecustom
Board

Board summary report

A short month-end summary for management and the board, drawn from the same computed figures as the monitor.

Audit

Audit trail

SHA-256 of the input file and the parameter set in the app; for the sample dataset, a hash-chained record of every computed block from the open-source library.

input file · chain head
sha256 → block → block → head

06Status

what exists today, and what does not

A working prototype. The institution-specific work is still to do.

  • RunningThe prototype runs end to end on synthetic data: the app, the sample dashboard and the audit trail.
  • Not doneCBS integration is pilot work and has not been done for any institution.
  • Not doneThe app has a column mapper for CSV exports, but mapping and checking an institution's own CBS/MIS export is pilot work and has not been done.
  • Not doneCalibration against current NRB directives is pilot work and has not been done.
  • IllustrativeThresholds and provisioning rates shown in the app and the sample dashboard are illustrative, to be calibrated.
  • Not claimedNo regulatory approval or compliance is claimed. Outputs are not a regulatory report.

Request a pilot

Try it on your own portfolio export.

Write with the CBS or MIS the institution uses and a contact in risk or MIS. The first step is a short call to walk through the template and the calibration list.

Request a pilot Open the app View sample dashboard

prabhawa@wavervanir.com