Project

General

Profile

Actions

Feature #132

closed

QC Process DCB

Added by Vijayakumar over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
High
Assignee:
Chandramohan
Start date:
11/12/2020
Due date:
11/17/2020
% Done:

0%

Estimated time:
Project categorization:

Description

Dear Chandra,

Pls find the proposed Process for DCB Operations . Kindly take this on priority

Branch

1. RO will source in the field.
2. RO will do Quick data entry for CB Check thru Api integration
3. CB status – Approved / Rejected
4. Only for Approved customers , Detail data entry should be done in CIMS Platform
5. Image capturing -5 images
a) Member – Live Photo (1)
b) Aadhar - Front & Back (2)
c) Voter ID – Front & Back (2)

Backend Operations - Pre QC mechanism

1. Ops team will do Quality Check for all members
2. Any data correction will be done at back end team- Ops
3. For image related issues , they will raise the discrepancy and send back to RO Queue
4. Once Pre QC is cleared, Account opening form will be Generated and sent to branch team

Branch

1. Branch Team will take Printout
2. In CGT / GRT – Bank Pass book Image will be captured in CIM’s mobile application
3. Post GRT- Documents to be uploaded in CIMS portal thru scanned mode
a. Signed Account opening form – Front & Back ( 2 )
b. Form -60 - Front & Back ( 2 pages)
c. Member – Aadhar card_ Front & Back ( 2 ) ( Along with member self-attested / OSV done by Bank – PSM)
d. Member – Voter card_ Front & Back ( 2 ) ( Along with member self-attested / OSV done by Bank – PSM)

Backend Operations -Post QC mechanism

1. Ops team will do check on the Signed Copy of all the above documents.
2. Once Post QC is cleared , will send the sanction request to bank team
3. At the same time will upload the DCU file (along with 12 columns ) in BR.Net

Bank

1. Bank will do underwrite the documents and Sanction will be done in BR.Net
2. Pre funding will be raised , based on sanction Documents.

Post Sanction, Ops team will generate the PSD Documents and share to branches. Branch team will take printout and disbursement happens.


Files

Actions #1

Updated by Chandramohan over 5 years ago

  • Assignee changed from Chandramohan to Payodhi

Dear Payodhi,

*This task is created for Technical approval request to the above mentioned project *

Actions #2

Updated by Payodhi over 5 years ago

  • Status changed from New to Approved
  • Assignee changed from Payodhi to Chandramohan

Dear Chandra,

Approved.Pls proceed.

Actions #3

Updated by Chandramohan over 5 years ago

  • Assignee changed from Chandramohan to Vijayakumar

Dear Vijayakumar,

Approved.Pls proceed.

Actions #4

Updated by Vijayakumar over 5 years ago

  • Status changed from Approved to In Progress
  • Assignee changed from Vijayakumar to Shiva_CIMS

Dear Siva,

  • This task is created for Development team **

Pls find the above description for updation required for DCB BC.

Actions #5

Updated by Shiva_CIMS over 5 years ago

  • Assignee changed from Shiva_CIMS to Karthik_CIMS

Dear Karthik,

This task is created for Testing unit **

Pls check the below UAT Apk test and confirm the working status.

5. Spouse name should be as per member Aadhaar only (wherever available), nominee (even if husband) details shall as per their KYC.

DCB SOURCING:
http://cimssoft.in/APKs/DCB-PROD/DCB-CB-CLOUD-4-27-9.apk

Actions #6

Updated by Karthik_CIMS over 5 years ago

  • Assignee changed from Karthik_CIMS to Shiva_CIMS

Dear sir,

Cross checked the UAT apk and confirmed everything is working fine.

Actions #7

Updated by Shiva_CIMS over 5 years ago

  • Assignee changed from Shiva_CIMS to Vijayakumar

Greetings,

We have completed the CB Integration for DCB BC and kindly check and confirm the UAT apk.

Pls note the updations in DCB portal,

1. Pre & Post QC MIS Report - Completed

2. Pre QC - We need “Remarks similar to RBL” in pre-qc stage for all images - Completed

• MKYC Front
• MKYC Back
• SKYC Front
• SKYC Back
• Photo

3. Post QC – to have 4 modules with Drop downs, only queries will reflect to branch - Completed

AOF - Member sign missing/ Member sign missing on photo/ Member sign not clear/Member photo missing/Scan copy not clear/Need full size scan copy/Witness sign missing/Father name mismatch/BM RTI Witness seal & sign missing

Form 60 - Member sign missing/ Member sign not clear/Scan copy not clear/Need full size scan copy/ Father name mismatch/BM sign missing/ BM RTI Witness seal & sign missing
Primary – Member sign missing /Member sign missing on photo / Member photo not pasted/ PSM sign missing/ Scan copy not clear/Need full size scan copy/Need Spouse proof/ BM RTI Witness seal & sign missing
Secondary – Member sign missing /Member sign missing on photo / Member photo not pasted/ PSM sign missing/ Scan copy not clear/Need full size scan copy/ Need Spouse proof/ BM RTI Witness seal & sign missing

4.Spouse name should be as per member Aadhaar only (wherever available), nominee (even if husband) details shall as per their KYC.- UAT Testing

DCB SOURCING:
http://cimssoft.in/APKs/DCB-PROD/DCB-CB-CLOUD-4-27-9.apk

Actions #8

Updated by Vijayakumar over 5 years ago

  • Assignee changed from Vijayakumar to Nagesh

Dear Nagesh,

  • This task created for Quality Level **

Find the above UAT apk and check and confirm the working status.

Actions #9

Updated by Nagesh over 5 years ago

  • Assignee changed from Nagesh to Vijayakumar

Dear sir,

Cross checked the UAT apk and confirmed everything is working fine.

Actions #10

Updated by Vijayakumar over 5 years ago

  • Assignee changed from Vijayakumar to Shiva_CIMS

Dear Shiva,

  • This task is created for production **

We have tested in UAT apk and its working fine.Kindly share the live apk.

Actions #11

Updated by Shiva_CIMS over 5 years ago

  • Assignee changed from Shiva_CIMS to Vijayakumar

Greetings,

On top of this update with Sourcing app was completed and released the updated APK versions.

4. Spouse name should be as per member Aadhaar only (wherever available), nominee (even if husband) details shall as per their KYC.

As discussed, this need to be updated from the RO end, since we have removed the validation to prepopulate the Spouse name as per the Nominee KYC, hence RO need to type the name correctly as per the customer KYC.

Kindly release the APK for MDM and NON MDM devices.

DCB SOURCING:
http://cimssoft.in/APKs/DCB-PROD/DCB-CB-CLOUD-4-27-9.apk

Actions #13

Updated by Vijayakumar over 5 years ago

  • Assignee changed from Vijayakumar to Chandramohan

Dear Chandramohan/Payodhi,

For your information,

Our new project was working fine confirmed with our respective OPS Head.

Actions #14

Updated by Vijayakumar over 5 years ago

Actions

Also available in: Atom PDF