KSFE CUSTOMER ONBOARDING

APPLICATION

Purification of Customer data in our Core application-CASBA has been a long

awaited activity. As part of this mission, we have started a 'Deduplication' project. The

main aim of the project being identifying the duplicate Unique IDs of a customer and

grouping them appropriately and, restricting further duplicate Unique ID creation for

existing Customers. For accomplishing these objectives, new Web and Mobile

applications are being introduced for customer related activities such as:

●​ New Customer creation

●​ Updating existing customer register
●​ Customer KYC
●​ Identifying and grouping of duplicate customer IDs

This document will be helpful in getting used to the new Application.

General guidelines regarding Deduplication:

1.​ Unique IDs in Casba will be classified into 3 categories:

●​ 'O'- Original ID
●​ 'D'- Duplicate ID
●​ 'Null '- Unique ID where deduplication is not performed
​ Category of a Unique ID will be seen as a new column named- DEDUPE STATUS

in Customer search result table as shown below. There will be no 'O' or 'D' value in this

cell if dedupe activity of that customer is not performed. Also the ORIGINAL ID of that

customer will be displayed in a new column named- ORIGINAL UID.

 2.​ After doing deduplication of a Customer, one of his/her Unique ID will be made
ORIGINAL - which is marked 'O' & if there are duplicate IDs, they will be marked 'D'
in Casba
3.​ Further new Scheme creations in Casba will only be allowed through 'O' or Null
status Unique IDs

HOW TO CREATE A NEW CUSTOMER

I.​ Customer creation through Web portal

Instructions for Onboarding a New Customer:

1.​ Ensure the correctness of Customer Mobile number, PAN & Aadhaar number
2.​ Collect the copies of KYC documents

Use the following URL in Computers in which CASBA is available: 10.20.8.63:32016 for

accessing the Web application.

Login screen will appear like this. Login password is the same as the password which

is used for logging in to the Powerapp Admin module. Click on Add New Customer

button.

Input the Mobile number of the Customer. An OTP will be sent to the Mobile number.

Enter the OTP. Start by selecting the Account type of Customer.

All the mandatory fields of Customer Register is marked with a red Asterisk (*).

Communication Mobile Number -can be given the same as that of the KYC Mobile

number or, can be a different Mobile number. If a different Mobile number is given as

the Communication Mobile Number, OTP Verification of that Mobile number should

also need to be done. 'One KYC Mobile number cannot be given to another Customer

but, one Communication Mobile Number can be given to any number of Customers'.

After completing all the fields in the first page, click on the Next button at the

bottom of the page. In the next page, input the Address details of the Customer. Input

the Bank details of the Customer in the next page however, it is not mandatory. On

Successful completion of onboarding, a message will appear as shown below.

Now click on the Applications button to see the new customer details. If the Status of

the Application is 'COMPLETED' , New Customer creation will be completed in Casba.

Check in Casba if the new Unique ID is created.

If the Status of Application is 'PENDING' in webportal , Click on the Name of the

Customer and click on the 'Dedupe Details' button as shown in the below image.
If no data is displayed under this button, this New Customer application will be

changed to 'COMPLETED' status automatically. Branches will have to do nothing

further. Customer creation will be completed in Casba.

Instead, if there are any Customer names listed under the Dedupe Details button,

they may be possible duplicate Unique IDs existing in CASBA - of that particular

Customer which were identified by the software. Software identifies these possible

duplicates based on the Mobile number, PAN, Aadhaar number given while creating

a New Customer. These identified IDs will be displayed under 2 headings-Similar

records & Different records.

We have to open the names one by one and check if they are duplicates. Mark those

Unique IDs as DUPLICATE/REJECTED appropriately.

If the selected ID is a possible duplicate ID of the same Customer, click on DUPLICATE

or else select REJECTED. Then click on UPDATE button. Only after marking all the listed

IDs as either DUPLICATE/REJECTED, a SUBMIT button will become active at the end of

the page.

Click on the SUBMIT button. In the next screen, a list of DUPLICATE marked Unique IDs

will be listed as follows.

Click on the Yes button to proceed. After proceeding, no further Scheme creations

will be permitted in Casba against those DUPLICATE IDs. Any New Scheme creation for

that particular customer will only be allowed through his/her ORIGINAL UNIQUE ID.

After clicking the Yes button, a pop-up message is shown. This message asks if the

Communication Address field of the DUPLICATE IDs needs to be updated with the

Communication Address details given in the ORIGINAL ID(Communication address

which was input during Customer creation).

On clicking Yes, the COMMUNICATION ADDRESS will be updated in all the

DUPLICATE Unique IDs. If this action is not required, please click on NOT NOW.
 After the status of an application is changed to 'COMPLETED' , a Unique ID will

be created in CASBA with Dedupe status 'O' and the DUPLICATE marked Unique

IDs will be marked as 'D'. Against each DUPLICATE marked Unique ID in Casba,

its ORIGINAL UNIQUE ID will be displayed for reference.

II.​ Customer creation through Mobile app

Mobile app can be downloaded from the following link:

https://drive.google.com/file/d/1pgiUa_V2JMczzYPbjo3kPCFt_THzzeY7/view?usp=sha

ring

Login ID & Password is the same as explained above. Start Customer creation by

