Sanction Screening Guide
Sanction Screening Guide
How to Set up an
Effective Sanctions
Screening Process
Table of Contents
Handling Matches 11
An Intro to Sanctions Compliance
Sanctions screening is a control designed to disrupt financial crime and sanctions risk
through comparing data sourced from an organization's operations, including customer
or other business partners and transactional records, against global sanctions lists
containing names and other indicators of sanctioned parties or locations to detect
similarities to determine whether a possible match exists.
Organizations will typically utilize two main screening controls to achieve their risk
reduction objectives:
The nature of Sanctions also adds to the complexity. Unlike economic embargoes,
which prohibit all activity and transactions involving a specific country, list-based or
smart sanctions target particular persons, entities, and organizations rather than a
specific regime or country. Secondary sanctions target third-party actors doing business
with specific regimes, organizations, persons, or entities. (A good example of secondary
sanctions includes many Ukraine-related programs, which target Russia’s financial and
energy sectors specifically). This means that customers who are not on a sanctions list
but have a relationship with a sanctioned entity could present a potential risk for the
organization in question.
There is a push particularly in Western nations to consider sanctions for a wider range
of concerns, including human rights violations and cyber-attacks;
● Sanctions evasion techniques such as the use of Virtual Assets are becoming
more sophisticated;
● Many legacy screening platforms are still in use, which is both cumbersome
and prone to large amounts of false positives.
For more information on Sanctions Compliance please refer to the following resources:
Non-compliance can be very costly, in the United States alone, OFAC’s enforcement
penalties hit a high of $1.2 billion in 2019.
Bear in mind that fines are not only levied for sanctions violations but also if the
Organization fails to implement adequate controls. In addition to fines and penalties, the
reputational damage is an additional risk to consider.
Setting up your Screening Process
Often the lack of data quality, integrity, or completeness is the reason sanction
screening systems fail or suffer from poor performance. Companies need to compile
and clean their KYC (Know Your Customer) information to avoid producing a large
number of false positives and to avoid the possibility of failing to detect sanctioned
entities during the screening process.
Data sources may be distributed across IT systems and must be mapped and identified
to obtain a more holistic view of the customer base. If possible, all data sources should
be linked and integrated and be subject to the same quality standards by extracting,
enriching, and loading the information to a single platform.
Entities Individuals
Name of the organization as registered Full Name (First, Middle, Last name)
Passport IDs
Defining the relevant Sanctions Lists for your Business
Businesses need to consider the relevant sanctioning bodies active in the countries they
operate in, the territories in which they and their partnerships and alliances trade, and
the currencies they are operating in.
Examples for some of the most relevant Sanctions lists for businesses operating in the
US and Europe:
● The HM Treasury Sanctions List applies to all individuals and legal entities
within or who undertake activities within the United Kingdom, as well as all
UK nationals and legal entities established under UK law. It’s enforced and
overseen by OFSI (the Office for Financial Sanctions Implementation).
● The OFAC Sanctions List applies to all US citizens and corporate entities
constituted in the US, as well as any entity that either trades in US dollars, US
goods, or US components or that has a US parent or affiliate. Its regulatory
body is the US Office of Foreign Assets Control (OFAC).
Before starting with the integration of any screening solution, it is very important to
understand how the search and name matching technology, including any match
scoring models work. Understanding the mechanics and limitations is very important for
a successful and reliable screening process that limits false positives - but even more
importantly, prevents false negatives.
The following examples are real world matching challenges. sanctions.io’s name
matching technology solves these challenges by blending machine learning with
traditional name matching techniques, such as name lists, common keys, and rules, to
determine an overall matching score.
Another very important factor for your Screening setup is the matching technology
utilized by your screening solution. The recommendations below are based on
sanctions.io’s advanced matching technology.
For Individuals, a good approach for example is to start with the Full Name and the Date
of Birth (DOB) or Year of Birth (YOB for a ‘wider’ approach) in your search request.
Usually, these two data points are sufficient and lead to good results with our smart
matching technology. Including additional data points like Country of Birth, Passport IDs
and/or Addresses in your search request can help reduce further the number of false
positives.
A recommendable approach for Entity screening is to use the Name of the Organization
along with the Country field. This will usually lead to good results and with a good name
matching algorithm you don't need to strip the organization's name of legal forms like
LLC, INC etc. (A challenge many screening solutons still struggle with).
Our database also contains vessel/aircraft names and IDs as well as Crypto Wallet
Addresses which can be searched for in the respective fields.
The above discussed screening setups should be a good starting point for most
organizations. The performance of this screening setup should continuously analyzed
and fine-tuned over time.
Transaction screening should be performed in such a way that the transaction may be
stopped before a violation occurs.
For managing potential matches we recommend using either a ticketing system (such
as Zendesk etc.) or, for a simpler workflow, recording all matches in an Excel or Google
sheet with an email notification to the respective compliance team/manager.
This whole workflow can also be set up without any coding involved, using no-/ or
low-code tools like Zapier or Integromat.
For a very simple workflow example using only low/no-code tools see our blog post on
How to integrate our API with any CRM system.
Handling Matches
It’s important to note that an alert that is generated during screening, indicating a match
between a customer or business partner and a record on a sanctions list, is not
necessarily an indication of a sanctions risk. It needs to be verified, confirmed, or
discounted using additional information to determine whether the match is true or a
false positive.
Manually review all of the client identity information you hold against the information
within the sanctions list. You may also wish to approach your client for additional
information.
If the individual or entity matches all of the information on the list, it is likely a positive
match and needs to be reported to your internal compliance team and/or you need to
file a Suspicious Activity Report (SAR). All transactions with this client or business
partner should be suspended.
If you are confident that the match is a false positive, you may wish to whitelist the
client’s name within your systems to avoid future matches.
For more information please refer to the FinCen Guide on filing SARs.