Sanctions List Monitoring: Real-Time Updates When Global Lists Change
Your client was clean at onboarding. The list changed last night. Do you know? Once-off OFAC screening and quarterly spreadsheet re-runs leave weeks of exposure every time UN, EU, or local sanctions lists publish new names.
We build the watchers that re-screen your book the moment lists move.
Sound Familiar?
These are the exact issues MLROs and Heads of Compliance described before we automated list-driven re-screening:
- Clients clear sanctions at onboarding, then sit unscreened until the next quarterly spreadsheet run
- OFAC, UN, EU, and local TFS lists change several times a week, so a clean take-on result goes stale fast
- A new designation published overnight only surfaces weeks later when someone finally re-runs the batch
- Compliance officers burn days matching Excel exports against downloaded list PDFs instead of reviewing exceptions
- FIC expects existing clients scrutinised when targeted financial sanctions lists update, not only at take-on
Weekly batch cycles leave 62–86 hour exposure windows after a Friday designation. Between January and September 2025 alone, OFAC published 47 separate list updates. A clean onboarding screen from Monday can be wrong by Friday afternoon.
What Real-Time Sanctions List Monitoring Actually Does
List changes → full-book re-screen → exceptions queued → audit trail locked. No waiting for the next calendar batch.
List Update Detected
UN, EU, OFAC, or FIC TFS feed publishes new or amended entries
Full Book Re-Screened
Active clients re-run against the new list version automatically
Exceptions Queued
True and near matches land in the compliance triage queue
Evidence Captured
List version, timestamp, and disposition ready for FIC or FSCA inspection
Everything You Need for OFAC Screening That Stays Current
Multi-List Change Detection
We watch UN, EU, OFAC SDN, and South African TFS list feeds for new entries, removals, and amendments so you know the moment a list version changes.
Automatic Full-Book Re-Screen
When a list updates, your entire active client base is re-screened against the new version without waiting for the next calendar cycle.
Exception Queue Only
True and near matches land in a triage queue. Clean records stay quiet, so analysts review hits instead of re-checking thousands of cleared names.
CRM and Core Sync-Back
Match status, list version, and disposition notes write back to the client record so relationship managers and compliance see the same picture.
List-Version Audit Trail
Every screen is timestamped with the list source and version used. Inspection packs show what you knew, when you knew it, and who cleared the hit.
Risk-Tiered Cadence Fallback
Even between list events, higher-risk segments can still run a scheduled safety net so your RMCP frequency requirements stay covered.
Lists and Systems We've Connected
From 180 Hours/Quarter to Same-Day Re-Screens
How an FSCA-regulated payment provider closed a multi-week sanctions exposure window across 12,000 active clients.
The Calendar Batch
- Three analysts exported the CRM book to spreadsheets each quarter
- Manual checks against downloaded OFAC, UN, EU, and FIC TFS files
- Roughly 180 analyst hours per cycle for 12,000 clients
- New designations between cycles sat unnoticed for weeks
- Audit evidence was a folder of dated Excel files and email trails
The List-Driven Process
- List watchers detect UN, EU, OFAC, and TFS updates within hours
- Full book re-screens automatically against the new list version
- Analysts only open the exception queue, not the entire client file
- Exposure window compressed from weeks to same-day review
- Every run stores list version, timestamp, and disposition for inspection
Before vs After Real-Time Updates
How It Works
From first conversation to live list-driven re-screening in 3–5 weeks.
Map Your List Gap
Which lists you screen, how often you re-screen, and where overnight designations currently hide between cycles.
Free Scoping Call
30-minute call to design list watchers, full-book trigger logic, exception routing, and RMCP evidence needs.
Build & Parallel Test
We wire list-change triggers, run parallel re-screens against a sample book, and validate the queue with compliance before go-live.
Go Live & Tune
Calendar batch runs step aside. List updates drive re-screens. We tune match thresholds so the exception queue stays workable.
Frequently Asked Questions
How is list-change monitoring different from ongoing World-Check alerts?
Ongoing screening products alert when a known client's risk profile changes in a commercial database. This build focuses on the lists themselves: when UN, EU, OFAC, or local TFS lists publish new entries, your whole book is re-screened against that fresh list version. Both matter. List-change monitoring closes the gap where a newly sanctioned party was clean at onboarding and never touched a risk-profile alert because your calendar batch has not run yet.
Which sanctions lists can you monitor?
Typical South African programmes cover the FIC targeted financial sanctions list (UNSC designations given effect domestically), OFAC SDN, the UN Security Council Consolidated List, and the EU consolidated financial sanctions list. We add UK, local PEP, and commercial screening feeds where your RMCP requires them. The integration watches for published changes and kicks the re-screen, rather than relying on someone to notice a press release.
How fast is the full-book re-screen after a list update?
Most mid-size books (under roughly 50,000 active parties) complete an automated re-screen within hours of the list feed updating. Larger books run overnight with priority tiers first. The point is closing the multi-day or multi-week exposure window that weekly and quarterly spreadsheet cycles leave open. OFAC alone has published dozens of separate list updates in a single year, often two to three times a week.
Will every list change flood our analysts with alerts?
No. The system re-screens silently and only queues true or near matches for human review. Clean records produce an audit log entry, not an inbox item. We calibrate fuzzy-match thresholds and secondary identifiers during parallel testing so your team sees exceptions worth investigating, not thousands of noise hits.
Does this satisfy FICA ongoing monitoring expectations?
FIC guidance expects accountable institutions to scrutinise client information against the TFS list at take-on and when the UNSC adopts or expands targeted financial sanctions measures. FICA section 21C also requires ongoing due diligence throughout the relationship. List-change driven re-screening, with list-version evidence and disposition trails, is how we help MLROs demonstrate that existing clients are re-checked when lists move, not only at annual CDD refresh.
How much does sanctions list real-time monitoring cost?
Builds that watch the core UN, EU, OFAC, and FIC TFS feeds and trigger automated full-book re-screens with an exception queue typically start from around R40,000. Broader programmes with multi-system sync-back, risk-tier fallbacks, and inspection packs usually sit between R55,000 and R110,000. Most clients weigh that against quarterly batch labour measured in hundreds of analyst hours and FIC Act administrative penalties that have reached into the millions of rand.
Stop Betting Compliance on Last Quarter's List
If your sanctions compliance still depends on calendar batches and spreadsheet exports, every overnight designation is a blind spot until someone remembers to re-run the file.
Tell us which lists you must cover, how large your active book is, and where exceptions should land. We'll show you how list-change monitoring and automatic re-screening would work for your RMCP.