Your next CIC miss won’t wait for the month-end.
It will show up on the 9th. Or the 16th. Or the 23rd. That’s the new reality for every NBFC ops team in India, as set out by the Reserve Bank of India. The old habit of fixing bureau errors “before month close” doesn’t work anymore. There is no single month-end deadline left to hide behind.
If your reject queue is still sitting untouched for two weeks, you’re already behind.
The RBI Rule Behind This Change
On December 4, 2025, the RBI issued the Reserve Bank of India (Non-Banking Financial Companies – Credit Information Reporting) Amendment Directions, 2025, along with matching amendments for banks, Housing Finance Companies, Regional Rural Banks, and other All India Financial Institutions. These amendments become effective from July 1, 2026, after RBI pushed the original April 1, 2026 date back by three months following industry feedback.
The directions revise how Credit Institutions, including NBFCs, must report data to Credit Information Companies (CICs) such as TransUnion CIBIL, Experian, Equifax, and CRIF High Mark. The RBI’s stated aim is to make credit information more accurate, more current, and more useful for underwriting decisions across the financial system.
This is why CIC reporting has become the operations headache of 2026. Under the earlier framework, NBFCs generally reported once a month. Under the amended framework, reporting now happens four times a month, and each submission carries its own timeline.
What the RBI Directions Actually Require
According to the amended directions, NBFCs must report credit information to CICs as on four fixed reference dates every month: the 9th, 16th, 23rd, and the last day of the month.
The RBI splits this into two distinct types of submission:
Full File Reporting. Data as on the last day of the month must be submitted by the 5th day of the following month. The RBI’s directions specify that the full file must include all active accounts in the NBFC’s books, as well as accounts where the relationship between the borrower and the NBFC has ended since the previous reporting cycle — for example, closed loans, foreclosed loans, settled accounts, and matured loans.
Incremental Reporting. For the 9th, 16th, and 23rd, NBFCs are required to furnish only incremental accounts, submitted to the CIC within four calendar days from each reference date.
Under the RBI’s directions, incremental accounts include:
- Accounts opened since the last reporting reference date
- Accounts where the borrower relationship has ended since the last reporting reference date
- Accounts with borrower-initiated changes
- Accounts with overdue payments
Two further requirements sit alongside this revised calendar:
- CKYC reporting, which the amended directions make mandatory wherever the Central KYC number is available for a borrower.
- DAKSH portal monitoring, under which CICs are required to report non-compliant institutions to the RBI’s supervisory DAKSH portal, giving the regulator direct visibility into which NBFCs are missing their deadlines.
The directions also require NBFCs to promptly rectify and resubmit any rejected data, rather than carrying it forward unresolved into the next cycle.
What Changed, In Plain Terms
| Under the Earlier Framework | Under the Amended Directions (Effective July 1, 2026) |
| Monthly full file | Full file by the 5th + incremental files four times a month |
| One reporting reference date | Four reference dates: 9th, 16th, 23rd, month-end |
| CKYC reporting not mandatory | CKYC number mandatory wherever available |
| DPD updated on a monthly cycle | DPD change reportable as part of incremental accounts |
| Limited regulatory visibility on delays | CICs report non-compliance to RBI’s DAKSH portal |
Every one of these changes touches a different part of an NBFC’s operations: the loan management system, the KYC records, the reject-handling desk, and the reconciliation team. That is why a structured, RBI-aligned checklist matters more now than it ever did under the old monthly cycle.
The Practical CIC Reporting Control Checklist
This checklist maps directly to what the amended RBI directions require. It is meant to be run every cycle, every month, by the ops team responsible for CIC reporting.
Build a Reject Management Loop, Not a Reject Pile
The RBI’s directions place direct responsibility on Credit Institutions to rectify rejected data promptly, before the next reporting cycle begins. Under the old monthly rhythm, ops teams had weeks to clear rejects. Under four reporting cycles a month, that time has shrunk sharply.
What to do:
- Assign clear ownership of rejects for each CIC, every cycle. Don’t let rejected records sit unassigned.
- Set an internal SLA shorter than the RBI’s own four-day window, so there’s buffer time before the regulatory deadline.
- Track reject reasons over time. Recurring errors point to a system problem, not a one-off mistake.
- Never let a rejected record roll into the next reporting cycle unresolved. That’s precisely what the RBI’s directions ask NBFCs to avoid.
Get CKYC Numbers Right, Not Just Present
The amended directions make CKYC reporting mandatory wherever the number is available for a borrower. This depends heavily on how completely CKYC data was captured at onboarding.
What to check:
- Does every active loan account carry a valid CKYC number in the core system?
- For older accounts opened before CKYC capture was standard practice, has a backfill exercise been run to fetch and attach the number?
- Is the CKYC number validated for format before submission, to avoid rejection?
- Is there a named owner for CKYC data quality across onboarding, ops, and compliance?
Sync DPD With Every Incremental Cycle
Under the amended directions, incremental accounts include those with overdue payments, meaning DPD-relevant changes are expected to be captured within each reporting cycle rather than smoothed into a single monthly figure.
What to build:
- A regular internal DPD refresh from the loan management system, aligned closely with each of the four reporting dates.
- A check for accounts where a payment was received but the DPD field wasn’t updated before the next reference date.
- A review step for accounts that moved between DPD buckets, since these changes carry significant weight in a borrower’s credit profile.
- Confirmation that closed or settled accounts reflect their correct status, not an outdated overdue figure.
Treat the Four-Day Incremental SLA as a Hard Stop
The RBI’s directions are specific: incremental data for the 9th, 16th, and 23rd must reach the CIC within four calendar days of each date. There is no ambiguity in this timeline.
What to do:
- Begin file preparation before the reference date arrives, not after.
- Maintain a submission calendar marking the 9th, 16th, 23rd, and month-end, along with the four-day deadline that follows each one.
- Assign a backup owner for every submission, so a single absence doesn’t put the SLA at risk.
- Log the timestamp of every submission, since CICs report non-compliance to the RBI’s DAKSH portal.
Don’t Miss the Full File Due by the 5th
Alongside the three incremental submissions, the amended directions require a full file, covering all active accounts plus those closed since the previous cycle, submitted by the 5th of the following month.
What to check:
- Does the full file include every closed, foreclosed, and settled account from the past month, as the RBI’s directions require?
- Is the file built to the CIC’s prescribed Uniform Credit Reporting Format?
- Has the full file been reconciled against the core loan book before submission, to catch accounts that may have fallen out of sync?
Run a Regular Data Quality Review
RBI’s broader Master Directions on credit information reporting require financial institutions to review their Data Quality Index and submit corrective action reports. Rather than waiting for the half-yearly review, a lighter monthly version of the same exercise helps catch issues early.
- Compare reject rates across the four submissions each month.
- Review CIC feedback for recurring field-level issues.
- Share findings with the team managing the loan management system, since most data quality issues originate at the point of data capture, not at the point of reporting.
Staying Aligned With the RBI’s Framework
The RBI’s amended directions did not simply add more paperwork. They tightened the clock on responsibilities NBFCs already had accurate borrower data, timely rectification of errors, and a complete, reconciled record of every account. What changed is the frequency: four reference dates a month instead of one, each with a defined SLA and direct visibility to the regulator through the DAKSH portal.
NBFCs that build these six controls into a standing operational rhythm, rather than a periodic scramble, will find the amended framework manageable. Those that don’t risk recurring rejects, DPD mismatches, and a compliance record the RBI can see.
For more guidance on staying aligned with RBI’s credit information reporting framework, connect with NBFC Advisory.
📞 Call NBFC Advisory: +91 93287 18979
🌐 Visit: nbfcadvisory.com
