Practical guide
Sanctions data freshness: publication, ingestion, and screening time
Evaluate sanctions data freshness by separating official publication, ingestion, active source versions, successful screening, and monitoring completion.
On this page
“Updated” can refer to several different events
An authority publishes or changes a record. A provider fetches data. A parser validates and normalizes it. A new snapshot becomes active. A screening uses that snapshot. A monitor later completes another check. Those events can happen at different times.
A homepage timestamp that shows the latest fetch does not prove that a valid new source version was activated or that every customer was rescreened. Ask which event a freshness field actually describes.
Preserve the version used by each result
A retained screening should identify the source version and completion time. This lets a reviewer understand the evidence available for the original decision. A later change should create a new historical comparison rather than rewriting the old one.
For an invented test, a source update adds an identifier after an analyst dismisses a candidate. The earlier decision and later change must both remain visible so the team can explain why the case returned to review.
Treat failed updates as operational issues
A malformed file, unexpected schema, suspicious record-count change, or unavailable source should trigger validation and investigation. A failed download must not be promoted as an empty sanctions list. Preserve the previous good version with an accurate status while following the documented failure policy.
Users need to know when required coverage cannot satisfy the workflow. A successful HTTP response from the application is not enough if the required source was silently skipped.
Review each authority’s publication model
Official sources differ in format, publication cadence, scope, and legal status. Canada’s autonomous consolidated list, for example, explains its administrative nature and the importance of current regulations. OFAC’s list service is a separate distribution model.
Do not infer a uniform global update guarantee from one source’s behavior. Source-specific limitations belong in the coverage register and any relevant reviewer guidance.
Separate fresh data from successful monitoring
A current source snapshot does not help a paused monitor or an outdated subject record. Track the monitored population, retained input version, last successful rescreen, and unresolved screening issues.
SanctionsKit monitoring combines schedules with qualified source-triggered full rescreens. The operational question is whether the required check completed with the intended scope, not merely whether a timer fired.
Ask for evidence behind a freshness claim
Request definitions for publication time, fetch time, activation time, source version, outage status, and screening completion. Test a source failure and a changed record. Confirm that historical evidence keeps its original context.
Use current coverage and the monitoring operations checklist. Avoid phrases such as “never stale” or “instant worldwide updates” unless their exact meaning is demonstrable and contractually supported.