[go: up one dir, main page]

0% found this document useful (0 votes)
98 views3 pages

Debt Collection App Requirements

The document outlines requirements for a debt collection application to help agents manage collections from clients. It describes functions like searching for clients, viewing debts and payments, collecting full payments, submitting amounts to banks, and viewing payment history. It includes user stories around logging in, searching for clients, viewing client details, collecting payments, submitting to banks, receiving confirmations, and logging out. It also lists fields needed for search, client lists, and client debt screens.

Uploaded by

lohitakshrce220
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
98 views3 pages

Debt Collection App Requirements

The document outlines requirements for a debt collection application to help agents manage collections from clients. It describes functions like searching for clients, viewing debts and payments, collecting full payments, submitting amounts to banks, and viewing payment history. It includes user stories around logging in, searching for clients, viewing client details, collecting payments, submitting to banks, receiving confirmations, and logging out. It also lists fields needed for search, client lists, and client debt screens.

Uploaded by

lohitakshrce220
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

For Debt Collection Application

1. Introduction
This document describes the requirements for the Debt Collection Application, designed to
facilitate debt collection agents in managing and collecting payments from clients for various
financial products.

2. Scope
 The application will enable agents to:
 Search for clients under their Agent ID.
 View debts and upcoming payments for products like Fixed Deposits (FD), Recurring
Deposits (RD), Loans, Monthly Income Schemes (MIS), or Daily Deposit Schemes (DDS).
 Collect full payments from clients and update the system.
 Submit collected amounts to the bank.
 View payment history for each product.

3. User Stories
3.1 Agent Login
 As an agent, I want to log in to the application so that I can access client information and
manage debt collections.
3.2 Search and List Clients
 As an agent, I want to view a list of clients under my Agent ID and search them by name,
so I can easily find the clients I need to manage.
3.3 View Client Debts and Payments
 As an agent, I want to view the details of debts and upcoming payments for each client,
including the product type, due date, and amount, so I can understand what needs to be
collected.
3.4 Collect Payments
 As an agent, I want to collect full payments (no partial payments) from clients for their
due products and update this in the system, to ensure accurate tracking of collections.
3.5 Bank Submission and Freezing Login (In how many No of days TTMS can configure from
system)
 As an agent, after collecting payments for the day, I need to submit these amounts to
the bank. My login should be frozen until I complete this submission, to ensure
accountability.
3.6 Receive Folio Number
 As an agent, once I submit the collected amount, the client should receive a folio
number via SMS for their respective product, confirming the payment.
3.7 Direct Processing to Product Account
Daily Collection Overview:
• By default, the Collection History screen should display the total
amount collected by the agent for the current day.
• The screen should provide an option to select a different date,
allowing the agent to view collections for past dates.
Collection Details:
• Each entry in the collection history should display the following
information:
• Date of Collection: The specific date when the amount was
collected from the client.
• Total Collected Amount: The sum of all payments collected on that
date.
• Client Details: A breakdown of collections, showing individual
client names and the corresponding collected amounts.
• Product Details: Details of the product for which the payment was
collected (e.g., FD, RD, Loan, etc.).
Submission to Bank:
• For each collection entry, there should be a status indicator
showing whether the collected amount has been submitted to the
bank.
• If submitted, the date of submission should be displayed.
• In cases where the submission is pending, a distinct indicator
should be present, prompting the agent for action.
Historical Data Access:
• Agents should have the ability to access and review their
collection history for a specified range of past dates.
• This could include a calendar view or a simple date selection tool.
Reporting Functionality:
• The application should provide an option to generate reports
based on the collection history.
• Reports should be exportable in formats like PDF or Excel for
record-keeping and analysis.

3.8 View Payment History


 As an agent, I want to view the payment history for each product associated with a
client, so I can track past transactions and ensure accurate record-keeping.
3.9 Collection History:
 Agent should be able to see how many amount he has collected by date in
collection screen by default it will be todays collection.

 Collected amount on which date submitted to bank.
3.10 Agent Logout
 As an agent, I want to securely log out of the application to ensure the confidentiality of
client information.

4. Fields Required
Search Screen
Search by customer name or customer id API
1. Customer Lists Screen array of customer
 Customer Name
 Customer ID
 Number of debt(total number of debt pending )
 Total amount Pending
2. Customer Debt Screen list of product
a. Product Id
b. Product Name
c. Due Amount
d. Due Date
e. Payment Status
f. Pay Button
On Click of pay button call api to update payment to pay.

You might also like