DIRECT BENEFIT TRANSFER STATUS
REPORT & ISSUES
DBT – STAKE HOLDERS
 EFMS
 Agency (State Government)
– MORD
– NIC
•
CEPT & SDC DOP
•
Similar in case of Central Plan Schemes Monitoring System (CPSMS)
Architecture & Flow…
1.DBT beneficiaries Details
submitted in softcopy along
with Fund Credit Details
2. Fund Disbursement
details sent to the bank
3. Beneficiaries detail
pushed to CEPT at
regular intervals after
7. Processed and rejection
details are sent to
NIC at
regular interval of time
funds sent to banks
4
9
6
8
3
s are
5.
Account Number Logic & Related Issues…
 Combination of eMO Station code + Actual account number + Sanchay Post code
•
•
•
•
•
This helps in
Grouping FTOs
Sending FTOs to the
HPO
Back to the Sub
Offices
Backend
configuration of eMO
code with HO is done
at CEPT
There are duplicate
Account numbers
under the same HPO
•
4
Sanchaypost code
helps in identifying the
correct SO posting at
HO-SB
DBT ISSUES
Issues with Agencies:
 Inaccurate Master Data with the Agency
–
SO Code wrongly updated
–
Incorrect Account Number
–
Freezing of accounts done without verification and authentication by respective
HPOs.
Issues with NIC

DSCs not shared to the extent of FTO generated

When we download list of active NREGA accounts in Post Offices from MGNREGA
website, bank names are displayed in the Post Office column.

Special characters are included in Account numbers

Around 10 offices reported non receipt of funds for more than 30 days. Eg: Dhar HO
and Hoshangabad HO under Madhya Pradesh
DBT ISSUES
Issues with us:

Pre-requisites not installed by many Pos.

Wrong SO-codes were either updated through CEPT link or shared with the State
Government.

FTOs could not be kept unprocessed at the EOD.

Day end in Sanchay Post could not be executed keeping FTOs pending.

Fund not credited into Postmaster’s account in time by the nodal bank.

Fund received – files not received cases also reported.

No report available to monitor FTOs received/processed/pending/incompletely
processed.
DBT ISSUES

Back end data correction was noticed in many HPOs when database was examined.

Binary values were altered in tables prescribed to handle day begin and day end
operations.

FTOs received in NREGAeMO were either deleted or over written with other FTOs.

4750 database discrepancies handled in SDC and solution provided.
Prerequisites & Available Sanchaypost Tools
 SO & SO-SB Data comparison ( Balance verification tool) – This helps in ensuring that all
accounts standing opened at SO are available at SO-SB also.
 NEGA Accounts mapping Tool – This helps in generation of proper MIS and LOT for
MGNREGS accounts
 BO mapping exercise in Sanchaypost - This helps in generating BO wise NREGA credit
reports at the SO concerned
Accounts verification tool – This helps in automatic verification of lakhs of accounts in a
single stroke there by helps in freezing
This tool can be used any number of times
MIS generation and Monitoring of FTOs through “All in one tool”
8
Prerequisites in Sanchaypost & eMO Client
 Accounts have to be identified as NREGA (mapping tool available in SDC site)
 All NREGA accounts should be available both at HO and SO
 DB Analyser released on 12th August 2013 should be run in all sites (This is to equip
database to handle login issues through backend automatically)
 Data Entry for SB in the SOSB module should be upto date for all SOs.
 Sanchaypost latest version 7.0 should be installed with all updates available in SDC site
eMO
 Latest eMO client along with script to be downloaded from CEPT website
http://ftp.ptcinfo.org/Meghdoot7/Updates/Update6toMeghdoot7/ and installed in both HO
and SOs.
9
New Tools to handle EFMS published by SDC Chennai
 Automatic Comparison Tool – This is aimed at automating the process of verification of
accounts, Sanchay Code and eMO code
 Second Tool - All in one Tool
-
Back & Restore Tool – enabling partial processing of FTOs
-
Diagnostic Tool – FTOs held up already due to various inaccuracies
-
Updating Tool – Updating the status of FTOs and generating return files
-
All kinds of monitoring like FTOs not received at PO, FTOs received at CEPT
and not received by HPO, FTOs not received by CEPT but listed at NIC etc.
A live demo of a Post Office is arranged at the end of this presentation….
10
eFMS Comparison Tool- NIC / CEPT Vs Sanchaypost
data
Objective of the Tool
 Freezing of State Govt NREGA data with HO Sanchay Post data
 Reduces rejection of FTOs due to wrong Sanchay Post Code / Account Number
 Sanitization of State Govt NREGA data
 Validation of Sanchay Post codes configured in eMO website
