KYC remediation in Luxembourg: getting ready for AMLR 2027
Laurent Tousch11 min readDEFREN

Learn more about AI implementation in Luxembourg, and see how the same controls apply to AI in Luxembourg family offices.
Most Luxembourg professionals I talk to have KYC files for every client. Far fewer have files that would pass a reviewer who asks three questions: who exactly are the beneficial owners today, when was this file last checked against the sanctions lists, and where is the evidence? Files opened years ago were built for the rules of the time, and many have only been touched when something went wrong.
I run document and compliance automation projects at 20 More. This guide sets out what the AMLR changes, who supervises whom in Luxembourg, and the remediation method I recommend: one data model per client file, a gap list, and automation for the repetitive parts. It is practical guidance, not legal advice; your supervisor's guidance and your own AML policy come first.
When does the AMLR apply, and what is it?
Regulation (EU) 2024/1624 was adopted on 31 May 2024, entered into force on 9 July 2024 and applies from 10 July 2027; for football clubs and agents it applies from 10 July 2029 (Article 90, EUR-Lex). It is a regulation, not a directive, so its due diligence rules apply as written in every Member State, and Directive (EU) 2015/849 is repealed from the same date (EUR-Lex summary).
It comes with a new EU authority. AMLA, the Authority for Anti-Money Laundering and Countering the Financing of Terrorism, is based in Frankfurt and started its activities in mid-2025 (AMLA). From 2028 it will directly supervise a limited number of large cross-border financial groups (AMLA explainer). A Luxembourg fiduciary or accounting firm will not be one of them: your supervisor stays national, but the rulebook it applies becomes European. The CSSF has published its own overview of the package (CSSF).
What changes for a KYC file on 10 July 2027?
Only items I could confirm in the official texts are in this table.
| Topic | Today (Law of 12 November 2004) | From 10 July 2027 (AMLR, Article 90) |
|---|---|---|
| Legal source | National law transposing the EU directives, plus supervisor guidance (Legilux) | Directly applicable EU regulation (EUR-Lex) |
| Beneficial owner through ownership | More than 25% of shares or voting rights (Article 1(7), 2004 law) | 25% or more of shares, voting rights or other ownership interest, indirect stakes multiplied along the chain (Article 52 AMLR) |
| Identification data | Identity of the customer and beneficial owners, verified on reliable sources (Article 3, 2004 law) | A defined list, including all names, nationalities and usual place of residence, and every data point used must be verified (Article 22 AMLR) |
| Review of existing files | Risk-based ongoing monitoring (Article 3, 2004 law) | At least every year for clients under enhanced due diligence, at least every five years for all others, plus a review when relevant circumstances change (Article 26 AMLR) |
| Record retention | 5 years after the end of the relationship (Article 3(6), 2004 law) | 5 years after the end of the relationship, then deletion of personal data (Article 77 AMLR) |
| Detailed rules | Supervisor regulations and guides | AMLA technical standards, including a draft standard on customer due diligence (AMLA) |
Two details matter for remediation planning. First, AMLA's draft technical standard on customer due diligence says files of existing clients should be brought into line on a risk-sensitive basis, within one year for higher-risk clients and five years for the others, counted from when that standard applies (AMLA final report, draft RTS Article 28(1)). It is still a draft until the Commission adopts it, so do not plan around the exact clock, but do plan around the principle: high-risk files first. Second, the same draft recitals say that consulting a beneficial ownership register is necessary but not sufficient to verify beneficial owners. A copy of the RBE extract alone will not close a file.
Who in Luxembourg is affected, and who supervises them?
The 2004 law splits supervision between supervisory authorities and self-regulatory bodies (Article 2-1, Legilux). The AMLR keeps that national structure.
| Professional | AML/CFT supervisor in Luxembourg |
|---|---|
| Banks, investment firms, other financial sector professionals (PSF), including PSF corporate service providers | CSSF (CSSF) |
| Insurance undertakings and intermediaries | Commissariat aux assurances (CAA) (CRF report) |
| Experts-comptables (Law of 10 June 1999) | Ordre des experts-comptables (OEC), a self-regulatory body (CRF report) |
| Accounting professionals who are not experts-comptables, tax advisers, real estate agents, and other professionals not covered by the other bodies, including many company and trust service providers | AED, the Administration de l'enregistrement, des domaines et de la TVA (Article 2-1(8), AED guide) |
| Lawyers, notaries | Their professional bodies (Bar associations, Chambre des notaires) (CRF report) |
| Family offices (Law of 21 December 2012) | Obliged entities under the 2004 law (Law of 21 December 2012); the supervisor depends on the family office's licence and status, so confirm yours |
Company and trust service providers must also be registered with the supervisor or self-regulatory body they fall under (AED). Since 1 October 2024 the AED has had a dedicated AML inspection unit for on-site controls (AED).
Can you still rely on the RBE?
You can use it, but not lean on it. After the Court of Justice of the EU ruled on 22 November 2022 in joined cases C-37/20 and C-601/20 that general public access to beneficial ownership registers breached the Charter of Fundamental Rights (CJEU press release), Luxembourg suspended public access to the Registre des bénéficiaires effectifs. Access was restored from 16 December 2022 for professionals subject to the 2004 law who apply to Luxembourg Business Registers, and for journalists through the Press Council (Government of Luxembourg).
In practice: request professional access if you have not, store each RBE consultation with its date, and compare it with what the client and the RCS extract tell you. Where they disagree, that disagreement is itself a finding for the file.
What does a KYC remediation project look like?
The projects that work treat remediation as a data problem first and a paperwork problem second. These are the steps I recommend.
- Scope by risk. Export the client list with its current risk rating and last review date. Files rated high, files never reviewed, and clients with complex ownership chains go into the first wave.
- Define one data model per file. Every file should answer the same fields (table below). If a field cannot be filled, that is a gap, not a judgement call.
- Run a gap analysis. Compare each file with the model and with the AMLR list. The output is a per-file list: missing document, expired ID, ownership chain not traced to natural persons, no source-of-wealth evidence, screening older than your policy allows.
- Reach out to clients in batches. One clear request per client, listing exactly what is missing, in the client's language, with a deadline and reminders. Clients who are asked for everything at once tend to answer nothing.
- Re-screen everyone. Run clients, beneficial owners and authorised signatories against the EU consolidated financial sanctions list (data.europa.eu) and your PEP source, and record the result and the list version. The AED publishes guidance on international financial sanctions for the professionals it supervises (AED).
- Keep an evidence trail. For each file: what was checked, against which source, on which date, by whom, and what was decided. A reviewer reads the trail before the file.
The client file data model:
| Field | What "complete" looks like |
|---|---|
| Identity | Identification data verified against an ID document or registry extract, with expiry date tracked |
| Beneficial ownership chain | Every layer from the client to the natural persons at 25% or more, or controlling by other means, with source per layer (RCS, RBE, foreign registry, shareholder register) |
| Purpose and nature of the relationship | Short statement, consistent with the services you actually provide |
| Source of funds / source of wealth | Documented where your risk assessment requires it |
| Risk rating | Rating, reasons and date, signed off by a named person |
| Screening | Sanctions and PEP results for client, BOs and signatories, with list version and date |
| Next review date | Set from the risk rating, never later than the AMLR maximum (Article 26 AMLR) |
What can be automated, and what stays human?
The split I use is simple: software reads, compares and chases; people judge.
| Task | Automate? | Who decides |
|---|---|---|
| Reading IDs, passports, RCS extracts from lbr.lu, articles and share registers | Yes, extraction into the data model | Reviewer checks low-confidence fields |
| Building the beneficial ownership chain from registry extracts | Yes, as a draft chain with sources | Compliance officer confirms the BOs |
| Sanctions and PEP screening, and re-screening when lists change | Yes | Analyst clears or escalates each hit |
| Gap report per file | Yes | Compliance officer prioritises |
| Client request letters and reminders | Yes, drafted per client and language | Relationship owner sends or approves |
| Risk rating | Proposed score only | Compliance officer sets it |
| Accept, keep or exit the client; suspicious transaction reports | No | Compliance officer and management |
This is what our KYC file remediation Agent Run does on a defined batch of files: fixed scope, EU-hosted models, a human sign-off on every change and a log of what was checked. For an ongoing setup inside your own tools, the document processing service is the better fit. If you also run AI tools in a CSSF-supervised context, our guide to AI use cases under CSSF supervision covers the governance side.
What about GDPR?
KYC files are personal data, often sensitive: identity documents, family structures, wealth, and sometimes information on criminal proceedings. The AML laws give you the legal basis to process it, but GDPR still applies, including data minimisation (Article 5(1)(c) GDPR, EUR-Lex).
Three rules I build into every remediation:
- Collect what the AML rules require, not everything the client sends. Extra documents in a file are extra risk.
- Retention is five years after the relationship ends, under both the 2004 law (Article 3(6), Legilux) and the AMLR, which then requires personal data to be deleted unless another law requires longer retention (Article 77 AMLR, EUR-Lex). Put the end-of-relationship date in the data model so deletion can be scheduled.
- Know where the processing runs. If a tool reads client IDs, you need to know where it is hosted, who can access it and whether data is used to train anything. That belongs in your processing records and, for a large remediation, a short DPIA.
Frequently asked questions
What is KYC remediation?
KYC remediation is the review and update of existing client files so that they meet current customer due diligence rules. It covers identity, beneficial ownership, purpose of the relationship, source of funds or wealth where needed, risk rating and sanctions screening, with evidence of each check. In Luxembourg it is being driven now by the EU AML Regulation that applies from 10 July 2027 (Article 90, EUR-Lex).
When does the AMLR apply in Luxembourg?
Regulation (EU) 2024/1624 applies from 10 July 2027 in every Member State, including Luxembourg, without national transposition (Article 90, EUR-Lex). The only exception is football clubs and agents, from 10 July 2029. Luxembourg supervisors such as the CSSF, the AED and the OEC will continue to supervise their professionals under the new rules.
Do accountants in Luxembourg have to do KYC?
Yes. Experts-comptables are obliged entities under the Law of 12 November 2004 and are supervised for AML by the Ordre des experts-comptables; other accounting professionals and tax advisers are supervised by the AED (AED guide). They must identify and verify clients and beneficial owners, assess risk and keep files up to date.
How often must KYC files be reviewed under the AMLR?
The AMLR sets maximum intervals: at least once a year for clients under enhanced due diligence and at least every five years for all others (Article 26 AMLR). A file must also be reviewed when the client's relevant circumstances change, for example a new beneficial owner. Your risk assessment can and often should set shorter intervals.
Can KYC checks be automated?
Much of the work can: reading documents, extracting data, building ownership chains from registry extracts, sanctions and PEP screening, gap reports and client reminders. The risk rating, the decision to accept or keep a client and any suspicious transaction report remain human decisions. A good setup logs every automated step so a supervisor can follow it.
If you want to know how long remediation of your files would take, send us a short description of your client base and current KYC setup.
Related Posts
AI for Luxembourg Family Offices: Cut Reporting
Luxembourg's ~150 family offices share the same trilingual reporting + KYC pain. 5 AI workloads that pay off in 2026 — and 3 vendor pitches to skip.
AI Contract Review for Luxembourg Firms: 60-80% Faster
Cut contract review 60-80% and KYC 50-60% without touching Article 458 secrecy: on-premise options, CSSF/CNPD monitoring, and what a setup really costs.
KYC Remediation in Luxemburg: Was die AMLR 2027 verlangt
Die EU-Geldwäscheverordnung gilt ab 10. Juli 2027. Was sich für Treuhänder, Buchhalter und Family Offices ändert und wie KYC-Akten bereinigt werden.