Guide · Re-KYC
Periodic re-KYC: running it by risk segment, without branch queues.
Re-KYC season often means customers queuing at branches to confirm details that have not changed, and accounts restricted when they do not come.
Periodic re-KYC is the routine update of customer identity and address information at intervals set by risk category under the institution’s KYC policy.
Segment before you send anything
| Segment | Typical route |
|---|---|
| No change in details | Self-declaration on a digital channel, where your policy allows |
| Change in address or details | Updated documents sent and read digitally |
| Higher risk or unclear cases | Review by a person, or a branch visit |
| No response | Reminders, then branch lists for follow-up |
How to run a re-KYC campaign
- Pull the list of customers due, with their risk category.
- Split them into segments by risk and by whether details are likely to have changed.
- Message each segment on WhatsApp with the right ask: confirm, or send documents.
- Read documents as they arrive and match them to the customer record.
- Send exceptions to a person, with the reason.
- Track progress by segment and send reminders.
- Give branches a list of customers who still need a visit.
- Keep every step in the audit log.
KYC requirements, periodicity and acceptable documents are set by your regulator and your own board-approved policy; confirm them with your compliance team.
How AutoKYC does it
AutoKYC handles onboarding and periodic re-KYC for banks, NBFCs and insurers. Customers send documents on WhatsApp, the web or at a branch; ID, address and income documents are read on arrival, and name, date of birth and address are matched to the application. Anything missing is asked for in the same conversation, and a video-KYC slot can be booked there too. PAN, CKYC and account-aggregator checks run where you allow them. Your policy rules and bands are applied the same way every time; outside the band a person decides, and only the exceptions reach a person, with the reason. Below threshold, maker-checker requires a second person to approve before anything is written to your core, and it writes only through the APIs you open; it is read-only by default, with a kill switch per agent. Re-KYC runs on WhatsApp by risk segment, and every read, decision and write is in one audit log. It runs on managed cloud, in your VPC or on-premises.
Questions
What is periodic re-KYC?
The routine update of customer identity and address information at intervals set by risk category under the institution’s KYC policy.
Can re-KYC be done without visiting a branch?
For many customers, yes: a self-declaration where nothing has changed, or updated documents sent digitally, where the institution’s policy allows. Others may still need a branch visit.
How should re-KYC campaigns be segmented?
By risk category and by whether the customer’s details have changed, so each group gets the right request.
See it on your own data. AutoKYC — Onboarding in hours, on WhatsApp. Book a 30-minute working session with an engineer.