One branch-scoped system for a microfinance lender's whole loan lifecycle, with regulator-ready reports on demand instead of a quarterly scramble.
Built by Talha Saleem
14
branches
5
delivery phases
system architecture
01The problem
A microfinance lender ran loans across 14 branches on paper forms, WhatsApp and spreadsheets. KYC was inconsistent, EMI schedules were error-prone and regulatory reporting was a quarterly scramble.
02My contribution
Delivered a five-phase platform: a NestJS + Prisma + PostgreSQL API with JWT auth and role guards, and a Next.js front end. It covers KYC with CNIC verification, configurable loan products, multi-level approvals, reducing-balance EMI schedules, disbursement, and collections with PAR-bucket tracking and a nightly overdue-detection job.
Branch, staff and borrower management with KYC document uploads.
PDF loan agreements generated from approved applications.
Branch and officer dashboards, plus SMS notifications.
03Outcome
The full loan lifecycle across all 14 branches in one system, with branch-scoped access for field staff, an audit trail behind every change and regulator-style reports exported to Excel or PDF.
04Product screens
Loan Management System for a 14-Branch Lender
05Engineering note
Microfinance lending in Pakistan follows SECP NBFC rules, not Western fintech conventions. Markup calculations differ from APR, KYC runs on CNIC data, and reporting fields differ from IFRS, so these rules have to be modelled from the start.