Compliance

Sanctions Screening for Vendors

Sanctions screening is the process of checking whether a vendor, its principals, or its parent entities appear on government-maintained sanctions lists — primarily OFAC (U.S. Treasury), EU Consolidated Sanctions, and UN Security Council lists. Engaging with a sanctioned entity can result in severe penalties including criminal prosecution, fines up to $20 million per violation, and reputational damage. Despite these consequences, many organizations omit sanctions screening from vendor due diligence, creating significant unmanaged legal and compliance risk.

Key sanctions lists for vendor screening

OFAC SDN List — The U.S. Treasury's Specially Designated Nationals list identifies individuals and entities owned or controlled by sanctioned countries, or acting on their behalf. U.S. persons (including organizations) are broadly prohibited from transactions with SDN-listed entities.

OFAC Sectoral Sanctions — Target specific sectors of sanctioned economies (e.g., Russian energy, financial services). More nuanced than SDN — specific transaction types are prohibited rather than all dealings.

EU Consolidated Sanctions List — The European Union's unified sanctions registry. Relevant for any organization with EU operations, EU customers, or EU data subjects.

UN Security Council Consolidated List — Maintained by the UN, these sanctions are implemented by member states. Covers terrorism financing, weapons proliferation, and specific country regimes.

Country-Specific Lists — UK (OFSI), Canada (OSFI), Australia (DFAT) each maintain their own sanctions programs that may apply depending on your jurisdictional exposure.

What sanctions screening reveals

Effective vendor sanctions screening goes beyond simple name matching. It should identify:

Direct matches — The vendor entity itself appears on a sanctions list. This is a critical finding requiring immediate action.

Ownership matches — The vendor's parent company, majority shareholders, or beneficial owners are sanctioned. Under the OFAC 50% Rule, an entity is considered sanctioned if one or more sanctioned persons own 50% or more of it, even if the entity itself is not listed.

Jurisdiction risk — The vendor is headquartered in or operates primarily within a comprehensively sanctioned country (currently: Cuba, Iran, North Korea, Syria, and the Crimea/Donetsk/Luhansk regions of Ukraine). Cross-border payment providers like Wise present elevated sanctions screening complexity due to multi-jurisdictional operations.

Near matches — Entities with similar names that require human review to confirm or dismiss. Fuzzy matching algorithms help identify these but create false positive management overhead.

Implementing vendor sanctions screening

Pre-engagement screening — Screen every new vendor before contract execution. This should be a gate — no contract proceeds without cleared sanctions screening.

Periodic rescreening — Sanctions lists are updated frequently (OFAC updates multiple times per month). Rescreen existing vendors at least quarterly, or when lists are updated.

Automated matching — Manual screening does not scale. Use automated tools that compare vendor names, aliases, addresses, and registration details against all relevant sanctions lists with fuzzy matching.

Documentation — Maintain records of all sanctions screening results, including negative results ("screened, no match found"). This documentation is essential for demonstrating compliance to regulators and auditors.

Escalation procedures — Define clear procedures for potential matches: who reviews, who approves, and what documentation is required. Never ignore a potential match.

Real sanctions screening walkthrough: Wise

ThirdProof's investigation of Wise demonstrates why automated sanctions screening with entity disambiguation matters. Wise (formerly TransferWise) is a global payment platform operating across 50+ countries with money transmission licenses in multiple jurisdictions. This cross-border profile creates elevated sanctions screening complexity.

ThirdProof assigned Wise a Tier 3 — Moderate Risk rating at 86% confidence. The sanctions screening itself returned Clear — No matches found against OFAC, EU, and UN lists. However, the investigation revealed significant regulatory enforcement history that a sanctions-only check would miss: multiple AML-related fines from the CFPB, multi-state US regulators, European regulators, and Abu Dhabi authorities, plus a CFPB action related to inaccurate fee advertising.

The recommended actions reflect how a compliance team should handle this profile: obtain documentation of remediation actions taken in response to the CFPB consent order, review the public enforcement record at consumerfinance.gov, and conduct manual sanctions screening for the specific legal entities (TransferWise Ltd / Wise Payments Ltd, incorporated in the UK). This walkthrough illustrates that sanctions screening is necessary but not sufficient — it must be paired with adverse media analysis and regulatory enforcement checks to catch the full risk picture.

False positives and entity disambiguation

False positives are the most operationally expensive problem in sanctions screening. Fuzzy name matching algorithms intentionally cast a wide net — comparing vendor names against sanctions lists using phonetic similarity, alternate spellings, transliterations, and partial matches. This catches evasion attempts but generates noise.

Consider a vendor named "Wise Payments Limited." A fuzzy match against the OFAC SDN list might flag entries like "Nest Wise Petroleum L.L.C" or entities containing "Like Wise" — neither of which is the payment platform. Without entity disambiguation, each match requires manual investigation: checking registration jurisdictions, corporate officers, addresses, and business activities against the sanctioned entity's profile.

