Compliance

BNR Regulatory Reporting, Generated From Live Data

Unguka360 produces the periodic returns non-deposit-taking financial service providers file with the National Bank of Rwanda directly from your loan book — with the portfolio already classified by risk bucket, and every figure traceable back to the loan that produced it.

The quarterly problem this replaces

For most institutions the reporting quarter ends and a finance team spends a week rebuilding the return by hand: exporting the loan register, ageing it in a spreadsheet, classifying each account, reconciling the totals against the ledger, and re-keying the result into the template. The work is repeated in full every quarter, and any error found afterwards is hard to trace because the spreadsheet is a snapshot, not a record.

Unguka360 treats the return as a view over data you already hold. You pick the cut-off date and the reporting period, and the workbook is generated — classification, ageing, and totals included.

Portfolio classification that is always current

Loans are classified continuously as arrears age, not reconstructed at quarter end. The standard buckets — Current, Watch, Substandard, Doubtful, and Loss — are applied from the repayment schedule and the payments actually recorded against it.

The consequence is that your reported portfolio-at-risk and your operational recovery list are the same number, taken from the same place. Management is not looking at one figure while the regulator receives another.

  • Continuous classification driven by days in arrears, not a quarter-end exercise
  • Portfolio-at-risk by branch, by officer, and by product
  • Every classified balance traceable to the underlying loan and its schedule
  • Prior-period figures preserved, so restatements are visible rather than silent

From generated workbook to filed return

The reporting screen takes a cut-off date and a reporting quarter, shows the classification preview so finance can review before anything leaves the building, and exports the workbook.

Nothing is submitted on your behalf. Your finance team reviews and files, exactly as they do today — what changes is that the numbers arrive already assembled and already reconciled to the ledger, rather than being built from scratch.

Audit trail, for when the figure is questioned

Every approval, disbursement, repayment, and correction is logged against the user who made it and the time it happened. When a board member or an examiner asks why a balance moved between periods, the answer is a query rather than an investigation.

Frequently asked questions

What is BNR reporting?
BNR reporting refers to the periodic returns financial institutions file with the National Bank of Rwanda, the country’s central bank and financial regulator. For non-deposit-taking financial service providers these returns cover the loan portfolio, its classification by risk bucket, and the institution’s financial position.
Does Unguka360 submit the return to BNR for us?
No. Unguka360 generates the reporting workbook from your live loan data and shows a classification preview for review. Your finance team reviews and files it. The software removes the assembly and reconciliation work, not your control over what is submitted.
How are loans classified for reporting?
Loans are classified continuously based on days in arrears against their repayment schedule, moving through the standard buckets — Current, Watch, Substandard, Doubtful, and Loss. Because the same classification drives both the regulatory return and the internal recovery workflow, reported portfolio-at-risk and operational figures agree.
What if we find an error after a period has been reported?
Prior-period figures are preserved and every correction is written to the audit trail against the user who made it, so a restatement is visible and explainable rather than overwriting the original position silently.

Related