Using Auto Elimination Rules Widget

Auto-Elimination Rules are implemented with an aim to reduce the amount of the alerts that need to be manually investigated by comparing an alert’s supplementary data items.

False positive alerts are a significant challenge to Compliance teams globally. Compliance teams have been trying for years to reduce the number of false positives. False positives are time-consuming to investigate and a drain on productivity and operational efficiency. The causes of such alerts may be due to inaccurate data, improper matching configuration, and other issues.

Auto-elimination of false positive alerts feature helps to reduce the amount of false positives during screening. This feature applies consistent auto-elimination rules that aim to reduce the number of alerts that need to be manually investigated by comparing an alert’s supplementary data items.

With this feature, it is possible to assess an alert and automatically close those alerts that fulfill criteria for the auto elimination as false positives.

Using the auto-elimination pre-set rules, you can use the Auto Elimination Rules widget to mark the events automatically as False Positive.

Note:

No custom Auto-Elimination rules can be created in the application.

User cannot reopen the auto-eliminated event.

Auto-elimination rules can be enabled or disabled anytime for specific case type.

All the Auto Elimination rules are applicable for both Real Time and Batch Screening.

The following table the auto-elimination rules and their priorities.

Note:

The higher the rule priority, the higher will be the priority of execution.

Table 7-4 Auto-Elimination Rules

Rule Priority Rule Name Description Applicable for Case Type Applicable for entity type
1 Difference in year of birth when there is a relationship to PEP as Mother or Father Where the Alert is against a Relative and Close Associate of a PEP, the relationship to the PEP is Mother/Father EDD Individual
2 Difference in year of birth when there is a relationship to PEP as Son or Daughter or Child Where the Alert is against a Relative and Close Associate of the PEP, the relationship to the PEP is Son/Daughter/Child EDD Individual
3 Difference in nationality Where the Nationality/Citizenship differs between customer and watchlist PEP and EDD Individual
4 Difference in country Where there are no matching Countries across any of the data available between customer and watchlist PEP and EDD Individual
5 Difference in gender Where the Gender differs between customer and watchlist PEP and EDD Individual
6 Difference in gender and country Where the Gender differs and there are no matching Countries across any of the date available in the customer and the Watchlist Profile SAN, PEP, and EDD Individual
7 Difference in year of birth Where the Year of Birth is greater than 2 years between customer and watchlist SAN, PEP, and EDD Individual
8 Difference in date of birth Where the Date of Birth differs between customer and watchlist SAN, PEP, and EDD Individual

Note:

If all the events are auto eliminated, the case will be auto eliminated.

If any of the event is not eliminated, the case status is updated as NEW.

Note:

If any one of the values (either source attribute or Target attribute) are null, the rule is not applicable.

Table 7-5 Auto Elimination Rules Mapping and Execution

Rules Priority Source Attribute Source Attribute Mapping from Data model Target Attribute Target Attribute Mapping from Watchlist data Decision
1 Date of Birth STG_PARTY_MASTER.D_DATE_OF_BIRTH Date of Birth
  1. FCC_WL_DJW_INTERIM1_RCA_PEP_RELATIONSHIP.V_PEP_RELATIONSHIP_TO_RCA
  2. fcc_wl_djw_interim1_date_types.V_YEAR
Where the Alert is against a Relative and Close Associate of a PEP, the relationship to the PEP is one of those listed below, and the YOB of the Customer is with in 10 years of the YOB of the related PEP, then the auto-elimination rule will apply
  • Mother
  • Father

Example: An Alert A1 is generated as an Relative or Close Associate(RCA) of the PEP, with relationship to PEP as 'Father'. If Year of Birth of related PEP(Father) is after the Year of Birth of the RCA then the alert is closed as Auto-eliminated.

2 Date of Birth STG_PARTY_MASTER.D_DATE_OF_BIRTH Date of Birth
  1. FCC_WL_DJW_INTERIM1_RCA_PEP_RELATIONSHIP.V_PEP_RELATIONSHIP_TO_RCA
  2. fcc_wl_djw_interim1_date_types.V_YEAR
Where the Alert is against a Relative and Close Associate of a PEP, the relationship to the PEP is one of those listed below, and the YOB of the Customer is with in 10 years of the YOB of the related PEP, then the auto-elimination rule will apply
  • Son
  • Daughter
  • Child

Example: An Alert A2 is generated as an Relative or Close Associate(RCA) of the PEP, with relationship to PEP as 'Son'. If Year of Birth of related PEP(Son) is within 10 years of the Year of Birth of the RCA (father)then the alert is closed as Auto-eliminated.

3 Nationality and Secondary Nationality
  1. STG_PARTY_MASTER.V_NATIONALITY_COUNTRY
  2. STG_PARTY_MASTER.V_SEC_CITZN_COUNTRY_CODE
 Citizenship V_CITIZENSHIP If the nationality and secondary nationality of the customer is different with citizenship from watchlist matches, then the event will be eliminated as a False Positive.
4 Country of Residence STG_PARTY_MASTER.V_ISO_COUNTRY_CD Country of Residence V_RESIDENCE If the country of residence, nationality, and secondary nationality of the customer is different with country of residence, citizenship from watchlist matches, then the event will be eliminated as a False Positive.
Nationality and Secondary Nationality
  1. STG_PARTY_MASTER.V_NATIONALITY_COUNTRY
  2. STG_PARTY_MASTER.V_SEC_CITZN_COUNTRY_CODE
 Citizenship V_CITIZENSHIP
5 Gender STG_PARTY_MASTER.V_GENDER Gender V_GENDER If the gender of customer is different with gender from watchlist matches, then the event will be eliminated as a False Positive.
6 Gender STG_PARTY_MASTER.V_GENDER Gender V_GENDER If the gender, nationality, and secondary nationality of the customer is different with corresponding gender, residence country, and citizenship from watchlist matches, then the event will be eliminated as a False Positive.
Country of Residence STG_PARTY_MASTER.V_ISO_COUNTRY_CD Country of Residence V_RESIDENCE
Nationality and Secondary Nationality
  1. STG_PARTY_MASTER.V_NATIONALITY_COUNTRY
  2. STG_PARTY_MASTER.V_SEC_CITZN_COUNTRY_CODE
 Citizenship V_CITIZENSHIP
7 Year of Birth STG_PARTY_MASTER.D_DATE_OF_BIRTH Year of Birth V_YOB If the year of birth of the customer is different with year of birth obtained from watchlist matches by 2 years, then the event will be eliminated as a False Positive.
8 Date of Birth STG_PARTY_MASTER.D_DATE_OF_BIRTH Date of Birth V_DATE_OF_BIRTHS

Note:

The watchlist data can contains multiple values for date of birth.
If the date of birth of the customer is different with date of birth obtained from watchlist matches by 2 years, then the event will be eliminated as a False Positive.