ThirdProof automates this disambiguation by cross-referencing multiple data points: the vendor's verified domain, GLEIF legal entity identifier, corporate jurisdiction, and business category against each potential match. When the automated check finds that a flagged entity operates in a different country, different industry, and has no overlapping officers with the investigated vendor, it classifies the match as disambiguated — not a true positive.

For compliance documentation, record both the initial match and the disambiguation rationale. Your auditor and OFAC examiner want to see that potential matches were investigated, not ignored. A documented disambiguation is stronger evidence of compliance than no matches at all — it proves your screening process works.

Multi-regime screening requirements

Vendors operating internationally must be screened against multiple sanctions regimes — not just OFAC. Each regime has independent authority and different list coverage.

OFAC (United States) — The SDN list and sectoral sanctions programs. Applies to all U.S. persons, U.S.-incorporated entities, and any transaction touching the U.S. financial system (which includes most dollar-denominated transactions). Updated multiple times per month.

EU Consolidated Sanctions — Maintained by the European Commission. Applies to all EU persons, entities incorporated in the EU, and transactions conducted within EU territory. Particularly relevant for vendors with European operations or EU customers.

UK OFSI (Office of Financial Sanctions Implementation) — Separate from EU sanctions post-Brexit. UK maintains its own financial sanctions list. Relevant for any vendor operating in or through the UK — including Wise, which is incorporated in the UK.

UN Security Council Consolidated List — Binding on all UN member states. Covers terrorism financing, weapons proliferation, and country-specific regimes. While most UN sanctions are also implemented by OFAC and the EU, some designations differ.

For vendors like Wise that operate across 50+ countries, screening against a single list is insufficient. A vendor could be clear on OFAC's SDN list but flagged under EU or UK sanctions — or vice versa. ThirdProof's investigation checks the OpenSanctions database, which aggregates 40+ international sanctions and PEP lists into a single cross-reference, providing multi-regime coverage in a single query.

See this in action

ThirdProof automates vendor risk assessment across 24 intelligence sources. Investigate any vendor in under 2 minutes — no questionnaires, no vendor cooperation required.

Try ThirdProof Free →

No credit card required

Frequently asked questions

What happens if you do business with a sanctioned entity?+
Doing business with a sanctioned entity can result in civil penalties up to $356,579 per violation (OFAC, adjusted annually) or criminal penalties including fines up to $20 million and imprisonment up to 30 years for willful violations. Beyond legal penalties, sanctions violations damage reputation, trigger banking relationship reviews, and can result in loss of government contracts and export privileges.
How often should vendor sanctions screening be performed?+
Vendor sanctions screening should occur at three points: before contract execution (mandatory gate), at every contract renewal, and on a recurring basis (quarterly minimum). OFAC updates its SDN list multiple times per month, so real-time or weekly automated screening provides the strongest compliance posture. High-risk vendors in sensitive industries or jurisdictions warrant more frequent screening.
Do all companies need to screen vendors for sanctions?+
Yes. OFAC regulations apply to all U.S. persons, which includes all U.S. companies, U.S. citizens regardless of location, and any entity operating within the U.S. financial system. EU sanctions apply to EU persons and entities. Non-compliance is a strict liability offense — meaning penalties apply even if the violation was unintentional or unknowing. Sanctions screening is not optional for any organization doing business in or with the United States or European Union.
What is the OFAC 50% Rule?+
The OFAC 50% Rule provides that any entity owned 50% or more, directly or indirectly, by one or more sanctioned persons is itself considered sanctioned, even if the entity does not appear on the SDN list by name. This means vendor sanctions screening must extend beyond the vendor entity to its ownership structure. If a vendor's parent company is sanctioned, the vendor itself is effectively sanctioned under this rule.
What is entity disambiguation in sanctions screening?+
Entity disambiguation is the process of determining whether a fuzzy sanctions match refers to the actual vendor being investigated or a different entity with a similar name. It involves cross-referencing the vendor's jurisdiction, registration details, business activities, and corporate officers against the sanctioned entity's profile. For example, a payment platform named 'Wise' might match against 'Nest Wise Petroleum' — disambiguation confirms these are distinct entities. Document both the match and the disambiguation rationale for compliance records.
How does fuzzy name matching work in OFAC screening?+
OFAC fuzzy name matching uses algorithms that compare vendor names against the SDN list using phonetic similarity (Soundex, Metaphone), Levenshtein distance (character-level edits), token matching (reordered words), and transliteration variants. This catches sanctions evasion through name variations, alternate spellings, and transliterations from non-Latin scripts. The trade-off is false positives — common names or partial overlaps trigger matches that require human review or automated entity disambiguation to resolve.

Put this into practice

Investigate any vendor across 24 intelligence sources in under 2 minutes. Your first investigation is free.

Start Free Investigation →

No credit card required