A customer file can be within its scheduled review date and still be materially out of date. Ownership may have changed, a business may have entered a new market, or actual account activity may no longer match the purpose established at onboarding. Effective KYC therefore needs both a review timetable and a reliable way to react when the facts change.
For UK regulated firms, regulation 28 of the Money Laundering Regulations includes ongoing transaction scrutiny and keeping due-diligence information current. The FCA’s April 2026 CDD findings provide supervisory context. Neither source makes a bank’s internal review calendar a substitute for responding to material changes.
Assign a different purpose to each type of review
Scheduled reviews check whether the accumulated customer record remains coherent. They can examine ownership, expected activity, documents, risk classification and outstanding questions together. Event-triggered reviews address a specific change and determine whether it requires a targeted update or a broader reassessment.
Designing these as separate purposes prevents two common problems. One is waiting for the next periodic review after a serious change. The other is restarting an entire customer review for every minor update, consuming capacity without materially improving understanding. The bank should define which changes require immediate assessment, which permit focused updates and which can be processed routinely.
No universal annual, three-year or five-year cycle should be assumed across all institutions and jurisdictions. Review frequencies need an applicable legal basis, a documented risk rationale and a mechanism for exceptions. An operational deadline should identify its source rather than being presented as a statutory deadline by default.
Make the trigger travel from the source to the reviewer
A trigger is only useful if somebody receives and acts on it. Map the complete route from an originating event to the KYC workflow. Possible sources include customer notifications, relationship-manager contacts, registry information, investigations and changes in product use. Define the information each source must provide and the person responsible for deciding its significance.
Give each trigger a persistent identifier. Record when it occurred, when it became known to the bank, when it entered the queue and when the review concluded. These dates answer different questions. A queue can appear timely even though the event took weeks to reach it.
Build reconciliation around the originating population. If a system records 400 ownership-change events but only 380 review cases exist, the missing twenty deserve explanation. Looking only at completed KYC cases cannot reveal triggers that never entered the process.
A hypothetical change in customer activity
Consider an importer whose account was opened for domestic supplier payments. It begins using cross-border services and notifies the relationship manager of a new shareholder. The existing file has another year before its periodic review date.
A proportionate response is to assess the new ownership and payment activity promptly, identify whether the customer’s risk profile has changed and update the relevant monitoring context. Depending on the facts and applicable requirements, the assessment may justify a full refresh. It should not be postponed merely because the original review is still marked current.
The reviewer should also examine the prior record. Was the expansion discussed at onboarding? Was the ownership change already captured elsewhere? Reusing reliable information reduces unnecessary customer requests while preserving the rationale for the final decision.
Close the review with an operational outcome
Completion requires more than attaching documents. Confirm that revised information reached the customer master record, the risk rating and relevant downstream controls. An updated ownership chart that never changes the screened-party population is an incomplete implementation.
Where information remains outstanding, record a decision with an accountable owner, an expiry and the applicable conditions. Customer communications should explain what is required in clear language, subject to confidentiality and reporting restrictions. Repeated requests for information already supplied create friction and can obscure the real gap.
Measure trigger capture, time to assessment, incomplete downstream updates and repeat file defects. Use separate reporting for periodic reviews and event-driven cases so that clearing one queue does not hide deterioration in another. The strongest KYC process maintains an accurate understanding of the relationship throughout its life, with the calendar serving as one control among several.

