EUR-Lex Legal Basis & Designation Reasons

The EU publishes the EU Consolidated Financial Sanctions List (EU_CSL) in XML, CSV, and PDF. It covers every individually sanctioned person and entity across every EU regime — freely downloadable, updated within hours of new designations.

Some screening providers price access to Russia or Iran sanctions data separately. In fact, every EU individual sanction — Russia, Iran, Belarus, North Korea included — is freely available in the EU Consolidated Sanctions List. We use that official source directly.

But the EU_CSL contains names, dates of birth, nationalities, and identifiers — not the designation reasons. For those you need the regulations themselves: Council decisions and implementing regulations published in the Official Journal via EUR-Lex.

The EU currently maintains 54 sanctions regimes. About 40 of them list individuals — persons or entities by name. Each regime is anchored by a base regulation, amended by implementing regulations whenever a designation, delisting, or detail change occurs.

Council Regulation (EU) No 269/2014 (Ukraine) has been amended by over 100 implementing regulations since adoption. Each amendment adds, removes, or modifies annex entries. The consolidated version folds all amendments into one document — the authoritative current state.

We monitor 34 regimes with daily checks against EUR-Lex. New consolidated versions are downloaded and parsed within hours.

The designation reason — why the EU sanctioned a specific person or entity — sits in the HTML annexes of the consolidated regulations. It is not part of the EU_CSL; you only get it by parsing the regulation text.

We have extracted over 7,400 rationale texts from 34 monitored regimes. Each is linked to the matching entity in the registry, shown on the entity detail page, and fed into connection detection.

Designation reasons frequently reference other sanctioned persons and entities: "son of [Name]", "associated with [Company]", "acting on behalf of [Person]". These references are structured enough to detect — and they map connections that are invisible in the flat sanctions list.

We build an alias-pattern matcher from 225,000 name patterns (every canonical name, alias, and variant in the registry) and scan every extracted rationale text in a single pass. Result: over 29,900 rationale-mention connections.

The connections are cross-source: an EU designation reason can name a person designated by OFAC but not the EU, or vice versa. Detection works across every source in the registry, not just within the EU regime.

For more on how entity connections work across all data sources, see Entity Connections & Network Intelligence.

EUR-Lex monitoring runs as a 3-tier daily cascade at 07:30 CET. For each of the 34 monitored regimes, three detection methods run in sequence: a SPARQL query against the EUR-Lex metadata endpoint, a content-hash comparison against the last known version, and an HTTP HEAD request as fallback. A newer consolidated version is downloaded, parsed, and matched against the entity registry.

Every week, a full re-scan runs across every rationale text — not just texts from newly updated regulations. That catches connections that only become detectable after new entities arrive from other sources.

Historical data is preserved: when a person is delisted from a regulation, the rationale text and the entity's listing history remain in the registry. Delisted persons are marked as inactive but their connections and legal basis are not deleted.