Every bank promises its supervisor that it reviews its customers periodically, more often the riskier they are. Most banks then discover a backlog: reviews scheduled by calendar quarter rather than by risk, high-risk customers overdue while low-risk files are refreshed on time because they are easy, and nobody sure which customers are next. Periodic review is a scheduling problem before it is an analysis problem.

In short

  • The cycle follows the rating. In the demo’s illustrative policy, high-risk customers are reviewed every year, medium every two, low every three. The bank sets its own.
  • The book knows who is next. Every customer has a last review and a next one, computed from the rating. Due, overdue and in review are filters, not a spreadsheet.
  • A due review is one click from a case. “Start review” opens a periodic-review case with the customer’s current documents and parties, and the agents prepare it like an onboarding.
  • The outcome resets the clock. When the review is decided, the new rating sets the next due date.

The situation

The case uses InsightKYC’s demo data for Harbourline Bank, a fictional bank. The customer book is synced from the bank’s customer records. On the day of the demo it holds:

383customers in the bookDemo data
374current: the next review is not yet dueDemo data
7with a review due in the next 60 daysDemo data
2with a review overdueDemo data
33rated high riskDemo data

The two overdue customers show why the cycle has to follow the rating:

CustomerRatingLast reviewNext reviewStatus
Redwood Trading LLC (C000485)Medium27 Sep 202427 Sep 2026Overdue
Silverline Engineering LLC (C000431)Low5 Nov 20234 Nov 2026Overdue

Two years after a medium rating, three after a low one. Each next date comes from the rating, not from a calendar someone filled in.

The customer book: counts of customers, current, due in 60 days, overdue, high risk and in review, and a table of customers with segment, risk, last review, next review, status and a Start review button
The customer book. Every customer’s rating, last review and next one. Filters for due, overdue and in review; a Start review button on each row.

Why backlogs build

  • Calendar scheduling. Reviews batched by quarter or by anniversary of account opening ignore that a customer’s rating may have changed since.
  • Easy files first. When a team is measured on volume, it finishes simple low-risk refreshes and the hard high-risk reviews age.
  • Starting is expensive. A review starts by gathering what the bank already has: documents, owners, prior screening, the last rating. If that takes an hour, the review waits.
  • No single list. Due dates live in a spreadsheet or a report that is stale the day after it runs.
TODAY A spreadsheet of due dates

Someone exports the due list monthly. The analyst assembles the file from three systems before the review can begin.

WITH INSIGHTKYC A live book and a prepared case

Due and overdue are filters on the live book. Starting a review opens a case with the customer’s parties and documents, and the agents prepare it before the analyst opens it.

How InsightKYC handles it

yes

Customer book
rating, last review

Next review
1, 2 or 3 years by rating

Due or overdue?

Start review
periodic_review case

Agents prepare
read, check, screen, rate

Analyst and lead decide

Book updated
new rating sets next date

The loop: a rating sets a date, the date opens a case, the case sets a new rating.

A periodic review is a case like an onboarding, with a different trigger. The agents read the documents on file and flag what has expired or gone stale. The ownership agent walks the registry again, because owners change. The screening agent screens every party against today’s lists. The risk agent rates the customer on current facts. Anything missing becomes a request the analyst can send.

The cases queue: case reference, customer, type, stage, risk rating, owner and due date for onboarding, periodic and event-driven reviews
One queue. Onboarding, periodic and event-driven reviews side by side, each with its stage, rating and due date.

The home page tells each person what needs them: reviews due or overdue in their book, cases waiting, and decisions the agents have prepared.

The InsightKYC home page for an analyst: open cases, cases past their due date, applications waiting, monitoring alerts open, what needs me, and what the agents did
What needs me. The analyst’s home: open work, what the agents prepared, and the reviews due in their book.

Who does what

CustomerKYC analystKYC leadInsightKYCBank's customer recordsCustomerKYC analystKYC leadInsightKYCBank's customer recordsSync the customer book1Next review from each rating2Filters to due and overdue, assigns3Start review on Redwood Trading LLC4Agents read, re-screen, walk the registry, rate5Prepared - stale documents, requests drafted6Sends the request for current documents7Uploads them - read and checked8Submits if high risk9Decides - next review date reset10

The lead manages the order; the agents prepare; the analyst and lead decide.

Running periodic reviews by riskOwners in the tag
1
Sync the bookKYC operations

Pull current customers from the bank’s records. New customers arrive with their onboarding rating.

2
Work overdue first, then due by ratingKYC lead

Filter to overdue, then due in 60 days. High risk before low risk.

3
Start the reviewKYC analyst

One click from the customer row. The case opens with the customer’s parties and documents.

4
Let the agents prepare itInsightKYC agents

Expired documents, changed owners, new screening matches and a fresh rating, all prepared before the analyst reads it.

5
Request what has changedKYC analyst

Send the drafted request for current documents or an updated ownership chart.

6
Decide and resetKYC analyst + lead

Approve, or decide to restrict or exit. The new rating sets the next review date.

The analyst’s choices

What the review findsOutcomeEffect on the book
Nothing material has changedApprove; rating unchangedNext review in the same cycle
The customer is now higher riskApprove with EDD, or restrictShorter cycle from the higher rating
A new owner or a new screening matchWork it as on onboardingThe case stays open until resolved
The customer doesn’t respondEscalate under the bank’s exit policyRecorded; the relationship decision is a lead’s

What it means for each audience

For the CCO & MLRO

A risk-based approach means the riskiest customers are reviewed most often. The book shows whether that is true today, and overdue high-risk reviews are a number, not a surprise.

Each review leaves a decision record like an onboarding.

For the KYC operations lead

The lead sees the whole book and assigns by risk. The analyst starts from a prepared case, not a blank file.

Requests for refreshed documents are drafted already.

For the board

“Are we up to date with our high-risk customers?” has a one-line answer: how many are overdue, and since when.

It is one of the first questions a supervisor asks.

Metrics to track

Overdue by ratingreviews past due, split by high, medium and low risk
Due in 60 daysthe pipeline the team must clear to stay current
Review timefrom Start review to decision, by rating
Rating changesreviews that changed the customer’s rating, and in which direction

What to be careful about

  • The cycle is policy. One, two and three years are illustrative settings for a fictional bank. Some regimes and some banks set different cycles, and some customers need trigger-based reviews in between.
  • Events don’t wait for the calendar. A monitoring alert, a new adverse media article or a change of ownership should open an event-driven review whatever the due date.
  • The book is only as good as the sync. If closed accounts stay in the book, the overdue count is wrong. Sync often.
  • Don’t refresh for the sake of it. A review that copies last time’s conclusion without re-screening is not a review.

Review the riskiest customers most often, and be able to prove you do.

Let the rating set the date, let the date open the case, and let the case set the next rating.

Keep reading