Professional Documents
Culture Documents
SOW - MSB-33 Pushback Case Resubmission To Credit V1 in NewGen V1.0 - Business Feedback V2
SOW - MSB-33 Pushback Case Resubmission To Credit V1 in NewGen V1.0 - Business Feedback V2
1|Page
Versions
Rel N. Date Description Author
1.0 19/02/2023 First version Sheikh Abdullah
Aleem
2|Page
Table of contents
1 Introduction ...............................................................................................................................................................................4
6 Assumptions...............................................................................................................................................................................6
3|Page
1 Introduction
This document describes NewGen SOW related to the change 2.1.2 as per MSB “
BRD_Pushback Case Resubmission to Credit V1 “ As per the demand the application when
pushed back from any of the credit approval Workstep to sales rework should land only on Team
leader Workstep in the business approval hierarchy and further should be pushed to credit
approval .This should happen only in the following two conditions:-
1. Adding or deleting an attachment
2. Adding a new note on the case
In order to meet the current demand, it is proposed that the if the case has been pushed from any
of the credit approval process to sales rework with the following pushback reason “Document
Issue - Missing / Expired / CA not signed” (the pushback reason shall be added as per demand
MSB-34),the case shall be opened on sales rework stage with the application tabs in ‘read only’
mode except for the following:-
The document Tab shall be enabled so that the user can reupload correct documents.
All the document generation buttons should be enabled at the Related party Tab.
Further on submit the case shall be pushed to the Team leader Workstep and upon submit the
application shall move to the same credit officer and further the normal flow to credit approvals
shall be followed. In case any other reason has been selected the case will follow the full
business approval as per usual BAU process.
Name Description
ARB KSA Al Rajhi Bank – HQ Riyadh - KSA
BRD Business Requirements Document
C/A Current Account
Queue BPM is a Queue based Workflow System i.e Work item flow from one Queue to another
in a Process. A ‘Queue’ can be defined as a shared workbench of users performing
similar operations
4|Page
Doc Name Description Date File
2 Requirement Summary
As per current system in the case when Sales officer updates a pushback case, the case goes into the
full business approval as we as credit approval matrix .In order to fasten the process it has been
proposed that the case should move from Team leader directly to credit officer and further into the
credit approval process.
3 Involved products.
The following products should be involved:
Products
1 MSB POS
5|Page
Note :- if any other reason is selected the full business approval as per BAU shall be followed.
After the Sales rework user has amended the document ,the case will submit to team leader .
SOW-2 post his submission the case shall be routed to Credit officer process and will follow full credit
approval as per BAU.
4.1 APPENDIX
N.A.
5 Out of Scope
This section describes the exclusions and assumptions that will be considered in this project.
# Description
1 This feature implementation is done in product Point of sale Finance for now. For Ecom/BIF
implementation can be done after the solution has been validated/tested for POS.
2 Existing application which are passed through this phase will not be considered to cover this
feature.
3 Reports Requirement is not under the scope.
4 The Digital Process if executing any handling at their end ,then they should handle this change at
their own end.
6 Assumptions
# Description
1 The solution would be delivered as per the provided Scope of work.
2 Any third-party testing would be Bank/ESB responsibility.
6|Page