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.
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.
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.
This is the question most compliance teams are asking. The rules answer it in two points.
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.
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.
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:
This event catalogue, validated by compliance, becomes the cornerstone of the framework: it states what triggers a review, and which actions follow.
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:
To reduce this delay, change detection becomes a central operational issue, in the logic of perpetual KYC.
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:
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:
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:
Two other provisions of the same article weigh on monitoring:
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.
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:
The provider's documentation also reveals limits that a compliant framework must address:
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).
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:
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.
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).
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)).
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.
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).
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.
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)).