Perpetual KYC: How Ongoing Monitoring Works and What Examiners Expect
ByVictoria okere
•5mins Read
Key Takeaways
Perpetual KYC (pKYC) keeps customer records and risk ratings current by reacting to changes as they happen, instead of waiting for a scheduled review.
The Central Bank of Nigeria (CBN) Customer Due Diligence Regulations 2023 set review cycles by risk: yearly for high-risk customers, every 18 months for medium-risk and every three years for low-risk.
Perpetual KYC does not replace those cycles. It adds event-driven checks between them, such as a sanctions list update or a sudden change in transaction behaviour.
The CBN's Baseline Standards for Automated AML Solutions, issued on 10 March 2026, require a tamper-proof audit trail of system and user activity.
When assessing a vendor, ask whether existing customers are re-screened automatically, and whether every decision is logged in a way an examiner can follow.
What is perpetual KYC?
Perpetual KYC is an approach to customer due diligence that keeps each customer's information and risk rating up to date continuously. It monitors for events that change a customer's risk, such as a sanctions designation, a new PEP status or unusual transactions. It then triggers a review when one happens, rather than only on a fixed date.
It is sometimes called pKYC, continuous KYC or event-driven KYC. Traditional periodic KYC reviews every customer on a calendar cycle, often by re-collecting documents. Perpetual KYC focuses effort on the customers whose risk has actually changed.
For banks, fintechs, payment companies and gaming operators in Nigeria, this matters because risk does not wait for review dates. This guide explains how perpetual KYC works, what the CBN expects, and the two questions buyers most often ask vendors about it.
Perpetual KYC vs periodic KYC
Periodic KYC
Perpetual KYC
When reviews happen
On a fixed schedule, by risk tier
When a risk event occurs, plus scheduled reviews
What gets reviewed
Every customer due in that cycle
Customers whose risk has changed
How risk is caught
Possibly months after it changes
Close to when it changes
Customer experience
Repeated requests for documents
Fewer requests, targeted to real changes
Main cost
Large review backlogs at cycle dates
Building reliable triggers and data feeds
Periodic reviews still have a place. They catch slow changes that no single event reveals. Our guide toperiodic KYC refresh explains how those cycles work. Perpetual KYC adds a second layer on top.
What triggers a perpetual KYC review?
A trigger is any event that suggests a customer's risk may have changed. The most common are a new sanctions designation or a change to a PEP list, and new adverse media about the customer or its owners. Changes in transaction behaviour also count, such as sudden volume spikes, new countries or new counterparties. Changes to the customer's own details matter too, such as a new address, new directors or a change in ownership.
Each trigger should lead to a defined response. Minor changes may simply update the record. Significant ones should re-score the customer's risk and, where needed, start enhanced due diligence (EDD) or a suspicious transaction report.
For list-based triggers, update speed matters. Our guide towatchlist screening covers how quickly sanctions changes should reach your screening.
What do FATF and the CBN require for ongoing monitoring?
Ongoing monitoring is not optional. The Financial Action Task Force (FATF) Recommendation 10 requiresongoing due diligence on the business relationship and scrutiny of transactions throughout its course. The aim is to ensure transactions are consistent with what the institution knows about the customer, its business, its risk profile and, where necessary, its source of funds. It also says due diligence should apply to existing customers on the basis of materiality and risk.
In Nigeria, theCBN Customer Due Diligence Regulations 2023 set review cycles in Regulation 23(b). High-risk customers must be reviewed every 12 months, medium-risk every 18 months and low-risk every three years, and also whenever the need arises. Regulation 13 adds triggers for existing customers, including significant or unusual transactions and material changes to a customer's profile or how an account is operated.
The CBN has previously required mass revalidation. ADecember 2023 circular required the BVN or NIN on all accounts and wallets to be electronically revalidated by 31 January 2024. Institutions with a perpetual KYC setup could run that against their existing records. Others had to start from scratch.
Can you re-screen existing customers automatically, or only at onboarding?
This is the question that tells you whether a platform supports perpetual KYC or only onboarding. Many tools screen a customer once, at sign-up. After that, the customer is checked again only if someone runs a manual batch.
There are three levels of capability. Onboarding-only screening checks each customer once. Scheduled batch screening re-checks the whole customer base on a fixed cycle, such as nightly or monthly. Event-driven screening re-checks affected customers as soon as a trigger fires, such as a list update.
Perpetual KYC needs the third level, with the second as a backstop. Ask the vendor whether a sanctions or PEP list update automatically re-screens your existing customers, or only new ones. Then ask whether a change in transaction behaviour can re-score a customer's risk without a person starting it.
For business customers, ask whether directors and beneficial owners are monitored too, not just the company. A clean company with a newly sanctioned owner is still a sanctions risk.
Finally, ask how the platform avoids flooding your team. Re-screening a large customer base can generate thousands of alerts. Good systems suppress repeat alerts that were already cleared and use secondary identifiers to cut false positives.
Does the platform keep an audit trail a CBN or NFIU examiner would accept?
This question has become harder to dodge. On 10 March 2026, the CBN issued itsBaseline Standards for Automated AML Solutions (circular BSD/DIR/PUB/LAB/019/002). They require a comprehensive, tamper-proof and immutable audit trail of all system and user activities, and a documented governance framework for the AML solution.
Institutions that use a third-party AML solution must also keep avendor and third-party management policy. It must cover procurement, implementation, support, change management, incident handling and exit. Your vendor's audit trail therefore becomes part of your own compliance evidence.
An examiner reviewing a perpetual KYC decision will want to reconstruct it. What triggered the review, and when? What data did the system hold at that moment? How did the risk score change, and why? Who reviewed the case, what did they decide, and was a suspicious transaction report filed with the Nigerian Financial Intelligence Unit (NFIU)?
Ask the vendor to show you a real case history, not a slide. The record should be time-stamped, unchangeable after the fact, and linked to the customer it concerns. It must also be kept for at least five years after the relationship ends, in line with the CBN Customer Due Diligence Regulations 2023.
Perpetual KYC checklist: questions to ask every vendor
Question to ask
A strong answer
A red flag
Do list updates re-screen existing customers automatically?
Yes, event-driven, with alerts raised the same day
Only new customers, or manual batches
Can transaction behaviour re-score customer risk?
Risk scores update automatically, with the reason recorded
Risk is set once at onboarding
Are directors and owners monitored, not just the company?
Each owner is screened continuously after approval
Company-level screening only
Can review cycles follow CBN risk tiers?
Configurable schedules by risk group, alongside event triggers
One fixed review cycle for everyone
Is the audit trail tamper-proof and complete?
Every trigger, score change, decision and reviewer logged and unchangeable
Logs that can be edited, or decisions kept in email
How do you control alert volume on re-screening?
Cleared alerts suppressed, secondary identifiers used
Every re-screen re-raises old alerts
How Youverify supports perpetual KYC
Youverify due diligence does not stop at approval. The entity record created on day one is the record that gets re-screened, re-scored and re-reviewed for as long as the relationship lasts.
Sanctions, PEP and adverse media screening continue after approval, and business owners stay under continuous monitoring, so a status change reaches you the day it happens. Enhanced due diligence can be scheduled by risk group, so review cycles can follow your own risk tiers.
Every check, its source, its timestamp and the officer who set the final status stay attached to the entity record. Re-screening and status changes append to that same record rather than creating a new one. A match opens a case with the evidence attached. Youverify'stransaction monitoring runs on the same record, so behaviour changes and screening results sit together.
Risk changes after onboarding, and regulators now expect your controls to keep up. Perpetual KYC does that by reacting to real events, while scheduled reviews catch what events miss.
When you assess a platform, ask two things. Does it re-check existing customers automatically? And can it show an examiner exactly what happened, when and why?
About the Author
Victoria Okere is a compliance content writer at Youverify, specializing in AML compliance, financial crime risk, regulatory technology, and emerging trends in financial services.
FAQs
Frequently Asked Questions
Perpetual KYC, or pKYC, is an approach that keeps customer information and risk ratings up to date continuously. Instead of waiting for a scheduled review, it watches for events that change a customer's risk, such as a sanctions designation or unusual transactions. It then triggers a review when one happens.
Periodic KYC reviews every customer on a fixed schedule, such as every one to three years depending on risk. Perpetual KYC reviews customers when an event suggests their risk has changed. Most institutions use both: event-driven checks to catch changes quickly, and scheduled reviews as a backstop.
Under the CBN Customer Due Diligence Regulations 2023, financial institutions must review existing customer records by risk category. High-risk customers are reviewed every year, medium-risk every 18 months and low-risk every three years. Reviews should also happen when risk changes, not only on those dates.
No. Perpetual KYC adds event-driven checks, but scheduled reviews still catch gradual changes that no single event reveals. Nigerian institutions must still meet the CBN's review cycles by risk tier. Perpetual KYC makes those reviews lighter, because most of the record is already current when the review date arrives.
A common way to describe KYC is in five stages. They are customer identification, customer due diligence, enhanced due diligence for higher-risk customers, ongoing monitoring, and record keeping with reporting. Perpetual KYC strengthens the fourth stage, ongoing monitoring, so that the other stages stay accurate over time.
A red flag is a sign that a customer may pose a higher risk. Examples include inconsistent identity details, a match on a sanctions or PEP list, adverse media, reluctance to provide information, and transactions that do not fit the customer's profile. Red flags should trigger further review, not automatic rejection.