A KYC periodic review is more than an annual reminder: it is a documented process for confirming that customer information, ownership, risk ratings, and monitoring decisions remain reliable. This guide provides a risk-based KYC refresh workflow, review triggers, evidence checklist, customer-contact template, and escalation framework that compliance and technology teams can adapt to their jurisdiction, products, and documented risk appetite.
Overview
Customer due diligence does not end when an account is approved. Customer information can become outdated, beneficial ownership can change, sanctions exposure can emerge, and account activity can stop matching the original risk assessment. A periodic review gives the business a controlled way to identify and resolve those changes.
There is no universal review interval that fits every business or customer. The appropriate cadence depends on the organization’s risk assessment, customer type, products and services, delivery channels, transaction patterns, jurisdictions, and applicable legal or regulatory expectations. A useful policy therefore combines:
- Scheduled reviews: recurring checks based on the customer’s assigned risk tier.
- Event-driven reviews: earlier reviews triggered by a material change or alert.
- Continuous or recurring monitoring: screening and activity controls that can surface new information between scheduled reviews.
- Quality assurance: testing that confirms reviews are completed consistently and supported by evidence.
The goal is not to request every document from every customer at every interval. The goal is to collect and verify enough current information to support the customer’s risk classification, monitoring approach, and decision to maintain, restrict, or close the relationship.
Before implementing a schedule, compare it with the rules and official guidance applicable to your business. Document why each tier has its cadence, what counts as a material change, who approves exceptions, and how long records are retained. Your KYC onboarding process should connect directly to this ongoing review workflow.
What to track
Customer and identity information
Track whether core identity information is complete, internally consistent, and still appropriate for the relationship. Depending on the customer type, this may include legal name, date of birth or incorporation, address, nationality or country of operation, registration details, contact information, and the identity of authorized representatives.
For individuals, an expired identity document may require a refresh, but it should not be treated as the only review signal. For businesses, confirm that registration information, directors, authorized signatories, ownership percentages, and beneficial owners remain current. When document verification or OCR is used, retain the result and any manual-review rationale rather than relying only on a pass or fail status. See the document verification security checklist for related control considerations.
Ownership, control, and purpose
Ownership and control changes can alter the customer’s risk profile even when the account’s transaction volume has not changed. Track changes to beneficial owners, control structures, senior management, authorized users, business activities, expected transaction types, source of funds, and source of wealth where relevant to the risk assessment.
Compare the current profile with the original stated purpose of the relationship. A customer whose business model, geography, counterparties, or expected payment flows have materially changed may need a new risk assessment and enhanced due diligence.
Screening and activity signals
Maintain a record of sanctions, politically exposed person, adverse media, and other screening results, including the search date, data used, disposition, reviewer, and escalation outcome. Screening tools can support the process, but a potential match still requires controlled investigation and a documented decision. The AML screening tools comparison covers evaluation questions for these capabilities.
Track unusual activity, rapid changes in transaction volume, unexpected locations, new high-risk counterparties, repeated failed verification attempts, account takeover indicators, and activity inconsistent with the customer’s stated purpose. A review triggered by activity should assess whether the issue is a data-quality problem, a legitimate change, a fraud concern, or a potential suspicious activity matter. Keep those decisions separate where required by internal procedures or applicable law.
Evidence and decision fields
A review record should make the decision understandable to another trained reviewer. At minimum, capture:
- Review date, customer identifier, risk tier, and assigned reviewer.
- Information and documents requested, received, verified, or still outstanding.
- Screening and monitoring results considered.
- Changes identified and their effect on the risk assessment.
- Decision, rationale, approver, conditions, and next review date.
- Customer communications, failed contact attempts, restrictions, and closure actions where applicable.
Cadence and checkpoints
A practical model uses three broad risk tiers. The labels and intervals below are planning examples, not a substitute for jurisdiction-specific requirements or a documented enterprise risk assessment.
| Risk tier | Planning approach | Typical review focus |
|---|---|---|
| Lower risk | Periodic refresh at a longer, policy-defined interval, with monitoring between reviews | Core identity, contact details, expected activity, document status, screening, and material changes |
| Standard risk | Regular scheduled review with defined reminders and quality checks | Full customer profile, ownership or control, purpose, activity consistency, screening, and risk rating |
| Higher risk | More frequent review and closer management oversight | Enhanced due diligence, source information, ownership, adverse information, transaction patterns, and documented approval |
Use a calendar that starts before the due date rather than on it. For example, create a preparation window, a customer-response window, a review-and-approval window, and an escalation deadline. Automated reminders should create tasks, not automatically mark a customer as reviewed.
Event-driven checkpoints
Start an earlier review when any of the following occurs:
- An identity document expires, becomes unreliable, or conflicts with other information.
- Beneficial ownership, directors, authorized users, or control arrangements change.
- A sanctions, PEP, adverse media, or other screening alert requires investigation.
- Transaction behavior is unusual or inconsistent with the customer’s stated profile.
- The customer changes products, services, jurisdictions, business activity, or expected volumes.
- There are repeated login, verification, chargeback, impersonation, or account takeover concerns.
- A failed refresh leaves material information unverified.
For teams using digital identity verification, an event-driven workflow may combine document verification, face verification, liveness detection, manual review, and account controls. Biometric checks should be proportionate and governed by applicable privacy and data-protection requirements; they should not be added merely because a system supports them. For implementation considerations, review Biometric Data and GDPR Compliance.
How to interpret changes
Not every change requires account closure or the same level of escalation. Use a decision framework that separates the facts from the response.
| Change or trigger | Initial action | Possible outcome |
|---|---|---|
| Expired document with otherwise consistent information | Request an acceptable replacement and record outreach | Complete refresh, temporary restriction, or escalation if not resolved |
| Ownership or control change | Reverify affected parties and reassess customer risk | Maintain, apply enhanced due diligence, or escalate for approval |
| Potential sanctions or PEP match | Pause automatic disposition and investigate the match | Clear false positive, enhanced review, restriction, or further reporting decision |
| Unusual activity | Compare activity with profile and review relevant evidence | Update profile, increase monitoring, escalate, or apply controls |
| Customer fails to respond | Follow documented contact attempts and deadline rules | Restrict services, place relationship on hold, or close with approval |
Escalation should be based on materiality, not simply on the presence of a data mismatch. A minor formatting discrepancy may be resolved through a controlled correction. A newly identified beneficial owner, unexplained high-risk activity, or unresolved screening concern generally deserves a documented second-level review.
Use a customer message that is clear without disclosing sensitive monitoring logic:
We are reviewing your account information to keep our records current. Please provide the requested information by [date] through [approved secure channel]. If your business activities, ownership, authorized users, or contact details have changed, include those updates. We may be unable to provide some services until the review is complete. Contact [support route] if you need assistance.
Do not request identity documents through ordinary email or an unapproved channel. Apply access controls, encryption, retention rules, and deletion procedures to documents and biometric data. Also maintain a clear audit trail when an automated identity verification or screening result is overridden by a human reviewer.
When to revisit
Revisit this workflow on a recurring schedule and whenever the variables that support it change. A monthly operational check can review overdue refreshes, failed customer contacts, unresolved alerts, manual overrides, and upcoming workload. A quarterly management review can examine completion rates by risk tier, aging of exceptions, repeat failure patterns, quality-assurance findings, and whether risk ratings are changing as expected.
Update the policy and system design when applicable laws, regulator guidance, sanctions or screening requirements, retention expectations, products, customer segments, jurisdictions, or risk appetite change. Also revisit the workflow before an internal audit, after a material incident, during a major onboarding-system change, or when replacing identity verification software or AML screening tools.
Practical implementation checklist
- Define risk tiers and document the factors that assign each customer to a tier.
- Set scheduled review intervals only after checking applicable local requirements and internal policy.
- List event triggers and map each one to an owner, service restriction, escalation route, and evidence requirement.
- Configure reminders, response deadlines, exception queues, and approval controls in the case-management system.
- Use a consistent evidence matrix for identity, ownership, screening, activity, outreach, and final decisions.
- Test a sample of completed reviews for accuracy, timeliness, rationale, and secure handling of personal data.
- Review metrics monthly or quarterly, then revise procedures when recurring failures indicate a control-design problem.
A well-run KYC periodic review process should make the customer record more accurate, the risk decision more defensible, and the next action easier to identify. Treat it as a living control rather than a calendar task, and align every refresh with the organization’s documented risk assessment and current compliance obligations.