Sanctions screening sounds simple: compare a name with a list. The difficult work begins when the system finds a possible match.
A compliance team must decide whether the subject is genuinely the listed person or entity, whether ownership or control changes the answer, which restrictions apply and what action is required. That is why effective screening depends on workflow and judgement, not just a database search.
Quick answer: What is sanctions screening?
Sanctions screening is the process of checking people, businesses, counterparties and relevant transaction information against sanctions data that applies to an organisation. It is used during onboarding, ongoing customer review and, where relevant, before or during transactions.
The purpose is to identify a possible exposure early enough for the organisation to investigate and take the correct action. Screening does not make the final legal decision. It creates a signal for review.
- Checks names and relevant identifiers
- Uses applicable sanctions information
- Flags possible rather than confirmed matches
- Supports investigation and escalation
A sanctions alert is therefore not proof of wrongdoing or a breach. It means the available data is similar enough to require assessment.
Why sanctions screening matters
Sanctions can restrict dealings with designated people, entities, governments, sectors, vessels, aircraft or territories. The precise measures differ between regimes. They may include asset freezes, restrictions on financial services, trade controls or prohibitions on making funds or economic resources available.
The operational problem is that a restricted party may appear at several points in a relationship. It could be the customer, a beneficial owner, a director, an authorised person, a counterparty or a party named in payment information.
In addition, sanctioned parties are not always obvious from the customer’s trading name. Ownership and control rules may extend restrictions to an unlisted entity. This makes sanctions screening closely connected with KYB and beneficial ownership checks.
Organisations must determine which regimes and obligations apply to their activities. A global company may have exposure through its legal entities, employees, customers, currencies, payment routes, goods, services and operating locations.
Who and what may need to be screened?
There is no universal list that fits every organisation. The screening population should follow the applicable legal requirements and the organisation’s sanctions risk assessment.
- Customers: individuals and legal entities entering or maintaining a relationship.
- Beneficial owners and controllers: people or entities behind a business relationship.
- Directors and authorised persons: parties acting for or controlling a customer.
- Counterparties: senders, recipients, intermediaries and other parties to activity.
- Payment information: names, banks, addresses, free-text fields and relevant routing data.
- Other relevant subjects: vessels, aircraft, goods, locations or identifiers where the business model requires them.
Good screening begins with accurate data. A name alone may be insufficient. Date of birth, nationality, address, registration number, passport details, aliases and other identifiers can be essential when distinguishing a genuine match from an unrelated person.
How does the sanctions screening process work?
- Define the applicable scopeIdentify the regimes, lists, parties, products, services and transaction points relevant to the organisation.
- Prepare the dataStandardise names, scripts, dates, addresses, identifiers and ownership information before matching.
- Run the comparisonCompare the subject with current sanctions data using exact and appropriately calibrated similarity rules.
- Triage the alertPrioritise the match using identifier strength, list context, customer risk and the activity involved.
- Investigate the subjectCompare aliases, dates, locations, documents, ownership and other evidence to establish identity.
- Assess the restrictionsDetermine which programme applies and whether ownership, control, licences or exceptions affect the outcome.
- Decide and escalateFollow the organisation’s approved process for clearing, restricting, rejecting, blocking, freezing or escalating activity.
- Record and rescreenRetain the rationale and evidence, then rescreen when lists, customer details or relevant risks change.
The process should not end with “match” or “no match”. It should produce a decision that another reviewer can understand and reconstruct.
Exact and fuzzy matching solve different problems
An exact match looks for the same text. It is easy to understand, but it can miss differences caused by spacing, word order, spelling or transliteration.
Fuzzy matching looks for similarity. It can identify “Mohammed”, “Muhammad” and other variations that may refer to the same person. It can also account for reordered company names or minor typographical differences.
However, wider matching produces more alerts. A threshold that catches every remote similarity can overwhelm analysts. A threshold that is too narrow can miss relevant variants.
| Matching approach | Useful for | Operational limitation |
|---|---|---|
| Exact matching | Strong identifiers and identical names | Can miss spelling, script and formatting differences |
| Fuzzy matching | Name variations, aliases and transliteration | Can create high false-positive volumes |
| Identifier matching | Passports, registration numbers and dates | Source data may be missing, old or inconsistent |
| Contextual matching | Combining names with geography, ownership and other evidence | Requires reliable connected data and clear rules |
The right approach usually combines these methods. More importantly, teams should test performance against their customers, languages, markets and known outcomes.
A potential match is the start of an investigation
Imagine a payment alert involving “A. Rahman”. The name resembles a listed individual, but the payment record contains little else.
An analyst should not clear or confirm the case on name similarity alone. They may need to review the customer’s full legal name, date and place of birth, nationality, address, passport details, aliases and relationship to the payment.
For a business, the analysis may extend to registration information, trading names, directors, shareholders and indirect owners. The team may also need to consider the sanctions programme, the type of restriction and any licence or exception.
This is identity resolution in practice. The analyst is answering two separate questions:
- Is this the listed party? Compare identifiers and evidence.
- If it is, what does the applicable regime require? Interpret the relevant restrictions and process.
Combining those questions into one automated score can hide important judgement. They should remain visible in the review record.
Why ownership and control cannot be ignored
Screening only the names shown on a sanctions list can leave a serious gap. Some regimes extend restrictions to entities owned or controlled by designated parties, even when the entity is not named separately.
For example, the US Office of Foreign Assets Control states that an entity owned 50% or more in aggregate, directly or indirectly, by one or more blocked persons is itself considered blocked. The UK applies its own ownership and control tests, which include more than 50% of shares or voting rights, board appointment rights and certain forms of control.
These are examples, not a universal formula. Thresholds and legal tests differ. Teams should apply the rules of the regimes that affect their organisation and obtain specialist advice where the answer is unclear.
Operationally, this means sanctions screening should connect with reliable corporate and beneficial ownership data. A flat name search cannot reveal layered ownership, indirect holdings or changes in control. Graph Intelligence can help investigators see relationships, but the legal conclusion still belongs to the organisation.
When should sanctions screening happen?
Screening is not only an onboarding check. Sanctions lists, customer details, ownership structures and transactions can change after a relationship begins.
| Screening point | What the team is trying to establish |
|---|---|
| Before onboarding | Whether the prospective customer and relevant connected parties create sanctions exposure. |
| Before activation or approval | Whether any unresolved result should prevent the relationship or service from starting. |
| During relevant transactions | Whether payment or trade parties, locations and other information require intervention. |
| After list updates | Whether an existing customer or connected party is affected by newly published information. |
| After customer changes | Whether new names, owners, directors, addresses or counterparties alter the assessment. |
| During customer review | Whether the relationship remains consistent with current information and applicable controls. |
The frequency and timing should reflect risk, legal obligations and how quickly the organisation needs to act. WIDTH’s guidance on KYC and KYC versus KYB explains how screening fits within the wider customer review process.
Sanctions, PEP, adverse media and transaction monitoring are different controls
| Control | Main question | Typical outcome |
|---|---|---|
| Sanctions screening | Is this party or activity exposed to applicable sanctions restrictions? | Clear, investigate, restrict or escalate according to the applicable regime. |
| PEP screening | Does the person hold, or have they held, a prominent public function? | Risk assessment and proportionate due diligence; a PEP result is not proof of wrongdoing. |
| Adverse media screening | Is there credible reporting relevant to the customer’s risk? | Source and subject assessment, followed by proportionate review. |
| Transaction monitoring | Does the activity show unusual behaviour or relevant risk patterns? | Alert investigation, escalation or additional due diligence. |
These controls can inform one another. For example, a sanctions alert may require transaction review, while unusual activity may reveal a previously unseen counterparty. See our practical guide to transaction monitoring.
Why sanctions screening creates false positives
False positives are not simply a software nuisance. They consume analyst time, delay customers and can hide genuinely important alerts inside a large queue.
- Common names produce many unrelated matches.
- Aliases and transliterations create multiple name variations.
- Customer records contain missing or inconsistent identifiers.
- Broad thresholds are applied without considering context.
- Duplicate customer or list records create repeated alerts.
- Low-quality aliases are treated like strong identifiers.
- Analysts cannot reuse reliable findings from earlier reviews.
- Closure reasons are too vague to support later tuning.
The answer is not to lower sensitivity until the queue becomes comfortable. Teams should improve data, matching, prioritisation and review while testing whether meaningful coverage is being preserved.
What makes sanctions screening effective and defensible?
A defensible programme connects the organisation’s risk assessment with its everyday screening controls.
- Document which regimes, lists and restrictions apply
- Define who and what enters the screening population
- Use reliable names, aliases and supporting identifiers
- Update sanctions data promptly and consistently
- Calibrate matching for languages, scripts and customer risk
- Separate potential matches from confirmed decisions
- Investigate ownership and control where relevant
- Set clear escalation, approval and reporting responsibilities
- Test list updates, matching behaviour and workflow routing
- Retain evidence, rationale, configuration and change history
OFAC’s compliance framework emphasises risk assessment, internal controls, testing, auditing and training. It also identifies outdated lists, missing identifiers, alternative spellings and incomplete ownership due diligence as recurring causes of sanctions-control failures.
What should teams look for in sanctions screening software?
Do not begin with the size of a vendor’s database. Begin with the decision your compliance team must make.
| Evaluation area | Question to ask |
|---|---|
| Coverage | Can the system support the sanctions sources and screening subjects relevant to the organisation? |
| Data preparation | Can it handle aliases, scripts, transliteration, reordered names and incomplete fields appropriately? |
| Matching | Can authorised teams understand and calibrate matching without turning it into a black box? |
| Context | Can analysts see customer, ownership, counterparty and earlier review information with the alert? |
| Workflow | Can alerts be assigned, investigated, escalated, approved and linked to a controlled case? |
| Rescreening | Can the organisation respond when sanctions data or customer information changes? |
| Governance | Can teams reconstruct the data, configuration, evidence and rationale behind a historical decision? |
| Testing | Can the organisation test updates and measure both alert quality and coverage? |
The platform should support the operating model. It should not replace the organisation’s sanctions risk assessment, legal interpretation or accountability.
How WIDTH supports connected sanctions screening workflows
WIDTH supports sanctions screening within customer onboarding and ongoing compliance workflows. Screening results can be connected with customer records, risk reviews and investigations.
This allows analysts to review a possible match with more of the context they need. Relevant customer information, connected parties, ownership details, earlier decisions and supporting evidence can remain part of one controlled process.
Where a result needs deeper review, it can move into case management with clear ownership, actions, rationale and approval history. Screening can also work alongside transaction monitoring and wider AML monitoring rather than operating as an isolated check.
WIDTH does not guarantee sanctions compliance or make the organisation’s legal decisions. It helps compliance teams connect the data, workflow and evidence needed to make those decisions with greater control.
Good sanctions screening connects the match to the decision
The weakest screening programmes focus on the alert. Stronger programmes focus on what happens next.
A name similarity must be investigated. An ownership link must be understood. The relevant restrictions must be interpreted. The final action must be approved, recorded and available for later review.
When those steps remain connected, sanctions screening becomes more than a list check. It becomes an accountable compliance workflow that helps the organisation identify exposure, respond consistently and explain its decisions.
See the OFAC Framework for Compliance Commitments, OFAC guidance on entities owned by blocked persons, UK financial sanctions guidance, the UN Security Council Consolidated List and the European Commission’s sanctions due-diligence guidance. Requirements differ by regime, jurisdiction and activity.
Frequently asked questions about sanctions screening
Sanctions screening compares people, businesses, counterparties and relevant transaction data against applicable sanctions information. Potential matches then require investigation using identifiers, ownership information and the rules that apply to the organisation.
The scope depends on the organisation, its exposure and applicable requirements. It may include customers, beneficial owners, directors, authorised persons, counterparties, payment parties, vessels, aircraft and other relevant parties or assets.
No. An alert shows that data matched defined screening criteria. It may be a false positive or require further investigation. Teams should establish whether the subject is the listed party and what restrictions apply before deciding.
Sanctions screening compares parties, locations or transaction information with sanctions data. Transaction monitoring examines activity and behavioural patterns. Both controls can inform the same investigation, but they answer different questions.
False positives often arise from common names, aliases, transliteration, incomplete records and broad matching thresholds. Better identifiers, calibrated matching and structured review can reduce avoidable alerts.
Fuzzy matching identifies similar rather than identical text. It can detect spelling changes, reordered names and transliteration differences, but it must be calibrated because broader matching can increase false positives.
Rescreening should reflect applicable requirements and risk. Common triggers include sanctions-list updates, changes to customer or ownership information, relevant risk events and scheduled reviews.
Ownership and control can extend restrictions beyond names shown on a list. Organisations should identify relevant owners and controllers, then apply the legal tests of the sanctions regimes that affect them.
Systems can automate data preparation, list updates, matching, alert routing and rescreening. Human judgement remains important for identity resolution, ownership analysis, legal interpretation, escalation and final decisions.
It should retain the data screened, lists and configurations used, possible match, evidence reviewed, analyst rationale, decision, approvals, timestamps and any resulting action.
Connect sanctions screening with the full customer risk workflow
Bring onboarding data, screening results, ownership context, investigations and decision records into one controlled operating environment.