Ongoing monitoring under the AMLR: is an annual KYB review still enough?

18 November 2026

A corporate client changes its beneficial owner on a Tuesday. It does not inform its bank, and nothing requires it to. The change must be filed with the central register within 28 days, and may only reach the KYB file at the next review, sometimes years later. In the meantime, the new beneficial owner has been neither verified nor screened against sanctions lists. Regulation (EU) 2024/1624 (AMLR) and AMLA's draft technical standard on customer due diligence require this gap to be closed. An annual review alone has never been enough; the AMLR adds harmonised maximum intervals and explicit triggers.

This article explains what ongoing monitoring requires during the business relationship, what the rules leave open, and how a data-driven monitoring framework can respond.

A person signs a corporate document at a desk, illustrating ongoing monitoring of legal entities under the AMLR


💡 Key takeaways

  • The AMLR combines a periodic review, at least once a year for high-risk customers and at least every five years for the others, with a review whenever something relevant changes.
  • An annual review alone has therefore never been enough, but no rule requires daily monitoring: the obligation is to react to every relevant change you become aware of.
  • Under AMLA's draft standard, a change of beneficial owner calls for a new sanctions screening, whatever the customer's risk level.
  • Corporate clients do not have to spontaneously tell their bank about such a change: they have 28 days to record it in the central register.
  • An AI agent can turn public signals into review triggers, as long as a person takes the decision.

What ongoing monitoring requires under the AMLR

Under the AMLR, which applies from 10 July 2027 (Art. 90), ongoing monitoring means you keep watching a customer throughout the business relationship, not only during customer due diligence at onboarding. You check that its transactions match what you know about it, keep its file up to date (at least once a year if the risk is high, at least every five years otherwise) and review it whenever something relevant changes (Art. 26). It also covers beneficial owners, sanctions screening and adjusting the level of due diligence.

  • Ongoing monitoring: verify that transactions are consistent with what you know about the customer, its business activities and its risk profile, taking into account its relationships within its group (AMLR Art. 26(1)).
  • Periodic review: update the file at least once a year for high-risk customers, and at least every five years for the others (AMLR Art. 26(2)).
  • Event-driven review: review the file when relevant elements of the customer's situation change, when a legal obligation requires the entity to contact the customer during the calendar year (to review beneficial ownership information, or under Directive 2011/16/EU on tax cooperation), or when the entity becomes aware of a relevant fact (AMLR Art. 26(3)).
  • Beneficial owners: verify their information by also consulting the central register, and report any discrepancy within 14 days (AMLR Art. 22(7) and Art. 24).
  • Targeted financial sanctions: screen the company, its beneficial owners and the persons who control it or hold more than 50%. Screen them regularly, and for credit and financial institutions, upon each new designation (AMLR Art. 20(1)(d) and Art. 26(4)).
  • Adjustment: end simplified due diligence if the low-risk conditions no longer apply, and apply enhanced due diligence if the risk becomes high (AMLR Art. 33(5) and Art. 34).

The draft regulatory technical standard (RTS) on customer due diligence, published by AMLA on 30 September 2026 and part of the AMLR's implementing rules, specifies several triggers. A change in customer due diligence data, including a change of beneficial owner, requires a new sanctions screening (Art. 25). New information requires checking without delay whether a beneficial owner has become a politically exposed person (Art. 17). This draft still has to be adopted by the European Commission, then be scrutinised by the European Parliament and the Council.

Annual review or daily monitoring: what level is expected?

This is the question most compliance teams are asking. The rules answer it in two points.

  1. An annual review alone is not enough. The event-driven review of Article 26(3) comes on top of the periodic review, whatever the risk level. An annual review is in fact only mandatory for high-risk customers; for the others, the ceiling is five years. This principle is not new: the previous directive already required an update when the customer's circumstances changed (Directive (EU) 2015/849, Art. 14(5)). What the AMLR adds is harmonised maximum intervals and explicit triggers.
  2. No daily monitoring is imposed. The rules refer to a change in situation or to "becoming aware" of a relevant fact. They do not require searching for register changes every day. The only expressly required fast reaction concerns sanctions: credit and financial institutions must check their customers upon each new designation (AMLR Art. 26(4)), and at each list update, existing customers and beneficial owners must be re-screened without undue delay (draft RTS, Art. 25).

The actual obligation lies between the two: leave no relevant change the entity is aware of without a response, and be able to show the supervisor that the framework is commensurate with the risks (AMLR Art. 20(4)). Daily monitoring then becomes a means, justified for the most exposed segments, not a general obligation.

  • High risk, complex structures, sanctions exposure: a review at least once a year, plus automated alerts on register changes.
  • Standard or low risk: a review within the five-year ceiling, plus systematic capture of the changes brought to the entity's attention.
  • All segments: a new screening of all known beneficial owners at each sanctions list update (AMLR Art. 26(4); draft RTS, Art. 25).

