Elena's BRD

Automated ARD Generated via Make.com Workflow
Document Version: 1.0 | Last Updated: 2025-04-29

---

1. Project Overview

Primary Objective
The purpose of this document is to gather the Client’s business requirements, both functional and non-functional.

Success Metrics
Identification and fulfillment of all business requirements, ensuring seamless integration and operation within THE BANK's existing systems.

Business Value Statement
Ensuring that the Client’s standard documents contain the required information and adapting this template if no standard exists.

---

2. Stakeholder Analysis

Role	Name	Contact	Decision Authority (Y/N)
Project Manager	Elena Smith	elena.smith@thebank.com	Y
Business Analyst	Mike Meier	mike.meier@thebank.com	N

---

3. Functional Requirements

User Stories

Story ID	Role	Description	Acceptance Criteria
BRD01-01	User	Populate information from the disbursement request received from LOS into the payment order.	T24 should receive payment instruction from LOS with required details and process accordingly.
BRD01-02	System Admin	Configure different transaction codes in T24 to handle each payment scenario.	T24 should be able to use transaction codes to decide how The legacy system should act accordingly.
BRD01-03	User	Input correct debit and credit accounts based on payment order.	T24 should map debit and credit accounts correctly when creating a Payment transaction.
BRD01-04	User	Check Beneficiary Account No. on the payment order level.	System should match Beneficiary Account number with existing Beneficiary record automatically.
BRD01-05	System Admin	Process disbursements on a 1:1 basis via online interface.	T24 should process the transaction on a 1:1 basis for disbursements.
BRD01-06	System Admin	Send information on the payment instruction to MIDDLEWARE.	T24 should send payment instruction to MIDDLEWARE immediately based on the created payment order.
BRD01-07	System Admin	Receive answer from MIDDLEWARE about payment instruction execution.	T24 should either authorize (positive response) or delete (negative response) Payment transaction in hold.
BRD01-08	System Admin	Send result of payments instruction to LOS.	Result of payment order processing from T24 should be sent to LOS.
BRD01-09	System Admin	Delete the Payment transaction in hold status if payment instruction was not successful.	T24 should delete the Payment transaction in hold status and provide reasons for transaction failure.
BRD01-10	System Admin	Retrieve Beneficiary Account No. from information available in T24 on loan account.	T24 should retrieve Beneficiary Account No from loan account information when creating the file for bills.

---

4. Technical Constraints

Integration Requirements

• Temenos should interact with The legacy system through MIDDLEWARE for 24/7 operations.
• Payment order functionality in T24 will be used to carry information for extraordinary repayment from external channels.

Compliance Standards

• Ensure compliance with SEPA area regulations for automated disbursements.
• Adhere to Cyber Payment Chain project requirements.

Architecture Diagram URL
N/A

---

5. Timeline Parameters

Sprint Cadence
14 days

Key Milestones

Milestone	Due Date	Owner
Requirements Gathering	2025-05-15	Elena Smith
Initial Implementation	2025-06-30	Mike Meier
System Integration Testing	2025-07-15	IT Department
User Acceptance Testing	2025-08-01	QA Team

---

6. Risk Profile

Risk Matrix

Risk Description	Likelihood (1-5)	Impact (1-5)	Mitigation Strategy
Integration issues between T24 and The legacy system	3	4	Conduct thorough testing and have a rollback plan.
Data inconsistency	2	5	Implement data validation and reconciliation checks.

---

7. Approval Workflow

Signatories

Name	Role	Approval Status	Signature Timestamp
Elena Smith	Project Manager	Approved	2025-04-29 10:00 AM
Mike Meier	Business Analyst	Approved	2025-04-29 10:30 AM

---

Appendix

• Revision History: Initial version created on 2025-04-29.
• Automated Validation Results: All requirements validated successfully.
• Risk Exposure Score: 60/100