Financial Economic Crime

The AML package, worked requirement by requirement

Your AML framework already exists, built over years of Wwft supervision. The AMLR, applying from 10 July 2027, does not ask you to start over. It asks you to prove, requirement by requirement, which policy answers which requirement, while AMLA is still publishing the standards that define compliance in practice.

RegAI Helia maps every requirement to your framework, documents and controls, and names what is missing. It covers:

The EU AML and CFT package: AMLR, AMLD6 and the AMLA Regulation
AMLA’s RTS, ITS and guidelines as published, including drafts in consultation
National rules: the Sanctiewet 1977 and the draft Dutch implementation act (Iwt)

10 July 2027 is fixed. Your evidence should not be a work in progress.

The Impact Assessment, across your policy framework

Requirements mapped to policy

Which articles and requirements apply to your organisation, and which policy clause carries each one.

Coverage checked

Each policy clause scored as a high, partial or low match, with a human in the loop to approve every score.

Gaps closed, expert approved

Helia identifies each gap and recommends how to remediate it; your compliance officer signs off.

From assessment to action

An Impact Assessment reads your AML policies and procedures against the requirements and shows what holds, what falls short and what is missing entirely.

Your documents, not a template

The assessment runs on the policies and procedures you actually have, so every gap is specific to your framework.

Findings become work

Each finding becomes a task with an owner and a deadline, tracked to closure.

Traceable back to the text

Every finding keeps the requirement it came from, the document version it was assessed against and the person who approved it.

Your controls, tested against the control objectives

Reuse what you already have

Your Wwft-era control framework already covers part of the AML package. The mapping shows exactly how much.

Coverage rated, with the reasoning

Each control objective is rated over-controlled, in control, partially controlled or under-controlled. The reasoning behind every rating is logged.

A leaner control framework

Duplicate and inconsistent controls against the control objectives are flagged, so you see where they duplicate and where potential harmonisation is needed.

The package keeps moving

AMLA is still publishing technical standards and guidelines, and supervisors keep issuing guidance. Horizon Scanning picks up each change and gives it an owner, so nothing new sits unread.

Change flagged at source

New standards, consultations and guidance are picked up as they are published.

An owner for every change

Each relevant change is triaged, assigned and reviewed.

Decisions on the record

Every classification, override and approval is traceable to the person who made it.

Next up

It all starts with an assessment of your own AML documents. See how it works in Impact Assessment.

Let us take you further

Schedule a 30 min call. No slide decks. Just a practical assessment of your needs and how we can help.

Book a demo