Support Portal

The Sanctions data health page shows, for every list your institution screens against, which export is in use right now, how it compares with the latest one published, whether the last collection recorded problems, and the full history of exports for each list. Use it when you need to confirm that a new designation is already covered, when a match (or the absence of one) needs explaining, or when an auditor asks which version of a list you were screening against on a given day.

Open it from Screening > Manual screening: expand the Sanctions data strip above the search form and click View sanctions data health. The page is available when your institution has the Screening product, like Manual screening itself.

Reading a list's status

Each card is one list. Two kinds appear:

• Lists published by OpenSanctions: Elucidate loads these from OpenSanctions, which collects each list from its official source on a published schedule.
• Lists collected by Elucidate: these carry the collected by Elucidate badge and show how many records are held, when the importer last collected them and, when known, the Last change.

For an OpenSanctions list, the card tells you:

An export is identified by a version such as 20260924061001-ixy. The first part is the date and time (UTC) at which OpenSanctions started collecting it: 24 September 2026 at 06:10.

Every time on the page is shown in your own local time. Hover over a time to see it with its time zone.

Status badges

A green dot means the list is in the screening index, its last collection succeeded without errors, and no newer export has been waiting for longer than 12 hours. Badges add detail, sometimes next to a green dot:

• indexing: OpenSanctions has published a newer export than the one in use. This is normal for a while after a publication, until the next combined release is loaded (see How exports reach screening below). Hover the badge to see when the first missing change was published.
• out of sync: the newer export has been waiting for longer than loading normally takes. Screening continues against the export in use; report it to Elucidate support if it persists.
• source quiet: OpenSanctions has not published the list within its usual rhythm, later than both its declared cadence and its own publication history allow, or its recent collection runs failed. Nothing is wrong on Elucidate's side; hover the badge for the details.
• version not named: the list is in the screening index, but the export in use could not be named at this moment. Screening continues against what the index holds, and the version reappears at the next check.
• not in screening index: the list is configured for screening but absent from the index, so nothing on it is being screened. This needs attention.
• collection failed: the last collection run at OpenSanctions did not complete, so no new export was published and the last successful one stays in use.
• collection incomplete: the run completed but logged errors, so the published export may be missing entries the official source has. The card summarises how many errors and warnings were recorded.
• version unconfirmed: the screening index could not be queried, so the version in use cannot be confirmed. Shown in grey: it means the check could not run, not that something broke.
• source unavailable: the OpenSanctions metadata for the list could not be retrieved, so its currency cannot be established.
• no records held and records unconfirmed: for a list collected by Elucidate — no records are held for it, so nothing is screened against it; or the watchlist index could not be queried, so the records held cannot be confirmed.

The Status checked time above the cards is when the page last queried the live status. Click Refresh to query again.

Checking problems in the last collection

When a card reports errors or warnings, expand the line that summarises them to read the messages OpenSanctions recorded while collecting the list. Their messages come straight from the collection run, so they name the source page or file that failed. Each entry shows its level, time and module; Only the most recent entries are shown. appears when the log was cut. The link at the end, View the source log on OpenSanctions, opens the raw log.

A list with a collection problem stays in use: the export in the index is the last one that was published, and screening against it continues. The log tells you whether that export can be trusted to be complete.

How exports reach screening

Understanding the loading path explains most of what the version history shows.

1. OpenSanctions collects each list on its own schedule and publishes an export whenever it runs.
2. Separately, about every six hours, OpenSanctions builds a combined release of all its lists.
3. The screening index checks for a new combined release every hour and loads it.

So a list export normally becomes the export in use within hours of publication. An export that is replaced by a newer one before the next combined release is built is never used: the release skips straight to the newer one.

Reviewing a list's version history

Expand Version history on any card to see the exports OpenSanctions still lists for it, its most recent hundred that changed the list, together with the newest export and any export Elucidate's checks recorded, most recent first, twenty per page. The line above the table states the date on which Elucidate's record of the screening index starts.

