← Agent catalogue
AI Agent Profile · LendingIQ · Bengaluru
Disbursement Agent AI
Invoked via: LOS post-sanction pipelineRuntime: AWS Bedrock · ap-south-1Model: Claude Sonnet 4Context window: 200K tokens
DivisionLending Operations
Resume
What this agent does
The Disbursement Agent AI runs the pre-disbursal checklist for every approved loan — verifying that all conditions precedent are met, that the borrower's bank account is verified, that the NACH mandate is active, and that the security documentation is in order for secured loans. It prepares the payment instruction for the disbursement officer to authorise, schedules the NOC post-repayment, and triggers the CBS loan account creation on confirmed disbursement. No funds move without a human officer's authorisation in the payment system.
Primary functions
Pre-Disbursal Checks
Every sanctioned loan — before payment instructionInvoked when: loan is approved and sanction letter is issued, and disbursement is being prepared
- Reads the sanction letter and generates the conditions precedent checklist — every condition the sanction letter specifies must be satisfied before disbursement: KYC completion, insurance policy assignment for mortgage loans, NOC from prior lender for refinancing cases, legal opinion on title for property loans, and any borrower-specific conditions added by the credit officer at sanction. Checks each condition against the document store and marks as satisfied or outstanding.
- Checks sanction validity — whether the sanction letter is still within its validity period. A sanction that has lapsed requires re-approval before disbursement can proceed, regardless of how close to the original approval the current date is. No disbursement proceeds on a lapsed sanction.
- For secured loans, verifies that the security creation documentation (equitable mortgage, registered mortgage, hypothecation, or pledge as applicable) has been executed and the charge has been registered in CERSAI — because disbursing on an unsecured basis against a secured sanction creates a security gap that cannot be remediated after the fact.
Output: Pre-disbursal check report — all conditions precedent with status (satisfied / outstanding), sanction validity status, security documentation check for secured loans. Any outstanding item halts the disbursal queue until resolved.
Account Verification & Payment Instruction
On pre-disbursal pass — immediately before payment prepInvoked when: all pre-disbursal conditions are satisfied and the account needs to be verified before the payment instruction is prepared
- Triggers a penny drop verification to the borrower's bank account — a real-time API call that confirms the account number and IFSC code are valid, that the account is active, and that the account holder's name matches the borrower's name on the sanction letter. A name mismatch or an inactive account stops the process immediately — the payment instruction is not prepared until the mismatch is resolved.
- Prepares the payment instruction for the disbursement officer's authorisation: beneficiary account details (verified), IFSC, disbursement amount, payment reference (linked to the loan account number being created in CBS), and any tranched disbursement schedule if the loan is disbursed in stages.
- Does not execute the payment. The payment instruction is submitted to the payment operations system where the human disbursement officer reviews the pre-disbursal check summary and authorises the transfer using their payment system credentials and authority.
Output: Penny drop verification result — account status, name match verdict. Payment instruction — beneficiary details, amount, reference, tranching schedule if applicable. Payment instruction is queued in payment ops system pending human officer authorisation.
NOC Scheduling
On loan creation — scheduled for post-repaymentInvoked when: disbursement is confirmed and the CBS loan account is created
- Calculates the loan maturity date based on the disbursement date, tenure, and EMI schedule, and schedules the NOC (No Objection Certificate) generation workflow for the date the final EMI is received — creating a calendar entry in the document management system that triggers the NOC preparation workflow automatically at maturity, without requiring a manual flag from the borrower or operations team.
- For secured loans, schedules the charge release workflow in CERSAI at the same maturity milestone — because the borrower is entitled to charge release on full repayment, and an unreleased charge that lingers after loan closure creates a legal encumbrance on the borrower's asset that LendingIQ has no right to maintain.
Output: NOC schedule entry — maturity date, NOC generation trigger, borrower contact details for NOC delivery. For secured loans: CERSAI charge release workflow scheduled. Both confirmed to the loan file record.
Hard guardrails
Will notPrepare a payment instruction on a lapsed sanction. Expired sanctions require re-approval from the credit officer before any disbursal activity resumes.
Will notProceed past a failed penny drop without human review. Account mismatch on verification requires the borrower's relationship manager to investigate before disbursement continues.
Will notTrigger the fund transfer. The payment instruction enters the payment ops queue; the authorised disbursement officer executes it. The agent has no access to payment execution credentials.
Known limitations
Penny drop confirms account ownership at the moment of verification — not the account's suitability for receiving loan proceeds. A joint account where only one joint holder is the borrower passes penny drop but may create legal complications for enforcement if repayment fails. The agent flags joint account structures for the disbursement officer's awareness.Build a joint account flag into the penny drop response handling — where the account holder name indicates a joint account, add a notation to the disbursement file for the officer's review before authorisation.
NACH mandate confirmation depends on the mandate having been processed by the sponsor bank — which can take 7–10 working days from registration. Where a borrower's first EMI date falls within this processing window, the mandate may not yet be active at disbursement. The agent flags this timing gap rather than proceeding on a pending mandate.For loans where the first EMI date falls within 14 days of disbursement, trigger the NACH registration at sanction rather than at disbursement preparation, to ensure the mandate is active before the first debit date.
Important Reads
Learn more about how to deploy Disbursement Agent AI to your lending workflow.
- Use case #0001Pre-disbursal checklist: the 22 checks Disbursement AI runs before releasing fundsA loan sanctioned is not a loan disbursed. Between sanction and fund release, twenty-two conditions must be satisfied — regulatory, legal, documentary, and operational. A single unsatisfied condition on a ₹45 lakh home loan is not a minor oversight. It is a potential legal liability, a regulatory exposure, or an inability to recover the funds if the borrower defaults. The Disbursement Agent AI verifies all twenty-two conditions before a single rupee moves.Read article →
- Use case #0002Account verification: how Disbursement AI validates penny drop and account ownershipA ₹1 penny drop that succeeds and returns a name is not the end of account verification — it is the beginning of it. The name returned must match the borrower's name in the loan record. The account must belong to the borrower, not a family member or an employer. And the account details must be consistent with what the borrower provided at origination. The Disbursement Agent AI treats penny drop as a verification step, not a formality.Read article →
- Use case #0003NOC scheduling: how Disbursement AI automates post-closure documentationLoan closure is the moment a borrower makes their final EMI payment. For most borrowers, it is also the moment they wait the longest — for a No Objection Certificate, for their original title documents, for the CERSAI charge release, for confirmation that their property is free of encumbrance. In most lending institutions, this wait runs 30 to 90 days. The Disbursement Agent AI triggers every post-closure documentation step automatically on the day of final payment — and tracks every step to completion.Read article →