AMLA consulted on draft guidelines on ongoing monitoring (AMLR Art. 26(5)) until 3 September 2026. The final guidelines, which could clarify the expected level, have not been published yet.

What is a "relevant fact" in ongoing monitoring?

Neither the AMLR nor the draft RTS defines a "relevant fact". Nor do they set a deadline for the review or a detection method. It is up to the entity to give this obligation substance, and then to be able to justify it.

The most defensible method is to start from what the rules themselves link to customer due diligence:

  • Identification data (AMLR Art. 22(1)(b)): legal form, name, registered office, principal place of business, country of creation, legal representatives, registration, tax identification number, LEI, nominees.
  • Changes cited for sanctions screening (draft RTS, Art. 25): name, residence, business activity, beneficial owner, designation of a beneficiary.
  • Changes cited for PEPs (draft RTS, Art. 17): any new information or change in customer due diligence data.
  • Risk factors (AMLR Annexes II and III): a low-risk or high-risk factor appears or disappears.
  • End of simplified due diligence (AMLR Art. 33(5)): doubt about the information, suspicion of money laundering or of sanctions evasion.
  • Legal obligations to contact the customer (AMLR Art. 26(3)): a review of beneficial ownership information or a tax cooperation review (Directive 2011/16/EU) due during the calendar year.

This event catalogue, validated by compliance, becomes the cornerstone of the framework: it states what triggers a review, and which actions follow.

Why beneficial owner changes slip past obliged entities

The legal framework has a structural gap. The corporate client must provide information on its beneficial owners during customer due diligence, but nothing requires it to spontaneously report a change to its bank or insurer. It must record it in the central register within 28 days (AMLR Art. 63). The entity can still ask for it: the company must provide this information whenever the entity applies due diligence measures (Art. 63(1)), which in our reading includes ongoing monitoring. A contractual clause can also require the customer to report any change.

For the obliged entity, there are three consequences:

  • a change of beneficial owner can remain unknown for weeks, or even until the next periodic review;
  • as long as it is not known, it triggers neither verification, nor identification of the new beneficial owner, nor sanctions screening;
  • the screening obligation nevertheless applies to all customers: AMLA did not accept a general risk-based approach to sanctions screening (final report, p. 53).

To reduce this delay, change detection becomes a central operational issue, in the logic of perpetual KYC.

How can an AI agent feed ongoing monitoring?

The principle is simple: turn public signals into review trigger events that are substantiated and traced. In our reading, Article 26(3) of the AMLR does not restrict where the relevant fact comes from, and the draft RTS itself cites reliable open sources, reputable data providers and reputable media among the usable sources (Art. 10, 19 and 23).

The first three steps can be automated:

  • Capture. The agent collects signals from registers (central beneficial ownership register, trade register, official gazettes), company data providers, the press, and updates to sanctions lists and lists of prominent public functions.
  • Matching and classification. It links each signal to the right company in the portfolio, to a beneficial owner or to a person who controls it, then compares it with the event catalogue.
  • Proposal. It opens a substantiated trigger event (source, excerpt, event), with a priority based on the customer's risk.

The rest is the analyst's job. The analyst verifies the information through a reliable source (draft RTS, Art. 8). By design, a signal never updates a file directly. For a beneficial owner, verification also goes through the central register (AMLR Art. 22(7)). The analyst then decides on the actions: new screening, discrepancy report, move to enhanced due diligence, end of simplified due diligence or suspicious transaction report.

Two design rules apply:

  • Size the monitoring to your processing capacity. In practice, information captured by the framework can hardly be ignored: very broad monitoring whose alerts are not processed creates more exposure than targeted, controlled monitoring. Classification by the agent is what keeps false positives down.
  • Make the scope proportionate to the risk. The draft RTS stresses limiting unnecessary data processing (recitals 5 and 14): the broadest monitoring is reserved for high-risk segments.

What the AMLR requires of AI in customer due diligence

The AMLR expressly regulates the use of AI in customer due diligence. Its Article 76(5) allows decisions resulting from automated processes or AI systems, under three cumulative conditions:

  • Limited data. The data processed is limited to data obtained under Chapter III, that is, customer due diligence (Art. 76(5)(a)). For a monitoring agent, you must confirm that OSINT data collected for ongoing monitoring, itself provided for in Chapter III, falls within this scope.
  • Meaningful human intervention. Any decision on whether to maintain a relationship, or to increase or decrease due diligence, is subject to meaningful human intervention (point (b)). The agent proposes, the analyst decides: no automatic change of risk level.
  • Explanation and challenge. The customer can obtain an explanation and challenge the decision, except for the suspicious transaction report (point (c)). Each trigger event therefore keeps its source, its excerpt and its classification.

