Master Client Creation_scenario_Test Cases_including Client On Boarding (5)

Business Functions - Moneyware Integra Thick Client

BSN Business Function Description Importance1 General setup Critical

2

3 Client Activation/Closure

4 Account Type Movement Account type conversion Critical5 MIS Report sending process

1. General Master2.Masters through BCIF

Client Creation & Product Defination

1. Family/Group creation -L1,L22. Client creation -L33. Account creation - L44. RM mapping5.Product Defination & Mapping6.Account Status7.Portfolio Mapping1. Client Activation2. Client Deactivation/Reactivation3. Client Closure4.Welcome letter & closure letter

1.MIS Report scheduling setting2.MIS report generation3.MIS sending through EMAIL

1 1.1.1 Generals - Setup1 1.1.2 Generals - Setup1 1.1.3 Generals - Setup1 1.1.4 Generals - Setup1 1.1.5 Generals - Setup1 1.1.6 Generals - Setup1 1.1.7 Generals - Setup1 1.1.8 Generals - Setup1 1.1.9 Generals - Setup1 1.1.10 Generals - Setup1 1.1.11 Generals - Setup1 1.1.12 Generals - Setup1 1.1.13 Generals - Setup1 1.1.14 Generals - Setup1 1.1.15 Generals - Setup1 1.1.16 Generals - Setup1 1.1.17 Generals - Setup1 1.2.1 Generals - Setup1 1.2.2 Generals - Setup1 1.2.3 Generals - Setup1 1.2.4 Generals - Setup1 1.2.5 Generals - Setup

1 1.2.6 Generals - Setup1 1.2.7 Generals - Setup1 1.2.8 Generals - Setup1 1.2.9 Generals - Setup2 2.1.1 Client Creation2 2.1.2 Client Creation2 2.1.3 Client Creation2 2.1.4 Client Creation2 2.1.5 Client Creation2 2.1.6 Client Creation2 2.2.1 Client Creation2 2.2.2 Client Creation2 2.2.3 Client Creation2 2.2.4 Client Creation2 2.2.5 Client Creation2 2.2.6 Client Creation2 2.2.7 Client Creation2 2.2.8 Client Creation2 2.2.9 Client Creation2 2.2.10 Client Creation

Business Function

Scenario #New

2 2.2.11Client Creation

2 2.2.12 Client Creation2 2.2.13

Client Creation2 2.2.14

Client Creation2 2.2.15 Client Creation2 2.2.16 Client Creation2 2.2.17 Client Creation2 2.2.18 Client Creation2 2.2.19 Client Creation2 2.2.20

Client Creation2 2.2.21 Client Creation2 2.2.22

Client Creation2 2.2.23 Client Creation2 2.2.24 Client Creation2

2.3.1 Account Creation2

2.3.2 Account Creation2 2.3.3 Account Creation2

2.3.4 Account Creation2 2.3.5 Account Creation2 2.3.6 Account Creation2 2.3.7 Account Creation2






2.3.17 Account Creation2 2.3.18 Account Creation

2 2.3.19 Account Creation2







2.3.30 Account Creation2 2.4.1 RM Mapping2 2.4.2 RM Mapping2 2.5.1 Product Definition2 2.5.2 Client Document2 2.6.1 Account status2 2.7.1 Portfolio Mapping3 3.1.1 Client Activation3 3.2.1 Client Deactivation3 3.3.1 Client Closure3 3.4.1 Welcome Letter3 3.4.2 Closure Letter4 4.1.1 Account Type Conversion5 5.1.1 MIS Report Process5 5.2.1 MIS Report Process5 5.3.1 MIS Report Process

Module

Company InformationCurrency MasterBank & D-mat informationCompany relationlocation masterzone masterRegion masterDocument CreationBroker MasterHoliday MasterTax MasterCustodian MasterFavorate tab functionDP master

Deactivation reasonClose reasonBusiness UnitBCIF Integration -Country MasterBCIF Integration -State MasterBCIF Integration -City MasterBCIF Integration -Branch Master

BCIF Integration -Occupation MasterBCIF Integration -RM MasterBCIF Integration -SRM MasterBCIF Integration -Investor type MasterBCIF IntegrationBCIF IntegrationBCIF Integration -Group L1 creationBCIF Integration -Group L2 creationGroup creation - L1 -International clientFamily creation - L2 - International clientClient creation - L3Client creation - L3Client creation - L3Client creation - L3Client creation - L3Client creation - L3Client creation - L3Client creation - L3Client creation - L3Client creation - L3

BCIF Integration -Customer Category Master

Client creation - L3

Client creation - L3Client creation - L3

Client creation - L3

Client creation - L3Client creation - L3Client creation - L3Client creation - L3Client creation - L3Client creation - L3

Client creation - L3Client creation - L3

Client creation - L3L3 Creation -International Client

Finacle Integration - L4 Creation

Finacle Integration - L4 CreationFinacle Integration - L4 Creation

Finacle Integration - L4 CreationFinacle Integration - L4 CreationFinacle Integration - L4 CreationFinacle Integration - L4 Creation



Finacle Integration - L4 CreationFinacle Integration - L4 CreationFinacle Integration - L4 CreationFinacle Integration - L4 Creation

Finacle Integration - L4 CreationFinacle Integration - L4 Creation

MFSS Integartion - L4 Creation

MFSS Integartion - L4 CreationMFSS Integartion - L4 Creation






MFSS Integartion - L4 CreationMFSS Integartion - L4 Creation

MFSS Integartion - L4 CreationKSEC-DP Integration - L4 CreationPMS Integration- L4 CreationL4 creation - International client

L4 creation - Debt & Managed accountRM MappingRM MappingProduct DefinitionClient DocumentAccount statusPortfolio MappingClient Activation Maker/CheckerClient Deactivation/ReactivationClient Closure

Welcome LetterClosure LetterAccount Type ConversionMIS Report SchedulingMIS Report GenerationMIS Report sending

Scenario Description Category Importance

To verify Company InformationTo verify the Currency MasterTo verify Bank & D-mat informationTo verify Company relationTo verify location masterTo verify zone masterTo verify region masterTo Verify Document CreationTo Verify Broker MasterTo verify Holiday MasterTo verify Tax MasterTo verify Custodian MasterTo verify Favorate tab functionTo verify DP masterDeactivation reasonClose reasonBusiness Unit - FAWCheck master creation for Country w.r.t BCIFCheck master creation for state w.r.t BCIFCheck master creation for City w.r.t BCIFCheck master creation for Home Branch w.r.t BCIF

Check master creation for Customer Category w.r.t BCIFCheck master creation for Occupation w.r.t BCIFCheck master creation for RM w.r.t BCIFCheck master creation for SRM w.r.t BCIFCheck for 'Investor type' master creationCheck the fields integrated from BCIF to Integra while integrationCheck for the integration process of client data from BCIF to MWICheck for L1 creation w.r.t Family CRNCheck for L2 creation w.r.t Family CRNTo verify Group L1 for International clientTo verify Family L2 for International clientCheck for the L3 creation w.r.t each CRN in BCIFCheck for L3 mapping to L2 where L2 existCheck for L3 mapping to L2 where L2 not existTo verify if the CRN no exist of L3Check for only wealth segment client flows in Integra from wealthCheck for Family consolidation flag Y/NCheck for Consent Flag Y/NCheck for statement preference Flag Y/NCheck for Report type Flag Y/NCheck for Individual report Flag Y/N