Features of the Tool
a)
Automatic comparison with HO Sanchay Post data for facilitating freezing of State Govt
NREGA data.
b)
To ensure the quality of NREGA data
How eFMS Comparison tools works
eFMS Comparison Tool
CEPT WEBSITE
Download Sanchay Post codes
mapped
in eMO web site in CSV format
NREGA WEB SITE
State Govt Records - List of Post office
accounts to be downloaded from mgnrega
website in excel format
Head Post Office
– Sanchay Post
(Local Database)
Pre-requisites for eFMS Comparison Tool
 Download NREGASanchay code in CSV format from eMO website and copy it in the eFMS
comparison application folder (NregSanchayCodes.csv)
 Downloaded file name for respective HO from MGNREGA website http://nrega.nic.in using the
following steps
a) Select the Circle Name available on the left side
b) Click on Link List of Active NREGA Workers Account in Post Office under MIS Report –
Latest Report
c) Click on accounts under No. of Post Office Accounts for the respective HO and download the
same in xls format by clicking Excel View
d) As we face errors while importing the xls file downloaded from MGNREGA site, save the
downloaded file as .xls in another location without altering the file name. Ensure that Sheet
name
e) Screenshots for downloading the xls file from MGNREGA site is available in Readme file.
eFMS Comparison Tool – Step by Step
 Creation of Super/User logins
eFMS Comparison Tool – Step by Step
 Once the Super/User logins are created, SQL information needs to be entered.
 First Match the Sanchay Post Code of HO with CEPT eMO data
eFMS Comparison Tool – Step by Step
Once HO Code is freezed, all Sub Office codes should be
compared with CEPT Sanchay Post Codes. No Sub office
data should be left out without matching.
You can proceed further only if HO and all Sub Office codes
are mapped.
eFMS Comparison Tool – Step by Step
Supervisor option
 Import the NREGA data (post??.xls) downloaded from NREGA website by browsing the
corresponding folder
eFMS Comparison Tool – Step by Step
Operator Login
 Click on “Compare” menu
 This Compares eFMS data (State Govt) with Sanchay Post Data
 Accounts with discrepancies like Invalid Sanchay Post Code, Account Number and Incorrect
Name will be listed for cleansing.
 These discrepancies can be cleared using “Solutions” Menu
eFMS Comparison Tool – Step by Step
Steps to clear the discrepancies using “Solutions” Menu in Operator Login
Incorrect Sanchay Post Code
Click on “PO Code – Account Number” under Solutions Menu
a)
Accounts with discrepancies only will be listed
b)
Check the accounts with office records
c)
Select the appropriate Office Name and click on the check box of the correct account
number which is mapped with incorrect Sanchay Code
d)
Click on “Update”. Now the account number with wrong PO Code will be mapped to
correct Sanchay Post Code
e)
This tool will list the discrepancy reason in the last column (Status) for reference
f)
Once all the relevant records are updated, left out accounts numbers will be treated
as rejected
g)
Click on “Reject” for rejecting the records without selecting any record
h)
These records will be returned with appropriate rejection reason to State Govt
authorities
eFMS Comparison Tool – Step by Step
Screen shot of Solutions – PO Code – Account Number
eFMS Comparison Tool – Step by Step
 Account Number 914449 with Sanchay Post Code PSS is changed to PJP Code
 If Name discrepancy is available for same account, a message will be
thrown to check Solution - Name
eFMS Comparison Tool – Step by Step
 Procedure to “Reject” records (without clicking check box) which
has discrepancy of Sanchay Post Code, Account Number
eFMS Comparison Tool – Step by Step
Steps to clear the “Name” discrepancies using Solutions Menu
Name Mismatch discrepancy
a)
Click on “Name” under Solutions Menu
b)
Accounts with discrepancies in Name only will be listed
c)
Check the accounts with office records
d)
Select the appropriate Office Name and click on the check box of the account for which the
name discrepancy is not critical
e)
Click on “Update”. Now the account number with Name as per Sanchay Post will be
returned to State Govt authorities for correcting their database.
f)
Once all the relevant records are updated, left out accounts numbers will be treated as
rejected
g)
Click on “Reject” for rejecting the records without selecting any record
h)
These records will be returned with appropriate rejection reason to State Govt authorities
along with Name availabe in Sanchay Post for examination
Procedure to clear Name Discrepancies
User
need to
confirm
with
office
record
and
confirm
correctne
ss
eFMS Comparison Tool – Step by Step
eFMS Comparison Tool – Step by Step
Procedure to reject record where name discrepancy is noted
eFMS Comparison Tool – Step by Step
Supervisor Login
Click on “Update” to check whether all records have been
matched with Sanchay Post by operator
eFMS Comparison Tool – Step by Step
Click on “Export to NIC” for generating the excel file.
This excel file with extention .xls should be sent to NIC
through eMail to nicdrd@nic.in
Reports
 Following reports are available for reference
