Sanctions sources and how updates work
Understand which source formats Reliance Risk Registry supports, how the daily import pipeline works, and what to check before relying on a screening result.
Supported sources describe platform capabilities, not a live claim that every feed is current or enabled in your deployment.
Supported sources
European Union
Consolidated financial sanctions XML import.
Official EU sanctions contextUnited Kingdom
UK Sanctions List XML import.
Official UK Sanctions ListUnited States — OFAC
SDN and consolidated non-SDN advanced XML imports are separate source definitions.
Official OFAC Sanctions List ServiceCanada
Consolidated sanctions XML import.
Official Canadian sanctions guidanceUnited Nations
Security Council consolidated list XML import.
Official UN consolidated listUkraine — NSDC individuals
Supported through an administrator-provided XLSX upload. This is not one of the default automated feed definitions.
NSDC sanctions resourcesReference links provide official context. They are not endorsements or proof that an individual source import succeeded.
Daily imports, then subscription screening
- Scheduled import: the default schedule is 00:00 UTC daily and can be configured by the operator.
- Source attempts: the job imports configured, importable source definitions. Administrators can see per-source outcomes and counts on the protected Sources page.
- Screening: after completed import attempts, active subscriptions are checked against stored sanctions data.
- Notifications: initial outcomes and changed screening results enter the configured delivery workflow.
A new screening timestamp is not proof that all feeds refreshed
Failed imports can leave older rows available. Completed attempts can trigger screening even if feeds failed; interrupted imports can skip screening. Review both job outcomes and the subscription’s screening status.
Administrators can manually trigger imports or a screening-only job. Screening-only runs do not fetch new feed data. Upload-based sources require their own update process.
What coverage does not establish
- A supported format does not guarantee that a deployment has enabled it or loaded the latest publication.
- The listed sources do not represent every jurisdiction, sanctions restriction, or regulatory obligation.
- The platform does not claim PEP or adverse-media coverage through these sanctions sources.
- A name match is a review candidate. A no-match result does not establish legal clearance or absence of risk.
Use official publications and your organization’s review process to determine the scope appropriate to your obligations. See the monitoring and matching guide for how candidate results are produced.