Using the Evaluator Rule Widget

The Evaluator Rule widget enables you to configure rules to create cases for each customer type.

Use the following criteria:
  • Risk Assessment Score is more than or equal to the configured Threshold score (Mandatory Configuration)

    Note:

    For any FIC_MIS_DATE, the F_KYC_REVIEW_TRIGGER_FLAG value in the stg_party_account_role_map table is provided as "N" then a case will not be created even when the threshold is exceeded. However, this condition does not apply to the case creation options below.

    In order for cases to be created using the Evaluator Configurations, update the F_KYC_REVIEW_TRIGGER_FLAG value in the stg_party_account_role_map table to "Y" for the consecutive days.

  • There is a change in the current vs last risk category for the customer.
  • There is a change in the current vs last risk score for the customer and difference is more than or equal to the configured risk tolerance score.
To create an evaluator rule, follow these steps:
  1. In the Pipeline Designer page, select the pipeline you want to edit. The Pipeline Designer window appears.
  2. Hover over the Evaluator Rule widget and click Edit Edit icon . The Evaluator window displays.
  3. Select a Customer Type. The criteria for case creation displays.
  4. Click Edit to update the scores as described in the following table.

    Table 11-8 Evaluator Rule Configuration

    Field Name Description
    Risk Assessment Score >=* This is a mandatory field.

    Update the threshold risk score for case creation in the Risk Assessment Score >= * field.

    If the Risk assessment score of the customer is equal or above the score in this field then the customer is marked for case creation.
    Create Case (if change in current vs last risk category) This is an optional field.

    Update the Create Case (if change in current vs last risk category) field accordingly with the available options on when to mark for the case creation.

    Available options are:

    • Any change in risk category
    • Current risk category is high
    • Current risk category is low
    • Not Applicable (default option)
    Create Case (if change in current vs last risk score) This is an optional field.

    Update the Create Case (if change in current vs last risk score) field accordingly with the available options on when to mark for the case creation.

    Available options are:

    • Any change in risk score
    • Current risk score is high
    • Current risk score is low
    • Not Applicable (default option)
    Risk Tolerance Score >= * This is a conditional mandatory field.

    The input box is only enabled when the value in the Create Case (if change in current vs. last risk score) drop-down list is NOT Not Applicable.

    If the value in the Create Case (if change in current vs. last risk score) drop-down list is other than Not Applicable, the current and previous risk scores are compared and if the difference between both the scores is greater than or equal to the configured Risk Tolerance Score, case creation occurs for that customer risk assessment.

    NOTE: Risk Score difference is computed as an Absolute value (or modulus).

    Example of a Case Creation when Risk Tolerance Score is Breached:

    • KYC Batch Case creation logic using Risk Tolerance for Customer Type “Individual” is configured as:
      • Create Case (if Change in current vs last risk score)
        • Current Risk Score is High
      • Risk Tolerance Score >= 25
    • Risk Category band for Customer Type “Individual” is configured as:
      • 0 to 40 (Low risk)
      • 41 to 80 (Medium Risk)
      • 81 to 100 (High Risk)
    • Consider Risk Assessment for an Individual "Customer A" as:
    • Customer A is risk assessed 1 year back. Risk Assessment score was 45 and risk category was "Medium risk”.
      • Customer A is risk assessed today because of Periodic Review or Accelerated Re-review or New Account Review. Risk Assessment score is 75 and hence, risk category is still "Medium risk”.
      • However, Risk Score difference between the 2 risk assessments = 30. (Note: Risk Score difference is computed as an Absolute value (or modulus), i.e., |75 – 45|)

        Even though customer's risk category has not changed, change in risk score is greater than the configured risk tolerance score (i.e., 30 >= 25). Hence, A new KYC Batch Case will be created with appropriate reason

    Note:

    Options for Case creation are displayed in the order of precedence.
  5. Click Save Save icon to save the values.
    To return to the Pipeline Designer window, click Close Close iconto close the window. Finally, click Save Save iconto save the updates made.