inputting the Mobile number and OTP.

 If the customer has provided a PAN & Aadhaar Card, click on

the PAN Card & Aadhaar Card button. If any one of the documents is provided, select

the appropriate button. On proceeding, verification of the selected KYC document

needs to be done. If Aadhaar Card is selected, an OTP will be sent to the Mobile

number linked with the Aadhaar.

If the customer has not provided any of the listed KYC Documents, there is an option

to Skip this step and proceed with customer creation. However, such Customer

creation is not promoted. Skipping this step is only allowed in emergency cases.

Skipping this step will decrease the chance of identifying the possible duplicate

Unique IDs of this customer.

After selecting the KYC Document, Branches can either Upload the document from

Mobile or Capture the image through Camera. In the coming pages, enter the

Personal details, Address, Bank details, Customer Photo, Customer signature etc of

the Customer.

After completing the steps in the Mobile app, remaining steps(DUPLICATE/REJECT

MARKING) are to be done in Webportal as mentioned earlier.

HOW TO UPDATE EXISTING CUSTOMER DETAILS

I.​ Customer updation through Web portal

Unique IDs in ‘D’ status cannot be edited through this portal. For editing Unique IDs in

‘O’ status or dedupe not performed ID, Click on Update Customer button –

Then input the Unique ID in the Search field and click SUBMIT. Click on the edit button

on the top right corner of the screen and edit the required fields. After editing,

click on the UPDATE button at the bottom of the page. Now

Customer register updation is completed. Now go to Applications, and select the

Application of this customer. Click on the Dedupe Details button. If any Unique IDs

are in PENDING status, select those IDs and mark DUPLICATE/REJECT appropriately.

Then click SUBMIT. The updated details will now be reflected in Casba.

II.​ Customer updation through Mobile app

Login to the Mobile app and enter the KYC Mobile number of an existing customer.

Enter the OTP that has been sent to the Mobile number - Select the type of Detail to

edit (Photo/Personal Details/Address Details/Bank Details/Documents) - Click on Edit

button - Update the fields - Click on Save.

If PAN or Aadhaar are updated through Mobile app, after completing the steps in

Mobile app, please check the status of that application in Webportal. If any

duplicate Unique IDs were identified by the software with the updated

PAN/Aadhaar, such IDs need to be marked DUPLICATE/REJECTED to complete the

process. When the status of the application is changed to COMPLETED, the changes

made will be reflected in Casba.

HOW TO UPDATE UNIQUE IDs IN

CATEGORY-"Insufficient Data" SEEN IN

DASHBOARD
Unique IDs in Casba belonging to the following categories will be grouped under the

Category: "Insufficient Data" in the Dashboard:-

●​ Missing Mobile number

●​ Invalid PAN Number
●​ Missing Permanent Address field
●​ Missing any Mandatory fields in Customer Register
For updating such Unique IDs, click on Dashboard - click on the button showing

count of Insufficient Data - Select an application - In the new page, update the fields

appropriately - click on Update button. Now this Customer application will be moved

to the Applications button. If the status of the application is 'PENDING' , click on the

application - click on Dedupe Details button and check if there are any duplicate

Unique IDs identified. If yes, mark each Unique ID as DUPLICATE/REJECTED and then

click on SUBMIT button. If no Unique IDs are listed under the Dedupe Details button,

the status of the application will automatically be changed to 'COMPLETED' status

and the changes made will be visible in Casba.

COMMON ERROR MESSAGES & THEIR

SOLUTIONS

1. While onboarding a customer through webportal, if the input Mobile number is

already existing in our new application, the following error message will be

displayed.
In this case, go to the Applications button and use the filter option on the

top right corner of the screen to find which Customer holds this Mobile number. If

the Mobile number belongs to the same customer, there will be no need for creating

a new Unique ID for this customer.

If the Mobile number is seen in the record of another customer, Branch needs to

verify the correct ownership of the number. If the Mobile number of that customer is

different, then Branches will have to Update that Unique ID with his/her correct

Mobile number using the UPDATE CUSTOMER button in our web portal.

2. While onboarding a customer through webportal, if the input PAN number is

already existing in our new application, the following error message will be

displayed.

In this case, go to the Applications button and use the filter option on the

top right corner of the screen to find which Customer holds this PAN number. If the

PAN number belongs to the same customer, there will be no need for creating a new

Unique ID for this customer.

If the PAN number is seen in the record of another customer, Branch needs to verify

the correct ownership of the number. If the PAN number of that customer is different,

then Branches will have to Update that Unique ID with his/her correct PAN number

using the UPDATE CUSTOMER button in our web portal.

3. While onboarding a customer through webportal, if the input AADHAAR number

is already existing in our new application, the following error message will be

displayed.

In this case, go to the Applications button and use the filter option on the

top right corner of the screen to find which Customer holds this AADHAAR number. If

the AADHAAR number belongs to the same customer, there will be no need for

creating a new Unique ID for this customer.

If the AADHAAR number is seen in the record of another customer, Branch needs to

verify the correct ownership of the number. If the AADHAAR number of that customer

is different, then Branches will have to Update that Unique ID with his/her correct

AADHAAR number using the UPDATE CUSTOMER button in our web portal.