Two other provisions of the same article weigh on monitoring:

  • Data relating to criminal offences may only be processed if the entity distinguishes between allegations, investigations, proceedings and convictions (Art. 76(3)). An agent that reads the press must therefore assess the nature of each piece of information before presenting it to the analyst.
  • The purpose is strictly limited to fighting money laundering and terrorist financing; any commercial use of the data is prohibited (Art. 76(4)).

The GDPR applies in full to this processing (AMLR, recital 150). The AMLR also refers to the definition of an AI system in the EU AI Act, whose application to a monitoring agent must be analysed case by case.

Register monitoring via API: benefits and limits

For company registers, capture can rely on specialised providers that monitor the companies in a portfolio and notify each change. Topograph, with which Harmoney announced a partnership on KYB data enrichment on 30 March 2026, for example offers a monitoring feature that checks official registers, daily in most countries, and sends a notification classified by change category.

These categories map naturally onto an AML/CFT event catalogue:

  • Beneficial owners or shareholding: verification in the central register, update of the structure, new sanctions screening, PEP check (AMLR Art. 22(7); draft RTS, Art. 11, 17 and 25).
  • Legal representatives and directors: data update, verification of the power of representation (AMLR Art. 22(1); draft RTS, Art. 14).
  • Registered office address or jurisdiction: review, new screening, assessment of geographic risk (AMLR Art. 26(3); draft RTS, Art. 11 and 25).
  • Name or business activity: review, new sanctions screening (draft RTS, Art. 25).
  • Status (liquidation, dissolution) or removal from the register: a relevant fact for the analyst to assess (AMLR Art. 26(3)).

The provider's documentation also reveals limits that a compliant framework must address:

  • The notification indicates the type of change, not the modified data. The updated data must be retrieved to classify the event, then verified through a reliable source.
  • The timestamp corresponds to detection, not to the date of the change. The audit trail benefits from recording both dates when they are known.
  • No filtering is applied: every detected change is notified. Classification by the agent is essential to control the volume.
  • Some data requires the obliged entity's own credentials, for example for the German beneficial ownership register, which is reserved for obliged entities for their own checks.

Using a provider does not transfer responsibility: the entity must always be able to demonstrate that its framework is adequate (AMLR Art. 20(4)) and that its sources are reliable (draft RTS, Art. 8).

Where to start?

Ongoing monitoring of legal entities under the AMLR comes down neither to a review calendar nor to undifferentiated monitoring. It rests on three building blocks:

  • An event catalogue that states what is relevant and what must follow, anchored in the rules and validated by compliance.
  • Detection sources proportionate to the risk: registers, data providers, and the press for the most exposed segments.
  • A traceable processing chain in which automation detects and classifies, and a human verifies and decides.

These building blocks can be built now, without waiting for the final adoption of the draft RTS or for AMLA's final guidelines on ongoing monitoring, which will clarify the expected timeframes.

Ongoing monitoring is about keeping a customer's identity reliable over the life of the relationship, not only at onboarding. Our white paper, From document verification to mastering identity entities, shows how to do that under the AMLR.

Harmoney EN

Frequently asked questions

What is ongoing monitoring under the AMLR?

It is the obligation to keep monitoring a business relationship after onboarding: checking that transactions match what you know about the customer, updating its file periodically (at least once a year for high-risk customers, at least every five years for the others) and reviewing it when relevant circumstances change (AMLR Art. 26).

Is an annual KYB review enough under the AMLR?

No, and it never was. The periodic review (at least once a year for high risk, at least every five years for other customers) must be supplemented by a review at each relevant change in the customer's situation, or each relevant fact the entity becomes aware of (AMLR Art. 26(2) and (3)).

Do company registers have to be monitored daily?

No rule requires it. The obligation is to react to known relevant changes and to demonstrate that the framework is commensurate with the risks. Automated register monitoring is a proportionate means for the most exposed segments.

Does a change of beneficial owner require a new sanctions screening?

Yes. AMLA's draft RTS, still to be adopted, expressly lists a change of beneficial owner among the events that trigger a new screening, with no exemption for low-risk customers (Art. 25).

Does a company have to inform its bank of a change of beneficial owner?

Not spontaneously. It provides this information during customer due diligence and must record the change in the central register within 28 days (AMLR Art. 63). A contractual clause can, however, require it.

Can an AI decide on its own the level of due diligence for a customer?

No. Any decision to maintain a relationship or to change the extent of due diligence must be subject to meaningful human intervention, and the customer must be able to obtain an explanation (AMLR Art. 76(5)).