Corrected on 3 November 2026. The version published on 5 March 2026 said monitoring runs continuously and finds a new sanctions designation within hours. Monitoring runs on a schedule, so how soon a change is found depends on how often you re-check. It also called the Money Laundering Regulations the FCA's, and made claims about FCA and FATF guidance that we can't source. The section on what regulators require now cites the regulations themselves.
Perpetual KYB, also called ongoing customer due diligence, is the practice of monitoring approved corporate clients throughout the life of the relationship, not just at the point of onboarding. It adds scheduled checks between periodic reviews, so a material change surfaces at the next check instead of the next review.
The term is common in vendor marketing, but what it actually involves in practice — and what regulators specifically require — is less well understood. This guide covers the definition, the regulatory requirements, the events that trigger a review, and how to configure monitoring frequency effectively across a tiered client portfolio.
What perpetual KYB means in practice
Traditional KYB operates on a fixed review cycle. A business is onboarded, its file is opened, and it is scheduled for periodic review — annually for standard risk clients, more frequently for higher-risk ones. Between reviews, the file is largely static. If a director is sanctioned six months after onboarding, the institution may not learn about it until the next scheduled review — or until a regulator asks why action was not taken sooner.
Perpetual KYB changes the underlying model. Between reviews, the platform re-checks the data sources that matter — sanctions lists, PEP datasets, company registries — on a schedule set by each client's risk, and alerts the compliance team when something relevant has changed for a client in their portfolio.
The practical difference is one of latency. A sanctions designation that would have waited for the next annual review is found at the next scheduled re-screen, which for a high-risk client might be a week or a month away instead of a year. A change in beneficial ownership that relied on the client telling the institution is found when the registry is next re-checked.
What regulators require
The regulatory basis for perpetual KYB sits in the ongoing customer due diligence requirements of the major AML frameworks.
FATF Recommendation 10 requires financial institutions to apply ongoing due diligence to business relationships, including scrutinising transactions and keeping customer documents and information up to date.
The UK's Money Laundering Regulations 2017, which the FCA supervises for banks and other financial firms, require ongoing monitoring of every business relationship: scrutiny of transactions, and reviews that keep customer due diligence documents and information up to date (regulation 28(11)). They also require due diligence on existing customers at appropriate times on a risk-based approach, and when a customer's circumstances relevant to the firm's risk assessment change (regulation 27(8)). (Source: MLR 2017, regulation 28)
The EU Anti-Money Laundering Regulation applies directly from 10 July 2027. It caps how long customer information can go without an update: one year for higher-risk customers under enhanced due diligence, five years for everyone else (Article 26(2)). Credit and financial institutions must also check whether their customers are subject to targeted financial sanctions upon any new designation (Article 26(4)). (Source: Regulation (EU) 2024/1624)
The UK regulations leave the frequency of checks to the firm's own risk assessment, and the EU regulation adds those ceilings. Perpetual KYB is how a firm keeps what it knows about a client current between reviews.
What triggers a perpetual KYB review
Perpetual KYB generates alerts when defined events occur for clients in the monitored portfolio. The events that should trigger a review fall into four main categories.
Sanctions list changes
Any addition of a client entity, a director, or a UBO to a sanctions list — OFAC, UN, EU, HM Treasury, or any other list relevant to the institution's jurisdictional footprint — should generate an alert, and a confirmed match needs action without delay. How soon a designation is found depends on how often the client is re-screened, so the re-screening cadence for each risk tier is a policy decision for the MLRO to approve and record. In the EU, from July 2027, credit and financial institutions must also re-check upon any new designation.
This also applies to delistings. An entity removed from a sanctions list may have outstanding restrictions that apply during a wind-down period, or may represent a client whose risk profile has changed in a way that warrants review even in the absence of a current designation.
Beneficial ownership and director changes
Company registry updates — new director appointments, director resignations, changes in persons with significant control, changes in share structure — are material events that may require re-verification or updated risk assessment. A new UBO who appears on a PEP dataset, or a director who is a national of a jurisdiction that has recently been FATF grey-listed, changes the risk profile of the relationship.
Where a registry publishes officers and owners, as Companies House does in the UK, these changes can be found by re-checking the registry on a schedule and comparing who is listed now with who was listed before. The platform alerts the compliance team when it finds a change.
Adverse media
Negative news coverage about a client entity, its directors, or its UBOs may indicate reputational risk, emerging regulatory action, or conduct that is relevant to the ongoing relationship. A perpetual KYB programme re-checks news coverage against the client portfolio and surfaces relevant coverage for analyst review.
The challenge with adverse media monitoring is specificity: filtering genuine adverse media from irrelevant coverage with similar entity names. Effective platforms use entity disambiguation — matching news content against the specific combination of entity name, jurisdiction, and identifiers in the client record — rather than simple keyword matching.
Jurisdiction risk changes
FATF grey-listing and black-listing decisions, changes to the EU's high-risk third-country list, and updates to national regulatory assessments of specific jurisdictions affect the risk profile of clients registered or operating in those jurisdictions. A client whose jurisdiction of incorporation moves onto a FATF list needs a prompt review of its risk assessment. In the UK, since 30 June 2026, a business relationship with a person established in a country on FATF's call-for-action list requires enhanced due diligence (Money Laundering Regulations 2017, regulation 33(1)(b)). A move onto the grey list is a risk factor for the firm's own assessment.
Configuring monitoring frequency by risk tier
Effective perpetual KYB does not apply the same monitoring intensity to every client. A listed company in a low-risk jurisdiction with a simple ownership structure and a long, clean transaction history does not require daily sanctions screening; a private company in a higher-risk corridor with a complex ownership structure and recent adverse media does.
Risk-tiered monitoring works by assigning each client to a monitoring tier at onboarding — or dynamically, as their risk score changes — and applying different check frequencies and alert thresholds to each tier.
High-risk clients — those with elevated risk scores, FATF-relevant jurisdictions, PEP associations, or complex ownership structures — warrant the most frequent monitoring. Sanctions and PEP screening should run daily or on every list update. Registry checks should run weekly. Adverse media should be re-checked on the same cycle.
Standard-risk clients — the majority of a typical corporate portfolio — can be monitored at lower frequency without materially increasing risk exposure. Weekly sanctions screening, monthly registry checks, and regular adverse media checks are a defensible baseline for this tier, subject to the institution's own risk assessment.
Lower-risk clients — simple structures, well-known entities, long-established relationships with clean histories — may be monitored at monthly or quarterly intervals for most checks, with sanctions screening kept frequent regardless of tier.
The monitoring schedule should be configurable without engineering involvement. Compliance policy on monitoring frequency will change as regulatory guidance evolves; the platform should allow compliance teams to update schedules directly.
Building the alert workflow
Monitoring generates alerts. How those alerts are handled is as important as how they are generated.
Effective alert workflows include three components. First, triage: automated assessment of whether an alert represents a confirmed match, a probable match requiring analyst review, or a false positive that can be dismissed. Second, escalation: routing confirmed or probable matches to the appropriate analyst with full context — the specific change detected, the client record, and the relevant history. Third, documentation: a complete, timestamped record of every alert, the triage outcome, and the analyst action taken.
This documentation is not merely good practice. In an FCA examination of a firm's ongoing monitoring processes, the ability to demonstrate that alerts were generated promptly, reviewed in a timely manner, and resolved with appropriate action is the evidence that the process works. Institutions that cannot produce this record face the same risk as those with no monitoring at all: they cannot demonstrate compliance.
Perpetual KYB is not a product feature. It is a compliance obligation, and increasingly an examined one. The question for financial institutions is not whether to implement it, but whether their current approach — annual review cycles, manual checks, spreadsheet-based tracking — is adequate to meet that obligation under the regulatory expectations that now apply.
See automated KYB in practice
Book a demo and walk through a live KYB case from application to decision.
Request a demo →