1.6 Manage Pipelines

This section details how to manage the CS pipelines.

Pre-configured, ready-to-use pipelines are available for batch and real-time screening for individuals and entities. Whereas 314A and external entity screening can be performed with batch screening. Data matches use Sanction, PEP, EDD, and PRB lists for individual, entity, and external entity screening, while 314A Screening uses FinCEN data matched against customer or external entity data. These out-of-the-box pipelines cannot be configured directly; they must first be copied, after which match attributes, rules, thresholds, and weightages can be modified.

Matching configuration is set using the Matching Rules widget. Each widget defines a match configuration for a source (customer) and target (watch list). The source and target can be filtered. This is how we set the different matching configurations for entities and individuals. It can also be used for setting different configurations for jurisdictions and domains.

Each ruleset can contain multiple rules and the score given to an alert is the maximum of the individual rule scores. An alert is generated only if the score is above the ruleset threshold. Within a rule configuration, source and target attributes are defined along with the match type (exact match, fuzzy match, or date match) and scoring method (Reverse Jaro Winkler, Jaro Winkler, Levenshtein). Each attribute level match has a threshold, below which the score is not considered, and a weightage. If the Must condition is set, then a match will not be created unless the score for that attribute is above the threshold.

To match the customer records with watch list data, run the IndividualScreening batch for an individual or Entity Screening batch for an entity in the Scheduler Service.