Re-screening existing clients after a sanctions list update
Screening a client once at onboarding is not enough — sanctions and PEP lists change, and a client who was clean last month can appear on a list today. Ustawi can re-screen existing clients so a newly-added name is caught without anyone re-checking the whole book by hand.
Why re-screening matters
A one-time check reflects only the lists as they stood on the day of onboarding. Lists are updated as designations are added or removed, so a borrower or guarantor who passed cleanly can later become a match. Re-screening exists to close that gap between the original check and the current lists.
How re-screening is triggered
- Screening can be configured to re-run periodically against existing borrower — and, where enabled, guarantor — records.
- Re-screening compares clients you already hold against the updated lists, rather than only checking new onboardings.
- Any new match raises a screening alert exactly like an onboarding hit, routed to compliance for a decision.
- The cadence and triggers are configurable per tenant to fit the institution's own AML policy.
What happens to a new hit
A hit surfaced by re-screening is handled the same way as any other: it opens an alert, it waits for the MLRO to judge whether it is a true match, and every step is written to the audit log. Nothing about a re-screen shortcuts the human decision — it simply makes sure a newly-listed client is not missed.
Re-screening frequency is a tenant setting. Confirm your institution's configured cadence matches its AML/CFT policy rather than assuming a default.