List delivery and updates
Sanctions lists change constantly. The gap between a designation being published and your systems knowing about it is pure exposure.
IN ONE LINE
An everyday analogy: the banned list at the gate is not printed once — new posters arrive continually, some are corrected, and some are taken down after appeals.
A gatekeeper working from last month's stack will wave through people banned last week and keep stopping people who were cleared.
Worse, some visitors are already inside the building: when a new poster arrives, someone has to walk the floors and re-check everyone against it, not just future arrivals at the gate.
Keeping the stack current, and re-checking the people already inside every time it changes, is the whole discipline of list updates and rescreening.
WHAT IT ACTUALLY IS
Issuers add, amend, and delist entries continuously, publishing updates through official channels and machine-readable files.
Legal obligations generally attach from the moment a designation takes effect — not from when a bank happens to load the file — so ingestion speed is a compliance parameter, not a convenience.
Two controls follow.
Transaction screening picks up new names automatically for future payments once the list is loaded.
Rescreening covers everyone already inside: the existing customer base is re-checked when lists change, either by re-running everything on a schedule or by screening the customer base against the delta — the set of added and changed entries.
Delisting matters too: removed entries should stop generating alerts, and holds based on them need review.
HOW IT WORKS
The practical questions are latency and verification.
How long passes between an issuer publishing an update and the new entries being live in every screening system — onboarding, payments, batch? Institutions measure this end-to-end, because a vendor feed, an overnight batch, and a weekly sync each add lag, and major geopolitical events produce bursts of designations exactly when the exposure is highest.
Ingestion is validated, not trusted: record counts, structural checks, and alerting when a load fails silently.
Rescreening scope is a documented choice — full-base rescreening is thorough but expensive; delta screening is fast but depends on correctly identifying what changed.
After large updates, teams also expect and staff for an alert spike rather than letting queues silently grow.
THE WORDS
- Rescreening
- Screening existing customers and held data again — on a cycle or after list updates — so changes in lists or records are caught, not just new business.
READ FIRST
CONNECTED TO
SOURCES
- Wolfsberg Group Sanctions Screening Guidance — The Wolfsberg Group
- Specially Designated Nationals and Blocked Persons List (SDN List) — US Department of the Treasury, Office of Foreign Assets Control
- Payments Signal editorial teaching models — Payments Signal
Derived from List delivery and updates. Every claim on this card is sourced on that page.