- +91 80768 85539
- info@expertvuw.com
- Pan-India service available.
Home / NBFC & Fintech / CKYC Compliance for NBFCs
The Central KYC Registry is supposed to mean a customer never re-does KYC across lenders — but that only works if your NBFC’s uploads are accurate and on time. CS Chetna Shoor keeps your CKYCR obligations current so records don’t quietly drift out of sync.
CKYC — the Central KYC Records Registry, operated by CERSAI — is the single registry where every reporting entity, including NBFCs, uploads customer KYC records, so a customer who has completed KYC once can be identified across the financial system through a 14-digit KYC Identifier (KIN) rather than repeating the process at every new institution. For NBFCs, this isn’t optional infrastructure to opt into when convenient — it’s a mandatory upload obligation for every new customer, and an update obligation whenever a customer’s details change.
This page is for NBFCs that need their CKYCR obligations genuinely working — not a one-time integration set up at onboarding and left unmonitored since. Chetna sets up the upload and update workflow and, critically, the ongoing reconciliation between your internal customer records and what’s actually reflected in the registry.
Every new customer's KYC record must be uploaded to CKYCR, not treated as optional
Window to update CKYCR once a reporting entity receives revised customer information
The KYC Identifier used to retrieve an existing customer's record instead of re-collecting documents
The body operating the Central KYC Records Registry
CKYCR templates cover corporate and legal-entity customers, not just individuals
Legal basis for the CKYCR obligation
RBI rejects over 40% of NBFC applications on the first attempt. Here’s what actually causes it.
A customer update recorded in the NBFC's own system but never pushed to CKYCR, or a CKYCR update the NBFC's system never pulls in, creates a divergence that often isn't noticed until an inspection or an audit specifically checks the two against each other.
CKYCR updates are event-driven — tied to whenever a customer's details actually change — rather than falling on a fixed calendar date. NBFCs without a system that flags these changes in real time tend to file the required update late, or sometimes not at all.
Corporate and legal-entity customers require a different CKYCR template than individuals, capturing beneficial ownership details specific to that entity type. Treating a corporate customer's KYC record like an individual's is a common, entirely avoidable filing error.
CKYCR compliance is one piece of a larger compliance picture, not a standalone substitute for it.
The specific, mechanical obligation to upload and keep customer KYC records current in CERSAI's central registry — the focus of this page.
The judgment-based due diligence, risk categorization, and FIU-IND reporting framework this obligation sits inside. See our NBFC KYC/AML Compliance service.
CKYCR compliance is necessary but not sufficient on its own — it's the registry mechanics layer of a complete KYC/AML program, not a replacement for the broader framework.
We review your current upload status and check for any backlog of unfiled or outdated customer records.
Internal customer records compared against CKYCR to identify any existing divergence.
Upload and update workflows built and mapped to the 7-day update window, so changes trigger filings automatically.
Every new customer's KYC record uploaded to CKYCR within the prescribed timeline.
CKYCR updated within 7 days whenever a customer's details change.
A recurring check between internal records and CKYCR, catching drift before it becomes an inspection finding.
CKYCR compliance works best as a continuous discipline, not a one-time integration project.
Regular reconciliation between internal records and CKYCR, not a single setup-and-forget integration.
KIN retrieval built into onboarding, so existing customers aren't asked to re-submit documents unnecessarily.
Coordination with the broader KYC/AML program — see NBFC KYC/AML Compliance.
Ongoing attention to legal entity template requirements as your corporate customer base grows.
CS Chetna Shoor’s team replies within 4 hours on WhatsApp.
CKYC is the Central KYC Records Registry, operated by CERSAI, where every reporting entity — including NBFCs — uploads customer KYC records so a customer’s identity can be verified across the financial system without repeating KYC at every new institution. For NBFCs, uploading new customer records and keeping them updated is a mandatory obligation, not an optional convenience.
A reporting entity must update the CKYCR with revised customer information within 7 days of receiving it. This is an event-driven obligation tied to when the change actually happens, not a fixed annual filing date, which is why NBFCs need a system that flags changes as they occur rather than relying on periodic manual review.
A KIN (KYC Identifier) is the 14-digit number assigned to a customer’s record in the Central KYC Registry. Once an NBFC retrieves a customer’s KIN, it can pull their existing KYC record from CKYCR instead of asking the customer to re-submit documents already verified by another reporting entity.
Yes. CKYCR maintains separate templates for legal entity customers, capturing beneficial ownership details and corporate structure information that don’t apply to individual customers. Filing a corporate customer’s KYC record using the individual template is a common error that creates gaps in the registry.
A divergence between an NBFC’s internal customer records and what’s reflected in CKYCR is treated as a compliance issue during RBI inspection, not a minor data-quality matter — it suggests either uploads or updates aren’t happening on schedule. Regular reconciliation between the two systems is the only reliable way to catch this before an inspection does.
Qualified Company Secretary · ICSI Member · Founder, Expertvuw Management Pvt Ltd
Chetna has guided NBFC promoters through RBI’s COR process end to end, with particular focus on structuring the Net Owned Fund and business plan so the application survives first-round RBI scrutiny rather than coming back with a query.