Check for the modification in Integra for L4

Check remapping of Family CRN.Check the Exception report w.r.t the fields updationCheck exception if previous exception updated in BCIF.Check for the 'Exception' & 'successful' status by MilesChange Client Status and perform round of testing.

Check for duplicate entry posting

Check the modification updation for masters in EOD.To verify Client creation-L3 for International client

To verify if the system creates the L4 based on holding patternTo verify if the CRN is missing

To verify the status of the AccountTo verify mode of operationTo verify if there is a multiple bank account

To verify the balance in the Application bank account (3 Days)

To verify the transaction in the Application bank account (3 Days)To verify if the Incremental data is pushed at EODTo verify L4 executionary is converted to L4 IASTo verify if L4 IAS account default bank account is closed

To verify if the Clear Balance is pushed for FD and TD accountTo verify the POA Logic

Check for the L4 creation for distribution client

Check for updation in Integra for client w.r.t updation in the BCIF system - L4 update

Check for modification details flow from BCIF to Integra if client segment has been changed from 'Wealth' to any other, for existing client in Integra

Check for the client data flow, if the segment changes to 'Wealth' in BCIF, for the customer which is not in Integra.

Change Customer segment and perform rounds of testing - Other than Wealth & Retail.

Check in exception report if same entries are not registered with different exception messages.

To verify if system flows only those data which tagged as Wealth client

To verify if the bank account number is mapped in investment account number at L4 in miles

To verify provision for back dated entried post conversion from Executionary to IAS

Check for the Investment account fields flow from MFSS for L4 creation for 'Relationship' client

Check for the Investment account fields flow from MFSS for L4 creation for 'Distribution' client

Check for the L4 creation for Relationship client

Check for L4 creation in INTEGRA as per holding pattern

To verify mapping of DP accountL4 creation through PMSTo verify Account creation-L4 for International client

Check the RM & SRM mapping to the client.RM & SRM mapping to the International ClientTo verify Product DefinationTo verify document with respect to clientTo verify the Account status screenTo verify scheme or portfolio mapping to clientTo verify Account type activation Maker/checker.To verify client deactivation / ReactivationTo verify client closureVerify Welcome LetterVerify Closure LetterTo verify Account type conversion Maker/checker.MIS Report scheduling settingMIS report generationMIS sending through EMAIL

Check for the the L4 creation or data flow for 'Wealth' segment, for 'Relationship' client type at CRN level

Check for the the L4 creation or data flow for 'Wealth' segment, for 'Distribution' client of RM.

Check for L4 creation if client changes to 'Distribution' to 'Relationship'

Check the data flow from MF to MWI if client segment & type changes with various combination

Check for L4 creation in INTEGRA for multiple investment account in MFSS

Check for the exception report if L3 does not exist for MFSS investment account.

L4 creation for Debt & managed account transaction as per holding pattern

Module Sub- Module Path

1.1.14

Generals - Setup DP master

1.1.14

Generals - Setup DP master

### 1.1.17

Generals - Setup Business Unit

### 1.1.17


### 1.1.17


### 1.1.17


2.1.5

Client Creation

2.1.6

Client Creation

2.1.6

Client Creation

Date of Test Case Preparation

Business Scenario

Ref #NEW

Set Up -> General -> DP Master

Set Up -> General -> DP Master

FAW>setup>General>Business Unit




Group creation - L1 -International client

Set Up -> Client -> Client Group L1

Family creation - L2 - International client

Set Up -> Client -> L2 (Maker)



2.1.6

Client Creation

2.1.6

Client Creation

2.1.6

Client Creation

2.1.6

Client Creation

2.1.6

Client Creation

2.1.6

Client Creation

2.1.6

Client Creation

2.1.6

Client Creation

2.1.6

Client Creation

2.2.1

Client Creation Client creation - L3






Set Up -> Client -> L2 (Checker)










Set Up -> Client -> L2 (Maker Login)



2.2.3


2.1.6

Client Creation

2.2.1


2.2.2


2.2.4


2.2.4


2.2.5


2.2.5


2.2.6


2.2.6




2.2.7


2.2.7


2.2.7


2.2.7


2.2.8


2.2.8


2.2.8


### 2.2.9


### 2.2.9


### 2.2.9


### 2.2.10


### 2.2.10


2.2.11


2.2.11


2.2.11


2.2.11


2.2.11


2.2.11


2.2.12


2.2.12


2.2.12


2.2.12


2.2.12


2.2.13


2.2.14


2.2.15


2.2.15


2.2.15


2.2.15


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.16


2.2.17


2.2.18


###

2.2.19


###

2.2.19


###

2.2.19


###

2.2.19


###

2.2.19


###

2.2.19


###

2.2.19


###

2.2.20


###

2.2.20


###

2.2.20


###

2.2.20


###

2.2.20


###

2.2.20


###

2.2.20


###

2.2.21


###

2.2.22


###

2.2.22


### 2.2.23


### 2.2.23


### 2.2.23


### 2.2.23


### 2.2.23


### 2.2.23


### 2.2.23


2.2.24

Client Creation

2.2.24

Client Creation

2.2.24

Client Creation

2.2.24

Client Creation

L3 Creation -International Client





