TL;DR: Event-driven customer due diligence refreshes cut stale records in perpetual KYC, OneID explains, by updating files when address, ownership, transaction patterns or screening results change. KYC controls need governed triggers and a clean baseline so review queues stay current instead of rebuilding backlogs.
Editorial analysis by NHI Mgmt Group, based on content published by OneID: “Perpetual KYC (pKYC): Keeping Customer Due Diligence Current”.
Key questions
Q: When does periodic KYC review fail in practice?
A: It fails when the review cycle is too slow for the pace of customer change.
Q: Should organisations prioritise remediation or perpetual KYC first?
A: Remediation should come first when the existing book is already inconsistent or heavily backlogged.
Q: How should firms decide which KYC changes deserve an immediate refresh?
A: Use a risk-based trigger model.
Practitioner guidance
- Define governed trigger lists Set out which customer events require a KYC refresh, how each trigger is risk-ranked, and what review depth follows from each rank.
- Separate record currency from transaction monitoring Assign identity re-checks to the customer file and keep transaction scrutiny in the monitoring function so the two controls are not conflated.
- Use remediation before perpetual operation Clean the back-book first, then move to event-driven refresh so pKYC does not inherit a backlog of stale or inconsistent records.
Bottom line: Perpetual KYC is an operating model for keeping customer records current, not a new legal duty or a replacement for ongoing monitoring.
Glossary terms: Perpetual KYC, Ongoing Monitoring, Identity Matching, Back-book Remediation
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Perpetual KYC is a record-currency model, not a substitute for ongoing monitoring. The article is clear that transaction scrutiny and customer-record refresh are different obligations, even though both sit inside the same regulatory duty. That distinction matters because many programmes treat review activity as a single control when it is actually two separate ones. Practitioners should design governance so the identity refresh layer, the behavioural monitoring layer, and the case-management layer remain distinct.
A question worth separating out:
Q: How can compliance teams tell whether KYC controls are actually working?
A: Look at the rate of false accepts, false rejects, manual review volume, and post-approval escalations. If approved users later trigger sanctions hits, fraud cases, or repeated verification failures, the control is not providing stable assurance. KYC should improve decision quality without creating unacceptable friction.
👉 Read our full editorial: Perpetual KYC keeps customer due diligence current under AML duty