RBI Tightens Credit Bureau Grievance Norms for Banks
We are re-checking the exact figures on this page against the official RBI text. Until that is done, please rely on the official RBI source cited below.
Current · Source: Reserve Bank of India · RBI/2023-24/73 · issued 26 Oct 2023 · ~2 min read
Quick answerRBI mandates CICs to alert customers via SMS/email when credit reports are accessed, and CIs to alert customers when defaults are reported. Banks must set up nodal officers for CIC grievances, conduct half-yearly root cause analysis, and explain data correction rejections. Compliance is mandatory for all credit institutions, effective six months from October 26, 2023.
The rule, in the simplest words
Credit Information Companies (CICs) must send alerts to customers via SMS or email when their credit report is accessed by authorized users
Credit Institutions (CIs) must send alerts to customers via SMS or email when they report defaults or late payments to CICs
Banks and lenders must appoint a dedicated nodal officer to handle customer grievances related to CICs and conduct regular root cause analysis of complaints
Clear reasons must be provided to customers when their requests to correct credit report data are rejected
How it plays out — a real example
A customer service officer at a bank in Mumbai will now send an SMS alert to a customer when their credit report is accessed by a loan officer, and another alert when the customer's late payment is reported to a credit information company. This increased transparency will help the customer stay on top of their credit history and resolve any disputes quickly.
What changed
RBI now requires CICs to send SMS/email alerts to customers when their credit information report is accessed by specified users, and CIs to send alerts when default/days past due data is submitted to credit information companies. Banks must appoint dedicated nodal officers for CIC grievance redress, conduct half-yearly root cause analysis of complaints, and provide reasons for rejecting data correction requests. CICs must review their search and match logic algorithm every six months with board oversight.
What it means for you
Banks and lenders must upgrade their systems to trigger real-time alerts for credit report access and default reporting, increasing operational costs but improving transparency. The half-yearly root cause analysis requirement pushes top management to actively monitor data quality and grievance patterns, reducing disputes. Clear rejection reasons for data corrections will empower customers and potentially lower complaint volumes.
What you must do
Implement SMS/email alerts for customers when their credit report is accessed by specified users and when default/DPD data is submitted to CICs.
Appoint a dedicated nodal officer for CIC grievance redress and notify CICs of any changes within 5 calendar days.
Conduct root cause analysis of customer grievances at least every six months and review findings annually with top management.
Provide clear reasons to customers when rejecting data correction requests, using the standardized list from CICs.
Organize awareness campaigns to encourage customers to share mobile numbers and email IDs for alert delivery.
Who it affects
All commercial banks including SFBs, LABs, and RRBs, Primary urban co-operative banks, state co-operative banks, and central co-operative banks, All NBFCs including housing finance companies, All-India financial institutions (Exim Bank, NABARD, NHB, SIDBI, NaBFID), Asset reconstruction companies, Credit information companies
Built from our lineage records — each fact carries its provenance; missing history simply is not shown (never guessed).
When must banks send alerts to customers under this circular?
CICs must send SMS/email alerts when a specified user accesses the customer's credit information report. Banks (CIs) must send alerts when they submit default or days past due data to credit information companies.
What is the deadline for appointing a nodal officer for CIC grievances?
The directions come into effect six months from the date of the circular (October 26, 2023), so by April 26, 2024. Changes to the nodal officer must be communicated to CICs within 5 calendar days.
📜 This document’s life story (1 recorded event, each backed by RBI’s own words)
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2023-24/73 · issued 26 Oct 2023. The plain-English explanation above is BankPulse’s own independent summary.
Example: if you are a Compliance officer at a bank this circular applies to (All commercial banks including SFBs, LABs, and RRBs, Primary urban co-operative banks, state co-operative banks, and central co-operative banks, All NBFCs including housing finance companies, All-India financial institutions (Exim Bank, NABARD, NHB, SIDBI, NaBFID), Asset reconstruction companies, Credit information companies), your first concrete step on “RBI Tightens Credit Bureau Grievance Norms for Banks” is: “Implement SMS/email alerts for customers when their credit report is accessed by specified users and when default/DPD data is submitted to CICs.” (RBI issued this 26 Oct 2023).
Circular: RBI/2023-24/73 -- RBI Tightens Credit Bureau Grievance Norms for Banks
Issued: 26 Oct 2023
Action required: Implement SMS/email alerts for customers when their credit report is accessed by specified users and when default/DPD data is submitted to CICs.
Action required: Appoint a dedicated nodal officer for CIC grievance redress and notify CICs of any changes within 5 calendar days.
Action required: Conduct root cause analysis of customer grievances at least every six months and review findings annually with top management.
Action required: Provide clear reasons to customers when rejecting data correction requests, using the standardized list from CICs.
Action required: Organize awareness campaigns to encourage customers to share mobile numbers and email IDs for alert delivery.
Owner: ____________ Target date: ____________
Board/committee approval needed? Y / N
Evidence filed in compliance register on: ____________
Built only from this circular’s own published fields — not legal advice; always confirm against the official RBI source.
💬 Banker Discussion
Discuss this circular with fellow bankers — reply, upvote what helps, report what doesn’t belong. Be professional; no client data. Views are the commenter’s own, not BankPulse’s.
BankPulse Compliance Evidence Pack — generated 03 Aug 2026 · status cross-checked against RBI’s official withdrawal register (refreshed weekly). Official RBI source: https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=12553&Mode=0 — Plain-English summary by BankPulse (bankpulse.ai), reviewed by our expert reviewer, CA Amit Jain. Independent platform, not affiliated with the Reserve Bank of India; is our own plain-English paraphrase, not RBI’s original wording.
Help us keep this accurate
Found an inaccuracy or have an improvement? Tell us. Every report is reviewed by our team before any change is made — nothing goes live unverified.
Public beta — plain-English informational summaries. Always verify against the official RBI source (circular number cited on every page) before making compliance, credit, treasury, audit, or operational decisions. · Join our WhatsApp channel ↗
BANKPULSE · FREE DAILY BRIEF
Get RBI updates for your role
Every important RBI update, decoded in plain English — for your career, exams & financial awareness.
We collect only your email, name and role, used solely to send your brief — never sold or shared. Withdraw anytime via the unsubscribe link in any email. Independent platform, not affiliated with the RBI. Information, not legal advice.
REPORT AN ERROR · BETA
Spotted an error? Earn 500 BankPulse Credits
Help us stay accurate. If your correction is verified true and approved by our founder, you earn 500 BankPulse Credits — redeemable when the platform monetises.
Reviewed by a human before any credit is awarded. We never change the site from crowd input without verification.
WANT A NEW FEATURE · BETA
What would make BankPulse more useful for you?
Tell us what to build next — a tool, a data view, a role page, anything. We read every suggestion.
Thank you — your ideas directly shape what we build.