AML & FIU
Sanctions/PEP screening, alert resolution, and Suspicious Transaction Report (STR) filing.
How sanctions and PEP screening works
When a client is screened, what a match looks like, and the resulting alert.
Resolving a screening alert
The open → resolved/dismissed path, and why resolution is restricted to the MLRO role.
Filing a Suspicious Transaction Report (STR)
When an STR is required, the 24-hour STR reporting clock, and the goAML export format.
Understanding the 24-hour STR clock
24hWhat starts the clock and what happens if it's missed.
Tipping-off controls explained
Why staff cannot inform a client that an STR has been filed, and how the system enforces this.
Re-screening existing clients after a sanctions list update
Automatic re-screening triggers on list updates.
Related categories
Frequently asked questions
Who can resolve a screening alert?
Only the MLRO role — dismissal or escalation to STR is a controlled action.
What is the STR filing deadline?
A 24-hour STR reporting clock runs from the point the required suspicion is formed.
What is goAML?
The FIU's standard electronic filing format; Ustawi exports STRs in that structure.
Can staff tell a client an STR was filed on them?
No — tipping-off is prohibited and the system's access controls reflect that.
How often are clients re-screened against sanctions lists?
On onboarding and on every list update, configurable per tenant.