You are on page 1of 2

SOP FOR OPERATING OFFICE USER (CWISS)

1. As per IRDAI guidelines KYC verification for policy holder has to be done before policy
issuance.
2. If an existing party holder code is used in the policy, PAN and DOB (if not already available
in party) will be captured at time of quote approval. For a new party code, PAN and DOB
will be captured at time of party creation.
3. At the time of quote approval, using PAN and DOB, system will check with CKYC database
to fetch KYC details available against that PAN.
4. If KYC details are received from CKYC database, existing policy issuance flow will continue.
5. If KYC details are not received from CKYC database, office user will be prompted to upload
any of the following documents of policy holder.
a. Driving License
b. Voter ID Card
c. Passport
d. Aadhaar Card
6. Based on the document uploaded, KYC details will be fetched. Post which existing policy
issuance flow will continue. If KYC details are NOT available, then user will not be allowed
to issue policy.
7. Once KYC for a policy holder is done, the above KYC flow will not be prompted again
during subsequent policy purchases using the same policy holder/party code.
8. Take written consent from the Customer that Customer is giving his/her consent to New
India Assurance to verify KYC for Policy issuance as mandated by the IRDAI.

SOP FOR ONLINE INTERMEDIARY CHANNEL

1. As per IRDAI guidelines KYC verification for policy holder has to be done before policy
issuance.
2. For existing policy holder codes as well as for new policy holder code, PAN and DOB (if
not already available in party) will be captured at time of entering personal details.
3. At the time of quote approval, using PAN and DOB, system will check with CKYC database
to fetch KYC details available against that PAN.
4. If KYC details are received from CKYC database, existing policy issuance flow will continue.
5. If KYC details are not received from CKYC database, intermediary will be prompted to
upload any one of the following documents of policy holder.
e. Driving License
f. Voter ID Card
g. Passport
h. Aadhaar Card
6. Based on the document uploaded, KYC details will be fetched. Post which existing policy
issuance flow will continue. If KYC details are NOT available, then policy issuance will not
be allowed.
7. Once KYC for a policy holder is done, the above KYC flow will not be prompted again
during subsequent policy purchases using the same policy holder party code.

SOP FOR OPERATING ONLINE CUSTOMER CHANNEL

1. As per IRDAI guidelines KYC verification for policy holder has to be done before policy
issuance.
2. PAN and DOB of the policy holder (if not available in party) will be captured at time of
entering personal details.
3. At the time of quote approval, using PAN and DOB of the policy holder, system will check
with CKYC database to fetch KYC details available against that PAN.
4. If KYC details are received from CKYC database, existing policy issuance flow will continue.
5. If KYC details are not received from CKYC database, the customer will be asked whether
customer’s mobile number is linked with Aadhaar.
6. If Yes, then customer will be redirected to Digilocker page where KYC will be verified by
means of Aadhaar based OTP and existing policy issuance flow will continue. If mobile
number is not linked with Aadhaar, then customer will be prompted to upload either of
the following documents:
i. Driving License
j. Voter ID Card
k. Passport
l. Aadhaar Card
7. Based on the document uploaded, KYC details will be fetched. Post which existing policy
issuance flow will continue. If KYC details are NOT available, then customer will not be
allowed to issue policy.
8. Once KYC for a policy holder is done, the above KYC flow will not be prompted again
during subsequent policy purchases using the same policy holder party code.

You might also like