KYC Periodic Review Orchestration
A scheduled review workflow that sorts customers by risk, requests documents through Botlit and waits for an analyst's decision.
These images are illustrations of the concept, not screenshots of the actual product.
Overview
This concept is a FluidGrids workflow for the periodic know-your-customer review cycle in a bank. Each customer's file has to be reviewed again on a schedule set by their risk, and a review can mean asking the customer for updated documents and recording an analyst's decision. The design envisions the whole cycle as one scheduled run: pick the customers who are due, sort them, request what is missing, wait, and hand each case to an analyst.
In banking and financial services, periodic reviews fall behind when they run on exported spreadsheets and reminder emails. Cases sit in inboxes, customers are chased by hand, and a review that slips past its date may surface only when audit finds it. The difficulty is not one hard decision but hundreds of small ones that no single view keeps track of.
The illustration shows the KYC Periodic Review workflow on the builder canvas, with its active version selected and Validate and Run controls. A daily schedule picks the customers whose reviews are due, a governed query loads each customer profile, and a versioned risk rating rule splits them. Low-risk customers with no changes go to a prepared quick check and an analyst confirmation. Medium-risk customers, and any customer rated high or with changes found, go to a Botlit document request carried to the online banking inbox, then to a wait that resumes when documents arrive through the bank's secure upload, with reminders on day 7 and day 14 and a limit of 21 days, and finally to an analyst review. Most steps carry a count of the sample cases at that point, and a side panel summarizes today's run: customers picked, documents received, cases awaiting an analyst, cases past their review date and the oldest waiting case.
Two other Burdenoff products take part by design. A Botlit assistant is designed to carry the document request to the customer through the bank's own inbox channel and to answer questions such as why a document is needed from a compliance-approved explainer library, with citations. Both paths end in a BigConsole DataSink node for the KYC backlog, which is designed to give the head of KYC a console of every run's status by risk tier and age. In this design, FluidGrids holds the sequence, the rule version and the waiting, Botlit handles the conversation, and BigConsole shows what is slipping before audit does.
What this concept shows
- A daily schedule trigger that selects every customer whose review is due, with the count shown on the node
- A governed query that loads the customer profile before any routing decision
- A versioned risk rating rule that separates low-risk unchanged customers from medium, high-risk or changed ones
- A quick-check path that prepares low-risk cases for an analyst to confirm
- A Botlit document request delivered through the online banking inbox as a custom channel
- A wait step that resumes on secure document upload, with reminders on day 7 and day 14 and a 21-day limit
- Analyst approval steps on both paths, ending in a BigConsole DataSink for the KYC backlog
- A run summary with customers picked, documents received, awaiting analyst, past review date and the oldest waiting case
How it works
- Each morning the schedule fires and the workflow selects the customers whose periodic review is due.
- A governed query loads each profile, and the versioned risk rating rule sorts customers by risk and changes since the last review.
- Low-risk customers with nothing new get a prepared quick check that an analyst confirms.
- Everyone else receives a document request from a Botlit assistant in the online banking inbox.
- The run waits for the customer's secure upload, sending reminders on day 7 and day 14, for up to 21 days.
- An analyst reviews the case and records the decision in an approval step.
- Each case's status is designed to flow to the BigConsole KYC backlog, where the head of KYC can follow it by risk tier and age.
Who it's for
- Heads of KYC and financial crime operations
- KYC analysts and reviewers
- Compliance and risk managers
- Banking operations and automation teams
Illustrations
1 illustration of this concept. Select one to view it full size.
Risk-Routed KYC Review Workflow with Today's Run
The illustration shows the FluidGrids builder with a KYC Periodic Review workflow open on an active version, with Validate and Run controls. A Node Palette groups schedule and webhook triggers, a governed query, a rule, approval and wait actions, and a datasink output. On the canvas, a daily schedule for reviews due feeds a governed customer profile query and a risk rating rule. A low, no-changes branch leads to a quick check and analyst confirmation; medium and high-or-changed branches lead to a Botlit document request via the online banking inbox, a wait of up to 21 days that resumes on secure upload, with reminders on day 7 and day 14, and an analyst review. Both paths end at a BigConsole DataSink for the KYC backlog, and most steps show a sample case count. A side panel summarizes today's run, flags cases past their review date and shows the oldest waiting case with its risk and age, and logs record the schedule firing, rule evaluation and Botlit requests sent.
Topics
- KYC periodic review automation
- customer due diligence refresh workflow
- risk-based KYC review
- KYC document request automation
- KYC backlog dashboard
- know your customer review workflow
- KYC analyst approval workflow
- bank compliance workflow automation
- KYC review reminders
- customer risk rating rules
Related concepts
Visual Decision Rules
Build a process's decision logic as a versioned tree of conditions, scores and outcomes, and test it against sample inputs.
1 illustration
Triggers, Schedules and Webhooks
Decide what starts a workflow — a cron schedule, an incoming request, an API call or a chat message — and keep every trigger under control.
3 illustrations
Datasinks and Live Dashboards
End a workflow with a datasink node and its output flows into a live dashboard that refreshes on a schedule.
2 illustrations
Workflow Library, Versions and Publishing
Track every workflow's status and version, compare and restore past versions, and publish with a pre-flight check that arms triggers.
3 illustrations
Part of an industry solution
This concept appears in a cross-product solution on burdenoff.com — see how it works alongside other Burdenoff products to solve a problem in that industry.
