> ## Content Index
> Fetch the complete content index at: https://www.waldvorlauternormen.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# AMLR Readiness: A Progress Check
- URL: https://www.waldvorlauternormen.com/en/amlr-readiness-ein-zwischenstand-en/
- Published: 2026-11-06T08:51:58.000Z
- Updated: 2026-11-06T08:51:58.000Z
- Description: From 10 July 2027, the AMLR applies directly to credit and financial institutions. From identifying beneficial owners to cleansing legacy data: how implementation can be managed in the months that remain – particularly in international groups.
- Author: Anna Izzo-Wagner
- Tags: Geldwäsche & Sanktionen, Bank- & Aufsichtsrecht, #en

**From 10 July 2027, the EU Anti-Money Laundering Regulation applies directly to credit and financial institutions. Implementation ranges from identifying beneficial owners and new decision-making channels to cleansing legacy data. How can this be managed in the months that remain – particularly in international groups?**

Four shareholders each hold 25 percent in a German limited liability company (GmbH). Under the current shareholding threshold, none of them qualifies as a beneficial owner on the basis of this shareholding alone. Under the AMLR, all four will reach the threshold for beneficial ownership. For the bank, this changes more than a number in the review template: forms, system rules and customer files must all produce the same result.

This example shows what matters in implementation. The legal assessment must remain traceable all the way into day-to-day processing. A revised policy is an interim step. Whether the new rule works is decided in the customer process.

## What is already settled

The AMLR – [Regulation (EU) 2024/1624](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L%5F202401624&ref=waldvorlauternormen.com) – is the binding basis for planning. Its date of application for institutions does not depend on whether a bank will later be subject to direct supervision by the AMLA. The application dates of supplementary technical standards must likewise be considered separately.

