Scribd
Upload
41 views3 pages

QATCH Compliance FSD for QIB Transfers

The Functional Specification Document outlines the changes needed for Qatar Islamic Bank (QIB) to comply with the Qatar Central Bank's new mandate requiring internal transfers to be reported via the QATCH system. Key updates include routing all account-to-account internal transfers through QATCH, enhancing the T24 core banking system, and updating the Salary Processing System. The document also details the testing scope, assumptions, and dependencies related to the implementation of these changes.

Uploaded by

Taiyyab Azim
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
41 views3 pages

QATCH Compliance FSD for QIB Transfers

The Functional Specification Document outlines the changes needed for Qatar Islamic Bank (QIB) to comply with the Qatar Central Bank's new mandate requiring internal transfers to be reported via the QATCH system. Key updates include routing all account-to-account internal transfers through QATCH, enhancing the T24 core banking system, and updating the Salary Processing System. The document also details the testing scope, assumptions, and dependencies related to the implementation of these changes.

Uploaded by

Taiyyab Azim
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

Functional Specification Document

(FSD)
1. Introduction

Qatar Central Bank (QCB) has issued a new mandate under the “QATCH ON US” initiative
that requires all within-bank (internal) transfers to be reported to QCB via the QATCH
system. This Functional Specification Document (FSD) outlines the changes required within
QIB’s core banking system (T24) and Salary Processing System to comply with this
mandate.

2. Business Requirement Summary

All account-to-account (A2A) internal transfers conducted within QIB must now be routed
to QCB through the QATCH system. These will be sent as post-transaction notifications,
aligning internal transactions with the existing QATCH reporting mechanism used for Off-
US transactions.

3. Scope of Change

• Include internal A2A transfers in QATCH post-transaction reporting.

• Generate and send QATCH files for internal transfers.

• Integrate updates in T24 and Salary Processing System.

• Departments impacted: Based on transaction mapping provided in the Excel file.

• Progressoft vendor changes already implemented; QIB systems need to integrate.

4. Current vs Proposed Workflow


Below diagrams illustrate the process flow before and after the implementation of the
QATCH ON US mandate.
Diagram 1: Current Process Flow (Pre-Implementation)

Diagram 2: Proposed Process Flow (Post-Implementation)

5. Functional Requirements

• Enhance T24 to detect internal transfers and generate QATCH files accordingly.

• Update Salary Processing System to tag internal salary transfers for QATCH.

• Implement logic to associate QATCH purpose codes based on transaction type and
department.

• Post-processing trigger to send transactions to Progressoft’s QATCH system.

• Handle exceptions and ensure acknowledgments from QCB are captured.

6. System Components

• T24 Core Banking System:

- A2A transaction identification

- QATCH file generation logic

• Salary Processing System:

- Internal payroll tagging

- File format alignment with QATCH

• QATCH System (Progressoft):

- Receives internal transaction files

- Transmits to QCB
7. Testing & UAT Scope

• Test scenarios for different transaction types (Retail, Corporate, Salary, etc.)

• Validate QATCH files generated for internal A2A transfers

• Confirm transmission and acknowledgment from QCB

8. Assumptions & Dependencies

• Changes from Progressoft have been completed

• Business has confirmed most transaction mappings; some items remain open

• Business rules and codes will be finalized before UAT

9. Appendices
Appendix A: Transaction and Purpose Code Mapping (Extracted from Excel)

Appendix B: Field Mapping Table

Appendix C: Process Flow Diagrams (to be inserted)

You might also like