User Stories
Table of Contents
- Introduction
- Purpose
- Scope
- User Stories
- Acceptance Criteria
- Definitions, Acronyms, and Abbreviations
- Appendix
- Approval
Introduction
The purpose of this document is to gather the Client’s business requirements, both functional and non-functional, for implementing a payment solution for loans.
Purpose
This document captures user requirements in a simple and understandable format, ensuring all stakeholders have a clear understanding of the desired functionalities and outcomes.
Scope
The scope of this document is limited to collecting the requirements from the Client, focusing on payments and funds transfers relevant to lending products.
User Stories
User Story 1: Loan Disbursement
- As a: Bank Officer
- I want to: Disburse a loan automatically and manually
- So that: Customers receive their loan funds promptly
Description
The system should support both automatic and manual loan disbursements, involving interaction with the legacy system through middleware for processing.
Acceptance Criteria
- System must capture payment order details correctly.
- Middleware must validate and confirm disbursement success.
- In case of failure, reasons should be available for further handling.
Notes
This scenario includes automatic and manual disbursement processes.
User Story 2: Regular Loan Repayment
- As a: Bank System
- I want to: Process regular loan repayments from generated bills
- So that: Loan repayments are processed efficiently and accurately
Description
The system should generate files based on bills for regular, past-due, and charge repayments, which are sent to the legacy system for processing.
Acceptance Criteria
- System must generate files daily for regular repayments and several times a day for past-due and charge repayments.
- Legacy system should process these files and send confirmation back to the system.
Notes
Priority should be given to past-due repayments over regular repayments.
User Story 3: Extraordinary Loan Repayment via Digital Channel
- As a: Customer
- I want to: Make an extraordinary loan repayment via the digital channel
- So that: I can manage my loan repayments conveniently
Description
The system should allow extraordinary loan repayments through the digital channel, utilizing existing payment interfaces between the legacy system and middleware.
Acceptance Criteria
- System must process guaranteed payments and send payment instructions to the legacy system.
- Loan account numbers should be synchronized with the payment bridge.
- Unsupported incoming payments should be re-routed to a special technical account.
Notes
This scenario reuses current digital channel functionality and existing payment interfaces.
Acceptance Criteria
- All user stories must include correct capturing, processing, and confirmation of payment orders.
- Error handling must be implemented to provide clear reasons for transaction failures.
- Files for repayments must be processed within specified timelines.
Definitions, Acronyms, and Abbreviations
- BRD: Business Requirements Document
- LOS: Loan Origination System
- T24: Core Banking System
- Middleware: System providing 24/7 availability
- Technical Nostro: Intermediary account used for transaction transfers
Appendix
Include any additional information or documents relevant to the User Stories document.
Approval
- Prepared by: [Your Name]
- Date: [Date]
- Approved by: [Approver's Name]
- Date: [Approval Date]