A dispute without evidence is a dispute that resolves based on who the institution believes — which is a governance and fairness problem as well as a regulatory one. A dispute with complete, source-attributed, timestamped evidence is a dispute that resolves based on what the records show — which is the standard the RBI's Integrated Ombudsman Scheme was designed to enforce. The Dispute Manager Agent AI gathers evidence from eight different source systems within 24 hours of a dispute being filed — automatically, without requiring the Nodal Officer to call five different departments and wait for email attachments. When the Nodal Officer receives the dispute file, the evidence is already assembled, cross-referenced, and marked with a preliminary assessment of whether the evidence supports or contradicts the borrower's claim.
The 8 evidence sources — and what each contributes to a dispute file
A complete dispute file requires evidence from sources that typically live in different systems, managed by different teams, with different access controls. Call logs are in the collections management system. NACH return codes are in the payment gateway portal. KFS and eSign records are in the document repository. CBS payment history is in the core banking system. Bureau consent records are in the KYC and onboarding system. Account Aggregator data is in the AA integration layer. Property valuation records are in the legal and property management system. Training and conduct records are in the HR and compliance system. The Dispute Manager Agent AI has read access to all 8 sources and retrieves the relevant evidence from each, simultaneously, within minutes of the dispute being filed.
The evidence file: DIS-2025-1848 · Collections conduct · Sunita Mehta
8 sources retrieved simultaneously
Manual equivalent: 3–4 working days
The 8 evidence sources — retrieval scope and typical assembly time
| Evidence source | System | What it provides | Retrieval time | Most relevant to |
|---|---|---|---|---|
| Collections call log | Call Management System | All outbound/inbound calls with timestamps, agent IDs, duration, call status (answered, missed, dropped) | Instant | Collections conduct, permitted hours, third-party contact |
| Call recording | Collections Management / Third-party CCaaS | Audio recording of the specific call — language, tone, content, third-party presence | 1–48 hours (depends on platform) | Abusive language claims, third-party contact claims |
| CBS payment history | Core Banking System | Full payment ledger — debit dates, amounts, DPD classification, penal interest accrual | Instant | Penal charge disputes, payment attribution, DPD claims |
| NACH return codes | Payment Gateway / NPCI | Specific return code per failed debit — distinguishes bank-side technical from borrower-side insufficiency | Instant (24h for aged records) | Penal charge disputes — bank fault vs borrower fault |
| KFS and eSign records | Document Repository | KFS with creation timestamp, borrower eSign timestamp, sanction letter date, MITC signed document | Instant | Disclosure disputes, rate disputes, prepayment charge disputes |
| Borrower consent records | KYC / Onboarding System | Consent forms signed, AA consent status, bureau consent date, digital consent with timestamps | Instant | Data disputes, bureau consent disputes, KFS acknowledgement disputes |
| Agent training records | HR / Compliance System | Training modules completed by specific agent, scores, dates — determines whether violation is training gap or conduct failure | Instant | Collections conduct disputes — distinguishes wilful violation from training gap |
| Borrower bank statement (via AA) | Account Aggregator Integration | Bank account credits and debits for the dispute period — requested from borrower via WhatsApp if AA consent not active | Instant (AA active) / 24–48h (requested) | Payment attribution disputes, double debit claims |
The evidence that distinguishes a bank-side NACH failure from a borrower-side EMI skip is a 2-digit return code in a payment gateway log — and the institution that cannot retrieve it within 24 hours cannot defend the penal charge it applied
A borrower who disputes a penal charge for a NACH bounce needs one piece of information to resolve their dispute: the NACH return code. If it is R29 (bank network error) or R01 with a bank-flagged technical note, the penal charge should be reversed — the borrower did not skip the payment, the bank system failed to process it. If it is R01 without a technical note, the borrower had insufficient funds. These two outcomes have entirely different remedies. An institution that does not retrieve the return code within 48 hours of the dispute is an institution that either applies a blanket reversal policy (expensive and incorrect) or maintains the charge regardless of cause (a potential FPC violation if the bounce was bank-side). The Dispute Manager Agent AI retrieves the return code within minutes and documents which type of failure caused the bounce — the most consequential piece of evidence in the most common dispute category, retrieved automatically, so the Nodal Officer can resolve correctly rather than guessing.