AMLA transaction-monitoring guidelines near final form after 2 July hearing

What happened

AMLA (the EU Authority for Anti-Money Laundering and Countering the Financing of Terrorism) held a public hearing on 2 July 2026 on its draft Guidelines on the ongoing monitoring of a business relationship. AMLA opened the consultation on 3 June 2026 under Article 26(5) of the Anti-Money Laundering Regulation (AMLR). The consultation closes on 3 September 2026.

The draft sets out two guidelines. Guideline 1 covers keeping customer information up to date through periodic and event-driven reviews. Guideline 2 covers the transaction and activity monitoring framework: how obliged entities design, implement, and test monitoring to detect unusual or suspicious transactions and activities.

AMLA states that the core principles apply across both financial and non-financial sectors, on a risk-based and proportionate basis.

Why it matters

The hearing was the last major input point before the 3 September close. Read that way, the binding EU standard for ongoing monitoring is near final form. Guideline 2 becomes the supervisory baseline for transaction monitoring and wider anti-money laundering (AML) controls across the bloc.

The framing around design, implement, and test signals an evidence expectation, not only an outcome expectation. A monitoring system that generates the right alerts but cannot show its threshold rationale, tuning history, and testing results may still fall short. The final text will set what supervisors look for, so the gap between your documentation and the guideline is the real exposure.

The proportionality language cuts both ways. It gives smaller obliged entities room to scale their controls to risk. It also removes any argument that transaction monitoring is only a bank problem. Non-financial sectors sit inside the same principles.

Practitioner angle

Read Guideline 2 line by line against your current transaction-monitoring framework. Where a provision conflicts with how your monitoring actually runs, file a comment before 3 September rather than inheriting a standard you cannot meet.

Build the design, implement, and test evidence AMLA expects. That means a documented threshold rationale, a tuning history that shows why each rule changed and when, and testing results that prove the system detects what it claims to.

Map your periodic and event-driven review triggers to Guideline 1. Confirm each trigger fires a refresh: a new beneficial owner, adverse media, or a product change should force a review, and stale customer information should never sit unreviewed.

If you operate in a non-financial sector, do not file this under banking. The core principles reach you too.

The single most important action: file your comment before 3 September on any provision your monitoring cannot meet today.