Customer due diligence

Perpetual KYC

Continuous, event-triggered customer review. AMLR Article 26 sets maximum intervals between updates and requires a review when relevant circumstances change.

Also referred to as: pKYC, event-triggered review

Legal reference: AMLR Article 26

Key points

  • Maximum interval between updates: 1 year (higher risk), 5 years (others) (Article 26(2)).
  • Event triggers apply in parallel (Article 26(3)).
  • An industry term, not defined in AMLR.

The legal basis: ongoing monitoring (Art. 20(1)(f) and Art. 26(1))

Ongoing monitoring is one of the core customer due diligence measures. Article 20(1)(f) requires "conducting ongoing monitoring of the business relationship including scrutiny of transactions undertaken throughout the course of the business relationship to ensure that the transactions being conducted are consistent with the obliged entity's knowledge of the customer, the business and risk profile, including where necessary the source of funds."

Article 26(1) repeats this duty and adds two points:

  • where a relationship covers more than one product or service, CDD must cover all of them;
  • obliged entities in a group must take into account information about the same customer's relationships with other entities in the group.

Maximum review intervals (Art. 26(2))

"In the context of the ongoing monitoring … obliged entities shall ensure that the relevant documents, data or information of the customer are kept up to date."

"The period between updates of customer information … shall be dependent on the risk posed by the business relationship and shall not in any case exceed:

  • (a) for higher risk customers to which measures under Section 4 of this Chapter apply, 1 year;
  • (b) for all other customers, 5 years."
Customer categoryMaximum time between updates
Higher-risk customers under enhanced due diligence (Section 4, Arts. 34–46), including PEPs, their family members and close associates1 year
All other customers5 years

These are upper limits. The text says the period "shall be dependent on the risk posed by the business relationship".

Event-driven reviews (Art. 26(3))

"In addition to the requirements set out in paragraph 2, obliged entities shall review and, where relevant, update the customer information where:

  • (a) there is a change in the relevant circumstances of a customer;
  • (b) the obliged entity has a legal obligation in the course of the relevant calendar year to contact the customer for the purpose of reviewing any relevant information relating to the beneficial owners or to comply with Council Directive 2011/16/EU;
  • (c) they become aware of a relevant fact which pertains to the customer."

This is the part of AMLR closest to what the industry calls perpetual KYC. Reviews are triggered by events, not only by the calendar.

Ongoing sanctions verification (Art. 26(4))

  • Obliged entities "shall regularly verify whether the conditions laid down in Article 20(1), point (d), are met", meaning whether the customer or beneficial owners are subject to targeted financial sanctions, or whether sanctioned persons control a customer that is a legal entity or hold more than 50% of its proprietary rights or a majority interest in it.
  • The frequency "shall be commensurate with the exposure of the obliged entity and the business relationship to risks of non-implementation and evasion of targeted financial sanctions."
  • For credit institutions and financial institutions, this verification "shall also be carried out upon any new designation in relation to targeted financial sanctions."

Other AMLR provisions that feed into continuous review

ProvisionWhat it saysReference
Enhanced monitoring (EDD)EDD measures may include "conducting enhanced monitoring of the business relationship by increasing the number and timing of controls applied"Art. 34(4)(f)
PEPs"conduct enhanced, ongoing monitoring of those business relationships"Art. 42(1)(c)
Simplified due diligenceAllows reduced update frequency and transaction scrutiny, but requires "sufficient monitoring … to enable the detection of unusual or suspicious transactions"Art. 33(1)
Unusual transactionsExamine the origin, destination and purpose of transactions that are complex, unusually large, in an unusual pattern, or without an apparent economic or lawful purposeArt. 34(2)
Beneficial ownership changes (company side)Legal entities must report changes to the central register within 28 calendar days and verify their beneficial ownership information at least annuallyArt. 63(2)
Register discrepancies (obliged-entity side)Report discrepancies with the central register within 14 calendar days of detectionArt. 24(1)

Guidance from AMLA

"By 10 July 2026, AMLA shall issue guidelines on ongoing monitoring of a business relationship and on the monitoring of the transactions carried out in the context of such relationship" (Art. 26(5)).

Check AMLA's website for the current status and content of these guidelines before relying on specific examples of trigger events.

Periodic KYC vs perpetual KYC under AMLR

Periodic review onlyEvent-driven ("perpetual") approach
Meets the Art. 26(2) maximum intervals?Yes, if the intervals are respectedYes, if the intervals are also respected
Meets the Art. 26(3) event triggers?Only if events between reviews are detected and acted onDesigned around detecting events
Sanctions re-verification (Art. 26(4))Must run in addition to the periodic cycleTypically continuous

AMLR does not require any particular operating model. It requires that the Art. 26(2) maximum intervals, the Art. 26(3) triggers and the Art. 26(4) sanctions checks are all met. Obliged entities must be able to demonstrate to supervisors that their measures are appropriate to the risks identified (Art. 20(4)).

FAQ

Is perpetual KYC required by AMLR?

The term isn't used in AMLR. AMLR requires ongoing monitoring (Art. 20(1)(f), Art. 26(1)), maximum update intervals (Art. 26(2)), and event-triggered reviews (Art. 26(3)).

How often must KYC be refreshed under AMLR?

At least every 1 year for higher-risk customers under enhanced due diligence, and at least every 5 years for all other customers (Art. 26(2)). It must also be refreshed sooner when an Art. 26(3) trigger occurs.

What events trigger a KYC review?

A change in the customer's relevant circumstances, a legal obligation that calendar year to contact the customer about beneficial-ownership information or under Directive 2011/16/EU, or becoming aware of a relevant fact about the customer (Art. 26(3)).

How often must customers be screened against sanctions lists?

Regularly, with frequency commensurate with sanctions risk. Credit and financial institutions must also verify upon any new sanctions designation (Art. 26(4)).

When do these rules apply?

From 10 July 2027 (Art. 90).

Sources