10.2.2.3 Filtering Watch List Data
The following sections provide information on how to enable and configure the watch list filters.
Enabling Watch List Filtering
Watch list data is filtered either during List Management, Screening, or both.
To enable filtering for a specific watch list, set the Prepare Filtering
phase(s) in the appropriate run profile to Y, and the
Prepare Without Filtering phase(s) to N.
Configuring Watch List Filtering
Note:
After data is filtered out, it is not possible to filter it back in. For example, if all entities are filtered out in the Watchlist Management project, even if the Transaction_Screening project is configured to include entities, they will not appear in the results data.Figure 10-8 Reference Data Editor - Filter - Settings Window

Note:
In the Filter - Settings reference data, a value of Y indicates that all records must be included - in other words, no filter must be applied.Broadly speaking, watch list filtering falls into four categories:
- By list and list subkey.
- By list record origin characteristics.
- By list profile record characteristics.
- By linked profiles.
Primary and Secondary Filtering, and Linked Records
- Primary filtering - These filters are used to return all profiles that match the criteria specified.
- Linked Profiles - If this value is set to Y, then all profiles linked to those captured by Primary filters are also captured. An example is a filter configured to capture all Sanctions and their related PEPs.
- Secondary filtering - These filters are applied to further filter any linked
profiles that are returned.
Note:
Only the World-Check and DJW watch lists can provide Linked Profiles.
Setting Multiple Values for Primary and Secondary Filters
The following filter options require further configuration in additional reference data:
- Origins
- Origin Regions
- Origin Statuses
- Primary and Secondary Name Qualities
- Primary and Secondary Name Types
- Primary and Secondary PEP Classifications
Note:
When you set the Filter - Settings reference data to N, only the records that match the values set in the corresponding reference data are included. For example, if you set the value of All name qualities to N in Filter - Settings, then you can determine which name qualities must be included for each watch list in the Filter - Primary Name Qualities reference data. For instance, if you include a row for high-quality names in the EU watch list, but you do not include rows for medium-quality and low-quality names for this watch list, then only records with high-quality names are included in the watch list.Some of these reference data sets are pre-populated with rows, to be edited or removed as required. These rows contain data (generally, but not always) supplied by each watch list provider and are all contained within the Watchlist Management project.
For example, to view all possible keywords for World-Check data, open the WC Keyword reference data in the Watchlist Management project. See the following example for further details.
Filtering World-Check Data
This example describes configuring filtering on the World-Check Sanctions list in the Watchlist Management project and setting further filters in the Transaction_Screening project. You can also perform the following actions:
- Enable filtering in the Run Profiles
- Configure the Primary filters in the Watch List Management project to return only active records for sanctioned individuals (not entities) originating from the EU list
- Enable the filtering of Linked Profiles in the Watch List Management project
- Configure the Secondary filters in the Transaction Filtering project to further filter out all Linked Profiles of deceased individuals.
Setting Filtering options in the Run Profiles
In the watchlist-management.properties Run Profile, set the
World-Check filtering phases as follows:
phase.WC\ -\ Prepare\ without\ filtering.enabled = N
phase.WC\ -\ Prepare\ with\ filtering\ (Part\ 1).enabled = Y
phase.WC\ -\ Prepare\ with\ filtering\ (Part\ 2).enabled = Y
In the watchlist-screening.properties Run Profile, set the World-Check filtering phases as follows:
phase.WC\ -\ Load\ without\ filtering.enabled = N
phase.WC\ -\ Load\ with\ filtering\ (Part\ 1).enabled = Y
phase.WC\ -\ Load\ with\ filtering\ (Part\ 2).enabled = Y
Setting Primary Filters and Linked Profiles in the Watchlist Management Project
To set the primary filters, follow these steps:
- In the
Directormenu, open theWatchlist Managementproject and expand theReference Datanode. - Locate the
Filter - Settingsreference data and double-click to open it. - Ensure the List/sub-list value in the WC-SAN row is set to Y.
- Set the
Entitiesvalue in the WC-SAN row to N. - Set the
Inactivevalue in the WC-SAN row to N. - Set the
All Originsvalue in the WC-SAN row to N. - Ensure all other values in the
WC-SANrow are set to Y. - Click OK to close the reference data and save changes.
- Locate the
Filter - Originsreference data and double-click to open it. - Add a new row with the following values:
- List Key - WC
- List Sub Key - WC-SAN
- Origin - EU
- Change the
Linked Profilesvalue in theWC-SANrow to Y. - Click OK to close the
Filter Settingsreference data and save changes.
Setting Secondary Filters in the Transaction_Screening Project
To set secondary filters, follow these steps:
- Open the
Transaction_Screeningproject, and expand the reference data link. - Locate the
Filter - Settingsreference data file, and double-click to open it. - Set the
Deceasedvalue in theWC-SANrow to N. - Click OK to close the reference data and save changes.
Screening All Data Using Sanctions Rules
By default, watch list records are routed to the different screening processes
depending on their record type, that is,
SAN,PEP,or EDD. This allows
different rules, and hence different levels of rigor, to be applied to the list data
according to risk appetite.
However, if you want to use the same screening logic for all list records, and do not
want the overhead of maintaining separate rule sets, the system can be configured to
reroute all list records to the SAN screening processes. To do this, set the
phase.*.process.*.Screen\ all\ as\ SAN value in the
watchlist-screening.properties Run Profile to Y.