Political War Over Welfare Starves Odisha’s Elderly: Years of Partisan Resistance, Rushed Tech Rollout Lock 63K Out of State Pension| Special Report

Bhubaneswar:A whopping 63,848 elderly and vulnerable beneficiaries of Odisha’s Madhu Babu Pension Yojana (MBPY) are currently caught in a bureaucratic and technological limbo, leaving thousands without access to their monthly social-security support at a time when the state has enhanced the pension for super-senior citizens to Rs3,500 a month.

The human cost is particularly stark in Ganjam, where hundreds of elderly beneficiaries are reportedly struggling without money to buy essential medicines. For people whose pension is often the only dependable source of cash for food, medicines and daily necessities, a payment freeze is not merely an administrative inconvenience – it can become a question of survival.

The obvious question, therefore, is: how did Odisha’s pension distribution system slip into such a mess – and why has a welfare programme meant for the state's most vulnerable become politically damaging for the government?

And was the crisis of 63,000 pensioners created all of a sudden in 2026?

Nooooooooooooooooooo!

The current disruption is the product of a much longer chain: years of political pushback over the architecture of pension delivery, accumulated errors in a legacy beneficiary database, delayed backend preparation and, finally, a hurried transition to a technology-driven payment ecosystem without adequate protection for beneficiaries who could not survive a failed digital transaction.

Pension Crisis: The Genesis

The scale of the problem becomes clearer when the two pension systems operating in Odisha are separated.

According to administrative data of the Department of Social Security and Empowerment of Persons with Disabilities (SSEPD), the state’s MBPY had 36,75,008 registered beneficiaries by the end of August 2026.

But the problem is not that 63,848 people suddenly disappeared from the MBPY database.

Instead, 63,848 online applications were stuck in limbo, with technical blocks and unverified profiles preventing them from moving through the normal payment process. The SSEPD review identified delays at the foundational database level, including pending processing under block-level BSSO and urban local-body MEO user IDs.

Collectors were subsequently put on a mission-mode exercise to manually scrutinise and clear the files, with a deadline of August 18 to facilitate resumption of payments.

That distinction is crucial.

The 63,848 figure represents beneficiaries caught in the state scheme’s processing and verification logjam – not 63,848 people formally deleted from the MBPY rolls.

The crisis, therefore, is less about a mass deletion than about a system that knows the beneficiary exists but cannot successfully push the pension through the payment pipeline.

And that is precisely where the politics of welfare delivery meets the politics of technology.

The Trigger Did Not Begin in 2026

The temptation is to blame the entire episode on the 2026 technology rollout.

But the timeline tells a different story.

The roots of the present disruption go back several years, when the Centre began tightening the financial architecture through the Single Nodal Agency (SNA) framework for Centrally Sponsored Schemes.

The Union government’s framework was formally introduced in March 2021, with states given a transition period to bring their financial and beneficiary-payment systems into a more tightly integrated architecture.

The initial implementation window envisaged the SNA framework becoming operational from July 1, 2021.

The architecture was subsequently tightened further. In July 2023, the Centre moved towards an integrated system linking the Public Financial Management System (PFMS), State Integrated Financial Management Systems and the RBI’s e-Kuber payment architecture – the technological foundation for what became the SNA-SPARSH ecosystem.

In other words, Odisha was not handed a new system in 2026 and told to switch it on overnight.

The state had several years to prepare.

It had time to clean legacy beneficiary databases, reconcile Aadhaar and bank details, correct spelling variations, identify dormant or mismatched accounts, test payment pathways and create a parallel mechanism for beneficiaries who could not immediately clear digital verification.

Yet the transition appears to have gathered momentum only as the mandatory compliance window approached.

That is why the 2026 trigger was not a bolt from the blue.

It was the point at which years of unresolved database and administrative issues collided with a stricter digital payment architecture.

The State Was Caught Napping

The most damaging part of the episode is therefore not simply that technology failed.

It is that the transition exposed how inadequately the state had prepared for technology to fail.

