Guide collection
Sanctions monitoring guides: setup, cadence and follow-up
Learn how to enroll subjects, choose repeat checks, investigate monitor failures and send new screening results to the right reviewer.
On this page
Enroll the relationships that need repeat checks
SanctionsKit monitoring rescreens retained subjects against selected sources. Start in Monitoring or use the monitoring API. The setup guide explains subject selection, coverage and cadence.
Use the frequency guide to apply your approved interval. Creating a monitor records the plan for later work. Inspect its runs to confirm that checks are actually completing.
Keep identity and monitor health current
The operations guide helps you check that the right subjects have active monitors. Look at the last successful run and resolve paused or failed work. An empty inbox is not proof that every check ran; it can also mean there was no completed result.
Keep saved facts current in Counterparties. When a change pauses linked monitors, follow the steps to confirm the new details before restarting them. Use the freshness guide to inspect source dates and versions when a check seems late.
Send new findings to a responsible person
Use the Review queue to assess a new candidate. The alerts and webhooks guide explains how to send events to your backend. Check the signature, handle repeated deliveries and fetch the result you are allowed to read before changing your app state.
A delivered message does not finish a review. Use the alert-management guide to assign the work and track the open question. Someone still needs to decide what the new facts mean.
Plan the workload alongside other controls
Monitoring shares the Production subject allowance with API, dashboard and batch checks. Inspect Usage & limits and use the cost-planning guide to account for scheduled and qualified source-triggered work.
If another system monitors payments or behavior, read sanctions vs transaction monitoring. Identity rescreening answers a different question and needs its own operational owner.
Frequently asked questions
Which monitoring guide should I read before enrolling customers?
Start with the setup guide to choose the subject and coverage, then the frequency guide for the approved interval. Confirm the first run completes before counting the relationship as successfully checked by the monitor.
Where should I look when no monitoring events arrive?
Use the operations guide to inspect monitor status, last successful runs and failures. Then check data freshness where relevant. Silence alone cannot distinguish a completed no-match from a check that never ran.
Which guide explains how monitoring events reach my application?
The alerts and webhooks guide covers delivery verification, duplicate handling and result retrieval. Pair it with alert management so a delivered notification is assigned to a reviewer when human work is required.
Can monitoring costs be planned separately from API screening usage?
Plan the activities separately, then combine them for the shared Production allowance. The cost guide explains how new checks, repeat checks and portfolio work add up without confusing HTTP requests with screened subjects.