Grid iList rules
You can attach a custom rule profile to each iList. The iList rule profile allows you to define specific matching rules tailored to your needs. It includes two types of rules: iList match content rules and Grid match content rules.
To create a iList rule profile that meets your specific needs, contact our Client Service team at ma_kyc_support@moodys.com.
iList match content rules
The following table shows the filter expression, description, and example for each iList match content rule. These rules apply exclusively to matching inquires with entries in the iList.
Filter expression | Description | Example |
|---|---|---|
MATCH_SCORE | Requires the inquiry's match score against the iList entry to be within a specified match score. | If the iList entry and the inquiry produce a match score above 85, there will be a match. |
COUNTRY_NO_MATCH | Typically, when used with a negation operator, such as | If the iList entry's country is the United States and the inquiry's country is Spain, there will be no match. |
EXACT_NAME_MATCH | Requires an inquiry's name to match exactly against the iList entries. | If the iList entry's name is John Smith, the inquiry's name must also be John Smith to match. |
ILIST_COUNTRY_CITY *Only for Country iList | Requires an inquiry's city to match the iList entry’s city. | If the iList entry's city is Los Angeles, the inquiry's city must also be Los Angeles to match. |
DOB | Requires the iList entry's date of birth (DOB) to be within a specified timeframe of the inquiry's date of birth. | If the iList entry's date of birth is 1/1/1980, the inquiry's date of birth must be within 3 years to match. |
ILIST_COUNTRY_POSTAL_CODE *Only for Country iList | Requires the inquiry’s postal codes to match the iList entry’s postal codes. | If the iList entry's postal code is 12345, the inquiry's postal code must also be 12345 to match. |
ILIST_COUNTRY_PROVINCE *Only for Country iList | Requires the inquiry’s provinces to match any of the iList entry’s provinces. | If the iList entry's providence is New York, the inquiry's providence must also be New York to match. |
Note
These examples don't consider filter settings. Matches and search results may vary depending on your CVIP and filter settings.
Grid match content rules
The following table shows the filter expression, description, and example for each Grid match content rule. These rules apply exclusively to matching inquiries with entities within Grid.
Filter expression | Description | Example |
|---|---|---|
ACTIVATION_DATE | Matches based on the entity activation date. | If the Grid entity’s activation date is after 2006, there will be a match. |
ALIAS_SCORE | Matches based on the alias score of the Grid entity. | If the Grid entity’s alias score is less than 50, there will be a match. |
COUNTRY_NO_MATCH | Typically, when used with a negation operator, such as | If the Grid entity's country is the United States and the iList entry’s country is Spain. there will be no match. |
CVIP | Matches based on a specified CVIP code. | If the Grid entity is categorized as Valuable, there will be a match. |
DOB | Requires the Grid entity's date of birth (DOB) to be within a specified timeframe of the inquiry's date of birth. | If the Grid entity’s date of birth is 1/1/1980, the inquiry's date of birth must be within 3 years to match. |
ENTITY_DATE | Matches based on the entity date, which is the most recent event date for all events associated with the entity. | If the Grid entity’s entity date is within 3 years, there will be a match. |
EVENT | Matches based on specified event categories and sub-categories. | If the Grid entity has a Murder (MUR) event, there will be a match. |
GEO_DISTANCE | Matches based on the specified distance between the inquiry's address and the closest address of the matched entity. | If the address of the Grid entity is within 50 miles of the address of the inquiry, there will be a match. |
INQUIRY_LAST_NAME | Checks whether the last name of the inquiry appears on a specified, pre-configured list. | If the last name of the inquiry appears on the Fortune500 name list, there will be a match. |
INQUIRY_NAME_ONLY | Matches based on whether the inquiry was a "name only" inquiry. Meaning, it did not specify an address (any address field) or a date of birth. | If the inquiry is "name only", there will not be a match. |
ITEM_SOURCE_KEY | Considers the source (monitored list and/or media) for each matched entity/event. | If the Grid entity comes from an OFAC list, there will be a match. |
MATCH_SCORE | Requires the inquiry's match score against the Grid entity to be within a specified match score. | If the Grid entity and the inquiry produce a match score above 85, there will be a match. |
NAME_LIST | Matches based on whether the Grid entity is on the name list file. | If the Grid entity is on the Fortune500 list, there will be a match. |
PEP_LEVEL | Considers the PEP level for entities with a PEP event. | If the Grid entity is a level 1 PEP, there will be a match. |
PEP_RATING | Considers the PEP rating for entities with a PEP event. | If the Grid entity has a PEP rating of C, there will be a match. |
PEP_TYPE | Considers the PEP type for entities with a PEP event. | If the Grid entity is a HOS, there will be a match. |
RISK_SCORE | Considers the risk score for the entity match. | If the Grid entity has a risk score greater than 75, there will be a match. |
SEARCH_TYPE | Considers whether the entity match resulted from onboarding/initial screening, or from portfolio monitoring. | If the Grid entity is a result of portfolio monitoring, there will be a match. |
Note
These examples don't consider filter settings. Matches and search results may vary depending on your CVIP and filter settings.