a)
Discrepancy Reports
* Account Number Discrepancies
* Sanchay Code Discrepancies
* Account Holder Name Discrepancies
b) Sanchay Post – CEPT Code Mapped Status
c) Log Report
d) Summary Report
Reports – Screen shot
VIDEO TUTORIAL ON eFMS Comparison Tool
32
All in one tool – The second tool – features & it’s
functionality
Why this tool?
 As of now no option available to check the number of FTOs Received, Processed, Pending,
Heldup to clear the pending FTO’s at Post Office end.
 Difference in FTOs Received/Processed/Pending exists between NREGA, eMO
 There is no tool to compare the details of pending FTOs vis a vis received for payment for HO
user
 Several Tools released by SDC from time to time to clear the held up/pending FTOs due to
various reasons are bundled in this All in One Tool with additional features
33
Pre requisites – eFMS All in One Tool
 Download the Pending FTOs in csv format from eMO website
 Download the Processed FTOs in csv format from eMO website
 Download the pending FTOs in xls format from NREGA website
Backup – Restore Tool
a)
Backup – Restore Tool – Facilitates Sanchay Post Day end with unprocessed FTOs (Due to
insufficient funds) by moving the unprocessed FTOs as backup and restoring FTOs only
when it needs to be processed ensuring day end operation.
NREGA User Update Tool
b) NregaUserUpdate – This tool updates the NREGA User, missing tables, rectifies the
exceeding range of account numbers issue
Diagnostic Tool
c) Diagnostic Tool – For processing the incompletely processed FTOs and to reject FTOs due to
invalid Sanchay Post Code and other reasons
Update Manual Payment Tool
Several FTOs which were paid manually due to various
reasons are pending in Local system. These needs to be
updated as processed. This tool updates the FTOs status in
local system as Processed by getting updated status from
eMO website which was already updated as processed.
Reports
Following reports are available for given period
a)
Fully Processed FTO – Received Datewise/FTOwise/Processed Datewise
b)
Pending FTOs as on date –FTOwise/Received Datewise
c)
Incompletely Processed FTOs – FTOwise/Processed datewise/Received datewise
d)
Comparison report – FTO pending at NREGA, CEPT and PO
VIDEO TUTORIAL on eFMS All In One Tool
40
DBT ISSUES
Status of FTOs handed
From 01/04/13 To 19/09/13
Circle
Total Received
Total Processed
2
1
GUJARAT
211
177
HARYANA
64
62
JHARKHAND
230
206
KERALA
672
510
49662
45772
7125
6711
ORISSA
287
248
RAJASTHAN
453
371
58706
54058
CHATTISGARH
MADHYA PRADESH
MAHARASHTRA
Total
FTO Pending Status as on 19-09-2013
FTOs Not Processed Circlewise
Cirlce
Total
1 Day
2 Days
4 Days
7 Days
15 Days
30 Days > 30 Days
GUJARAT
36
22
0
0
5
4
1
4
KERALA
162
0
0
0
79
69
13
1
RAJASTHAN
82
42
7
0
21
2
10
0
JHARKHAND
24
17
7
0
0
0
0
0
MADHYA PRADESH
3890
587
365
45
237
341
552
1763
MAHARASHTRA
414
306
59
7
12
15
8
7
HARYANA
2
2
0
0
0
0
0
0
CHATTISGARH
1
1
0
0
0
0
0
0
ORISSA
39
18
2
0
17
0
2
0
Total
4650
995
440
52
371
431
586
1775
Responsibilities of nodal officer, circle office
 Monitoring of eMO website for NREGA FTO pending status > 7 days.
 Verification of Sanchay Post codes in eMO configuration
 Coordination with Local Banks for settlement of non credit
 Coordination with NIC, CEPT, SDC for issues raised by Post offices.
 Monitoring over the funds received from State Govt authorities with funds credited into DOP
account.
Workshop at Bhopal, Jaipur & Ranchi

We were really struggling to handle many FTOs at a time during the
implementation phase at Madhya Pradesh

Around 54058 FTOs were handled after the workshop at Bhopal

The contribution of System Administrators, Postmasters is tremendous

Issues pertaining to FTOs handling were discussed with System
Administrators

Confidence level is the only concern.
Future to come …. In pipeline
 CPSMS will be introduced shortly
 All benefits will be credited only through account
 A master data verification tool is published for CPSMS by SDC Chennai
 This has been evaluated at 17 places including the following
Warangal (AP)
PujaPoora (Kerala)
Vidhisha (MP)
Wardha (MH)
Gondia (MH)
45
Enhancements in the Tool planned from the workshop
at Pune..
 Provision of a search option of FTO in the backup and restore tool - provided
 Provision of a bulk selection of accounts based in the SOcode for rectification instead of every
single account - Provided
Reach Us…..
 Contact for EFMS Solution
Email: efmsindiapost@gmail.com
Phone: 044-28524482,
Mobile:
Shri Mohandoss
:
+91 96002 53873 or
Ms Narmadha
:
+91 99448 80218
47
Thank You