Early accessNow onboarding design partners.Request access
AutoCompliance
← All articles

20 November 2026

Sanctions lists explained: UN, OFAC, EU, UK and India

A practical guide to the main official sanctions lists, who publishes them, who needs to screen against them and what makes each one different.

If your business onboards customers or moves money, you are almost certainly expected to screen people against sanctions lists. Which lists apply depends on where you are licensed, which currencies you touch and who your counterparties are. This guide covers the five lists most regulated fintechs start with.

UN Security Council Consolidated List

The United Nations Security Council maintains a consolidated list of all individuals and entities subject to sanctions measures imposed by its sanctions committees, such as the ISIL (Da’esh) and Al-Qaida regime.

Why it matters: UN member states are obliged to implement Security Council sanctions, so the UN list is the common baseline. Many national regimes, including the EU and India, transpose UN designations into their own law.

Practical notes: entries often include several aliases of different quality, partial dates of birth and nationalities. Name quality varies widely, which makes fuzzy matching essential.

OFAC SDN List (United States)

The Office of Foreign Assets Control of the US Treasury publishes the Specially Designated Nationals and Blocked Persons List (SDN). US persons are generally prohibited from dealing with listed parties, and their assets are blocked.

Why it matters outside the US: any transaction in US dollars, or involving US banks, correspondents or technology, can bring OFAC into scope. Most payment providers screen against the SDN list regardless of where they are licensed.

Practical notes: OFAC also applies the “50 percent rule” to entities owned by blocked persons, even if those entities are not listed themselves. Name screening is the first line, not the whole picture.

EU Consolidated Financial Sanctions List

The European Commission maintains the consolidated list of persons, groups and entities subject to EU financial sanctions, also published as the Financial Sanctions Files (FSF).

Who needs it: any company incorporated in the EU, and any business carried out in the EU. EU sanctions regulations apply directly, without national transposition.

Practical notes: the EU list includes many transliterations for each person, for example several Latin spellings of Arabic or Cyrillic names. That helps recall but also increases the number of near-duplicates you have to deduplicate.

UK financial sanctions

Since Brexit, the United Kingdom runs its own autonomous sanctions regimes. Designations are published by the UK government, and HM Treasury’s Office of Financial Sanctions Implementation (OFSI) enforces financial sanctions.

Who needs it: UK firms, UK nationals anywhere in the world, and business conducted in the UK, including transactions that pass through UK-based banks.

Practical notes: UK and EU designations overlap but are not identical. Screening against only one of them leaves gaps.

India: MHA designated individuals and UAPA

In India, the Ministry of Home Affairs publishes individuals designated as terrorists under the Unlawful Activities (Prevention) Act, 1967 (UAPA). UN Security Council designations are implemented through orders under the same Act.

Who needs it: regulated entities such as banks and NBFCs. RBI’s KYC directions expect them to check customers against the UN lists and the lists maintained under UAPA before onboarding and on an ongoing basis.

Practical notes: Indian names frequently include mononyms, initials and regional spelling variants. A screening engine has to match these without flagging every customer who shares a common given name.

How to choose your lists

  • Start with your licence. Your regulator’s guidance usually names the lists you must screen.
  • Follow the money. USD exposure brings OFAC into scope, EUR business brings in the EU, GBP and UK banking bring in the UK.
  • Follow your customers. Cross-border flows often require screening against the regimes of both ends of the corridor.
  • Keep versions. Auditors may ask what a list looked like on the day you screened someone. Store the list version with every result.

AutoCompliance screens against all five lists in one API call, refreshes them daily and returns the list version with every match. You can restrict screening to specific lists per project or per request.

This article is general information, not legal advice. Confirm your obligations with your compliance counsel and regulator.

Screen smarter from day one

We are onboarding a small group of design partners. Tell us about your screening volume and lists, and we will set up sandbox access.