The financial sector is moving beyond exclusively calendar-based reviews toward perpetual Know-Your-Customer (pKYC) monitoring. As automation and AI evolve stronger real-time capabilities, the USEU, and UK increasingly expect institutions to operate timely, risk-based monitoring frameworks that respond to material changes in customer profiles and activity. So, the faster and more focused regulatory landscape that regtech and compliance leaders have anticipated for years is starting to arrive. The timing is critical, as compliance violations are costing financial institutions worldwide more than ever.
This transformation can reduce banks’ risk exposure and make money laundering and fraud more difficult. If account freezes and client offboarding decisions are fast but opaque, however, continuous KYC can erode customer experience for trustworthy clients. It’s not enough for financial institutions to upgrade to real-time monitoring for fast detection and response. They also need to ensure that those quick actions are explainable.

What does pKYC do for compliance and bank operations?

Perpetual KYC solves two major problems with legacy customer reviews. Until the AI automation era, the industry standard was to review all customers every two to five years, whether or not their information had changed. This practice wastes resources on reviewing unchanged accounts. It also allows changes in beneficial ownership, legal filings, or transaction velocity acceleration to go undetected for long periods of time between reviews.

Because it compares integrated customer onboarding data and activity to a set of defined trigger events, pKYC allows banks to identify trigger events in real time and prevents the waste of operational resources on low-risk customers.

Building the pKYC infrastructure

These benefits rest on new technology that banks are implementing now or will need to soon, including:

  • Event-driven architectures
  • Continuous customer record updates
  • Stronger entity resolution
  • Automated workflow orchestration

System integration is a strategic capability. Many organisations currently leak risk intelligence at the boundaries between legacy onboarding, transaction monitoring, fraud detection, sanctions screening, and case management platforms that don’t operate as a unified ecosystem.

As data moves between these systems, context and subtle risk indicators can be lost. Tightly integrating onboarding data into new workflows is also critical.

Timing is also a challenge

While internal systems may operate in near real time, many external data sources — such as beneficial ownership databases — update on delayed cycles. A change in ownership may be legally effective immediately but visible in structured data feeds weeks later. In practice, this means institutions have to design their monitoring frameworks with those external timing realities in mind.

Explainable speed is the core pKYC challenge

When a client’s account is flagged or frozen, they deserve to know why and what steps, if any, they can take to resolve the issue. This is similar to the temporary blocks that fraud controls sometimes impose on customer transactions pending verification. Ideally, pKYC works the same way, by combining fast detection with proportionate responses to trigger events.

Proportionality can prevent continuous monitoring from turning into constant customer friction.

Strategically applied AI can use confidence scoring and severity thresholds to determine responses that are calibrated to event severity and confidence in the underlying data.

For example, a low-confidence signal should trigger enhanced monitoring, while a high-confidence signal should trigger step-up verification or direct outreach. Humans should remain in the loop to review all account restrictions and closures. False positives, repeat outreach, and resolution time metrics can inform threshold adjustments to reduce customer friction without sacrificing speed or risk responsiveness.

What continuous monitoring changes for KYC and AML teams

Perpetual KYC doesn’t eliminate the need for KYC and AML professionals, but it does change what they focus on. Until now, most of these analysts’ time has been spent on routine reviews that often show little to no change. As organizations transition to event-driven monitoring and automation takes on more repetitive low-risk tasks, human analysts can focus on work that requires their judgment, such as:

  • complex investigations of layered ownership structures and network-level exposure
  • control testing and threshold calibration
  • continuous improvement of typologies and escalation playbooks

These judgment- and context-focused roles for humans will fall into two categories: in the loop and on the loop. Humans in the loop will review high-impact system decisions, especially account restrictions and offboardings. Those on the loop will monitor the pKYC system models for bias, drift, or unexpected behaviour. These activities can provide a layer of accountability for the system’s signal detection at speed.

Planning for a successful transition to pKYC

Moving from static to dynamic monitoring requires planning early to deal with some common challenges.

Balance speed and accuracy in KYC data. Automated solutions offer speed but usually lack the accuracy of manual sourcing. Unfortunately, manual sourcing is too slow to support real-time monitoring and too costly to scale. Each institution will need to create a sourcing model that meets its needs for both speed and accuracy.

Identify and close coverage gaps. Banks sometimes find jurisdictions missing when they implement global KYC data solutions. Emerging markets and specialised registries are the areas most likely to be left out. It’s important to verify coverage for operating jurisdictions before choosing a vendor.

Create trust hierarchies. Make sure there’s a clear path for resolving conflicting data from different sources, based on each source’s trust level.

Expect integration challenges. Many KYC data sourcing platforms don’t integrate seamlessly with legacy customer lifecycle management systems. Allow time for technical challenges.

Confirm compliance documentation capabilities. pKYC systems need to support proper documentation, data lineage, and audit trails to avoid compliance issues.

Set realistic ROI and time-to-value targets. pKYC system components are unlikely to match ideal performance targets in production. Base evaluation criteria on actual operating conditions.

Addressing these challenges as early as possible paves the way for a smoother transition to pKYC. Banks that plan strategically and methodically for their move from periodic reviews to continuous monitoring can avoid roadblocks and generate fast, explainable decisions that reduce compliance risk without adding customer friction.

Mark Rubin, Associate Principal, Technology & Product Strategy at eClerx