Goodlisting
Salv remembers matches that have been closed as false positives and automatically goodlists them to avoid duplicate alerts, using an entity’s goodlist identifiers + matches for the goodlist record.
You can select which information will be used for goodlisting (up to three parameters). It can be, for example, customer name + account number (e.g. IBAN). This means that every time you close an alert that was triggered for a name (and features also the same account number) our system will automatically add this combination (customer name + account number) into your goodlist. This means - no duplicate alerts for this combination. It doesn't have to be name+account number, you can decide yourself based on the data you have.
⚙️ Please be aware that currently you cannot configure or modify Goodlisting settings yourself. If you need to set up or adjust your Goodlisting configuration, please contact our support team.
NB! A new alert will be generated for a goodlisted entity, if there's a new entry in the matching sanctions lists (read more about it below under Significant Update Indicators).
An in-depth example how goodlisting works:
You have a payment coming from Vladimir Tutin from account DE123456789 on 23rd of November 2022. You get sanction alert with Vladimir Turin (Dow Jones ID: 1438028) and you mark it as false positive. This will add it to goodlist (Vladimir Tutin + DE123456789 and Dow Jones ID: 1438028).
On 24th of November 2022 you have a payment from account DE123456789 and name Vladimir Tutin you will not get an alert because previous alert with Vladimir Turin (Dow Jones ID: 1438028) as it resolved by goodlist.
On 24th of November 2022 you have another payment from account DE987654321 and name Vladimir Tutin you will get an alert with Vladimir Turin (Dow Jones ID: 1438028), as this account number was not in goodlist yet.
On 25th of November 2022 Vladimir Putin (Dow Jones ID: 98141) is added to your selected sanction list.
On 26th of November 2022 you have another payment from account DE123456789 and name Vladimir Tutin you will now get an alert with Vladimir Putin (Dow Jones ID: 98141), but match with Vladimir Turin (Dow Jones ID: 1438028) is not raised as it is in goodlist.
If there are no matching entries in the goodlist, an alert with NEW status is created.
When there are matching entries in the goodlist, an alert with a FILTERED status is created. This alert includes a note under the Filtered matches section, indicating that the alert was filtered due to goodlisting. The note displays the goodlisting keys and the ID of the initial (source) alert. If you click this blue note, it will lead you to the source alert so you can check why this alert was goodlisted:
Setting up Transaction Goodlisting
Transaction Goodlisting setup is part of Screening Flows configuration. Learn more about it here.
Significant Update Indicators
Significant Update Indicators in Transaction screening work together with Goodlisting.
📥 Salv remembers matches that have been closed as false positives and automatically goodlists them to avoid duplicate alerts, using an entity’s goodlist identifiers + matches for the goodlist record.
However, these matches are removed from the goodlist under two conditions:
when the status of the associated alert changes
when there’s an update in the list record
Not all list record changes are significant enough to revoke goodlisting; for instance, correcting a typo in record’s source description.
Therefore, you can select which list record updates are significant enough to remove matches from the goodlist, by navigating to the Significant Update Indicators page under Screening configuration and clicking Edit:
If a field is ticked, its change is treated as Significant Update. Unticked fields, when updated, do not warrant a match to be removed from goodlist.
You can read more about what each Dow Jones field stands for here.