TL;DR. Fund administrators do not get a fixed screening frequency handed to them by regulation. FATF Recommendation 10 requires ongoing due diligence, and the practical interpretation across OFAC, EU, and UN list updates is real-time or same-day screening against list changes, not periodic batch review. Most fund admin programmes that fail an audit are running weekly or monthly batch screening when the underlying sanctions lists update multiple times per week.
Why screening frequency is not a fixed number
Sanctions programmes in the United States, European Union, and United Nations do not publish on a calendar. OFAC’s Specially Designated Nationals (SDN) list changes whenever the US Treasury issues a new designation, which can happen several times in a single week during periods of active geopolitical enforcement. The EU sanctions map updates on a similar irregular cadence tied to Council decisions.
This means a fund administrator screening on a fixed monthly batch cycle can carry an undetected sanctioned party on their books for up to 29 days after a designation goes live. For funds domiciled in jurisdictions with strict secondary sanctions exposure, that gap is the difference between a clean audit and a regulatory referral.
What FATF Recommendation 10 actually says
FATF does not specify a screening interval. The requirement is for ongoing due diligence proportionate to risk. See FATF ongoing monitoring guidance for how this obligation interacts with broader AML monitoring layers.
In practice, examiners in the US, UK, and Singapore treat “ongoing” as functionally equivalent to real-time or daily screening against list deltas, not full-file re-screening. Full-file re-screening on a quarterly or semi-annual basis remains appropriate for periodic KYC refresh, but list-delta screening is a separate, faster-cadence obligation.
Real-time vs batch screening: the practical difference
| Approach | Detection lag | Typical use case |
|---|---|---|
| Real-time API screening | Minutes to hours | New designations against active investor base |
| Daily batch screening | Up to 24 hours | Mid-sized fund admins without API integration |
| Weekly batch screening | Up to 7 days | Legacy programmes, high audit risk |
| Monthly batch screening | Up to 30 days | Not defensible under current FATF interpretation |
See how registry verification supports the broader CDD file
Audit trail expectations
Examiners ask for three things during a sanctions screening review: the screening frequency policy in writing, evidence the policy was followed (timestamped logs), and evidence of what happened when a potential match was flagged (disposition records, escalation timing, and false-positive clearance rationale).
A fund admin cannot rely on the fact that no true match was ever found as evidence the programme works. The programme is judged on process discipline, not outcome luck.
Where compliance teams get this wrong
The most common gap is treating sanctions screening as a one-time onboarding check. FATF Recommendation 10 folds sanctions screening into the same ongoing monitoring obligation as beneficial ownership refresh and transaction monitoring. Splitting it out as a “day one only” control is a documented finding in multiple public enforcement actions.
The second most common gap is screening the fund’s direct investors but not layering through to underlying beneficial owners disclosed at onboarding, leaving indirect exposure unmonitored between periodic KYC refresh cycles.