Set -> Client -> L3(maker



2.2.24

Client Creation

2.2.24

Client Creation

2.2.24

Client Creation

2.2.24

Client Creation Set Up -> Client -> L3

2.2.24


2.2.24


2.2.24


2.2.24


2.2.24


2.2.24















2.2.24


2.2.24


2.3.1

Account Creation

2.3.1

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation











2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation











2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation

2.3.2

Account Creation











2.3.2

Account Creation

2.3.2

Account Creation

2.3.3

Account Creation

2.3.3

Account Creation

2.3.3

Account Creation

2.3.3

Account Creation

2.3.4

Account Creation

2.3.5

Account Creation

2.3.5

Account Creation

2.3.5

Account Creation











2.3.5

Account Creation

2.3.5

Account Creation

2.3.5

Account Creation

2.3.5

Account Creation

2.3.6

Account Creation

2.3.6

Account Creation

2.3.6

Account Creation

2.3.6

Account Creation

2.3.6

Account Creation

2.3.7

Account Creation











2.3.7

Account Creation

2.3.8

Account Creation

2.3.8

Account Creation

2.3.9

Account Creation

2.3.11

Account Creation

2.3.12

Account Creation

2.3.12

Account Creation

2.3.12

Account Creation

2.3.12

Account Creation

2.3.12

Account Creation











2.3.13

Account Creation

2.3.13

Account Creation

2.3.14

Account Creation

2.3.14

Account Creation

2.3.14

Account Creation

2.3.14

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation










2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation



Finacle Integration - Product code master

Finacle Integration - Product code master







2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation











2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.15

Account Creation

2.3.16

Account Creation MFSS Integartion - L4 Creation










2.3.17


2.3.18


2.3.18


2.3.18


2.3.18


2.3.18


2.3.18


2.3.19


2.3.19


2.3.19


2.3.19


2.3.19


2.3.19


2.3.19


2.3.19


2.3.20


2.3.20


2.3.21


2.3.21


2.3.22


2.3.22


2.3.22


2.3.23


2.3.23


2.3.23


2.3.23


2.3.23


2.3.23


2.3.23


2.3.23


2.3.23


2.3.23


2.3.23


2.3.23


2.3.23


2.3.23


2.3.24


2.3.24


2.3.25


2.3.25


2.3.26


2.3.26


2.3.26


2.3.27

Account Creation

2.3.27

Account Creation

2.3.27

Account Creation

2.3.27

Account Creation

2.3.28

Account Creation PMS Integration- L4 Creation

2.3.29

Account Creation Set Up -> Client -> L4

2.3.29


KSEC-DP Integration - L4 Creation




L4 creation - International client


2.3.29


2.3.29


2.3.29


2.3.29


2.3.29


### 2.3.30


### 2.3.30


### 2.3.30


2.4.1

RM Mapping RM Mapping

### 2.4.1







L4 creation - Debt & Managed account



### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.1


### 2.4.2


### 2.4.2


### 2.4.2


### 2.4.2


### 2.4.2


### 2.4.2


### 3.4.1 Welcome Letter Welcome Letter




### 3.4.2 Closure Letter Closure Letter



### 4.1.1 Account Type Conversio Account Type Conversion



















4.1.1 Account Type Conversio Account Type Conversion






### 5.1.1 MIS Report Process MIS Report Scheduling









































### 5.2.1 MIS Report Process MIS Report Generation




### 5.3.1 MIS Report Process MIS Report sending










Test Case Description

Verify Creation of DP master - View option

Create new 'Business Unit'

Check for 'Edit' business Unit

Check for 'Delete' business Unit

Verify Creation of DP master - Editing the existing details

Check for the master window of 'Business Unit' in FAW

Verify Client group creation FOR 'International Client' in order to map it to a family

Verify Creation of new family for International client - L2

To verify save action available on new family creation window by inserting details.

To verify mandatory validation on save action.

To verify family authorization using same maker login

To verify checker authorization from checker login

To verify Edit option available on main window.

To verify save action from edit window

To verify view option available on main window.

To verify Delete option available on main window.

Check for L3 creation after L2 & L1 creation

To verify Reject option available on Maker window- L2.

To verify Reject option available on checker window-L2.

Check the tagging of the newly created L2 & L3

To verify duplicate creation of family name.

Check if L3 for CRN exist in the system

Check if L3 for CRN exist in the system

To verify if the Client is not a wealth client

To verify if the Client is a wealth client

To verify if the family consolidation flag is kept as YES

To verify if the family consolidation flag is kept as NO

Check for L3 creation for the client whose L2 exist in Integra.

Check the tagging of the newly created L3 to the existing L2

To verify if the Concent flag is kept as YES

To verify if the Concent flag is kept as NO

To verify if the Statement preference flag as E

To verify if the Statement preference flag as H

To verify if the Report type flag as Abridge for client

Check for the report for ' Family Office' client

To verify if the concent flag was YES and than changed to NO

To verify if the concent flag was NO and than changed to YES

To verify if Statement preference flag is selected as E and H

To verify if the Report type flag as Detailed/Full for client

To verify if the Individual Report flag as Y for client

To verify if the Individual Report flag as N for client

To verify if the address is changed after the client is converted to Advisory

To verify if the contact is changed after the client is converted to Advisory

To verify if any other details changed other than Contact number Address and Email id after client is converted to Advisory

To verify if any detail is Updated for the Executionary client

To verify if the address is changed after the client is converted to Advisory and the Statement preference is kept as "H"

To verify if the email id is changed after the client is converted to Advisory and the Statement preference is kept as "E"

To verify if system allow to manually update address of IAS account at L4

To verify if system allow to manually update contact number of IAS account at L4

Check if changed Family CRN doesn't exist in Integra

Check if changed Family CRN exist in Integra

To verify if system allow to manually update Email id of IAS account at L4

To verify if system allow to modify manually any other details other than Contact number Address and Email id at L4 for IAS client

To veirfy if system allow to modify manually any detail for the Executionary client

To verify if the client segment is changed from Wealth to retail

To verify if the client segment is changed from Retail to Wealth

While updation from BCIF, if Family CRN changed for any L3 from one currently mapped

Check tagging of L3 to new L2 as per created from update come from BCIF

Check if 'First name' missing in data coming from BCIF

Check for the exception report for 'IT type' master, for client data from BCIF, where respective 'IT type' value is already exist in the master

Check for the exception report for 'IT type' master, for client data from BCIF, where respective 'IT type' value is not exist in the master

Check for the exception report for 'Country' master, for client data from BCIF, where respective 'Country' value is already exist in the master

Check for the exception report for 'Country' master, for client data from BCIF, where respective 'Country' value does not exist in the master

Check for the exception report for 'State' master, for client data from BCIF, where respective 'State' value is already exist in the master

Check for the exception report for 'State' master, for client data from BCIF, where respective 'State' value does not exist in the master

Check for the exception report for 'City' master, for client data from BCIF, where respective 'City' value is already exist in the master

Check for the exception report for 'City' master, for client data from BCIF, where respective 'City' value does not exist in the master

Check for the exception report for 'Occupation' master, for client data from BCIF, where respective 'Occupation' value is already exist in the master

Check for the exception report for 'Occupation' master, for client data from BCIF, where respective 'Occupation' value does not exist in the master

Check for the exception report for blank 'Client CRN'

Check for the exception report for blank 'Family CRN'

Check for the exception report for 'RM' master, for client data from BCIF, where respective 'RM' value is already exist in the master

Check for the exception report for 'RM' master, for client data from BCIF, where respective 'RM' value does not exist in the master

Check if respective RM is deactivated in master & same is tagged with client while flowing from BCIF to Integra

Check if respective RM is deactivated in master & same is tagged with existing client & flowing from BCIF to Integra as daily update

Check for the exception report for 'Branch' master, for client data from BCIF, where respective 'Branch' value is already exist in the master

Check for the exception report for 'Branch' master, for client data from BCIF, where respective 'Branch' value does not exist in the master

Check for the exception report for 'Category/Segment' master, for client data from BCIF, where respective 'Category/Segment' value is already exist in the master

Check for the exception report for 'Category/Segment' master, for client data from BCIF, where respective 'Category/Segment' value does not exist in the master

Check if respective update has done in master as per exception, & then do the Integration

Check for the 'Exception' & 'successful' status by Miles to the staging in log file

Check if client details flow in the Integra, if the client status is 'Active' & 'Authorised

Check if client details flow in the Integra, if the client status is 'Active' & segment is other than 'Wealth'

Check if client details flow in the Integra, if the client status is 'Active' & 'Unauthorised'

Check if client details flow in the Integra, if the client status is 'Active' & 'Unauthorised' & segment is 'Wealth'

Check if client details flow in the Integra, if the client status is 'Active' & 'Unauthorised' & segment is other than 'Wealth'

Check if client details flow in the Integra, if the client status is 'Active' & 'Rejected'

Check if client details flow in the Integra, if the client status changes from 'Acitive' to 'Inactive' & segment is 'Wealth'

Check if client details flow in the Integra, if the client segment is 'Retail Liabilities'

Check if client details flow in the Integra, if the client segment changes from 'Wealth' to 'Retail Liabilities'

Check if client details flow in the Integra, if the client segment is 'Corporate Banking'

Check if client details flow in the Integra, if the client segment changes from 'Wealth' to 'Corporate Banking'

Check if client details flow in the Integra, if the client segment is 'Retail Assets'

Check if client details flow in the Integra, if the client segment is 'Cards'

Check if client details flow in the Integra, if the client segment changes from 'Wealth' to 'Cards'

If any entry present in the 'Exception' in previous day & same data entry posted successfully in the Integra on second day.Check for the integration of Previous exception entry after correction in exception

Check for the Integration of client data after correction in EXCEPTION, if respective entry is having multiple exception comment

Check for the Integration of client data after correction in only one EXCEPTION comment, if respective entry is having multiple exception comment

Check for the master data integration on each EOD, irrespective of any updation in master data in BCIF

Check the master level updation type on EOD

Check for the 'CRN' field available in L3 window

Check for the searching of client through 'CRN'

Check for the 'Authorised signatory' field in 'L3 window'

Verify Creation of new Client with family at L3

Check for the mapping of authoriesd signatory mapping to current L3

Check for the rights available to 'Authorised signatory' for respective L3, in 'Client portal'

Check for mandatory field validation on L3 window, while International client creation

Check for authorization of newly created client at checker level.

To verify if client can be saved without Last name Field getting filled(Except if the client's investor type is Company or body corporate)

To verify Reject option available on checker window.

Verify PAN different account different PAN

To verify save action available on new client creation window by inserting all details.

Verify Creation of new Client at L3 without family in L2

Verify Edit function for the Existing International client details - L3

Verify validation if you are providing single PAN no to multiple client.

Verify CPA file for 'Date of Incorporation' where account name has investor type as 'Company'

Verifying whether joint holder of one account can hold a new account on his name. Client carry same PAN no. and MF holding nature is joint in both cases.

To verify if creating 2 accounts where in one account with joint holder and second account name is 1st accounts joint holder name with same PAN number and save,where mf holding nature kept as 'Anyone Or Survivor''.

To verify where creating 2 accounts with same joint holder having same PAN number and save.

joint holder with Three holders

To verify if the L4 does not exist for the given CRN

To verify if the L4 exist and the holding patter is same

to verify referencing of L4 maintained at l3 level

joint holder with two same name like "Salman Shah" Single holder & "Salman Shah" with Joint holder as " nimita Shah"

To verify if the system flow only those data which is of wealth segment

To verify if the system flow data other than wealth segment

To verify all relevent fields should flow to MWI from Finacle

To varify data flow for 1st holder CRN, in case of joint holding pattern

To varify data flow for 2nd holder CRN in case of joint holding pattern

To verify data flow for holding pattern single holder

To verify data flow for holding pattern joint holder

To varify data flow for 3rd holder CRN, in case of joint holding pattern

To varify data flow for bank account no field, in case of joint holding pattern

To varify data flow for 1st holder CRN, in case of single holding pattern

To varify data flow for 2nd holder CRN in case of single holding pattern

To varify data flow for 3rd holder CRN, in case of single holding pattern

To varify data flow for bank account no field, in case of single holding pattern

To varify mode of operations for various holding pattern.

To varify Name of Primary holder in case of single holding pattern

To verify account type

To verify account effective date

To verify Bank IFCI Code

To verify flow of LG codes

To verify barred LG codes

To varify Name of Primary holder in case of joint holding pattern

To varify Name of Subsequent holder in case of joint holding pattern

To verify relationship of primary holder and subsequent holder

To verify process date is updated by miles in staging tabel "STAGING_ACCOUNTS_OPENED"

To verify process flag is updated by miles in staging tabel "STAGING_ACCOUNTS_OPENED"

To verify if the CRN Number is missing

To verify if the secondary holder CRN does not exist

To verify if the third holder CRN does not exist

To verify if the account status blank

To verify if the account status is Active

To verify if the account status is missing

To verify process remark is updated by miles in staging tabel "STAGING_ACCOUNTS_OPENED"

To verify if the Holding pattern is different than the one which is there in the System

To verify if the CRN number which is missing if not located

To verify if the Bank account number is mapped to investment number in miles

To verify if the account status is Dormant

To verify if the account status is De Activate

To verify if the account status is Closed

To verify if Mode of operation is Single

To verify if Mode of operation is Joint

To verify if Mode of operation is Either or Survior

To verify if system allow to add the IFSC code

To verify if there is multiple bank account

To verify if the account status is closed does it allow to activate again in miles

To verify if system has the L4 consisting or single holding partern and new information flow joint holding

To verify if only incremental data is flow to the miles

To verify if there is multiple bank account and dafault bank account is not selected

To verify if the client is moved from executionary to IAS effect of corpus on L4

To verify if the client is moved from executionary to IAS effect of backdated entries on L4

To verify the balance in the Application bank account (3 Days)

To verify if the system allow to create the new L4 of IAS

To verify if system allow to change the Clinet from IAS to Executionary

To verify if system allow to change the Clinet from Executionary to Heldaway

To verify if system allow to change the Clinet from Heldaway to IAS

To verify if the automatic corpus outflow happens in case of client is converted from IAS to Executionary, Executionary to IAS, Executionary to Heldaway and Heldaway to IAS

To verify if the system push only the clear balance

To verify manual update in default bank POA account

To verify the by dafult POA flag in the system

To verify if the default bank account is closed for IAS L4

To verify if the default bank account is closed for IAS L4

To verify if the system push the data of FD / TD account

To verify if the system push the unclear balance for FD and TD

To verify if the Client is converted to IAS form Executionary does the system ignore the FD and TD balance

To verify default bank account mark by system in case of multiple POA

To verify if the combination of LG code and the product id does the system keep the POA as yes

To verify CRN reference at L4 level

To verify DP POA flag

To verify product code ID

To verify product code

To verify various Fields present in LG code master

To verify "New" functionality availble in LG code fild

To verify drop down functionallity in POA fielld

To verify options provided in POA field

To verify drop down functionlity working in LG code field

To verify drop down functionlity working in LG code field

To verify functionality of Exclude tab

To verify functionality of save tab

To verify functionality of Cancel tab

To verify functionality, if POA flag is "NO"

To verify functionality, if balances will be included if POA flag is "YES" and Exclude flag is "NO"

To verify functionality, if balances will be included if POA flag is "YES" and Exclude flag is "YES"

To verify funcitonality, if POA flag is "NO" and Exclude flag is "NA"

To verify process date is updated by miles in staging table "STAGING_CASA_BALANCES"

To verify process remark is updated by miles in staging table "STAGING_CASA_BALANCES"

To verify process date is updated by miles in staging table "STAGING_TD_BALANCES"

To verify Updation of FX rates in the miles at EOD

Verify flow of base currency.

Verify flow of alternate currency.

To verify process remark is updated by miles in staging table "STAGING_TD_BALANCES"

To verify updation of process date in S_PROCESS_DATE column in table named STAGING_FX_RATES

To verify updation of process remark in S_PROCESS_REMARK column in table named STAGING_FX_RATES

To verify updation of process date in S_MILES_PROCESS_DATE column in table named STAGING_FX_RATES

To verify updation S_MILES_PROCESS_FLAG column in table named STAGING_FX_RATES

To verify updation of process remark in S_MILES_PROCESS_REMARKS column in table named STAGING_FX_RATES

Check the fields flow from MFSS to MWI while L4 creation for Distribution client

Check if Investment account doesn't found in MWI

Check for L4 creation after L3

Check if same holding pattern L4 exist in MWI system

Flow the 'Distribution client' investment account in MWI

Check if 'Investment account number found for the respective 'Distribution client'

Check if 'Investment account number found for the respective 'Distribution client' & there are some modification from MFSS

Check if any modification comes from MFSS for 'Distribution client' L3

Check for L3 creation from MFSS if L3 doesn't found in MWI for respective distribution client

Flow the 'Relationship client' investment account in MWI

Check if different holding pattern L4 exist in MWI system.

Check if L3 doesn't found as per 1st holder CRN

Check if L3 for 1st holder CRN

Check the tagging of newly created L4 to L3

Check if same Investment account with same holding pattern exist in the MWI

Check if L4 doesn't exist for respective investment account

Check the data flow or L4 creation for segment as 'Wealth' for 'Relationship' client

Check the data flow or L4 creation for segment as 'Retail' for 'Relationship' client

Check the data flow or L4 creation for segment as 'Wealth' for 'Distribution' client

Check the data flow or L4 creation for segment as 'Retail' for 'Distribution' client

Check if client type changes from 'Distribution' to 'Relationship' in MFSS system.

Check for the L3 creation for the client whose type changes from D to R

Check for the L4 creation through MFSS for the client whose type changes from D to R

Check the MFSS details flow for 'Relationship- retail' client

Check the MFSS details flow for 'Distribution- retail' client

Check the data flow if 'Relationship' client segment changes from 'Retail' to 'Wealth'

Check the data flow if 'Relationship' client segment changes from 'Wealth' to 'Retail'

Check the data flow if 'Distribution' client segment changes from 'Retail' to 'Wealth'

Check the data flow if 'Distribution' client segment changes from 'Wealth' to 'Retail'

Check the data flow if 'Relationship' client type changes to 'Distribution' type & segment same as 'Retail'

Check the data flow if 'Relationship' client type changes to 'Distribution' type & segment same as 'Wealth'

Check the data flow if 'Relationship' client type changes to 'Distribution' type & segment 'Retail' to 'Wealth'

Check the data flow if 'Relationship' client type changes to 'Distribution' type & segment 'Wealth' to 'Retail'

Check the data flow if 'Distribution' client type changes to 'Relationship' type & segment same as 'Retail'

Check the data flow if 'Distribution' client type changes to 'Relationship' type & segment same as 'Wealth'

Check the data flow if 'Distribution' client type changes to 'Relationship' type & segment 'Retail' to 'Wealth'

Check the data flow if 'Distribution' client type changes to 'Relationship' type & segment 'Wealth' to 'Retail'

Check for the L4 creation w.r.t multiple investment account in MFSS for different holding pattern

Check for the L4 creation w.r.t multiple investment account in MFSS for same holding pattern

Check for the L4 creation in Integra if investment account is of single holding

Check for the L4 creation in Integra if investment account is of joint holding

Verify New function for L 4

Verify Save action on new window for L 4

Check for the exception report for the data coming from MFSS, where respective client L3 doesn't exist

Check for the exception report for the data coming from MFSS, where respective investment account 2nd holder L3 doesn't exist

Check for the exception report for the data coming from MFSS, where respective investment account 3rd holder L3 doesn't exist

To verify if the DP ID is mapped on the basis of account number

To verify if the account number mentioned in the DP id is different than the account number mentioned in the L4

To verify if the DP POA is set as Yes if the POA flag is YES

To verify if bank POA is NO does the DP POA is also no

To verify View function available on main window.

Verify Broker Code different account same code

Verify Broker Code different account different code

Check for the RM mapping to the client

Verify Edit function for the Existing client details for L 4

To verify new option for bank details available on new window.

Check for creation of L4 for any client w.r.t debt & managed account transactions

Check for L4 is exist as per 'Holding pattern' of debt & managed account transaction.

Check for L4 is not exist as per 'Holding pattern' of debt & managed account transaction.

Check the screen for manual mapping of SRM to client

Check for the field validation.

Check for the deletion of Primary RM of any client

Check for the deletion of secondary RM of any client

Check the SRM mapping to the client manualy

Check for Upload of excel file for Rm & SRM mapping

Check RM & SRM mapping through file upload

Check the fields available in the 'Account relationship map' window

Check for same WEF date for both the primary RM, if selected two RM in Primary RM list

Check for same WEF date for both the secondary RM, if selected two RM in secondary RM list

Check the excel file format for the RM & SRM mapping

Check for the client SRM mapping file upload format

Check the SRM mapping to the client as per excel upload

Check for the exception error while excel file upload for RM SRM mapping where RM & SRM not exist

Check for the exception error while excel file upload for RM SRM mapping where duplicate reocrd in same file

Check for the exception error while excel file upload for RM SRM mapping where Future date

Check for the mapping of SRM to any client as per file upload

Check for the impact on RM SRM mapping of any other client after mapping file upload for client SRM.

Check for the impact on SRM client mapping, if RM SRM file is uploaded.

Check if SRM for the client is different than what is mapped to the primary RM through excel upload.

Check the screen for RM & SRM mapping for International client.

Check for the RM mapping to the International client

Check for the SRM mapping to the International client

Check for Edit in the RM SRM mapping to the client

Keep blank Rm mapping & save the data

Check for the 'Welcome letter' format

Check for deleteion in the RM SRM mapping to the client

Check for generation of 'Welcome letter' for the IAS client which are activated

Check for the system generates 'Welcome letter' for those client which are activated within\ the selected date range

Check for the 'Welcome letter' generation for the client which are not active

Check for generation of 'Closure letter' for the client which have closed the L4-IAS

Check for the 'Closure letter' format

Check UI of the 'Account type conversion' window

Check for the client- L3 field

Check for the searching of the client

Check for the 'Convert account from' field.

Check for the 'Convert account To' field.

Check for the 'Welcome letter' generation for the client which are active

Check for the account-L4 in 'Convert Account from' field as per selection of client-L3

Check for the creation of the new account which will be selected while conversion as 'To account'.

Check for the account-L4 in 'Convert Account To' field as per selection of client-L3

Check for the proct class details in the window

Check for the 'With Effective from' date

Check for the W.E.F date for product

Check for the ISIN managed account list.

Check for the 'Investment account number'

Check for the 'Wrapper' in case of 'Equity' product

Check for the movement activity in account type

Check for the data movement for any product if there is no Holding

Check for the data movement for MF if there is no Holding

Check the asset class display in the window if any one asset class movement activity completed

Verify Account type tagging approval by checker.

Verify data transfer after checker's approval.

Verify data transfer after checker's approval.

Verify Account type tagging rejection by checker.

Check the capturing of Email ID of the client

Tick the 'Hand' check box

Select account from-L4, account To -L4, select w.e.f date & all the wrappers w.r.t products then press 'OK'

Verify Account type conversion checker window for the display of account type tagging.

Verify Audit trail report for the account type conversion.

Check the autopopulate of Email ID of the client after tick on 'Email' checkbox

Tick the 'Email' check box

Untick the 'Mail' check box

Check for the MIS report sending to all client

Check for the Email send to the client is CC to its RM

Check the types of schedular

Check for the Global level schedular

Check for the Client level schedular

Check the window for 'Global setting'

Check for the filed 'Reoccurance pattern'

Select multiple 'Reoccurance pattern' at a time

Select 'Daily' radio button

Select 'Every day' radio button

Select 'Every weekday' radio button

Select all days radio button at a time

Select any day from the list

Check for the Day of Occurance

Check the of reoccurance pattern if selected as 'Weekly'

Check the of reoccurance pattern if selected as 'Fortnightly'

Check the of reoccurance pattern if selected as 'Monthly'

Check for the report scheduling if 'Monthly' reoccurance is selected

Keep value as 6 in the 'Day of Occurance' field

Check for the 'Report start date' field

Untick the 'Report start date field

Select any date in 'Report start date' field

Check for the End date option

Select 'Selected Days' radio button

Select any date in 'Report End date' field

Select 'Month last day' radio button

Select 'Month last day' radio button

Check for the range of occurance field

Check validation for the 'range of occurance' field

Check for month field

Select any month from the list

Check for the 'Day' field.

Enter any day in the field

Check for setting for MIS schedular at client level

Check the MIS schedular window for client

Generate client report

Check for the cover page

Check the of reoccurance pattern if selected as 'Monthly'

Check for the master for cover page letter

Check for 'Cover page' as per set in master

Check for the Email sending screen

Check for the 'Branch' field

Check for the 'Account' field

Check for the 'Report for' field

Check for 'From Date & To date'

Check for the client data for any Branch, if the setting has been done at global level

Check for the client data for any Branch, if the setting has been done at client level

Select the date range & press 'Get data', for global level setting

Clieck on 'Send' button for selected client

Check the status after sending the report

Expected Output Comments

Should allow to make changes.

Library

Should not allow to make changes.

Library

Ok

System should allow to edit the 'Business unit details

System should allow to delete the 'Business unit details

Library

Library

Library

Test case Source

In the DP account will be created via Integration L4 , hence modification should not be allowed.

System should open the 'Business Unit window, should contain fields as 'Unit Name, Short name, Ext map code, Investment Suitability'

System should allow to create new 'Business Unit' & save the same in master.

System should allow to create 'Group-L1' for International clients.

System should allow to create new Family for 'International client'

New family details should save by displaying successful message on save action.

Library

Library

Not clear ?

System should authorize family by using checker login.

Library

Not clear ?

Library

Ok

Library

Ok

Library

OK

Delete button should not be enabled.

Library

Ok

Library

Ok

Library

System should create new L3 with respective CRN.

Should pop up mandatory validation message for following fields;Family NameClient GroupReason

Reason should not be mandatory

System should pop up validation message to user as 'Maker cannot be checker'.

System should open family window while displaying already saved values.

System should save modified values and when you retrive same family then modified values should display.

Should open family window with displaying all saved values but make sure save button should not enabled on view mode.

Should pop up validation message to user as 'Maker can not be checker'.

Should successfully reject family name and again display in maker module.

once displayed in Maker , should be allowed for edition.

CRN ? Autogenerated or manual input?

Library

System should create new L3 with respective CRN.

System should update master details in Integra if not present.

Update ?

System should not create the record

not clear ?

System should create the L3

System should generate the report at the Family level

System should generate the report at the client level

System should tag newly created L3 to the respective newly created L2.

Multiple l3s can be tagged to L2

System should pop up validation message to user as 'Same family name is already present in the system'.

System should tag newly created L3-client to the respective Family exist in the system, identify w.r.t family CRN.

Family CRN,this is autocreated when will data flow from BCIF

System should update other details of client at L3 & L4 level in Integra as per data received.

System should generate the report for Bank and MF only

System should generate report only for Bank and MF only

System should send the Email copy of report to client

MIS report should be send to the client is in 'Detail' level.

Formats will differ

System should generate the report including Equity, MFSS, Bank

System should generate the report including Equity, MFSS, Bank

System should sent the report copy for printing and not send the Email copy

System should sent the Email copy and also send for the printing

MIS report should be send to the client is 'Abridged' means brief level.

Different Abridged report Format is applicable

Bydefault 'Full' report should be send to the 'Family office' client

MIS report should be send to the client at Family level

System should automatically update the information at L4 level

MIS report should be send to the client at individual account level

System should update the L3 but should not reflect the changed address at L4

System should update the L3 but should not reflect the changed address at L4

System should update the details at L4 if details update other than Contact number Address and Email id for IAS client

System should send the statement copy to the address mentioned at the L4 and not on updated L3 address until it is manually changed at L4

System should send the statement copy to email id mentioned at the L4 and not on updated L3 email id until it is manually changed at L4

System should allow to update the address manually for IAS account at L4

System should allow to update the caontact number manually for IAS account at L4

System should create new L2 & L1 w.r.t family CRN of L3

System should map existing L3 to newly created L2.

System should tag L3 to modified L2.

System should allow to update the Email id manually for IAS account at L4

System should not allow to modify manually any other details except Contact number Address and Email id at L4 for IAS client

System should not allow to modify manually any detail for Executionary client

System should flow to detail even if the segment is changed from Wealth to retail

System should flow to detail right from the start date of the client

System should check for the existance of respective 'Family CRN-L2' in integra.

System should generate exception report as 'First Name' missing w.r.t CRN

System should not give exception report





System should generate exception report as 'It type' not exist in the Master w.r.t CRN details

System should generate exception report as 'Country' not exist in the Master w.r.t CRN details

System should generate exception report as 'State' not exist in the Master w.r.t CRN details

System should generate exception report as 'City' not exist in the Master w.r.t CRN details

System should generate exception report as 'Occupation' not exist in the Master


System should generate exception report as 'Deactivated RM'



System should generate exception report as 'RM' not exist in the Master

System should generate an exception report & should not create the client.

System should generate exception report as 'Branch' not exist in the Master

System should generate exception report as 'Category/Segment' not exist in the Master.

System should generate exception report as 'Client CRN' is blank

System should generate exception report as 'Family CRN' is blank

System should process the the client creation activity.

System should flow the details for 'Active client

System should not flow client details in INTEGRA





Need to discuss


Log file should get generate for 'Exception' & 'Successful' details w.r.t integration details

System should flow client details in the INTEGRA






Then its incorrect.

Entry should not be present in the exception report any more (post successful entry posting in integra).

System should enter only one entry in INTEGRA, after correction in exception.

System should integrate the master data in the INTEGRA & update the master details

Integration & updation should be at increamental level.

System should display 'CRN' column in list.

It should be available.

It should be available & should display all 'UCC' exist in the system.

Authorised signatory should have rights for the same.

Library

System should authorize client by using checker login.

Library

Should Give a pop mentioning last name mandatory

Library

Library

System should allow to map existing L3 to newly created L3 as 'Authorised signatory'

Should pop up mandatory validation message to user if data saved without entereing mandatory fields.

Should open window with input details to save new client under family.

Library

System should not allow to create L3 client without L2- family.

Library

Library

Should allow the editing of the data

Library

Should not be allowed by the system

Library

Should be allowed by the system

Library

Library

Library

Library

Library

Should save new client details as entered and available for authorization at checker level.

Should successfully reject the details entered in maker level and again display in maker module.

System should pick Date of Incorporation if accounts investor type selected as 'Company'.

System should allow to save account name having same PAN no. which is the joint holder name of another account name.

System should allow to save account name having same PAN no. which is the joint holder name of another account name where MF holding nature kept as 'Anyone or Survivor'." MF FEED FILE & REPORT should be shown as first holder name

Though the Mf holding nature is same of two different account name but the joint holder names and PAN are same,system should allow to save the account details.

" MF FEED FILE & REPORT should be shown as first holder name

Library

" MF FEED FILE & REPORT should be shown as first holder name

Library

System should flow only those clinet which is of weath segment

System should create the New L4 as executionary

System should display CRN for 1st holder as primary holder

System should display CRN for 2nd holder

System should not flow other data which is not of wealth segment

System should update the new information if the holding patter is same

System should update referencing at L3 level for 2nd and 3rd holder CRN

MWI should update following fields:CRN for primary holders and secondary holdersBank account noStatusProduct ID,Holding PatternMode of operationsName & relationship of primary and secondary holderAccount typeEffective from dateBank IFSC Code and LG code

System should display CRN for 3rd holder

System should display bank account no with validations.

System should display CRN for 1st holder as primary holder

System should not display CRN for 2nd holder

System should not display CRN for 3rd holder

System should display bank account no with validations.

System should display holding as single

System should display holding pattern as "Joint"

System should display "single/ Joint / Eighter or Surviour

Should display name of primary holder, as in L3

Should display name of primary holder, as in L3

System should display name of subsequent holder's name.

System should display bank IFCI code in specified format

System should display eligible LG code.

MWI Should update process date.

Process flag is "Y" if processed by miles else"N"

System should display relationship of primary and subsequent holder as flown from finacle

System should display account type as CA/SA/TD as the case may be

System should display effective date on which account is activated

System should ignore account creation and no balances to be reported for MIS for LG codes like, KSFPG, KSPMSP, KSCATT & PMSRLB

Process remark should be updated by miles.

System will generate the Exception report if CRN is missing

System should give an Exception report

System should give an Exception report

System should give an exception report

System should update the status as active

System should give the exception

System should create the New L4 if the holding pattern is different

System should remove the exception and proceed with the creation of New L4

System should mapped the bank account number to investment account number in miles

System should update the status as Dormant

System should update the status as De activate

System should update the status as Closed

System should not allow to reactivate the same

System should create the new L4 with joint holding

System should allow select one default bank account

System should search for the Existing L4 on the basis of Single holding partern if found update the information or create new



System should update the IFSC code in the bank creation screen

System should update only the incremental data

System should allow to create the new L4 for IAS

System should allow to create the L4 from IAS to Executionary

System should allow to create the L4 from Heldaway to IAS

System should do automatic cash out flow and inflow of corpus

System should give an exception report to select the default bank account

System should move all the corpus from Executionary to IAS automatically

System will be reposted afresh all entries in executionary and advisory account respectively

System should accept the balance for the Last 3 days and update the same in the Application Bank Account

System should allow to create the L4 from Executionary to Heldaway

System should generate the Exception report

System should generate the Exception report

System should push the data for FD / TD account

System should not push the Un clear balance

System should push only the clear balance and not the accrual

System should allow to edit default bank account.

System should ignore the FD and TD balance once the client is converted to IAS from Executionary

System should tag default bank account basis first account information flown into MWI

System will set the POA by default as Yes based on LG code and Product ID

System should keep the POA as "NO" by default and on the conbination of LG code and Product id will be "YES"

DP POA flag will be "Y" by default if Bank POA is "Y"

No format mentioned in FSD

No format mentioned in FSD

Sysemt Should allow drop down.

System should show existing values.

System should allow to add new LG code

Sysemt Should allow drop down.

System should allow to select eighter Yes or "No" in drop down

Following fields should be present in LG code master:LG CodePOAProduct CodeExcludeSave ButtonCancel Button

System should allow to save the newly entered data

System should allow to cancel the newly entered data

System should include balances

System should not include balances

System should disable "Exclude" drop down

System should not take any action.

Process date should be updated by miles

Process remark should be updated by miles

Process date should be updated by miles

System should allow to select eighter Yes or "No" in exclued tab drop down

Process remark should be updated by miles

System should update FX rates in miles at EOD

Miles should update correct value of base currency

Miles should update correct value of alternate currency

Miles should update process date

Miles should update process remark

Miles should update process date

Miles should update process remark to " "

Miles should update process remark

MFSS should flow fields as 1.CRN - Investment account number+Default CRN as 99999.2.Investment account number3.Closure date

System should modify the details in respective L4.

System should check for existance of the L3

System should check the existance of L4 w.r.t holding pattern

System should check whether 'Investment account' number is already exist in the Integra

System should not generate new Investment account - L4, it should skip the L4 creation process.

System should modify the client related details in L3 of respective 'Distribution client' e.g RM, branch, etc

System should create new L3,L2 $ L1 with number as 'Investment account No+Default CRN 99999'

System should create new L4 & mapped under L3 of distribution client.

System should tag the 'Investment account' to that L4 which is already exist.

System should create new L4 with respective holding pattern, & tag the investment account to the same.

System should not create new L4 in the system.

System should search for the L3

System should tag L4 to the L3 of first holder.

System should give exception error for L3 missing, & L4 creation should be pending till L3 creation.

System should create L4 with respective holding pattern & tag it to respective L3.

System should flows the data or create L4 of those client whose segment is 'Wealth' for 'Relationship client

System should not flow the data or create L4 of those client whose segment is 'Retail' for 'Relationship client

System should flows the data or create L4 of those client whose segment is 'Wealth' for 'Distribution' client

System should not flow the data or create L4 of those client whose segment is 'Retail' for 'Distribution' client

CRN should be created for respective client in BCIF & flow to MWI

New L3 should get create in MWI after data flow from BCIF.

System should not flow any data if client segment is RETAIL.

System should not flow any data if client segment is RETAIL.

No data should flow in MWI, as this is Retail client

System should create new L4 as per investment number & holding pattern & tag to the respective L3.

1.System should flow the holding details from MFSS to Integra.2.New CRN also get generated through BCIF

1.System should flow the holding details from MFSS to Integra.2.No reporting to the client.

1.System should flow the holding details from MFSS to Integra.2.L3 should get created as per default CRN


Here new CRN L3 & L4 should get generate for the distribution client with default CRN-99999, data should be continue to flow on new L3-L4

No data should flow in MWI, as this is Retail client

Need to confirm

1.Here new CRN L3 & L4 should get generate for the distribution client with default CRN-99999,2.Data should be flow on new L3-L4 since inception


1.Here new CRN L3 should get generate for the relationship client through BCIF2.MFSS Data should be flow on new L3-L4 since inception

1.System should flow the holding details from MFSS to Integra.2.New CRN also get generated through BCIF

System should create different L4 w.r.t holding pattern for each investment account.

MFSS should not have multiple investment account with same holding pattern.

System should create new L4 under L3 with single holding pattern.

System should create new L4 under primary holder L3 with joint holding pattern.

System should give the exception report

System should keep the DP POA as YES if the POA flag is YES

Library

Should save new client details as entered.

Library

System should give exception report that 'L3 missing' for the client.

System should give exception report that 'L3 of second holder is missing' for the client.

System should give exception report that 'L3 of third holder is missing' for the client.

System should mapped the DP id on the basis of account number mapped to L4

System should keep the DP POA as NO if the POA flag of BANK is NO

Should open Account information window to save new client for L4

Should allow the editing of only bank and DP POA

Library

Should save bank details for the client entry.

Library

Library

Should not be allowed by the system

Library

Should be allowed by the system

Library

Client details should open in view mode and save button should be disabled.

System should allow to create new L4 for Debt & managed account Product as per holding pattern.

This product account should tag to existing same holding pattern account - L4.

System should allow to create new L4 for Debt & managed account Product as per holding pattern.

RM should be mapped to the client through BCIF integration only

SRM mapping should be done through 'Account relationship' map window.

System should not allow to delete primary RM

System should allow to delete Secondary RM

It should have fields as 'Primary RM code, Secondary RM code'

It should have fields as 'Account , Primary relationship, WEF date,Secondary relationship, WEF date, Asser class RM, WEF date'

1.Account field should display all account in the system2.Relationship manager field for 'Primary, secondary & Asset class' should display all the RM as per master3.WEF date should be in DD-MM-YYYY format

System should not allow same WEF date for two different primary RM at a time.

System should not allow same WEF date for two different secondary RM at a time.

System should be able to map secondary RM to the client manully & save the same.

System should allow to upload the file & respective mapping should get save in the system.

System should save the data as per uploaded in the excel file w.r.t RM & SRM mapping.

Need to discuss

It should have fields as 'Secondary RM code & UCC'

Need to discuss

System should tag the SRM to the client w.r.t Primary RM code from BCIF & RM SRM mapping data uploaded in the MWI.

System should give message while file upload as 'RM & SRM not exist in the system'

System should give message while file upload as 'Duplicate record in file'

SRM should be mapped to the client as per data uploaded in the excel file.

There should not be any impact on any client RM SRM mapping, this SRM client mapping should change the SRm mapping of the client whose UCC number is mentioned in the mapping file.

System should override the RM SRM mapping for client as per file uploaded

Mapping for the RM SRM mapping should be done thruogh the same screen as 'Account Relationship Map'

System should allow to map RM to the International client.

System should allow to map SRM to the International client.

System should not allow to save blank Rm details

System should not generate 'Welcome letter'

It should be as per mentioned in FSD.

System should generate closure letter for those client

System should allow to edit in the RM SRM mapping of the client.

System should allow to delete existing RM SRM mapping of the client & add new.

System should generate 'Welcome letter' for activated IAS client.

System should generate 'Welcome letter' only for those IAS client which are activated within selected date range

System should not generate 'Closure letter' for active client.

It should be as per mentioned in FSD.

It should be a search field with search button & list box field.

New L4 should be created manualy as 'IAS' account.

It should display 'Clinet L3, Account convert from, Account convert To, Product, With Effective from date, ISIN list & scheme name for Managed Account, Debt scheme, Bank account number FD/TD, Investment account number, Ok & Cancel button'.

System should search existing client w.r.t CRN number or client name enetered in the field.

System should display all the L4 mapped to the client with respective product definition.

System should display all the L4 mapped to the client with respective product definition.

It should be the Executionary L4-Account of client from which all the corpus need to move to new account

It should be the IAS L4-Account of client in which all the corpus need to move from old executionary account

It should be the date field.

Respective security should not be moved.

Its Invest account number & folio number should be move.

1.System should display products as 'Equity, Debt, Managed account, Mutual Fund'2.It should be check box field.

System should auto transfer the corpus from Executionary to IAS account on selected W.E.F date.

System should display all the ISIN as per holding of account under 'Debt/Managed account' product.

System should display all the Investment account number of account under 'Mutual Fund' product.

All the scripts under one BO code should be moved to destination account on W.E.F date.

System should display only remaining asset class data in conversion window.

This account type movement should be allow to be done in , 1.Executionary to IAS2.IAS to heldaway3.Heldaway to IAS4.IAS to executionary5.Executionary to Heldaway6.Heldaway to executionary

Should display account type tagging done by maker.

Client should get 'Hard copy' of the MIS report

1.System should tag the conversion as per selected by MAKER.2.Respective tagging should be displayed to the Checker's window

Checker should be enabled to approve account type taging done by maker

Relevant data should be transferred from original account to new account if checker approves tagging.

Relevant data should be transferred from original account to new account on W.E.F date selected.

Checker should be enabled to reject account type taging done by maker

Audit trail report for the account type conversion should be available and should contain relavant details.

In L3 window, on reports tab system should capture Email ID for Mail sending

Email ID which is capture in 'Contact' details should get autopopulate once user tick the 'Email' check box

Client should get soft copy of MIS on his EMAIL

Client should not get soft copy.

MIS report should be send to only IAS client.

System should send Email to client with copy to its RM.

System should not allow.

System should have two types of Email schedular as 'Global & Client level'

1. In this setting, schedular should generate report for all clients in the system.2. In this setting all the client should get his MIS report on his EMAIL, w.r.t availabily of EMAIL ID.

1. In this setting, schedular should generate report for all those clients for which individual setting has been done2.In this setting only respective client should get his MIS report on his EMAIL.

It should have fields as 'Reoccurance pattern, Send to account, No End date, End after,End date' & 'Save, cancel, delete' button.

It should have options as 'Daily, Weekly, Fortnightly, Monthly, yearly', all should be radio button, should be selected one at a time

System should schedule report generation process EVERYDAY.

It should display new fields all days name with radio button

System should not allow.

System should schedule report generation process on that DAY.

System should schedule & send the report on Monthly basis.

It should display new fields as 'Everyday & Every Weekday', both should be radio button

It should be Daily report scheduling of the weekdays from Monday to Saturday

System should schedule report generation process on every 15 days i.e, twice in the month.

It should display fields as ' Day of occurance, Report start date, Report End date, End date option'.

It should be a text field & should accept only numeric characters from 1 to 31

It should have two radio buttons as 'Selected Day & Month last day'

Report End date' field should be disable.

Respective month last date should be 'To date' for the MIS Report.

System should schedule & generate report on 6th of every month.

1.It should be 'date field & should open calender after clicking on it.2.Should navigate properly.

System should default take '1' as start date (From date) for report generation.

Respective date should be consider as 'From date' for report generation for that month.

System should enable 'Report End date' field & allow user to select month last date for MIS.

Respective selected date should be 'To date' for the report to be generated.

1.It should be 'date field & should open calender after clicking on it.2.Should navigate properly.

It should be the date on which report to be generated.

It should display two fields for 'month & day'.

It should be a drop down field & should display all months

Yearly report should be get generate on selected month

It should be text field & should accept only numeric characters from 1 to 31.

Yearly report should get generate on the respective day of selected month.

Schedular setting should be done from 'L3' window at Report tab

Window UI & its setting should be same as explained above.

Cover letter should be attched with MIS Email send to the client

System should generate the report for respective client, for specified period as per setting

There should be master for setting the format for 'Cover page letter'

System should send same 'Cover page letter' as per master.

It should have fields as 'Branch, Account, Report for, From & To date & Buttons as 'Get data, Generate client Email data, Send & Cancel.

It should be drop down field, & should display all the branches as per master

It should be drop down field, & should display all the client account in the master.

It should be drop down field & should display all report name which comes under MIS.

It should be date field, 'From date' should not be selected greater than 'To date'.

System should list down all the client list w.r.t branch for which MIS report need to send

System should list down those client w.r.t branch for which MIS report setting has been done.

System should display client list for whom MIS report to be send.

Status should be change to 'Sent'.

System should send the MIS report on respective client Email ID which is saved in the master.

Documents

Master Client Creation_scenario_Test Cases_including Client On Boarding (5)