The pension sent to someone else with the same name
👩 Sushma Sahu, 36, in Pandri, Raipur, began receiving ₹1,000 every month from the Mahtari Vandana Yojana in March 2024. The transfers came regularly, and she had budgeted for the money. In January 2026, when she checked her bank passbook, she noticed something odd: the deposits had been transferred to "Sushma Sahu, Bilaspur." She had been receiving the money but the official recipient name in the system was different. When she called the district office to ask about it, she was told: "There are two Sushma Sahus in the system with the same Aadhaar. This is a data error. We need to correct it, but you'll have to wait. The District Programme Officer is handling these cases one by one."
🚨 The problem
When identical names are entered in government databases, the system doesn't catch duplicates early. Payments can be credited to the wrong person's account (though the right bank account), creating confusion about who the official beneficiary is. Corrections require district-level investigation and take months.
🚀 How GabFORGE helped
GabFORGE escalated the duplicate-name issue beyond the backlog queue:
- 🔍 Verified the mismatch. Confirmed that Sushma's bank account was correct but her name in the Mahtari Vandana system had been registered differently—possibly a typo or a duplicate entry.
- 📞 Escalated to state-level Social Welfare Department. Contacted the state department instead of waiting for the district queue, reporting a potential data integrity issue affecting beneficiary confirmation.
- 📋 Documented the financial impact. Calculated that the name mismatch had created ₹24,000 in ambiguity (10 months × ₹1,000, plus three months pending), even though the money reached her account.
- 🏛️ Requested priority correction. Asked the state department to prioritize this case as a data-integrity issue that could affect future eligibility confirmation or pension continuation.
The state Social Welfare Department investigated within two weeks and found that Sushma's account linkage was correct; the name error was a display issue in their internal system. They corrected the record and issued a formal beneficiary confirmation letter. Sushma's eligibility was officially clarified, and she faced no disruption to future payments. ✅
🇮🇳 Why this matters
Duplicate-name errors shouldn't create years-long correction queues. GabFORGE reveals that state-level escalation can bypass district bottlenecks and that system corrections are a state responsibility, not a beneficiary burden.
The long version has Sushma's discovery of the name mismatch in her account, the months of waiting for district correction, and how escalating to the state level resolved what seemed like a permanent bureaucratic tangle.