A 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.
Why pre-disbursal verification is the highest-stakes step in lending
Every stage of the lending lifecycle carries risk. But at disbursement, the institution becomes irrevocably exposed. Before disbursement, the credit decision can be reversed, the sanction can be cancelled, the documents can be requested again. After disbursement, the loan exists, the funds are released, and the institution's recourse depends entirely on the quality of the conditions satisfied before that RTGS instruction was submitted.
In a manual pre-disbursal process, the checklist is typically managed by a disbursement officer reviewing a physical or digital file, checking items off a checklist, and authorising release when satisfied. The error rate in manual checklist execution in high-volume disbursement operations ranges from 2% to 6% of files — meaning between 2 and 6 applications per 100 are released with at least one condition not fully verified. At a portfolio level, this represents significant cumulative exposure.
The Disbursement Agent AI eliminates the human execution of the checklist. Every check is a parameterised verification against a live data source — not a checkbox against a PDF review.
"A pre-disbursal checklist that a human checks is only as good as the human's attention on the 47th file of the day. A checklist that a machine checks is the same on file 1 and file 4,700."
The 22 checks — organised by category and outcome on failure
Category 1 — Sanction Conditions Verification
6 checks · All must pass before proceeding
01
Sanction letter signed by authorised officer — within sanction validity periodSanction letter must be signed by the designated credit authority and must be dated within the institution's sanction validity window (typically 90 days). An unsigned sanction or an expired sanction cannot trigger disbursement.Block: unsigned or expired sanction → legal team alert · No disbursement until re-sanction
Auto-verify
02
Borrower acceptance of sanction terms — signed loan agreement receivedThe borrower's signed loan agreement must be received and the signature must be verified against the KYC record. eSign signatures are validated via the eSign service provider confirmation; physical signatures require scan upload.Block: unsigned loan agreement → disbursement held pending receipt
Auto-verify
03
All sanction conditions listed in the sanction letter — verified and loggedThe sanction letter may list specific conditions precedent (additional document, co-applicant signature, property title search completion). Each listed condition must be individually verified and the verification logged before the disbursal checklist can proceed.Block: any unverified sanction condition → specific condition owner alerted · Disbursement held
Block on fail
04
Loan amount in disbursal instruction matches sanctioned amountThe amount in the RTGS instruction must exactly match the sanctioned loan amount (or the draw-down amount for partial disbursements under a construction-linked plan). Any discrepancy — even ₹1 — blocks disbursement pending reconciliation.Block: amount mismatch → disbursement team alert · Reconciliation required before release
Block on fail
05
Borrower's MIS data — loan account created in core banking systemA loan account must exist in the institution's core banking system before funds can be disbursed against it. The disbursement instruction must reference a valid, active loan account number. Disbursement against a non-existent loan account is a fund control failure.Block: loan account not created → CBS team alert · Account creation required before disbursal
Block on fail
06
NACH / ECS mandate registered and confirmed — EMI collection set upBefore disbursement, the NACH mandate for EMI collection must be registered with the borrower's bank and the confirmation received. Disbursing a loan before the repayment mechanism is confirmed creates a collection risk on the first EMI.Hold: NACH not yet confirmed → disbursal held · Release triggered automatically on NACH confirmation
Hold
Category 2 — Legal and Security Documentation
6 checks · Critical for secured loans · Failure blocks disbursement
07
Mortgage deed executed and stamped — registration pending or completedThe equitable mortgage deed must be executed by the borrower and stamped at the applicable stamp duty value. For registered mortgages, the registration must be completed before disbursement. For equitable mortgages (deposit of title deeds), execution and stamping must be confirmed.Block: mortgage not executed → legal team alert · No secured loan disbursement without executed mortgage
Block on fail
08
CERSAI charge registration — confirmed and registration certificate receivedThe institution's charge over the property must be registered with CERSAI before disbursement for all secured loans. The CERSAI registration certificate must be received and its details (DRN, charge date) logged in the loan file.Block: CERSAI registration not confirmed → DRN verification · No release without CERSAI confirmation
Block on fail
09
Property title — legal opinion received, title clear confirmedThe legal opinion on the property title must be received from the empanelled advocate, and the title must be confirmed clear and marketable. A title with encumbrances, disputes, or unclear ownership chain must be resolved before disbursement.Block: title opinion not received or title not clear → legal team escalation · Disbursement held
Block on fail
10
Original title documents received and custody confirmedFor home loans and LAP, the original title documents (sale deed, prior title chain) must be in the institution's custody or in a verified safe custody arrangement. A loan disbursed without the original documents creates an unsecured exposure for a product priced as secured.Block: original documents not received → legal team alert · Disbursement held until custody confirmed
Block on fail
11
Property insurance — policy taken, institution named as loss payeeProperty insurance is typically a sanction condition for home loans and LAP. The policy must be taken before disbursement, and the institution must be named as the loss payee so that any insurance proceeds flow to the institution, not the borrower, in the event of a claim.Hold: insurance policy not received → borrower reminder triggered · Release on policy receipt
Hold
12
Encumbrance certificate — final EC confirming no new encumbrances post-sanctionA final encumbrance certificate covering the period up to the date of disbursement is required to confirm that no new encumbrances (charges, attachments, court orders) have been created on the property between the date of the title search and the disbursement date.Block: EC not current (older than 30 days) or shows new encumbrance → legal team alert
Block on fail
Category 3 — Account and Fund Control Checks
5 checks · Beneficiary account and amount verification
13
Penny drop completed — beneficiary account verified and name matchedA penny drop (₹1 credit to the beneficiary account) must be completed and the account holder name returned by the IMPS/NEFT system must match the borrower's name in the loan record. Name mismatch triggers a hold — funds cannot be released to an account where ownership is unverified.Block: penny drop not completed or name mismatch → account verification required · Full article #2
Block on fail
14
IFSC and account number — validated against RBI IFSC directoryThe IFSC code provided must be valid and active in the RBI's IFSC directory. The account number format must match the length and format requirements for that bank's account numbering convention. An invalid IFSC results in a fund transfer failure — detecting it pre-disbursement prevents the delay and the return charge.Block: invalid IFSC or non-standard account format → borrower communication triggered · Correction required
Block on fail
15
Disbursement beneficiary matches approved disbursement instructionFor third-party disbursements (builder payments, seller payments), the beneficiary name and account must match the party named in the approved disbursement instruction. A payment to an unapproved third party is a fund control failure regardless of the borrower's instruction.Block: beneficiary not matching approved instruction → disbursement team alert · Manual authorisation required
Block on fail
16
Funds source confirmation — treasury authorisation for the disbursal amountThe institution's treasury must confirm available funds for the specific disbursement amount before the RTGS instruction is submitted. This prevents disbursement instructions from being submitted when the institution's RTGS account does not have sufficient funds — a rare but operationally embarrassing event.Hold: treasury confirmation not received → treasury alert · RTGS submission held
Hold
17
Processing fees, stamp duty, and other charges — collected or netted from disbursementAll upfront charges must be collected before disbursement (or netted from the disbursement amount as per the sanction letter). A disbursement made before processing fees are collected results in an unsecured fee receivable that is difficult to recover post-disbursement.Block: charges not collected or deducted → reconciliation required · Disbursement held
Block on fail
Categories 4, 5 — KYC Currency and Compliance Checks
5 checks · Regulatory compliance before fund release
18
KYC refresh — confirmed current within 12-month validity windowIf the KYC was completed more than 12 months ago (or the product-specific KYC validity period has elapsed), a KYC refresh must be completed before disbursement. Disbursing against a stale KYC creates an AML compliance exposure.Hold: KYC older than validity period → KYC refresh workflow triggered · Disbursement held
Hold
19
AML and watchlist re-check — run at disbursement, not only at originationAML and watchlist screening must be run again at the time of disbursement — not just at origination. A borrower who appeared on an international sanctions list update after sanction but before disbursement must be caught at this stage.Block: new AML/watchlist hit → CCO immediate alert · Disbursement frozen pending review
Block on fail
20
Priority sector or subsidy tagging — for eligible loans, scheme compliance verifiedLoans under PMAY, PMEGP, MUDRA, or other government subsidy schemes must have scheme eligibility verified and the required regulatory tags applied in the system before disbursement. A disbursement without the required tags results in subsidy claim failure.Hold: subsidy flag not tagged → scheme desk alert · Disbursement held pending tag confirmation
Hold
21
Data consent — borrower's DPDP Act data processing consent confirmed and loggedThe borrower's data processing consent under the DPDP Act must be confirmed and logged in the system before disbursement. The consent must cover the data sharing required for loan servicing (credit bureau reporting, NACH processing, recovery agency data sharing if applicable).Hold: consent record incomplete → consent confirmation workflow triggered · Disbursement held
Hold
22
RTGS submission window — disbursement instruction submitted within RTGS operating hoursRTGS operates within defined hours (typically 7 AM to 6 PM on working days). A disbursement instruction submitted outside these hours will be queued for the next working day — creating a borrower expectation failure. The AI confirms the submission window before triggering the RTGS instruction.Hold: outside RTGS window → instruction queued for next available window · Borrower communication sent
Hold
The disbursal decision output: all 22 in under 4 minutes
Pre-Disbursal Check — Application LA-2025-8841 · Priya Ramachandran Sharma · ₹28,00,000
Home Loan · Nov 14, 2025 · 14:08:22 · Executed in 3 min 44 sec
Checks 01–03: Sanction signed (Oct 28, 2025 — within 90-day validity), loan agreement signed via Aadhaar eSign (confirmed from eSign provider), all 3 sanction conditions verified (V-KYC, title search, insurance)PASS
Checks 04–05: Disbursal amount ₹28,00,000 matches sanction exactly. Loan account LA-2025-8841 active in CBS — created Nov 10, 2025PASS
Check 06: NACH mandate registered HDFC Bank Acc XXXXXX4821 — confirmation received Nov 12. EMI ₹26,180 on 5th of each month from Dec 5, 2025PASS
Checks 07–08: Mortgage deed executed and stamped Nov 11. CERSAI DRN 2025BLRHL8841 — registration confirmed Nov 12. Certificate on file.PASS
Checks 09–10: Legal opinion dated Nov 8 — title clear, no encumbrances, marketable. Original sale deed and title chain (4 documents) in branch custody since Nov 11.PASS
Check 11: Property insurance HDFC ERGO policy 4821-2025 received Nov 13. Sum insured ₹52,00,000. Institution named as loss payee confirmed.PASS
Check 12: Final EC dated Nov 13, 2025 received — covers period to Nov 13. No encumbrances created post-sanction. EC current (1 day old — within 30-day validity).PASS
Check 13: Penny drop completed Nov 13 — ₹1 credited to HDFC XXXXXX4821. Name returned: "PRIYA RAMACHANDRAN SHARMA" — matches loan record (full name, exact match).PASS
Checks 14–15: IFSC HDFC0001234 — valid in RBI directory, active. Account format valid (12 digits). Beneficiary is borrower's own account — no third-party instruction.PASS
Checks 16–17: Treasury authorisation confirmed for ₹28,00,000. Processing fee ₹28,000 collected Nov 10. Stamp duty ₹16,800 collected Nov 11. No outstanding charges.PASS
Checks 18–19: KYC completed Nov 7 (7 days ago — well within validity). AML re-check Nov 14 — clear. Watchlist re-check Nov 14 — clear. No new hits.PASS
Checks 20–21: No subsidy scheme applicable. DPDP Act data consent confirmed and logged Nov 7 during V-KYC. Consent covers: bureau reporting, NACH, general servicing.PASS
Check 22: Current time 14:12 IST — within RTGS operating window (07:00–18:00). File will process same day. RTGS instruction submission: 14:15 IST estimated.PASS
Pre-disbursal check result
22 / 22
All checks passed
Decision
RELEASE FUNDS
RTGS instruction queued · 14:15 IST
● 22 checks · 3 min 44 sec · 22 passed · 0 holds · 0 blocks · RTGS queued
● Disbursement record sealed · Borrower notification queued · Post-disbursal monitoring activated
22Pre-disbursal checks — across sanction, legal, account, compliance, and fund control categories
3m44sAll 22 checks completed — before any RTGS instruction is submitted
ZeroManual intervention for a clean file — every check auto-verified from live data sources
14:15 ISTRTGS instruction queued — within same-day RTGS window, borrower receives funds same day
The 22 checks are not bureaucracy — they are the institution's last line of defence before irrevocable exposure
Every check on the pre-disbursal list exists because someone, somewhere, suffered a loss when that check was skipped. Disbursement without a final AML check, because the borrower was clean at origination, produces a compliance failure when a post-sanction watchlist update is missed. Disbursement without the final EC produces a secured loan that is actually unsecured because a creditor attached the property in the interim. The Disbursement Agent AI runs all 22 checks not because they are procedural requirements but because each one represents a specific, documented risk that the institution's policy has determined must be verified before funds can move — on every file, every time, with no exceptions for volume pressure.