System Requirements Document for tough-loan

1. Introduction

The tough-loan project aims to develop a micro loan-collection fintech software product targeting small Non-Banking Financial Companies (NBFCs), local finance companies, and Microfinance Institutions (MFIs) with approximately 1,000–20,000 borrowers. The software will provide tools for efficient loan collection, including dashboards for managers and field agents, customer management, GPS tracking, and digital receipts.

2. System Overview

The tough-loan system is designed to support loan collection operations for small financial institutions. It provides a dashboard for managers to oversee portfolio performance and tools for field agents to manage collections. The system includes features such as customer lists, GPS/location tracking, payment history, promises to pay, WhatsApp/SMS reminders, digital receipts, and collection tracking. The product targets small NBFCs, local finance companies, and MFIs, and is not intended to compete with enterprise-scale solutions like Credgenics.

2a. Product Interpretation and Delivery Boundary

The product is a micro-focused loan-collection platform, not a lending product. It supports organizations already giving loans by providing software for loan collection. The system includes self-service enrollment and login for identity verification, role-based access for field agents and managers, and backend persistence for collection records. It integrates with WhatsApp/SMS providers for reminders and uses GPS/location capabilities for field collections.

2b. Source Content Inventory

Not applicable as there is no explicit content_source directive.

2c. Page Content and Component Coverage

Landing

• Information/State: Introduction to the platform, target organizations, and collection workflows.
• Primary Actions: Navigate to Sign Up or Login.
• Components: Hero section with typographic headline, overview of features.

Login

• Information/State: User authentication for returning users.
• Primary Actions: Enter credentials, submit login.
• Components: Login form, error messages for failed attempts.

Sign Up

• Information/State: User registration for new users.
• Primary Actions: Enter registration details, submit form.
• Components: Registration form, confirmation message.

Dashboard

• Information/State: Portfolio value, due today, collected, overdue, collection rate.
• Primary Actions: View detailed reports, manage collections.
• Components: Data visualizations, summary metrics, manager oversight tools.

Customers

• Information/State: List of customers for field agents.
• Primary Actions: View customer details, initiate collection.
• Components: Customer list, search/filter options.

Locations

• Information/State: GPS/location information for borrowers.
• Primary Actions: View map, track borrower location.
• Components: Map interface, location details.

Payment History

• Information/State: Borrower payment history.
• Primary Actions: Review history, update records.
• Components: Payment history table, filters.

Promises

• Information/State: Promises to pay.
• Primary Actions: Record new promises, update status.
• Components: Promise management interface.

Reminders

• Information/State: WhatsApp/SMS reminder setup.
• Primary Actions: Send reminders, schedule future reminders.
• Components: Reminder setup form, scheduling options.

Collections

• Information/State: Collection activity and status.
• Primary Actions: Record collection, update status.
• Components: Collection tracking interface.

Receipts

• Information/State: Digital receipt generation.
• Primary Actions: Issue receipts, send to borrowers.
• Components: Receipt generation form, delivery options.

3. Functional Requirements

• As a Field Agent, I should be able to access a customer list to manage collections. (explicit)
• As a Field Agent, I should be able to view GPS/location information for borrowers. (explicit)
• As a Field Agent, I should be able to review payment history to inform collection efforts. (explicit)
• As a Field Agent, I should be able to record and manage promises to pay. (explicit)
• As a Field Agent, I should be able to send WhatsApp/SMS reminders to borrowers. (explicit)
• As a Field Agent, I should be able to issue digital receipts for collections. (explicit)
• As a Collection Manager, I should be able to view a dashboard showing portfolio performance metrics. (explicit)
• As a Collection Manager, I should be able to oversee collection operations and track performance. (explicit)
• As a User, I should be able to sign up for the platform to access its features. (required_inference)
• As a User, I should be able to log in to access my account and operational records. (required_inference)

4. User Personas

• Field Agent: Responsible for managing collections, accessing customer lists, viewing GPS/location data, reviewing payment history, managing promises to pay, sending reminders, and issuing digital receipts.
• Collection Manager: Responsible for overseeing loan collection operations, viewing portfolio performance metrics, and managing collection strategies.

5. Core User Flows

Field Agent Flow

1. Access Customers Page: View and search customer list.
2. Select Customer: View customer details and payment history.
3. Initiate Collection: Record collection activity and update status.
4. Send Reminder: Use Reminders page to send WhatsApp/SMS reminders.
5. Issue Receipt: Generate and send digital receipt to borrower.

Collection Manager Flow

1. Access Dashboard: View portfolio performance metrics.
2. Analyze Data: Use data visualizations to assess collection rates and overdue amounts.
3. Manage Collections: Oversee field agent activities and adjust strategies as needed.

6. Visuals Colors and Theme

• Muse: Erik Spiekermann
• Palette:
  • Background: #F8F8F8
  • Surface: #FFFFFF
  • Text: #212121
  • Primary: #D32F2F
  • Accent: #FFA726
  • Muted: #BDBDBD
• Typography:
  • Headings: Fira Sans — Bold, large scale, tight tracking, all-caps
  • Body: Source Sans Pro
  • Scale: 1.5 modular, 48/32/24/16/14
• Shape Language: Clear columns, rounded corners, distinct sections with iconography
• Layout: Structured grid layout with clear margins and typographic hierarchy
• Motion: Functional animations with short and purposeful transitions

7. Signature Design Concept

An oversized data-driven hero with a typographic focus will be featured on the Landing page. It will include a large typographic headline above a clear, data-driven dashboard preview. The background will be light with a warm accent to draw focus to key metrics. The design will emphasize clarity and ease of navigation with a structured grid layout and strong typographic hierarchy.

8. Interaction Model & Motion Direction

• Interaction Model: Static
• Motion Tempo: Restrained
• Hero Dimensionality: Flat
• Landing Hero Motion Brief: The hero section will feature a large typographic headline with a data-driven dashboard preview. The motion will be minimal, focusing on smooth transitions between sections and interactive elements.

9. Non-Functional Requirements

• The system must support approximately 1,000–20,000 borrowers.
• The system must provide reliable and secure access to sensitive financial data.
• The system must integrate with WhatsApp/SMS providers for sending reminders.
• The system must support GPS/location tracking for field collections.

10. Tech Stack

• Frontend: React
• Backend: Python/FastAPI
• Database: PostgreSQL
• Containerization: Docker/docker-compose
• Deployment: Kubernetes (if required)

11. Assumptions and Constraints

• The product is designed for small NBFCs, local finance companies, and MFIs.
• The product is not intended to compete with enterprise-scale solutions like Credgenics.
• The product supports organizations already giving loans, not as a lending product.

12. Glossary

• NBFC: Non-Banking Financial Company
• MFI: Microfinance Institution
• GPS: Global Positioning System
• SMS: Short Message Service