Last Updated on: 24st August 2026 | Last Reviewed on: 24st August 2026
What to do if your KIN is Wrong or Duplicated
Most problems fall into a few patterns: the KIN not arriving, a duplicate number, incorrect details, a rejected record, or a deactivated identifier. Each has a practical cause and a practical response. Approach the reporting entity that holds the record, and escalate serious cases, such as another person’s data appearing, at once.
KIN number not received
If your KIN did not arrive, common causes are a mobile or email not recorded correctly, a record not being uploaded, rejection of an upload, processing still pending, an existing identifier returned instead of a new one, or a communication failure. Confirm your contact details with the reporting entity and ask it to check the upload status.
Duplicate KIN or duplicate CKYC number
If the same person appears to have a duplicate CKYC number, do not assume both are valid because both show up in reporting entity systems. Ask the entity to investigate, check whether one identifier has been deactivated, stop circulating both numbers, and keep evidence of the complaint. De-duplication is designed to resolve exactly this.
Incorrect details in a CKYC record
If there are incorrect details in the CKYC record, such as a wrong name, date of birth or address, approach a reporting entity with documentary evidence and request an update. The entity verifies the evidence and uploads the correction, and CKYCR updates the central record. The full update route is on the update and correction page.
CKYC record rejected or a deactivated KIN
If a CKYC record is rejected during upload, it has not passed validation checks, and no KIN is generated until the reporting entity corrects the errors and resubmits it. A KIN may be deactivated following duplicate record resolution or another action taken by the registry. Rather than assuming the reason, the customer should ask the reporting entity to confirm the active KIN and explain why the earlier one was deactivated. Once a KIN has been deactivated, it should no longer be used.
KIN and CKYC statuses: an illustrative guide
The following are illustrative operational messages rather than a definitive statutory list. Exact terminology, meaning and remediation steps may differ between CKYCR, institutional systems and sector-specific interfaces. Rely on the explanation given by your reporting entity or CKYCR for your specific case.
Status or message | What it generally indicates |
KYC generated | The identifier has been created for the record |
Pending KYC generation | The record is uploaded but the identifier is not yet issued |
Record rejected | The upload failed validation and needs correction |
Probable match | The record resembles an existing one and needs reconciliation |
Exact match | An existing record already matches, returning its identifier |
Update pending | A change has been submitted but not yet reflected centrally |
Record deactivated | The identifier has been switched off, for example in duplicate resolution |
Existing KIN found | A search located an identifier already held for the customer |
Another person's details appear in your record
Treat this very seriously. Do not circulate or rely on the affected KIN until the reporting entity confirms the correct active record, inform the reporting entity immediately, preserve screenshots and communications, and escalate through the grievance mechanism. Consider the identity-theft risk and monitor your accounts and credit reports. Suspect fraud where you see an unknown mobile or email, an unrecognised photograph, a different PAN or officially valid document, or an unexpected CKYC download alert.
How to raise a complaint
- First approach the reporting entity that holds the record. Provide your name and account details, a masked KIN, the nature of the error, supporting documents, any previous complaint number, and the correction requested.
- Escalate through the institution’s grievance process, which may run through the service desk, a nodal officer, a grievance redressal officer, and the relevant sectoral ombudsman or regulator where applicable.
- Where the issue sits with the registry, use the official CKYCR or CERSAI contact and grievance page rather than named officer details that may change.
Preserve a full evidence trail: the complaint email, ticket number, CKYC card or screenshot, relevant SMS, the date and time of any attempted access, the masked identifier, supporting documents, and the reporting entity’s written response.
Where to escalate by sector
If the reporting entity does not resolve the matter, the escalation route depends on the sector. Use the current grievance page of the institution or regulator rather than a named officer, because contacts change.
Sector | Escalation route to check |
Banks and NBFCs (RBI) | The entity’s grievance redressal officer, then the RBI Ombudsman scheme |
Securities intermediaries (SEBI) | The intermediary’s grievance process, then SEBI SCORES |
Insurers (IRDAI) | The insurer’s grievance cell, then the IRDAI Bima Bharosa portal and the Insurance Ombudsman |
Pension and NPS (PFRDA) | The Point of Presence or intermediary, then the PFRDA grievance mechanism |
IFSC entities (IFSCA) | The entity’s grievance process, then the IFSCA grievance mechanism |
The registry itself | The official CKYCR or CERSAI contact and grievance page |
Are CKYC Errors Piling Up On Your Compliance Desk?
Duplicate KINs, rejected uploads and wrong records land with the reporting entity first. We review how your team detects, corrects and escalates them.
Frequently Asked Questions
Ask the institution to investigate the duplicate, check whether one has been deactivated, and stop using both in parallel. Keep evidence, since duplicate resolution is part of CKYCR’s de-duplication.
Give documentary evidence to a reporting entity you hold an account with and request an update. It verifies and uploads the correction, and CKYCR updates the central record.
The upload did not pass validation, so no identifier is generated until the entity corrects and resubmits the record. Ask the entity what failed validation.
Likely reasons include incorrect contact details, a record not uploaded or rejected, processing pending, or an existing identifier returned instead of a new one. Confirm your details and ask the entity to check the status.
First, you should directly complain to the reporting entity where you completed your KYC, as it is responsible for submitting corrections to CKYCR. If you are not satisfied, use the reporting entity’s grievance process or, where the issue lies with the registry, the official CKYCR or CERSAI grievance channel.
About the Author
Pathik Shah
FCA, CAMS, CISA, CS, DISA (ICAI), FAFP (ICAI)
Pathik is a Chartered Accountant with more than 26 years of experience in governance, risk, and compliance. He helps companies with end-to-end AML compliance services, from conducting Enterprise- Wide Risk Assessments to implementing the robust AML Compliance framework. He has played a pivotal role as a functional expert in developing and implementing RegTech solutions for streamlined compliance.
Reach Out to Pathik
