The EU consolidated financial sanctions list

What the list helps with

The data.europa.eu catalogue offers XML, CSV and PDF files and states public access and daily periodicity. The FSF database supports downloads and notifications; FAÚ distinguishes EU Login access to the database from public one-off open-data downloads. Choose a route consistent with your operation and the access terms actually used.

Retain the entry identifier, names and aliases, other identifiers and links to the sanctions instrument. Do not automatically count the same person multiple times when importing different formats. Consolidation facilitates searching; it does not merge all regimes’ legal effects into a universal prohibition.

What requires checking the law

After confirming identity, locate the specific regulation, annex and amendments on EUR-Lex. For example, Article 2 of Regulation 269/2014 distinguishes freezing funds and economic resources from prohibiting their direct or indirect availability. Exceptions and authorisations have separate conditions. A general financial-sanctions label does not answer these questions.

Distinguish the file’s publication date from the legal entry-into-force date of a listing or amendment. An annex may apply before your system imports it. Consolidated EUR-Lex texts aid navigation; verify the published act and its effective date for the decisive change. Waiting solely for the next scheduled import is not an adequate response to an applicable prohibition.

What remains outside the file

Separately assess the Czech list, UN sources, ownership and control, and the transaction’s subject. An unlisted subsidiary may be linked to a designated owner. A service may be restricted under a substantive or territorial regime without a customer listing. Daily catalogue periodicity is neither an uptime guarantee nor proof that your local copy is current.

Verifying an automated distribution’s origin

Verify a public XML link through the official catalogue’s specific distribution rather than a token copied from a discussion. Catalogue metadata includes download address, format and access rights. Also retain the metadata link to explain where the application obtained data. Public-file access and an account for managing notifications are different operational routes. Public access does not itself promise uninterrupted availability.

For each update, verify successful download and parsing of the expected format. An HTML error page must not be accepted as a new empty XML list. Preserve the last valid copy, but flag its age and failed update. Assess access and licence metadata for the selected distribution; different formats within one catalogue need not share the same licence entry.