Reporting and later correction are different controls
Paragraphs 35–36 of RBI’s Commercial Banks card Directions require the specified credit-information notice, the approved-policy process and prior intimation before default-status reporting. They also require the issuer to update status with the CIC within thirty days of settlement after default reporting. Pending disputes receive particular protection: disclosure/release of information, particularly default information, is to occur only after the dispute is settled. This guide uses the text updated on 1 October 2026 and checked on 26 October 2026. RBI Commercial Banks card Directions: paragraphs 3, 35–36, updated 1 October 2026.
Confirm issuer and the actual reporting event
These Directions’ Commercial Banks definition excludes Small Finance Banks, Payment Banks and Local Area Banks. Establish the legal issuer and applicable framework before transplanting this rule. Distinguish routine credit-history reporting from a default-status event. Paragraph 35 requires explicitly bringing to the customer’s notice that credit-history/repayment information is provided under the Credit Information Companies (Regulation) Act, 2005. That general notice is not a substitute for paragraph 36’s prior-default intimation.
Use the approved process without inventing a fixed advance notice
Paragraph 36 requires prior intimation and adherence to the approved policy. It does not, in this wording, prescribe a universal number of advance-notice days. Preserve the policy, actual message, delivery evidence and reporting timestamp. Paragraph 36 also requires a well-laid-down procedure to be followed transparently and made part of the Most Important Terms and Conditions (MITC). A later message does not prove prior notice. Separately establish the actual default facts and applicable payment/classification rules; a default entry is not validated solely because a message was sent.
Resolve disputes before the relevant disclosure
Maintain a transaction-specific dispute register linked to the reporting file, with opening, investigation and settlement evidence. Do not assume a customer’s unresolved fraud complaint has disappeared because the bill carried forward. Conversely, a dispute label does not itself establish that the customer owes nothing: the merits require the actual resolution process. Keep the reporting restriction and the debt determination distinct, and avoid suppressing a material pending dispute from the reporting approval pack.
Start the update control from actual settlement
Where dues are settled after default reporting, retain the settlement terms and actual completion evidence. A promise to pay, a partial payment not constituting settlement or an unfulfilled offer does not automatically start the statutory update period. The requirement is to update the status with the CIC, not to guarantee a particular score increase or delete accurate historical data. Compare the submitted update with the resulting report and investigate residual discrepancies through the applicable correction process.
Maintain one chronology for audit and complaints
Record statement/payment facts, prior intimation, reporting, dispute milestones, settlement and CIC update. Preserve amounts and identifiers so payments are not applied twice or a different account’s update used as proof. Compensation for delayed credit-information correction has its own framework; no amount is calculated here merely from a paragraph 36 delay. The dates below use calendar-day addition for the thirty-day update control, subject to actual settlement and applicable counting requirements.
Applicable primary references
RBI Commercial Banks card Directions: paragraphs 3, 35–36, updated 1 October 2026
Six worked illustrations
All facts and amounts below are fictional. Assumptions describe the model, not additional statutory rules.
Illustrative example 1: Settlement update control
Verified settlement occurs on 5 October 2026. Adding thirty calendar days gives 4 November 2026 as the control date. A completed update on 30 October is twenty-five elapsed days after settlement; preserve submission evidence rather than relying on a planned batch date.
Illustrative example 2: Month-end settlement
Settlement occurs on 31 January 2027. Thirty calendar days later is 2 March 2027, not 28 February merely because that is month-end. The tracker must add days rather than substitute the next month’s last date.
Illustrative example 3: Partial payment is not assumed settlement
Outstanding dues are ₹60,000 and a customer pays ₹20,000 without any agreed settlement of the balance. ₹40,000 remains. On these facts the payment alone is not evidence that all dues were settled for starting the update clock.
Illustrative example 4: Chronology of prior intimation
A default intimation is delivered on 1 June 2026 and the reporting event occurs on 3 June: a two-day interval. This proves only the chronology assumed here; the Directions do not create a universal two-day safe harbour. Verify the approved process and all default/dispute facts.
Illustrative example 5: Separate disputed amounts
The statement balance is ₹50,000, including ₹12,000 under an unresolved transaction dispute and ₹38,000 of other items. The reporting pack must identify both components and the pending dispute; simply presenting ₹50,000 as an undisputed figure omits ₹12,000 of material context. Apply paragraph 36’s actual restriction, not an automatic net-reporting workaround.
Illustrative example 6: Review population
Of 80 settled, previously reported accounts, 72 have verified timely CIC updates and 8 lack adequate evidence. The unresolved proportion is 10%. Those eight need investigation; an internal completion flag does not prove an update reached the CIC.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Confirm the regulated issuer | Commercial Bank definition and applicable card framework. |
| 2 | Identify the reporting event | Routine history distinguished from default status. |
| 3 | Verify the paragraph 35 notice | Customer-facing credit-information disclosure. |
| 4 | Read the approved default-reporting policy | Current process and responsibilities. |
| 5 | Establish prior intimation | Actual message, delivery and report timestamps. |
| 6 | Check pending disputes | Transaction linkage and documented resolution status. |
| 7 | Verify the underlying dues | Payments, allocations and actual contractual/default facts. |
| 8 | Establish settlement completion | Terms, receipts and remaining obligations. |
| 9 | Track the thirty-day CIC update | Dated submission, acknowledgment and resulting status. |
| 10 | Resolve exceptions through the correct route | Evidence gaps, report discrepancies and separately applicable complaint rules. |
Sixteen practitioner FAQs
1. Is every routine credit-history report a default report?
No. Identify the particular event and apply the relevant notice/process requirements.
2. What does paragraph 35 require the issuer to explain?
That the specified credit-history/repayment information is being provided under the CIC Regulation Act, 2005.
3. Is that general disclosure sufficient prior-default intimation?
Not by itself. Paragraph 36 contains a separate prior-intimation requirement.
4. Does paragraph 36 prescribe a universal twenty-one-day warning?
The current wording cited here requires prior intimation and approved process, without that fixed advance period.
5. Does sending a message prove default existed?
No. Establish the underlying payment and default facts independently.
6. Why must unresolved disputes enter the reporting review?
The paragraph specifically restricts disclosure/release, particularly default information, until the dispute is settled.
7. Can a dispute simply be ignored because a bill was issued?
No. Reconcile it to the investigation and resolution record.
8. Does opening a dispute prove the debt is zero?
No. Merits and reporting safeguards are separate questions.
9. What triggers the thirty-day update requirement?
Settlement of dues after the cardholder has been reported as a defaulter, on the stated facts.
10. Does every partial payment count as settlement?
No. Examine actual terms and whether settlement was completed.
11. Must accurate history automatically be erased?
The rule requires a status update; it is not a promise to delete accurate historical information.
12. Does the rule guarantee a higher credit score?
No. A particular score outcome is not guaranteed by this status-update duty.
13. Are thirty calendar days always the next month-end?
No. Add the actual days and confirm applicable counting rules.
14. Does an internal system flag prove CIC submission?
No. Preserve actual transmission/acknowledgment and report evidence.
15. Is compensation automatic from the examples here?
No. Any compensation claim needs the independently applicable framework and facts.
16. Does this cover every category of bank or issuer?
No. It uses the specific Commercial Banks Directions and their defined scope.
Conclusion
Link default reporting to prior intimation, dispute status and verified settlement, then track the CIC update without promising deletion of accurate credit history.