4.11.6 Match Persistence and Flag Keys

Customer Screening parses all customer records against all watch list records daily. This allows new alerts to be created due to changes in either the customer or the watch list data. When there is no change to the customer or the watch list record and the match is identical to a previously generated relationship, no new alerts are created.

Many attributes can change on a customer or watch list record but not all changes result in a new alert. These attributes are controlled based on the flag key value.

Note:

If a new alias name that matches the customer record is added to a watch list, then this results in a new alert.

An example of a flag key is date of birth. Some potential matches are eliminated because the value the customer has provided and the value in the watch list records are different. So, if the value changes, then any potential matches related to the date of birth must be re-reviewed. An example of a field that is not included in the flag key is account balance. This value changes frequently and does not impact the match decision. Flag keys are set in individual match processes, and a hash value is generated which is used for comparison.

Note:

The order of fields in the flag key is important. If the order changes, this will result in a new alert.