KYCOB Case Management: Re-Evaluate KYC Risk Score Functionality (Doc ID 2906682.1)

Last updated on NOVEMBER 07, 2022

Applies to:

Symptoms

Qn1:On : 8.0.7 version, Web UI

KYCOB Case Management: Re-Evaluate KYC Risk Score Functionality

When trying to work on a KYCOB case via ECM, the actions taken against the name screening matches is not getting considered in the overall re-calculation via the Re-Evaluate KYC Risk Score functionality. See attached PDF for details.

Steps to Reproduce Problem

1. Create KYC On-Boarding request payload with 1 Primary Applicant and 1 related customer. Ensure that both customers will have matches for name screening.
2. Ensure that their algorithm-based scores are both low, and no rule-based is triggered. Both of which would undergo FULL KYC.
3. Call the KC InitiateOnboarding web services API passing the JSON request payload created above.
4. By virtue of name screening hits, a case should be created for this request, with a KYC Risk Score of 100.
5. Go to ECM and open the case. Ensure that the above conditions from step 1 are observed.
6. Adjudicate the name screening hits per below:
7. Make all hits for Primary as False Positive then all hits for the related customer as True Positive.
8. Press the Re-evaluate KYC Risk Score
9. At this point, the new KYC Risk Score is populated and the score should stay at 100 because the Primary applicant is associated with a high-risk related customer.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.