2.9 Bureau reporting
Rule summary
Section titled “Rule summary”Under the Credit Information Companies (Regulation) Act, 2005 (CICRA) and subsequent RBI directions, every RE (bank, NBFC, HFC, etc.) must:
- Become a member of all four RBI-licensed Credit Information Companies (CICs):
- TransUnion CIBIL (
cibil.com) - Experian Credit Information Company of India (
experian.in) - Equifax Credit Information Services (
equifax.co.in) - CRIF High Mark Credit Information Services (
crifhighmark.com)
- TransUnion CIBIL (
- Submit monthly data on all borrowers and loans to each CIC in the standard formats.
- Use CIC reports for credit decisions and submit enquiry data for each report pulled.
Source
Section titled “Source”- Credit Information Companies (Regulation) Act, 2005 (
indiacode.nic.in). - Credit Information Companies Rules, 2006 and Regulations, 2006.
- RBI directions to CICs and CIs (Credit Institutions) issued periodically.
Data submission formats
Section titled “Data submission formats”| Customer type | Standard format |
|---|---|
| Consumer (individual) | CIBIL Consumer Bureau format, broadly aligned across all four CICs |
| Commercial (entity) | CIBIL Commercial Bureau format (CB) — non-individual borrowers |
| MSME | Submitted under both consumer (for proprietor) and commercial (for entity) where relevant |
The data file is a monthly cumulative file per loan, with:
- Borrower identifiers (PAN, Aadhaar reference, name, DoB, address, mobile, GSTIN for entity).
- Loan identifiers (account number, type, sanction date, sanction amount).
- Repayment behaviour (DPD bucket, last 24/36 months).
- Asset classification (Standard / SMA-0 / SMA-1 / SMA-2 / Sub-standard / Doubtful / Loss).
- Outstanding balance.
- Other loan terms.
Frequency and deadlines
Section titled “Frequency and deadlines”- Monthly submission, by the 15th of the following month (extended to month-end in some practical cases). RBI’s strict interpretation is “monthly”, and CICs accept files daily, weekly, or monthly.
- Best practice: weekly submission to all four CICs to keep the bureau view fresh.
Enquiry reporting
Section titled “Enquiry reporting”- Every time you pull a bureau report (consumer or commercial), the CIC records an enquiry against the borrower’s credit file.
- Repeated enquiries (rate-shopping by borrower or aggressive multi-lender pulls) lower the borrower’s score temporarily.
- For SME WC repeat-loan flows, this matters — pulling fresh bureau for every renewal hurts the borrower’s score. Solutions: use soft pulls where possible; cache reports per borrower for a defined refresh period (
30 – 90days), with policy-defined refresh.
Borrower dispute resolution
Section titled “Borrower dispute resolution”- Borrowers can dispute incorrect bureau data via the CIC.
- The CIC forwards the dispute to the lender.
- Lender must investigate and respond within
30 days. - If dispute is valid, lender corrects and re-submits.
Compliance penalties
Section titled “Compliance penalties”- RBI penalises CIs that fail to submit, submit late, or submit poor-quality data.
- CICs publish quarterly data quality reports ranking CIs on completeness, accuracy, and timeliness.
Product implications
Section titled “Product implications”- Bureau pull at onboarding for every applicant (consumer for individual / proprietor, commercial for entity).
- Bureau policy rules — eligibility cuts based on bureau score, DPD, total exposure, multiple enquiries, write-off history.
- Disputes UX in borrower portal — allow borrower to flag incorrect data the platform reports.
System implications
Section titled “System implications”- CIC integration — one connector per CIC for both pulling reports and submitting monthly data.
- Bureau report parser — bureau reports are not JSON-friendly; XML/PDF/structured-text parsing required. Reliable parser libraries are the long pole.
- Monthly submission generator — batch job that produces standard-format files for all four CICs from your loan book.
- Submission acknowledgement tracker — each CIC returns an acknowledgement / error file; reconcile against expected and re-submit on errors.
- Enquiry pull rate-limiting — avoid duplicate pulls per borrower.
- Bureau report cache — TTL-based, configurable per product / risk policy.
Documents that must be generated
Section titled “Documents that must be generated”- Monthly bureau submission files (four × per month) with acknowledgements.
- Daily / weekly bureau pull logs.
- Dispute investigation files.
Workflow that must exist
Section titled “Workflow that must exist”- Monthly submission job with error-handling and re-submission.
- Bureau pull on application + on policy-defined refresh.
- Dispute investigation
<= 30 days. - New-CIC onboarding when joining additional bureaus.
Reports that must be produced
Section titled “Reports that must be produced”- Monthly submission success / failure / rejection report.
- Bureau data quality (internal).
- Dispute resolution SLA report.
Audit evidence required
Section titled “Audit evidence required”- Submission files and CIC acknowledgements.
- Dispute logs.
- Bureau membership certificates.
- Sample of bureau pulls referenced against credit decisions.
Vendor and integration notes
Section titled “Vendor and integration notes”- All four CICs have direct integration; or use a bureau-aggregator vendor (Karza/Perfios offers a unified API, as do some other vendors). Pricing: per-report, with volume tiers.
- Submission file generation is best built in-house (the format is stable and the data is yours); pulling reports via aggregator is convenient.
- Match-rate optimisation — bureaus may return “no record” if name / DoB / PAN don’t match exactly. PAN is the strongest identifier and reduces false negatives.
Sources
Section titled “Sources”- Credit Information Companies (Regulation) Act, 2005.
- Credit Information Companies Rules / Regulations, 2006.
- RBI directions to CICs and CIs on data quality, accuracy, and dispute resolution.
- CIC URLs:
cibil.com,experian.in,equifax.co.in,crifhighmark.com.