Step by step procedure to trace the unverified newly created cif in DOP Finacle
- As we all know that recently in DOP finacle application aadhar is mandatory for all the cif creations i.e., document column in every cif creation should be filled with aadhar card number.
- In finacle during migration of accounts from sanchay post software to finacle application multiple cif ids are created and transferred to finacle for the same customer.
- Also previously there is no validation of aadhar linked to cif id hence multiple cif ids are created with same aadhar number in DOP Finacle.
- In order to avoid multiple cif ids for the same customer in DOP Finacle a validation of aadhar mandatory placed for cif id.
- While creation of cif id's system is throwing the error i.e., Aadhar is already linked to some other account. In order to find the existing cif id with the entered Aadhar numbers all the DOP finacle users can CLICK HERE.
- In DOP Finacle we generally use the menu CCRC for creation of new cif id's, sometimes during cif creation we will forget to note down the cif id number for any reason then what is the procedure to trace the unverified newly created cif id?
- The answer to the above question is explained below in a step by step manner.
Step by step procedure to trace the unverified newly created cif in DOP Finacle :-
- Invoke the menu CCRC then the system will display the below screen shot as shown
- Then select the function as verify as shown
- In the next step enter the first 4 digits of the cif number (first 4 digits can be traced depending on the previously created and known cif for previous account opening) as shown in below figure
- Then just give a tab and press then Enter button then system will display the list of unverified cif ids as shown
- From the above screen shot it is clear that system is displaying the list of unverified cif ids but note that those mentioned cif ids are pertaining to all SOL's hence check all the pages to trace your unverified cif id from the list.
ADD THE FACEBOOK WIDGET CODE HERE
CommentsComment