A customer service point with missing deposits and a conflict of interest
The sarpanch of a village complains that 11 customers of a Customer Service Point run by Mr K cannot withdraw balances they have deposited. Records show 38 accounts opened or operated through the CSP in the last quarter. Passbooks carry deposits totalling 4.60 lakh that do not appear in the core banking system. Three customers say they handed over cash but received no receipt. The CSP's biometric device was offline for three days in that period, and Mr K says those entries were pending upload. The daily CSP reconciliation reports for the same weeks were signed by the branch's relationship manager, who is Mr K's cousin, and show no gap. One customer has already posted a video, and a local newspaper has called the branch. Bank policy requires the CSP to deposit collections by the next working day.
1. List, in order, the first five actions the branch manager should take within 24 hours, with the reason for each, and identify the single action that cannot wait for the investigation.
Read the worked answer
- Suspend the CSP channel: get the business correspondent ID and device mapping blocked in the core system and inform IT in writing. Reason: stops fresh collections being exposed and freezes the trail as it stands. This is the action that cannot wait - every additional day adds deposits that may never reach the bank.
- Acknowledge all 11 complaints the same day, in writing, with complaint numbers and copies of passbooks retained. Reason: a documented response limits the social media and press escalation and preserves customer-side evidence.
- Reconstruct the trail for all 38 accounts for the full quarter, including batch upload logs, the CSP settlement account and cash-in-transit entries. Reason: separates a technical upload failure from misappropriation before anyone is accused.
- Escalate in writing to the regional head and the financial inclusion cell, and record the conflict of interest: the relationship manager who signed the reconciliation is the CSP operator's cousin. Recuse that officer from the enquiry and take custody of the reconciliation sheets.
- Secure evidence - device, register, receipt books, phone messages - and instruct staff not to let Mr K 'correct' any entries.
2. How would you separate a genuine posting failure from misappropriation? Give at least four tests and the inference each supports.
Read the worked answer
First, check whether the cash reached the CSP settlement account in the core system on the same or next working day. If it did, the customer's passbook entry is a printing or posting error and no money is lost; if it did not, the question becomes where the cash went. Second, check whether the customer received the core-banking SMS at the time of deposit. A genuine posting generates an alert; a passbook entry with neither an SMS nor a settlement credit points to manual entry. Third, inspect the CSP portal upload logs for the three offline days. A failed batch that was later re-uploaded indicates a technical failure; amounts that never entered any queue do not. Fourth, examine the passbooks themselves - different ink, missing CSP stamp, no receipt numbers, entries bunched together only after complaints. Fifth, test the reconciliation control: were the signed daily reports backed by a system-generated statement, or signed blank? Blank signing converts a possible technical failure into a definite control failure and moves the enquiry upstream.
3. Draft the substance of the note to the controlling office. What must be reported, and what must not be promised to customers at this stage?
Read the worked answer
Report only verified facts: 38 accounts in scope, 11 complaints, 4.60 lakh of passbook entries not traced in the core system, the three-day device outage, the next-working-day deposit rule, the actions already taken (channel blocked, complaints acknowledged, trail under reconstruction), and the relationship between the CSP operator and the relationship manager, with the recusal already applied. Give a dated commitment for the next update and name the officer responsible. Do not conclude that a fraud has occurred, do not put a figure on the loss, do not name Mr K as a defaulter in writing, and do not blame the system before the logs are tested - each of these creates defamation, HR or customer-compensation exposure if the finding changes. To customers, promise only a written outcome within a stated number of days. Do not promise refunds or compensation, and do not admit liability, before the trail is reconciled; equally, do not tell them the bank owes nothing. Where a customer acted in good faith and the shortfall is verified, the bank's liability for transactions put through its own agent channel must be assessed on its merits and settled promptly once confirmed.