• Published: when OpenSanctions published the export.
• Used for screening: the period during which that export was the data screening ran against, as seen by Elucidate's regular checks of the screening index. A dot marks every export that was in use: green when the checks were clean, amber or red otherwise. The current badge marks the newest export OpenSanctions has published, which may not be in use yet.
• Adoption lag: the time between publication and the export being in use. It is blank for exports that were never in use.

Rows without a green period say why:

• not loaded yet: the newest export, still waiting for the next combined release.
• never loaded — replaced by a newer export first: a newer export arrived before the release was built, so this one was skipped.
• no changes to the list: the export changed no entries, so its content is the same as the last export before it that did, and that one was in use.
• A dash: no check covers that period. The date on which Elucidate's record of the index starts is stated above the table; earlier exports cannot be accounted for.

Hover over any of these labels for the evidence it rests on.

Seeing what an export changed

Click View changes on an export to open the list of parties it added, modified, re-identified or removed. Exports that changed no entries offer Details instead, and exports older than the change records OpenSanctions still keeps are greyed out with an explanation on hover. The dialog is titled Export followed by the version, states when the export was published, lists each party under Change, Party and Type, and ends with the run's Collection log and the links View this list on OpenSanctions and Open the raw collection log.

The headline counts parties, because that is what screening matches against. The sentence beneath it explains the underlying records: a newly designated party arrives with its own sanction, address and identifier records, and an export can also update those details for parties already listed, without changing who is screened against.

Two situations are worth knowing:

• Re-identified means OpenSanctions changed the party's identifier while the party stayed listed. OpenSanctions publishes this as the old identifier removed and the new one added in the same export; the page shows it as one entry, and it is not a new designation.
• Removed parties are named when an earlier export or today's index still carries their details. The note next to the name says whether the party is still listed on this list under a new identifier, still listed on other lists, or no longer listed anywhere. When no details survive, only the identifier can be shown.

A party's name opens its record in Manual screening in a new tab, so the history you are reading stays open. Parties that are no longer listed have no link, because there is no record to open.

Large exports are shown a page at a time. If OpenSanctions has withdrawn the file describing what an export changed, which it does for all but its most recent exports, the page says so instead of listing changes.

The PEP list is a collection: OpenSanctions assembles it from many source lists and publishes a new export of it every day, but records changes only per source list. Its version history therefore shows every published export and which one was in use, while Details names the source lists that published a new export since the previous one. Open a source list there to see what its export changed, in the same view used for any other list, and return to the collection's export with the Back to export link at the top. A source list that joined the collection with that export carries a new to the collection badge.

The Wikidata Profiles list, shown on this page under its OpenSanctions title Wikidata, is a single list for which OpenSanctions publishes exports but no change records, and so is the list of parties linked to sanctioned, export-controlled or politically exposed ones (shown here as Graph-based entity tagging). Their version history shows every published export and which one was in use; Details states that no change records are published for them.

Seeing what changed in a party

For a modified party, click What changed to compare the export with the previous export that touched that record.

The comparison lists, per property, the values that were added or removed, shows a rewritten value as was and now, and points out a value that was only re-filed under another property (for example an alias moved to previous names) rather than reporting it as removed and added. Supporting records that changed in the same export, such as the party's designation or an address, are listed beneath the party with their own changes.

When the earlier state of a record cannot be shown, the panel says why. OpenSanctions publishes what each export changed, not the full record before it, so the earlier values are only available if an export it still keeps change records for touched the record. The panel states how far back it looked and whether that is the end of what OpenSanctions publishes or as far as the comparison reads. If not every earlier export could be read, the comparison is marked incomplete; close and open it again to re-run it.

How this relates to your customers

Your customer records are re-screened on a schedule against the entries that are new or changed since the previous run, measured from the exports in use at that run. Once an export shows as in use on this page, every customer has been, or is about to be, checked against what it added. See Batch Screening for how those runs raise tickets.