N D Savla & Associates assists banks, NBFCs, mutual funds, and insurance companies with CKYCR Registration and ongoing Central KYC Registry compliance in India. The Central KYC Registry is a centralised repository of customer KYC records for the financial sector, governed by the Central Registry of Securitisation Asset Reconstruction and Security Interest of India (CERSAI) under the Prevention of Money Laundering Act. Every regulated entity onboarding customers is expected to be part of this system, and CKYCR registration is usually one of the first compliance steps a newly licensed financial entity has to complete before it can start onboarding customers in the ordinary course.
This page explains what CKYCR registration involves, which entities are required to register, how the registration and ongoing upload process works, and what happens when reporting entities fall behind on their obligations. If your entity has recently been licensed by RBI, SEBI, or IRDAI and hasn't completed CKYCR onboarding yet, this is where to start.
?? Note: CKYCR registration is not a one-time formality. Once onboarded, a reporting entity has to keep uploading, verifying, and correcting customer KYC records on an ongoing basis — the registration is the starting gate, not the finish line.
What Is the Central KYC Registry and Why Was It Created?
Before CKYCR existed, a customer opening accounts with multiple banks, mutual funds, and insurers had to submit the same KYC documents separately to each institution, and each institution stored that data independently. CERSAI was tasked with building a single centralised registry so that once a customer's KYC is verified and uploaded by one regulated entity, every other regulated entity can retrieve that same verified record instead of repeating the process from scratch. The customer receives a 14-digit KYC Identifier Number (KIN) once their record is successfully registered, which can then be used across the financial sector.
For reporting entities, the benefit runs the other way: once a customer's KIN exists, onboarding becomes faster because the KYC data doesn't need to be freshly collected and verified every time. But that benefit only exists because participating institutions are obligated to upload accurate, verified records promptly — which is exactly where CKYCR compliance work, rather than a one-time registration, becomes an ongoing responsibility for the reporting entity.
Which Entities Are Required to Register with CKYCR?
CKYCR registration applies to every entity that qualifies as a “reporting entity” under the PMLA and its associated KYC Master Directions issued by the relevant regulator:
- Scheduled commercial banks, cooperative banks, and NBFCs onboarding individual or corporate customers.
- Asset management companies, mutual fund distributors, and registrars collecting investor KYC as part of fund subscriptions.
- Life, general, and health insurance companies regulated by IRDAI that collect KYC at the policy issuance stage.
- Payment system operators and other financial intermediaries specifically brought within the reporting entity definition by their sectoral regulator.
If your entity falls into any of these categories and hasn't yet registered with CERSAI, this is usually flagged during a regulatory inspection or audit before it becomes a problem on its own — registering proactively avoids that conversation entirely.
What Our CKYCR Services Include
- CKYCR Registration: end-to-end assistance identifying the correct reporting entity category and completing entity-level registration with CERSAI.
- KYC Upload Support: setting up a structured, repeatable process for uploading and validating customer KYC data as new customers are onboarded.
- Portal Access & Credential Setup: coordinating activation of CKYCR portal credentials so the compliance team can begin uploading records without delay.
- Documentation Review: checking that KYC documents being uploaded meet CERSAI's format and verification standards before submission, reducing rejection and rework.
- Ongoing Compliance Support: managing periodic updates, corrections, and re-verification when customer details change or documents expire.
- Regulatory Liaison: responding to CERSAI or regulator queries on behalf of the reporting entity where discrepancies are flagged.
Our CKYCR Registration Process
- Identify the entity's reporting category — bank, NBFC, mutual fund intermediary, or insurer — since this determines the applicable onboarding pathway.
- Prepare the registration documentation required by CERSAI, including entity constitution documents and regulator licence details.
- Submit the CKYCR registration application through the designated CERSAI process for the entity's category.
- Complete portal access setup and credential activation once the registration is approved.
- Begin KYC upload and reporting for new customers, with a structured internal process for ongoing accuracy checks.
Documents Typically Required for CKYCR Registration
- Certificate of incorporation and constitution documents of the reporting entity.
- Copy of the regulatory licence or registration certificate — RBI NBFC licence, SEBI intermediary registration, or IRDAI licence, as applicable.
- PAN and GST registration details of the reporting entity.
- Details of the designated compliance officer responsible for CKYCR reporting.
- Board resolution authorising the entity's registration and designating signatories for the CERSAI portal.
Ongoing CKYCR Compliance Obligations
Registration is only the beginning. Once onboarded, a reporting entity must upload new customer KYC records within the timeline prescribed under the KYC Master Directions, verify and validate documents before upload, and update records whenever a customer's details change — an address change, a document renewal, or a name change following marriage, for instance. Entities also need a process for periodic re-KYC, since regulators require refreshed verification at defined intervals depending on the customer's risk category.
The compliance burden here is less about the initial registration and more about building a repeatable internal workflow that survives staff turnover — a common failure point is when the one employee who understood the CKYCR upload process leaves and the backlog starts building quietly until an inspection surfaces it.
What Happens If CKYCR Compliance Is Neglected?
Failure to register or maintain CKYCR compliance is treated as a PMLA compliance gap, and regulators — RBI for banks and NBFCs, SEBI for mutual fund intermediaries, IRDAI for insurers — actively check CKYCR compliance during routine inspections. Persistent non-compliance can result in regulatory action against the entity, ranging from formal warnings to monetary penalties, and in serious cases can affect the entity's standing when it applies for other regulatory approvals or licence renewals.
How CKYCR Fits Into a Broader AML Compliance Framework
CKYCR registration rarely sits in isolation from an entity's other anti-money laundering obligations. The same customer onboarding data feeding a CKYCR upload is also relevant to an entity's FIU-IND registration and transaction reporting obligations, since both frameworks rely on accurate, verified customer identification as their starting point. Entities that treat CKYCR as a standalone task, separate from their broader KYC and AML policy, often end up maintaining duplicate or inconsistent customer records across systems, which surfaces during a regulatory inspection as a broader control weakness rather than an isolated filing gap.
A well-run compliance function typically brings CKYCR upload, periodic re-KYC, and transaction monitoring under one internal owner, with a single source of truth for customer identity data. This isn't a regulatory requirement in itself, but it's the practical difference between an entity that handles a CERSAI query in an afternoon and one that spends weeks reconstructing which version of a customer's KYC record is actually current.
What to Expect: Timeline and Common Setup Costs
Most entities underestimate the internal effort CKYCR onboarding takes, focusing on the registration paperwork while underestimating the process design work needed to upload records accurately at volume. Entity-level registration itself is usually the quicker part; building a repeatable, error-checked upload workflow that a compliance team can run without constant escalation typically takes longer and is where most engagements spend the bulk of their time.
For newly licensed entities, we recommend starting CKYCR registration in parallel with FIU-IND registration and the broader KYC policy drafting, rather than sequencing them one after another, since all three draw on the same underlying customer data architecture. Treating them as a single coordinated setup exercise, rather than three separate compliance projects, is usually faster and produces a more consistent internal process.
Frequently Asked Questions
Is CKYCR registration mandatory for all NBFCs?
Yes. NBFCs onboarding customers are classified as reporting entities under the PMLA framework and are required to register with CERSAI and upload customer KYC records to the Central KYC Registry as part of their standard compliance obligations.
What is a KYC Identifier Number (KIN)?
A KIN is a unique 14-digit number allotted to a customer once their KYC record is successfully registered on the Central KYC Registry, allowing that verified record to be reused across participating financial institutions without repeated documentation.
How long does CKYCR entity registration typically take?
Timelines depend on how quickly the entity's documentation is ready and how CERSAI processes the specific reporting entity category, but registration typically takes a few weeks from submission of a complete application to portal access being activated.
Do existing customers need to be re-registered under CKYCR?
Entities are generally required to upload existing customer KYC records progressively, in addition to new customers going forward, following the timelines and prioritisation set out in the applicable KYC Master Directions for their sector.
What happens if KYC records uploaded to CKYCR contain errors?
Errors identified during CERSAI's validation process are flagged back to the reporting entity for correction. Entities are expected to promptly correct and re-upload inaccurate records, since uncorrected discrepancies can affect the reliability of the shared registry and draw regulatory attention.
Does CKYCR registration replace the need for FIU-IND registration?
No. CKYCR and FIU-IND registration serve different purposes and are both independently mandatory for a reporting entity — CKYCR centralises customer identity records, while FIU-IND registration enables statutory transaction reporting such as Cash Transaction Reports and Suspicious Transaction Reports.