Reporting Hub

The Reporting Hub groups analytical views for portfolio, credit & collections, finance and operations. This page describes how business and risk users consume and navigate these reports.

Overall User Story

As a business, risk or finance analyst, I want a single catalogue of reports grouped by domain, so that I can quickly find the right report and drill down into loan-level details without memorising technical names.

  • Entry points: `Reports` menu item in the sidebar or deep links from dashboard cards.
  • Outcome: user lands on a report card grid (by category) and opens a specific report such as Portfolio, Loan Overdue, IFRS or Loan API Hits.

Report Categories

  • Loan Overview: portfolio trends, origination funnel, eligibility metrics.
  • Credit & Collection: overdue loans, collection performance, repayment transactions.
  • Finance: IFRS provisioning, disbursement analysis, profitability.
  • Operation: integrations/API health and throughput.

Common Behaviour Across Reports

  • Filters & parameters: each report provides standard filters such as date range, product, portfolio and branch.
  • Column customisation: users can choose which columns to display in detailed tables and save personal views.
  • Drill-down: from aggregated charts, users can click to see detailed lists and, where relevant, open the underlying loan in Loan Inquiry.
  • Export: downloadable output (CSV/XLSX) respects applied filters and selected columns.
  • Security: access to each category can be limited to roles (e.g., only Finance can open IFRS reports).

Key Use-Cases by Category

  • Portfolio / Loan Overview: track active book size, new originations, approval rates and eligibility funnel performance.
  • Credit & Collection: monitor ageing buckets, cure rates, promises-to-pay, broken promises and collector performance.
  • Repayment Transactions: reconcile individual payments, support dispute investigations and internal/external audits.
  • IFRS & Finance: generate expected credit loss views, portfolio staging, yield and profit analytics.
  • Operations / Integrations: monitor availability and latency of external services such as credit bureau, payment gateways and government integrations.

Non-Functional Requirements

  • Performance: heavy reports should be pre-aggregated or run on a reporting replica to avoid impact on transactional workloads.
  • Data freshness: the UI should clearly indicate whether a report is real-time, near real-time or end-of-day.
  • Audit & lineage: stored procedures or ETL jobs feeding reports must be traceable and versioned.