An error without a taxonomy is a problem that cannot be measured, trended, or systematically fixed. A QC process that records errors in free text — "document missing," "date issue," "wrong account" — produces a register that can tell you how many errors were found but not which operations teams or which process steps are generating them, whether they are increasing or decreasing, or what interventions would reduce them most efficiently. The Quality Control Agent AI tags every error with a standard code from a 20-error taxonomy — covering origination errors, property documentation errors, loan documentation errors, regulatory compliance errors, and operational processing errors — making every error instantly attributable, trendable, and actionable. The error code determines who receives the correction routing, what the correction requires, and how long the correction typically takes.
The 20-error taxonomy: grouped by category
Photograph on submitted identity document does not match the applicant's onboarding selfie — face verification failure
Catches synthetic identities and document substitution. Flagged for enhanced due diligence. If face match score below 70%: hold file and refer to Fraud team.
Borrower's declared current address is in a different district than the Aadhaar address without supplementary address proof
Address proof document required. Routes to RM to obtain supplementary proof before proceeding.
Submitted bank statements do not cover 12 contiguous months — one or more months missing or statements cover a non-contiguous period
Most common origination error. Routes to RM to request the missing period from borrower. Correction typically resolved in 1–2 days.
ITR computation sheet submitted but the NSDL e-filing acknowledgement number is not present — filing not independently verifiable
ITR without acknowledgement is a declaration, not a verified filing. Routes to RM to obtain the acknowledgement from borrower or pull from NSDL portal.
GSTIN is active but one or more quarterly GST returns are not filed — income verification chain broken for the unfiled quarter
GSTN portal checked for filing status on all quarters. Routes to RM to explain and document the unfiled quarter or provide alternative income evidence for that period.
EC was valid at application but has aged past the 180-day limit — a fresh EC must be obtained before sanction or disbursement
Routes to RM to request fresh EC from SRO. Correction: 3–7 working days for EC from sub-registrar. If sanction is imminent, sanction can proceed with fresh EC condition on disbursement.
Valuation report was obtained at application but has aged beyond the 180-day validity window
Routes to Legal team to arrange fresh valuation from an approved panel valuer. Correction: 5–10 working days. If original valuation showed major structural issues, fresh valuation takes priority.
Valuer was on the panel at the time of the valuation but has since been removed — or was never on the panel
Routes to Legal team to obtain a fresh valuation from a currently approved panel valuer. QC flags this as critical — panel valuer requirement is a regulatory expectation under RBI guidelines for collateral valuation.
No CERSAI search in the file, or the existing search is stale — a new charge may have been registered since the original search
Routes to Ops team to complete a fresh CERSAI search. 24-hour resolution. Critical — disbursement without a fresh CERSAI search creates risk of lending on already-encumbered security.
Borrower is purchasing an under-construction unit — the project's RERA registration is pending, invalid, or not present in the file
Routes to RM and Legal team. RERA registration is mandatory for home loans on under-construction projects per RBI Digital Lending and Housing Finance guidelines. Pending registration is not acceptable — disbursement must await confirmation.
KFS creation or acknowledgement timestamp is the same date as or later than the sanction letter date — FPC pre-acceptance disclosure violated
Routes to Compliance team for FPC breach notation. System block (where implemented) is the long-term fix. Short-term: delay sanction until KFS is re-issued with confirmed pre-sanction acknowledgement. Highest-priority compliance error.
Bank account number or IFSC code on the NACH mandate is different from the account shown in the borrower's verified bank statements
Routes to Ops team for NACH re-execution. High consequence — a wrong-account NACH will bounce on first debit with penal charge and service failure. Correction before disbursement takes 1–3 working days.
eSign completion record shows fewer signed pages than the agreement template requires — an amendment page or addendum was not put through the eSign flow
Routes to Ops team to identify the unsigned page and route it through the eSign flow with the borrower before disbursement. Correction: 24–48 hours depending on borrower availability.
The borrower's signed consent for credit bureau enquiry was obtained on a date after the bureau enquiry was already run
Routes to Compliance team. Bureau enquiry without prior consent is a regulatory violation. FPC notation required. For the specific account: document the consent was obtained and note the sequence error. For the process: system block required to prevent recurrence.
Fee collected is lower than the scheduled fee and no fee waiver approval document signed by the authorised officer is present in the file
Routes to Finance for reconciliation and to the RM's manager for a retrospective waiver approval. The fee concession itself may be fine — the documentation is the issue. Finance must decide whether to collect the outstanding fee or formally document the waiver.
No AML screening result in the file, or the screening was run more than 90 days before disbursement — required to be current at disbursement
Routes to Compliance team for immediate re-screening. Disbursement blocked until AML clearance is confirmed. PMLA obligation — non-compliance is a criminal offence for the institution, not just a process gap.
The interest rate set up in the core banking system for this account does not match the rate stated in the KFS — systematic or manual entry error
Routes to Credit Ops for CBS rate correction before disbursement. A rate discrepancy creates a dispute risk immediately after the first statement is generated. Correction: 4–24 hours through Credit Ops rate change workflow.
The property being mortgaged is a commercial property being used to secure a residential home loan product, or vice versa
Routes to Credit team for product-property alignment review. A commercial property pledged against a home loan product creates a legal and regulatory mismatch. Options: switch to an appropriate LAP product, or decline the application on the grounds of product mismatch.
The CBS account for this loan has been set up with parameters that differ from the sanction letter — tenure, rate band, product type, or amount
Routes to Operations team for CBS correction before disbursement. Every parameter that is wrong in CBS at disbursement will be wrong for the life of the loan — amortisation schedules, statement generation, and CIBIL reporting will all reflect the incorrect setup.
The disbursement instruction in the payment system has a different amount or beneficiary account than the sanction letter authorises
Routes to Finance team as a critical hold. Disbursing an amount different from the sanctioned amount, or to a different account, is a regulatory violation and a potential fraud signal. No disbursement proceeds until Finance reconciles the discrepancy and confirms the correct instruction.
The error code that routes ERR-LOAN-NACH-MISMATCH to the Ops team is not a notification — it is a work order with a correction specification, a responsible party, and a disbursement-blocking condition that will not lift until the Ops team confirms the correction is complete
The routing is not advisory. When the QC AI tags an error as ERR-LOAN-NACH-MISMATCH and routes it to Ops, the Ops team receives a task with specific fields: the file ID, the NACH account number that was submitted, the correct account number from the verified bank statement, and a disbursement block confirmation that tells them the loan will not proceed until they mark the task complete. The QC AI then tracks the correction — if the Ops task is not marked complete within 24 hours, a supervisor alert is generated. If it is not complete within 48 hours, an escalation to the Head of Operations is generated. The taxonomy turns every error from a notification into a managed work item — with an owner, a deadline, and an escalation path if the deadline is missed. A QC system that finds errors and reports them is a QC system that produces reports. A QC system that finds errors, routes them as work items, tracks their resolution, and escalates overdue corrections is a QC system that produces disbursements.