Periodic reviews were built for paper files: every one, three or five years, depending on risk. Most of those reviews find nothing new, and the changes that matter happen in between.

A high-risk customer reviewed every year can still change owners in month two and be reviewed in month twelve. A low-risk customer reviewed every five years may never change at all. The calendar treats both the same way, and gets both wrong.

What a calendar costs

Periodic review is a backlog that grows by itself. Every new customer adds a future review date. When the team falls behind, files go stale in bulk, and the catch-up project reviews thousands of unchanged files to find the few that moved.

Arcwell, one of the customer stories on this site, had fallen two years behind on periodic reviews. The fix was not more reviewers. It was reviewing the files that had changed, and leaving the others closed with a record of why.

The events that should trigger a review

A new beneficial owner, a registered address that moves offshore, a director who appears on a sanctions list, a sudden change in transaction pattern. Each one is a reason to look again now, not at the next anniversary.

• Change of beneficial owner, director or controlling party.

• Registered address or country of incorporation changes.

• A related party appears on a sanctions or watch list.

• Adverse media that matches the customer after resolution.

• Transaction volume or corridors move outside the declared profile.

• A new product opened that carries a higher risk rating.

• Documents on file expire: passport, license, registration.

The list is short on purpose. Every trigger has to be something a system can detect and a person can explain.

How KYC Refresh works

The KYC Refresh agent watches registries, screening results and account activity. When an event lands, it reopens the file, updates what it can verify, and lists what still needs the customer.

What it can verify, it verifies from the source: a registry for directors and owners, the screening system for list status, the bank's own ledger for activity. It records each update with the date and the source. What it cannot verify, such as a new source of funds or the purpose of a new corridor, it turns into a short request for the customer, drafted for the relationship manager to send.

The agent then recalculates the risk rating with the new facts and shows what moved. An analyst approves the new rating. A rating that goes up never changes silently.

Keeping the triggers honest

Event triggers have their own failure mode: too many of them. A trigger on every small change in transaction volume reopens files every week and recreates the backlog under another name. Each trigger needs a threshold that the team can defend, and a record of how often it fires and how often it finds something.

The KYC Refresh agent reports that for every trigger, every month. A trigger that reopens hundreds of files and changes no risk ratings is a candidate for tuning. A trigger that never fires may be broken, or watching a data source that stopped updating. Both are questions for the team, answered in writing, with the same care as a monitoring rule. Treat the trigger list as part of the program, reviewed and versioned, not as a configuration screen nobody owns.

What examiners will ask

An event-driven program has to show two things: that events are actually detected, and that files without events are not forgotten. Most programs keep a minimum review interval as a backstop, so a file with no events is still looked at, less often.

The record for each file should show the last event, the last review, what was checked and who signed. If the answer to "why was this file not reviewed for four years?" is "nothing changed", the record must show that someone checked.

What changes for the team

Reviews arrive when they are useful, with the reason stated at the top. Low-risk files that have not changed stay closed.

Analysts spend their review time on files where something happened. Relationship managers send fewer blanket document requests, so customers hear from the bank when there is a reason. The backlog stops being a single number and becomes a list of events, each with an owner.

What to do on Monday

Take the last 50 periodic reviews your team closed. Count how many found a material change, and for each one, note when the change actually happened. The gap between the change and the review is the case for moving to events.