Bureau & Data Agent AI

INVOKED WHEN: loan origination pipeline signals application completeness, or monthly batch refresh run is due

• –Triggers bureau pulls at the correct pipeline stage — after KYC verification and application completeness are confirmed, before the underwriting assessment begins — using the applicant's PAN and date of birth. Applies the bureau pull sequence per credit policy: CIBIL as primary for retail and MSME, with Experian or CRIF as secondary where dual bureau checks are required by the product policy.
• –Manages bureau API failure handling: where a primary bureau API is unavailable, triggers the secondary bureau automatically and flags the primary failure for the operations team to investigate. Does not delay the underwriting pipeline waiting for a failed primary bureau — the secondary bureau result proceeds the file with the failure noted.
• –Tracks the bureau pull log — every pull with timestamp, bureau, PAN, result, and cost — for operations monitoring and bureau cost management. Pulls wasteful or duplicate pulls are flagged to the operations team.

INVOKED WHEN: bureau report is received and requires an interpretation summary for the underwriting queue

• –Reads the full bureau report and produces a structured interpretation summary: score band, score change since last pull (where a prior pull exists in the portfolio), DPD summary across all tradelines, total outstanding obligation, and the most significant negative items (90+ DPD, write-off, settled, or ongoing legal action). The summary is designed to give the credit officer and the Underwriting Agent AI a quick orientation to the bureau picture — not to substitute for reading the full report.
• –Flags specific bureau signals that require human credit officer attention regardless of the overall score: a very recent (within 90 days) new secured loan or credit card — possible undisclosed obligation; a tradeline that shows 'settled' (the borrower paid less than the full amount owed) — credit behaviour signal; or multiple hard enquiries in the last 30 days — active loan shopping that may indicate undisclosed applications at other lenders.

INVOKED WHEN: a borrower raises a data quality concern or the credit team identifies a bureau data error

• –Reads the dispute details — what data the borrower or credit team believes is incorrect, the evidence supporting the dispute, and the credit information company whose data is in question — and prepares the dispute correspondence in the format required by CIBIL, Experian, or CRIF's dispute resolution process: the loan reference number, the specific field being disputed, the evidence of the correct data, and the request for correction.
• –Tracks the dispute through the bureau's response cycle — logging the submission date, the bureau's acknowledgment, the investigation outcome, and the corrected data once the bureau updates its records. Alerts the credit officer when a dispute has been pending beyond the bureau's published resolution timeline (typically 30 days under RBI's CIC regulations).