Odisha's pension ecosystem is enormous. The MBPY alone has more than 36.75 lakh registered beneficiaries, many of them from rural and semi-urban areas. A significant portion of the database has evolved over years through local-level registration, creating the possibility of spelling differences, incomplete documentation, outdated bank details and other legacy inconsistencies.

Such a database cannot safely be thrown into a rigid automated verification pipeline without a safety net.

The state could have conducted block-wise data audits before migration. It could have run the new and old systems in parallel. It could have isolated doubtful accounts for manual verification without stopping payments. It could also have deployed field teams in advance to correct Aadhaar, bank and beneficiary-profile mismatches.

Instead, the difficult work of reconciliation appears to have followed the disruption.

The result was a classic administrative paradox: the government knew who many of the beneficiaries were, but the payment system could not confidently establish that they were digitally compliant.

For an elderly person waiting for pension money, that distinction means little.

What Was Role Of BJD, BJP Govt Behind The Mess?

The accountability for this systemic failure falls on both sides of the aisle: the foundation of the mess was laid by the previous Naveen Patnaik-led BJD government, while the rushed, unmitigated execution rests with the incumbent administration.

The previous BJD administration, which held power for more than twenty years until mid-2024, bears core responsibility for the structural vulnerabilities that triggered this lockout, directly contradicting the principles of its highly visible 5T framework

The BJP government, meanwhile, owns the responsibility for how the transition was executed after it came to power.

BJD’s Legacy

The MBPY was built over years since the launch year of 2008, when both BJD-BJP were in alliance. Since then it become one of the core pillar of Odisha's social-security politics.

The longer the system remained dependent on local records and physical distribution, the greater became the challenge of migrating a huge legacy beneficiary base into a tightly integrated digital ecosystem.

Despite consistently championing its heavily hyped 5T framework – which promised to use Technology and Time to revolutionize the administrative hierarchy – the previous BJD government completely ignored the multi-year window introduced by the Centre's SNA guidelines. Instead of using that runway to cleanse the database and build a resilient transition architecture, the administration chose political delay over digital readiness.

It did not complete that task sufficiently before leaving office.

That left the incoming government with a difficult inheritance: millions of beneficiaries, a large legacy database and a central compliance architecture that was becoming progressively harder to avoid.

BJP Government’s Mistake: Compliance Without A Cushion

When the political transition happened in 2024, the new administration still had roughly two years before the 2026-27 compliance horizon.

It inherited the problem – but it also inherited the responsibility to fix it.

The immediate failure was therefore one of execution.

A government preparing to shift a welfare system serving millions should have treated the payment network as critical infrastructure.

Instead of allowing automated verification to become the first line of defence, the state could have established a parallel cash safety net for beneficiaries whose digital records failed.

It could have completed the data-cleaning exercise before switching live payment flows.

And it could have identified vulnerable categories – particularly octogenarians, bedridden beneficiaries and persons with severe disabilities – for automatic manual intervention.

The fact that SSEPD eventually had to order mission-mode verification, manual processing, physical cash delivery and local-level interventions shows that the administration eventually recognised the problem.

But the safety net came after the fall, not before it.

63K Stranded: Not A Sudden Deletion

The distinction between MBPY and the Centre-linked National Social Assistance Programme (NSAP) is also important.

The NSAP dashboard showed beneficiaries falling from 20,13,426 in 2024-25 to 19,79,373 in 2025-26 – a reduction of 34,053 accounts.

The NSAP reduction reflects beneficiaries no longer appearing in the active central tracking matrix after the stricter digital integration and verification process.

The MBPY's 63,848, meanwhile, refers to online applications caught in the state scheme's verification and processing bottleneck.

The numbers therefore cannot be treated as a single pool of 97,901 pensioners "deleted" from Odisha's pension system.

The common denominator, however, is unmistakable: digital migration has exposed weaknesses in the state's beneficiary-data architecture.

The Key Takeaway: The lesson for the government is straightforward: clean the database before switching the system, keep a parallel payment route until the new architecture stabilises.
Also Read: