UPPSC RO/ARO study materials
UPPSC RO/ARO study resources

PM-KISAN Instalment Hold: Aadhaar-Bank Seeding Backlog

UPPSC RO/ARO · Put your knowledge to work in context.

All case studies

PM-KISAN Instalment Hold: Aadhaar-Bank Seeding Backlog

In a block of 1,200 PM-KISAN beneficiaries, the latest instalment has not reached 1,200 farmers. The agriculture office's preliminary list shows 780 cases of name mismatch between Aadhaar and bank records, 210 accounts closed or dormant, 150 farmers whose land records are not linked to Aadhaar, and 60 suspected duplicates. The next verification window closes in 10 days. The block has three Common Service Centre (CSC) operators, one bank branch 25 km away, and two agriculture supervisors. Farmers have started gathering at the block office; two local leaders allege that money has been diverted. The bank says it cannot handle more than 80 account-verification cases a day. The CSC operators charge Rs 50 per correction, which many farmers say they cannot pay. The District Magistrate wants a plan that is both fast and auditable.

1. Categorise the 1,200 cases by the action each needs and propose a 10-day redressal plan with realistic daily targets.

Read the worked answer

Categories and action: A. 780 name mismatch - Aadhaar/bank name correction and re-seeding; bank or CSC. B. 210 closed/dormant accounts - account revival or new account, bank branch. C. 150 land-record not linked - revenue/agriculture office verification and linking. D. 60 suspected duplicates - field verification before any correction. Capacity check: the bank can do 80 account cases/day = 800 in 10 days, but A+B alone is 990, so the bank alone cannot clear all. CSC operators can handle Aadhaar/name and e-KYC cases if authorised; agriculture supervisors can handle C. Plan: Day 1: de-duplicate lists, assign token numbers, SMS each farmer the category and documents needed. Days 2-6: daily camp at panchayat bhawan: bank desk 80/day (priority B, then A), 3 CSC desks 40 each/day (A), 2 agriculture desks 15 each/day (C). Targets: bank 400, CSC 600, agriculture 150 over five days. Days 7-8: mop-up for A and B; duplicate verification. Days 9-10: reconcile, publish status, escalate unresolved cases with reasons. Why this is realistic: it uses the bank's stated 80/day limit, does not pretend CSC can do bank work, and keeps a buffer for no-shows.

2. Farmers are agitated and allege diversion. What immediate transparency and communication measures do you take, and how do you handle the Rs 50 CSC fee?

Read the worked answer

Transparency: publish a category-wise status board at the block and panchayat bhawan with token number, category, and next action-not full Aadhaar or account numbers. Issue a receipt for every document collected. Announce a daily 5 p.m. progress update and a control-room number. Explain that 'not received' is mostly a seeding/account mismatch, not proof of diversion; invite anyone with a specific case to show documents. Audit trail: keep a register of who corrected what, with time and signature; no cash should change hands at the camp. Fee: do not let Rs 50 become a barrier. Ask the CSC operators to waive the fee for this redressal camp or charge a single documented camp rate; if they refuse, request the district e-governance/agriculture office to bear it or provide a free alternative for BPL/small farmers. Any fee must be displayed, receipted, and optional-never a condition for listing the case. Communication: separate the allegation from the service problem: 'We will verify every complaint; meanwhile, here is how to get your case corrected.'

3. What preventive steps will you recommend so that the next instalment does not produce the same backlog?

Read the worked answer

Preventive system, not a repeat camp:

  1. Pre-instalment verification: start 30-45 days before each instalment; run Aadhaar-bank-land triangulation and generate an exception list by category.
  2. Automatic alerts: SMS/IVR to farmers whose seeding failed, with the nearest CSC/bank and documents required; send a second reminder 10 days later.
  3. Single window: designate one nodal officer for PM-KISAN in the block and a weekly reconciliation meeting with bank, CSC, and revenue.
  4. Data quality: detect duplicates and invalid account lengths at entry; do not accept 9-digit accounts; require PIN and mobile number.
  5. Grievance tracking: token number for every complaint, dashboard of pendency, and escalation if unresolved in 15 days.
  6. Awareness: panchayat-level announcements about free/nominal correction camps and the fact that no agent can demand money for PM-KISAN.
  7. Audit: quarterly sample verification of 5% of beneficiaries, especially new and transferred land records.