Financial Intelligence Units sit at the centre of the AML/CFT architecture. FATF Recommendation 29 (R.29) codifies expectations on their mandate, independence, access to information and resourcing. Egmont’s Europe II horizontal analysis of IO.2, IO.6, R.29 and R.40 takes a hard look at how 23 FIUs in the region perform against these standards. Technical ratings are high: • 91% of jurisdictions are Compliant or Largely Compliant with R.29 • 9% are Partially Compliant • 0% are Non-compliant On the surface, this suggests only minor issues. But once you read across the Mutual Evaluation Reports, a more nuanced picture emerges: resource constraints, weak strategic analysis mandates, non-centralized reporting and limited operational independence all continue to drag down effectiveness—even where R.29 is “green”.
R.29 is not just a checklist of legal provisions. It embodies a model of the FIU as an independent, well-resourced intelligence hub that can:
Egmont’s introduction summarizes this succinctly: FIU establishment and operational effectiveness are “fundamental components” of FATF standards, with R.29 setting out clear expectations on independence, resources and legal mandate.
The Europe II region performs well technically:
Egmont’s horizontal reading shows that the nature of deficiencies is remarkably consistent:
In other words, R.29 compliance does not automatically translate into IO.6 effectiveness. The micro-deficiencies that keep FIUs at LC or PC are precisely the factors that undermine their ability to generate high-quality intelligence and demonstrate outcomes.
Egmont’s summary of the two Partially Compliant jurisdictions is instructive:
Despite these weaknesses, Egmont also notes positive features:
To move towards full compliance, Egmont recommends three headline actions:
Legal and procedural clarity – improve mechanisms such as Further Information Orders to streamline access to data from reporting entities.
For the nine Largely Compliant jurisdictions, Egmont finds strong foundations but visible gaps:
Common deficiencies include:
At the same time, these FIUs already exhibit many strengths associated with mature R.29 implementation:
Egmont’s recommended actions for Largely Compliant FIUs effectively define a finishing-school agenda for R.29:
Establish centralized reporting mechanisms and mandate comprehensive data collection for account holders and beneficial owners.
In the 12 Compliant jurisdictions, assessors found no R.29 deficiencies. These FIUs exemplify what a fully aligned R.29 implementation looks like:
Key characteristics:
These FIUs illustrate that R.29 “Compliant” is achievable—and directly supports IO.6 and IO.2 performance—when mandate, independence, access and resourcing are treated as a single design problem.
Egmont’s paper is clear that Recommendation 29 is not an isolated topic. It is analyzed precisely because of its link to IO.6 (use of financial intelligence) and, to a lesser extent, IO.2 (international cooperation).
From an evaluation standpoint, weak R.29 foundations almost always show up later in IO.6 scores—even if the technical rating for R.29 itself is LC rather than PC.
Egmont’s analysis effectively provides a shortlist of structural reforms that FIU directors, ministries and donors can use as a design brief.
Egmont repeatedly links high performance under R.29 and IO.6 to strong IT platforms, extensive database access and advanced analytics.
This is precisely where integrated FIU solutions such as FIU360-type systems become relevant:
In other words, technology is the practical mechanism for turning R.29’s legal requirements on mandate, independence and resourcing into a functioning operating model.
Egmont’s Europe II horizontal analysis finds that 91% of FIUs are technically Compliant or Largely Compliant with Recommendation 29, but structural weaknesses remain. Insufficient resources, limited strategic analysis, non-centralized reporting and fragile operational independence all undermine IO.6 effectiveness. High-performing FIUs combine robust legal mandates with strong IT platforms, broad data access and clear governance—turning R.29 compliance into genuine analytical capacity and operational impact.