Deprecated (16384): The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 150
 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php. [CORE/src/Core/functions.php, line 311]
Deprecated (16384): The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 151
 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php. [CORE/src/Core/functions.php, line 311]
Warning (512): Unable to emit headers. Headers sent in file=/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php line=853 [CORE/src/Http/ResponseEmitter.php, line 48]
Warning (2): Cannot modify header information - headers already sent by (output started at /home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php:853) [CORE/src/Http/ResponseEmitter.php, line 148]
Warning (2): Cannot modify header information - headers already sent by (output started at /home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php:853) [CORE/src/Http/ResponseEmitter.php, line 181]
LATEST NEWS UPDATES | Hollowing out a promise -Jean Dreze

Hollowing out a promise -Jean Dreze

Share this article Share this article
published Published on Jul 13, 2018   modified Modified on Jul 13, 2018
-The Indian Express

NREGA is a demand-driven programme and if the demand vanishes because wages are low and uncertain, nothing will be able to save it.

The National Rural Employment Guarantee Act (NREGA) is going through a deep crisis of delayed and failed wage payments. The problem is not new, but it is more serious than ever and threatens to undermine the entire programme.

The crisis has at least four manifestations: Delayed payments, rejected payments, diverted payments and locked payments. Let me try to spell them out, one by one.

Delays in wage payments have plagued NREGA ever since bank payments were introduced about 10 years ago. In recent years, there has been some improvement in what might be called first-step delays — the delays that occur before the final signature of a Fund Transfer Order (FTO). First-step delays are reasonably transparent and the system is designed to calculate the compensation due to workers (by the state government) when they occur. But the system hides the second-step delays — the delays that occur when bank transfers themselves are held up. In a recent analysis of NREGA wage payments in 10 states, Rajendran Narayanan, Sakina Dhorajiwala and Rajesh Golani found that second-step delays were as long as two months on average in 2016-17. Repeated demands for second-step delays to be disclosed and compensated for by the central government have fallen on deaf ears so far.

One reason why delays have persisted for so long is that the payment system is constantly being re-designed. First it was cash payments, then post-office payments, then bank payments, then specific banks, then various avatars of what is now called the National electronic Fund Management System (NeFMS), and now the Aadhaar Payments Bridge System (APBS). None of these innovations, so far, has been able to ensure payment within 15 days of the work being done, as prescribed under NREGA.

Even as the delays continue, the latest payment systems are largely responsible for rejected payments, diverted payments and locked payments. Rejected payments were not unknown earlier but they have become endemic ever since the linking of NREGA wage payments with Aadhaar. Linking the bank accounts of NREGA workers with Aadhaar may seem like a trivial matter but in practice it creates endless problems, associated for instance with inconsistencies between different databases — job cards, bank accounts and Aadhaar. Today, “e-KYC” (biometric authentication of Aadhaar-linked accounts) is compulsory for NREGA workers, if not in theory then certainly in practice. That, too, is a fountain of technical glitches. A senior official at the Ministry of Rural Development (MoRD) recently told me that the MoRD had identified more than 200 different possible reasons for a payment to be rejected. Some of the error codes, like “inactive Aadhaar”, are beyond the comprehension of the MoRD itself and even of UIDAI — both pleaded ignorance in response to an RTI on this matter. According to the NREGA’s management and information system (MIS), nearly Rs 500 crore of wage payments were rejected in 2017-18 alone.

Diverted payments is a pathology of the Aadhaar Payments Bridge System (APBS), the latest — but probably not the last — reconfiguration of the NREGA wage payment system. Under APBS, Aadhaar effectively becomes a financial address and wages are automatically paid into the worker’s last Aadhaar-linked account. Most workers, of course, are unaware of this rule, so they often look for their money in the wrong account. Worse, wages are sometimes paid into accounts that workers know nothing about, for example, accounts opened without consent in the initial Jan Dhan Yojana frenzy, or Airtel wallets. Even worse, wages are sometimes sent to the wrong person, because that person’s account has been linked to the concerned worker’s Aadhaar by mistake (for instance, due to data entry errors). These diverted payments are very difficult to retrieve — most NREGA workers are powerless to do anything about them.

Please click here to read more.

The Indian Express, 13 July, 2018, https://indianexpress.com/article/opinion/columns/nrega-scheme-rural-employment-wages-farem-crisis-modi-govt-5257239/


Related Articles

 

Write Comments

Your email address will not be published. Required fields are marked *

*

Video Archives

Archives

share on Facebook
Twitter
RSS
Feedback
Read Later

Contact Form

Please enter security code
      Close