![Timeline with three numbered dates: 1 October 2026, final AMLA drafts sent to the Commission; 10 July 2027, AMLR directly applicable to institutions; RTS application, a separate date after adoption and entry into force](https://storage.ghost.io/c/f1/62/f162e43a-b151-4c92-9438-c13a2dbd1050/content/images/2026/11/Figure1_AMLR_Timeline.gif)

Figure 1: Timing of the application of the AMLR and of the delegated acts. As of November 2026.

## Planning with drafts and keeping changes manageable

On 1 October 2026, the AMLA submitted final draft regulatory technical standards on customer due diligence, on business relationships and occasional transactions, and on group requirements to the European Commission. These drafts are not yet binding legal acts. Application six months after their entry into force has been proposed.

Nevertheless, it would be risky for institutions to defer further implementation until all procedures have been completed. Data models, interfaces and service-provider processes cannot be changed at short notice. The drafts should therefore already be analysed and used for functional specifications. It must remain clear which requirement is settled and which solution rests on a provisional assumption.

In practice, a requirements register is advisable, recording the source, the version analysed, the procedural status and the application date. For open legal questions, it should also record the provisional position, the person responsible and the trigger for a renewed review. If a draft changes, it must be traceable which functional specifications, system rules and tests are affected. An archived version is more reliable for this purpose than a link to a continuously updated website.

## A gap analysis must evidence the gaps

The comparison should cover both the rulebook and actual processing. A work instruction may describe an obligation in full even though the system lacks a required data field. Conversely, a technical check may exist without responsibility and the handling of exceptions having been defined. Both cases require action.

![Table in five steps from legal provision to proof of implementation: requirement, identified gap, measure, test and evidence](https://storage.ghost.io/c/f1/62/f162e43a-b151-4c92-9438-c13a2dbd1050/content/images/2026/11/Figure2_AMLR_Proof_of_Implementation.png)

**Figure 2: A gap is only adequately described once the measure, the test and the evidence of completion have been defined.*

“Not applicable”, “not yet reviewed” and “interpretation question open” should be reported separately. An unresolved question is not evidence of compliance. Likewise, deficiencies under the current German Money Laundering Act (GwG) must be kept separate from future AMLR adjustment needs. Remedial measures that are already due are not postponed by the project.

## Beneficial ownership as a test case for implementation

Article 52(1) AMLR already captures direct or indirect ownership of 25 percent or more of the shares, voting rights or other ownership interests. The current threshold under Section 3(2) GwG is more than 25 percent. Where ownership is evenly divided among four natural persons, the result will therefore differ in future.

![Four persons each holding 25 percent of a GmbH: today the shareholding threshold is not met, under the AMLR all four meet it](https://storage.ghost.io/c/f1/62/f162e43a-b151-4c92-9438-c13a2dbd1050/content/images/2026/11/Figure3_AMLR_Threshold.gif)

**Figure 3: Simplified case with identical shareholding and voting-right percentages; no special rights or deviating control arrangements.*

First, the new threshold must be reflected in the data collection form and in the work instructions. It must then be checked whether the KYC system actually recognises exactly 25 percent. A test using only a 30 percent shareholding would not detect the decisive error. The boundary cases of 24.99, 25 and 25.01 percent are more meaningful.

The shareholding threshold does not replace the review of control via other means. Anyone who, for example, determines the key decisions on the basis of special rights may need to be recorded irrespective of their shareholding. The technical implementation must not switch off this line of review when the threshold value is changed.

Then there is the existing customer base. The bank must be able to determine which ownership structures are affected, which information is already available and where evidence is missing. If, until now, only the persons recorded as beneficial owners were stored, the need for adjustment may not be identifiable through a simple data query. This is a separate processing effort that must be accounted for in the project plan.

Functional acceptance and the processing of existing customers should therefore be planned together. The new system rule requires a documented test result. Affected customer cases require a legally justified timetable and a traceable processing status. A successful system test does not yet prove that the customer files have also been updated.

## Group standards must fit the German entity

A group-wide project can provide common rulebooks, data models and systems. The German entity must, however, check whether these cover its customers, products and actual processes. Article 16 AMLR requires group-wide policies, procedures and controls to take into account the specificities and risks of the individual branches.

The local review should take place early. If it only becomes apparent shortly before the date of application that a central system does not provide for a required data field, there is hardly any time left for a viable solution. Deliveries from group headquarters therefore require named owners, fixed deadlines and clear acceptance criteria. A release must be available early enough for the German entity to test it itself and report errors back.

Statutory approvals also belong in the timetable. Under Articles 9 to 11 AMLR, tasks are assigned in particular to the management body, the compliance manager and the compliance officer. For example, the compliance officer prepares the business-wide risk assessment; the management body in its management function approves it. A steering committee can prepare this, but it does not replace the required approval.

## For group services, the actual task is decisive

A legally independent service company is not exempt from the outsourcing rules merely because it belongs to the group. Article 18 AMLR sets limits that must be reflected in the contract and in the technical allocation of tasks.

![Two-column comparison of the preparatory tasks of the service company and the decisions reserved to the obliged institution](https://storage.ghost.io/c/f1/62/f162e43a-b151-4c92-9438-c13a2dbd1050/content/images/2026/11/Figure4_AMLR_Separate_Powers.png)

**Figure 4: Example of a division of tasks for outsourced KYC preparatory work. The graphic does not cover the full catalogue of Article 18(3) AMLR.*

The acceptance test is particularly revealing: can the service provider take a reserved decision itself or bypass an approval step? A contract that reserves the decision to the bank does not help if the access rights in fact allow the service provider to establish business relationships on its own.

## Distinguishing outsourcing from reliance on other obliged entities

Outsourcing must be distinguished from reliance on other obliged entities under Articles 48 and 49 AMLR. In outsourcing, a service provider performs tasks on behalf of the institution. In reliance, the institution uses due diligence measures carried out independently by another obliged entity.

An example: Bank A has identified a corporate customer for its own business relationship and verified its beneficial owners. Bank B uses these results under the conditions of Articles 48 and 49 AMLR. If, by contrast, Bank B engages a company to review its customers in accordance with Bank B's specifications, the arrangement must be assessed under the outsourcing rules. Another bank can also act as a service provider in this role.

Reliance is limited to the measures under Article 20(1)(a) to (c) AMLR. Ongoing monitoring is not included. In both models, responsibility remains with the institution. It is therefore not a suitable criterion for drawing the distinction.

## Update deadlines require reliable data

Article 26 AMLR requires customer information to be updated on a risk-sensitive basis. For higher-risk customers subject to enhanced due diligence, the interval must not exceed one year; for all other customers, the maximum period is five years. Certain events trigger an earlier update.

This requires the risk class, the date of the last complete update and relevant change events to be brought together. A common weakness is the distribution across several applications: the KYC system holds the ownership data, another application the last review date and a third the risk class. Without a reliable link, neither accurate due dates nor a fully prioritised work queue can be generated.

The inventory should therefore also cover data quality. Where review dates are missing, it must be clarified whether they can be reconstructed from records or whether a new review is required. An arbitrarily chosen substitute date would merely create the appearance of an orderly process.

## Third-country law may require additional measures

International groups also face legal obstacles to the exchange of information. Where local data protection or banking secrecy law restricts the transfer of customer or suspicious-activity information, the group must determine specifically which provision affects which information and which recipient. A general reference to data protection is not sufficient for this assessment.

Where third-country law does not permit compliance with the AMLR, Article 17(2) requires additional measures and that the home supervisor be informed of these measures. It must be examined which controls are possible locally and whether remaining risks can be managed through permissible measures. If these are not sufficient, restrictions up to and including the cessation of operations may become necessary.

## Planning backwards from the date of application

The sequence of implementation should be based on legal urgency, risk and lead time. Changes to data models and central systems must be commissioned early. Editorial adjustments can often be finalised later. Prioritisation does not, however, determine whether an applicable obligation must be fulfilled.

![Bar chart of the project phases from November 2026 until after 10 July 2027: gap analysis, rulebook and IT specification, technical implementation, tests and approvals, existing customers and controls](https://storage.ghost.io/c/f1/62/f162e43a-b151-4c92-9438-c13a2dbd1050/content/images/2026/11/Figure5_AMLR_Backward_Planning.gif)

**Figure 5: Illustrative project sequence. The processing of existing customers depends on the applicable obligations and deadlines; it must not be deferred across the board until after 10 July 2027.*

By the end of 2026, institutions should have identified the material gaps, determined their staffing and IT requirements for 2027 and agreed delivery dates with group headquarters. In the first quarter of 2027, the functional requirements for data fields, calculations, approvals and update triggers in particular should be sufficiently advanced that implementation does not founder on open questions of principle.

The second quarter is needed for integration tests, bug fixing, functional acceptance and training. Training should relate to the processes actually in use. If employees are trained on a draft version that does not match the final system, the training must be repeated or supplemented.

## How project progress should be measured

For senior management, what matters is which requirements have already been implemented and tested, which decisions are outstanding and where deadlines are at risk. A statement such as “80 percent complete” says little if it remains unclear whether the remaining 20 percent consists of a text module or the still-missing customer review logic.

A report on specific open items is more useful: Which obligation is affected? What are the consequences of the gap? Who will close it, and by when? Which delivery from the group or a service provider is missing? And what evidence will demonstrate implementation?

After the date of application, it remains to be checked whether the new processes work in operation. Rulebooks, approvals and successful test cases form the basis for this. Only ongoing controls show whether, for example, update tasks are generated in full, exceptions are handled correctly and reserved decisions actually remain with the institution.

## Legal bases and further sources

- [Regulation (EU) 2024/1624 – in particular Articles 9–11, 16–18, 26, 48–49 and 52](https://eur-lex.europa.eu/eli/reg/2024/1624/oj/eng?ref=waldvorlauternormen.com)
- [AMLA – Final draft RTS for the private sector of 1 October 2026](https://www.amla.europa.eu/press-release-amla-finalises-key-standards-private-sector%5Fen?ref=waldvorlauternormen.com)