Use case #0002

Account verification: how Disbursement AI validates penny drop and account ownership

A SGD1 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.

Why penny drop fails to catch the most common account errors

A penny drop confirms that an account exists and can receive funds. It returns the account holder name as registered with the bank. That is all it does. It does not confirm that the account belongs to the loan applicant. It does not confirm that the account number was not mistyped. It does not flag that the returned name is a spouse's name, an employer's name, or a family member's name.

The Disbursement Agent AI uses the penny drop result as input to a multi-step account verification process — not as the verification process itself. The penny drop provides the name; the AI cross-checks that name against the borrower's name in the loan record using the same name reconciliation logic the KYC / CDD system uses, checks the account type for eligibility, and confirms that the account metadata is consistent with the borrower's stated financial profile.

"A penny drop that returns 'Meera Rahman' when the loan is in the name of 'Rajesh Rahman' is not a successful verification — it is an ownership mismatch that must be resolved before a dollar (SGD) is sent."

The account verification sequence

Account Verification Report — Application LA-2025-8841
Priya Ramachandran Rahman · Home Loan SGD28L · Verified: Nov 13, 2025 · 11:42:08
Step 1 — Account Details Submitted
BankDBS Bank
bank code / SWIFT BICDBS0001234
Account numberXXXXXXXXXXXX4821
Account type statedSavings
Step 2 — bank code / SWIFT BIC and Format Validation
bank code / SWIFT BIC DBS0001234 — valid in MAS / Central Bank bank code / SWIFT BIC directory. Branch: DBS Bank, Indiranagar, Singapore. Status: Active. No recent branch closure or bank code / SWIFT BIC change notice.
Account number format: 16 digits — consistent with DBS Bank account numbering convention. No transposition pattern detected (common error: digit pairs switched).
Step 3 — Penny Drop Execution and Result
Penny drop amountSGD1 via IMPS
Transaction referenceIMPS-2025-88412341
StatusCredit confirmed
Name returned by bankPRIYA R SHARMA
Account type returnedSavings account
Account statusActive
Step 4 — Name Match Analysis
Loan record name: Priya Ramachandran Rahman | Bank-returned name: PRIYA R SHARMA — Middle name abbreviated to initial. Name reconciliation confidence: 97%. Auto-resolved: middle name abbreviation is a known and common bank record convention. No manual review required.
Account type matches: loan record states savings account, bank confirms savings account. No mismatch.
Bank statement in loan file is from DBS Bank Indiranagar branch, same bank code / SWIFT BIC — consistent with penny drop result. Account is the same account used for income verification.
Account number last 4 digits (4821) match the account number on the bank statement submitted at origination. Additional consistency check passed.
Step 5 — Ownership Confirmation Verdict
Account ownership confirmed: Name match 97%, account type confirmed, bank and branch consistent with income verification documents, account number last-4 consistent with origination submission. All 5 ownership confirmation checks passed. Account approved for disbursement.
● Penny drop completed Nov 13 · Name match 97% · Ownership: confirmed · Account: approved for disbursal ● SGD1 will be recovered from first instalment or processing fee deduction

The account mismatch scenarios — and how the AI handles each

Mismatch TypeReturned Name ExampleLoan Record NameMatch ScoreAI ClassificationResolution
Middle name abbreviation PRIYA R SHARMA Priya Ramachandran Rahman 97% Auto-resolve Known bank convention — auto-approved, reconciliation note logged
Initials format S K PILLAI Suresh Krishna Pillai 92% Auto-resolve Initial expansion pattern — auto-approved
Case and spacing variation RAMESH KUMAR Ramesh Kumar 100% Auto-resolve Exact match after normalisation — auto-approved
Name change (marriage) PRIYA AGARWAL Siti Rahman 41% Hold — verify Different surname — possible married name at bank vs maiden name on loan. Request confirmation of name change documentation.
Spouse name on joint account MEERA RAJESH KUMAR Wei Ming Tan 28% Hold — verify Joint account with spouse first-listed. Request borrower's individual account or confirmation that borrower is joint holder.
Employer/company account TECHCORP INDIA LTD Priya Ramachandran Rahman 0% Block Company account provided instead of individual account. Loan funds cannot be disbursed to a company account. Borrower must provide personal account.
Unknown third-party account VIJAY PRAKASH Priya Ramachandran Rahman 0% Block + alert Unrelated third-party name. Possible account substitution fraud. Fraud team alerted. Disbursement blocked. Application under review.
5Verification steps — bank code / SWIFT BIC validation, format check, penny drop, name match, ownership confirmation
97%Minimum name match confidence for auto-resolve — below 80% triggers a hold for human review
HoldSpouse or married-name mismatches — not blocked but held pending verification of account ownership
Block + alertUnknown third-party name — fraud team alert triggered, not just a hold · Potential account substitution

The penny drop is the start of account verification, not the end of it

A SGD1 penny drop that credits and returns a name has confirmed that the account exists. It has not confirmed that the account belongs to the borrower, that the name is close enough to the loan record to be the same person, that the account type is eligible for loan disbursement, or that the account details are consistent with the documents submitted at origination. The Disbursement Agent AI treats these as five separate verification questions, each with its own answer, and only approves disbursement when all five have been affirmatively resolved — either automatically for standard patterns, or after human confirmation for ambiguous ones.

← Back to Disbursement Agent AI