Download Report

MGNREGA: e-FMS/DBT Manual for integration with Banks
Introduction to e-FMS:
MGNREGA has a MIS viz. NREGASoft; the architecture of the NREGASoft is equipped to
capturing all the transactions in almost real time. One of its most important modules is the
Electronic Fund Management System (e-FMS).
The e-FMS operates on principle of decentralized decision-making and centralized fund
management. Under this system, every expenditure point is electronically linked to the
central server through which the implementing agencies can generate fund transfer orders
(FTO) which automatically pull the required amount from the State Fund and credit the
account of the end users (wage seekers or suppliers)
e-FMS system not only promises reduction of delays in payments, corruption, parking of
funds but increases accountability, transparency and optimization of resource utilization.
Steps involved:
1. State will open/ declare a Nodal Agency Account preferably at State or at District
level in a Commercial Bank (Sponsor Bank). This will be the Debtor Account.
Beneficiaries to whom payments are to be made may have their account in any of the
Commercial Bank/RRB, Co-operative Bank or Post Office.
2. Each Nodal Agency will register their nodal agency account in NREGASoft.
3. Each FTO from that Nodal Agency will contain that nodal agency account as D ebtor
Account and many credit accounts in different Commercial Bank/RRB.
4. The FTO will be shared with Sponsor Bank having nodal agency account.
5. NREGAsoft has setup SFTP server which act as a communicating point for banks.
Fund T ransfer O rder after dually digitally signed will be placed on this SFTP server in
different folders. Four folders will be created for each Sponsor Bank. The name and
purpose of these folders are as follows:
a. FTO-<bank-short-name> (eg. fto-sbi): This will contain all FTOs generated
for payment with debiting account (nodal agency account) in State Bank Of
India. NREGAsoft will place these FTOs and Nodal agency Sponsor bank will
pull it. Each FTO will be digitally signed by two signatories of MGNREGA.
b. FTO-ack-<bank-short-name> (eg. fto-ack-sbi): This will contain all responses of
fate of transactions from nodal agency Sponsor Bank. The response will be
generated twice, pre-crediting and post crediting the account of worker.
Sponsor bank will place these responses and NREGASoft will consume the same
and reflect it in its MIS. Each response will be digitally signed by authorized
person from Sponsor Bank.
c. FTO-failed : This will contain all FTOs which are found tampered/corrupt by
Sponsor Bank. Sponsor Bank will place these FTOs and NREGASoft will consume.
d. account_statement: This will contain account statement of the nodal agency bank
account. Nodal agency account bank will place the statement and NREGASoft will
take. Account statement will be digitally signed by authorized person from bank.
e. Digital Signature Certificate (DSC) Management:
i. DSC of authorized signatories will be shared with bank through web
services.
ii. Bank will share the authorized signatory of bank to NREGASoft
through web service.
f. Response received from bank will be incorporated into NREGAsoft database at
10.00 a.m. and 5.p.m. daily.
Note: Sponsor Banks must automate the above to avoid any delays in the payments. The
response of the transaction must be sent latest in T+1 days without any default. Otherwise
the responsibility of any further delay will be with the Banks
6. Bank will identify a machine which will communicate with NREGAsoft SFTP server
and give t h e R eal Static IP address of that machine to NIC ([email protected]). NIC will
get the required port open for that machine and will confirm through reply all email
The file formats, Table structure and naming convention of FTOs, Response of FTOs and
Account statement are as follows:
Fund Transfer Order (FTO):
Objective
: To credit the amounts to NREGA beneficiaries a/c having account in Bank/
Post Offices from the debit account (through NEFT/CBS).
Sender
: Second signatory as designated by State. Example: Block Development Officer
(if eFMS is implemented at Block level and FTOs are sent from Block level)
Second signatory as designated by State. Example: Gram Pradhan
(if eFMS is implemented at Block level and FTOs are sent from Block level)
Receiver
: Banks
Folder
: ‘fto-<bank_short_name of the nodal bank>’ in the respective SFTP server.
Eg.: fto-sbi for ‘State Bank of India’
DSC required?: Yes
XML TAG Description for ‘NON-AADHAAR’ based FTO:
SN
TAG NAME
Type
Length
Remarks
1o.
Account_debit
char
18*
Debit account no.
2
2
ifsc_code_debit
char
11
IFSC CODE of debit A/c no.
3
trans_date
char
10
Date on which FTO generated(dd/mm/yyyy)
4
reference_no
char
32*
Unique reference no.
5
Bank_name
char
35
Credit Account's Bank name
6
branch_code
char
20
Credit Account's Branch code
7
wg_branch_name
char
50
Credit Account 's Branch Name
8
ifsc_code_credit
char
11
Credit Account's IFSC Code
9
account_credit
char
18*
Credit Account no.
10
name
char
70*
Account holder name
11
job_card_no
char
34
NREGA Job Card No. of Account Holder
12
Aadhar_no
char
12
Aadhar number of Account Holder, if available
13
address
nvarchar
60
Account holder address
14
currency
char
5
Rupee or Paisa
15
d_c
char
6
Debit/Credit
16
narration
char
75*
17
amount
char
16
18
email
char
30
Amount in rupees round up to 2 decimal
places
email of account holder (credit)
19
bc_agency_code
char
8
Business Correspondent 's agency code
20
csp_code
char
25*
CSP Code
21
card_ref_no
char
25*
Card/reference no. of BC
Note: Length has been changed for the * marked cases.
NOTE: The “reference_no” is a unique code for each transaction and will never be duplicate.
If it is found to be in duplicate by the bank at any point of time, then it should not be
processed and the same should be communicated to MoRD. (Neither Processed nor
Rejected/Invalid)
(Sample) XML FILE FOR ‘NON-AADHAAR’ BASED FTO:
<FTO>
<account>
<account_debit>00001234567</account_debit>
<ifsc_code_debit>SBIN0012109</ifsc_code_debit>
<tran_date>14/12/2011</tran_date>
<reference_no>2412021000NRG231120110019967</reference_no>
<bank_name>State Bank of India</bank_name>
<branch_code>SBIN0012109</branch_code>
<wg_branch_name>SHERAGADA</wg_branch_name>
<ifsc_code_credit>SBIN0012109</ifsc_code_credit>
<account_credit>31033639108</account_credit>
<name>MANU DAS</name>
<job_card_no>OR-12-021-003-001/29416</job_card_no>
<Aadhaar_No />
<address>House No, BARAMUNDULI, SHERAGADA, GANJAM, ODISHA</address>
<currency>Rupee</currency>
<d_c>Credit</d_c>
<narration>Wage</narration>
<amount>750</amount>
<email>[email protected]</email>
<bo_agency_code />
<csp_code />
<card_ref_no />
</account>
</FTO>
Filename Format for ‘Non-Aadhaar’ based FTO:
S i g n _ < location code>_<creationDate>FTO_<serialno>.xml
Or
S i g n _ < location code>_<creationDate>FTO_<serialno>_p.xml
Or
S i g n _ < location code>_<creationDate>FTO_<serialno>_c.xml
where ‘creationDate’ should be in ‘ddmmyy’ format.
Example:
If location code is KN1505004009 and Fund Transfer Order is created on 27/08/2012 and
serial no. is 583, then FTO filename will be: Sign_KN1505004009_270812FTO_583.xml
2. BANK RESPONSE FILE (For Non-Aadhaar FTOs)
Objective
: To send the responses of fate of transactions from nodal agency account
(Sponsor Bank) for the FTOs and transactions sent. NREGASoft will consume these response
files and updates NREGA db.
Sender
: Banks
Receiver
: NREGAsoft
Folder
: ‘fto-ack-<bank_short_name of the nodal bank>’ in the respective SFTP server.
Eg.: fto-ack-sbi for ‘State Bank of India’
DSC required? : Optional
XML TAG Description for Bank Response XML File:
SNo
Column_name
Type Length
Remark
1
DT_TRAN
char
10
Trans_date as in FTO XML file
(MM/DD/YYYY )
2
REF_NO
char
32*
Reference_no as in FTO XML file
3
CR_IFSC
char
11
Credit Account’s IFSC Code
4
CR_ACCOUNT
char
18*
Credit Account no.
5
AMOUNT
char
16
Amount credited
6
FLAG
char
1
7
currency
char
5
Possible value is P/R/I
where:
P (Processed)
R (Rejected)
I (Invalid Account)
Rupee or Paisa
8
UTRNO
char
16
9
PROCESS_DT
char
10
Value UTR NO. in case of NEFT;
Space -> Direct CR in account (CBS)
Date of processing (MM/DD/YYYY)
char
10
REJECTION_REASON
30
Reason in case of rejection
Note: Length has been changed to the * marked cases.
Ref-no is Unique to Transaction and it is comprising of:

10 digit location code from where transaction is authorized (2412021000)

3 char Scheme Short name (NRG)

8 digit date (23112011)

7 digit serial no. 0019967
(Sample) RESPONSE FILE from Bank (for Non-Aadhaar FTO)
<NewDataSet>
<Table>
<DT_TRAN>12/14/2011</DT_TRAN>
<REF_NO>2412021000NRG231120110019967</REF_NO>
<CR_IFSC> SBIN0012109</CR_IFSC>
<CR_ACCOUNT>31033639108</CR_ACCOUNT>
<Currency>Rupee</Currency>
<AMOUNT>1250</AMOUNT>
<FLAG>P</FLAG>
<UTR_NO> SBIN001210936529</UTR_NO>
<PROCESS_DT>12/15/2011</PROCESS_DT>
<REJECTION_REASON />
</Table>
</NewDataSet>
Frequency for response by bank: Daily at 7.00 p.m.
Filename Format for Bank Response File (For Non-Aadhaar):
response_<bankshortname>_<debiting account no>_<Date>.xml
where ‘Date’ -> Date of Response Generated and should be in ‘ddmmyy’ format.
Bank can add incremental counter at the end of file name if there is more than one response
file.
Example:
If bank is State Bank of India (SBI), account no. of nodal agency is 1201 and date of response
generation is 27/08/2012, then response filename will be:
response_sbi_1201_270812.xml
3. Nodal agencies Account Statement
Statement of account from bank
Objective
: To send the Statement of account from bank
Sender
: Banks
Receiver
: NREGAsoft
Folder
: ‘account_statement’ in the respective SFTP server.
DSC required? : No
Frequency
: Daily
XML Structure for the Statement of account
<Statement>
<Account_Info>
<Account_Number></Account_Number>
<Statement_date>(DD/MM/YYYY)</Statement_date>
<Opening_balance></Opening_balance>
<Closing_balance></Closing_balance>
</Account_Info>
<Transaction_Info>
<ifsc_code_debit></ifsc_code_debit>
<Account_debit></Account_debit>
<Reference_no></ Reference_no>
<utr_no></utr_no>
<dr_cr_flag></dr_cr_flag>
<Tran_type></Tran_type>
<ifsc_code_credit></ifsc_code_credit>
<Account_credit></Account_credit>
<Chq_no></Chq_no>
<Amount></Amount>
<Description></Description>
</Transaction_Info>
</Statement>
Details of parameters used in Statement:
• For account statement of one account , <Account_info> tag will appear once in the file
whereas <Transaction_info> tag will repeat for each transaction.
• Opening and Closing Balance is referring to opening and closing balance for the
statement date. Statement date must be in DD/MM/YYYY format.
• IFSC code will be available, if it is NEFT Transaction otherwise it is blank
• UTR no. will be available, if it is NEFT transaction else tran id will be available.
• Dr_cr_flag will contain ‘Dr’ for Debit and ‘Cr’ for Credit.
• File will contain balance details, if there is no transaction on a particular day.
• Transaction Type with two character CODE:
1. Receipt -(RE)
2. NEFT -(NE)
3. CBS -(CB)
4. Cheque -(CH)
5. Refund -(RF)
6. Interest -(IN)
6. Bank Charges -(CG)
Filename Format for statement:
NREGA_<accountno>_<Date>.xml
where <Date> should be ‘ddmmyyyy’ format.
Example:
If your account no is 1201 and date is 21/09/2012 (dd/mm/yyyy), then the filename will be:
NREGA_1201_21092012.xml
4. AADHAAR Based Fund Transfer Order (FTO)
Objective
: To credit wage-amount to NREGA workers’ a/c having Aadhaar seeded in NPCI
Mapper with worker’s bank account.
Sender
: Second signatory as designated by State. Example: Block Development Officer
(if eFMS is implemented at Block level and FTOs are sent from Block level)
Second signatory as designated by State. Example: Gram Pradhan
(if eFMS is implemented at Block level and FTOs are sent from Block level)
Receiver
: Banks
Folder
: ‘fto-<bank_short_name of the nodal bank>’ in the respective SFTP server.
Eg.: fto-sbi for ‘State Bank of India’
DSC required?: Yes
XML Tag Description for ‘AADHAAR’ based Fund Transfer Order (FTO)
SNo
TAG NAME
Type
Length
Remarks
.
1
Account_debit
char
18*
Debit account no.
2
2
ifsc_code_debit
char
11
IFSC CODE of debit A/c no.
3
trans_date
char
10
Date on which FTO generated(dd/mm/yyyy)
4
reference_no
char
32*
Unique reference no.
5
Npci_ref_no
char
13
Unique reference number for use by bank to
transact with NPCI
6
Bank_name
char
35
Should be blank for Aadhaar Based Payment
7
branch_code
char
20
Should be blank for Aadhaar Based Payment
8
char
50
Should be blank for Aadhaar Based Payment
9
wg_branch_nam
eifsc_code_credit
char
11
Should be blank for Aadhaar Based Payment
10
account_credit
char
18*
Should be blank for Aadhaar Based Payment
11
name
char
70
Account holder name
12
job_card_no
char
34
NREGA Job Card No. of Account Holder
13
Aadhar_no
char
12
Aadhaar no. of Account Holder, if available
14
address
nvarchar
60
Account holder address
15
currency
char
5
Rupee or Paisa
16
d_c
char
6
Debit/Credit
17
narration
char
75*
18
amount
char
16
19
email
char
30
Amount in rupees round up to 2 decimal
places
email of account holder (credit)
20
bc_agency_code
char
8
Business Correspondent 's agency code
21
csp_code
char
25*
CSP Code
22
card_ref_no
char
25*
Card/reference no of BC
Note: Length has been changed for the * marked cases.
NOTE :
“Npci_ref_no” is a 13-character unique code for each transaction and will never be
duplicate. If it is found to be in duplicate at any point of time, then bank should not process
it and communicate the same to MoRD. (Neither processed nor rejected/Invalid)
(Sample) XML FILE FOR ‘AADHAAR’ BASED FTO:
<FTO>
<account>
<account_debit>123456789</account_debit>
<ifsc_code_debit>XXXX0040681</ifsc_code_debit>
<tran_date>05/01/2014</tran_date>
<reference_no>XX25007023NRG020120140527283</reference_no>
<npci_ref_no>XXXXXXXXXXXXX</ npci_ref_no>
<bank_name/>
<branch_code/>
<wg_branch_name/>
<ifsc_code_credit/>
<account_credit/>
<name>Lokamma</name>
<job_card_no>XX-25-007-023-002/341</job_card_no>
<Aadhaar_No>XXXXXXXX</Aadhaar_No>
<address>House No</address>
<currency>INR</currency>
<d_c>Credit</d_c>
<narration>Wage</narration>
<amount>1218</amount>
<email/>
<bo_agency_code/>
<csp_code/>
<card_ref_no/>
</account>
</FTO>
Filename Format for ‘Aadhaar’ based FTO:
S i g n _ < location code>_<creationDate>APB_FTO_<serialno>.xml
where ‘creationDate’ should be in ‘ddmmyy’ format.
Note: In FTO Filename, APB is included to identify the Aadhaar Based FTO.
Example:
If location code is KN1505004009 and Fund Transfer Order is created on 27/08/2012 and
serial no. is 583, then FTO filename will be: Sign_KN1505004009_270812APB_FTO_583.xml
BANK RESPONSE FILE (For Aadhaar FTOs)
Objective
: To send the responses of fate of transactions from nodal agency account
(Sponsor Bank) for the Aadhaar based FTOs and transactions sent. NREGASoft will consume
these response files and updates NREGA db.
Sender
: Banks
Receiver
: NREGAsoft
Folder
: ‘fto-ack-<bank_short_name of the nodal bank>’ in the respective SFTP server.
Eg.: fto-ack-sbi for ‘State Bank of India’
DSC required? : Optional
XML TAG Description for Bank Response XML File:
SNo
Column_name
Type Length
Remark
1
DT_TRAN
char
10
Trans_date as in FTO XML file
(MM/DD/YYYY
) in FTO XML file
Reference_no as
2
REF_NO
char
32*
3
NPCI_REF_NO
char
13
Unique reference number for use by
bank to transact with NPCI
4
CR_IFSC
char
11
Credit Account’s IFSC Code – Can be left
blank
5
CR_ACCOUNT
char
18*
Credit Account no. – Can be left blank
6
AMOUNT
char
16
Amount credited
7
FLAG
char
1
8
currency
char
5
Possible value is P/R/I
where:
P (Processed)
R (Rejected)
I (Invalid Account)
Rupee or Paisa
9
UTRNO
char
16
Unique Transaction number generated
by sponsor bank
10
PROCESS_DT
char
10
Date of processing (MM/DD/YYYY)
char
11
REJECTION_REASON
30
Reason in case of rejection
Note: Length has been changed to the * marked cases.
Ref-no is Unique to Transaction and it is comprising of:

10 digit location code from where transaction is authorized (2412021000)

3 char Scheme Short name (NRG)

8 digit date (23112011)

7 digit serial no. 0019967
(Sample) RESPONSE FILE from Bank (for Aadhaar FTO)
<NewDataSet>
<Table>
<DT_TRAN>12/14/2011</DT_TRAN>
<REF_NO>2412021000NRG231120110019967</REF_NO>
<NPCI_REF_NO>XXXXXXXXXX</NPCI_REF_NO>
<CR_IFSC> SBIN0012109</CR_IFSC>
<CR_ACCOUNT>31033639108</CR_ACCOUNT>
<Currency>Rupee</Currency>
<AMOUNT>1250</AMOUNT>
<FLAG>P</FLAG>
<UTR_NO> SBIN001210936529</UTR_NO>
<PROCESS_DT>12/15/2011</PROCESS_DT>
<REJECTION_REASON />
</Table>
</NewDataSet>
Frequency for response by bank: Daily at 7.00 p.m.
Filename Format for Bank Response File (For Non-AAdhaar):
response_<bankshortname>_<debiting account no>_<Date>.xml
where ‘Date’ -> Date of Response Generated and should be in ‘ddmmyy’ format.
Bank can add incremental counter at the end of file name if there is more than one response
file.
Note – The banks are expected to send separate response files for Aadhaar based FTOs than
Non-Aadhaar FTOs. The banks are expected to provide ‘final and correct’ response for Aadhaar
based FTOs within timeframe of T+2. This response should incorporate all settlements done by
sponsor banks with beneficiary banks out of the system (especially in case of transactions with
‘Deemed Success’ status). Additionally, it is recommended that the banks use ‘Dispute
Management System’ developed by NPCI to settle all disputes on transaction status.
Example:
If bank is State Bank of India (SBI), account no. of nodal agency is 1201 and date of response
generation is 27/08/2012, then response filename will be:
response_sbi_1201_270812.xml
SHARING OF Signatories’ DSCs to BANKS
Objective
: To match DSCs by Bank
Sender
: NREGAsoft
Receiver
: Bank
Folder
: ‘DSC_DETAIL’ in the respective SFTP server
DSC required?: No
Sample XML file to share DSCs with Bank:
<NewDataSet>
<Table>
<district_code>3129</district_code>
<Block_code>3129000</Block_code>
<Panchayat_code>3129000797</Panchayat_code>
<CName>CN=SINGH MANOJ KUMAR</CName>
<Cemail/>
<Cissuedt>2014-02-06T11:57:02+05:30</Cissuedt>
<CExpireddt>2016-02-06T11:57:02+05:30</CExpireddt>
<cCertificate>01100111...01100111</cCertificate>
<Enrollmentdt>2014-02-06T16:28:51.67+05:30</Enrollmentdt>
<cou>OU=FOREST</cou>
<level>Acnt</level>
<status>C</status>
</Table>
</NewDataSet>
TAG Description of the XML file to share DSCs with Bank
S.No.
Tag Name
Type
Length
Description
1
district_code
char
4
Location of signatory
2
Block_code
Char
7
Location of signatory
3
Panchayat_code
Char
10
Location of signatory
4
CName
Varchar
250
Name of Signatory
5
Cemail
Varchar
50
Email of Signatory
6
Cissuedt
datetime
Issue date of DSC
7
CExpireddt
datetime
expiry date of DSC
8
cCertificate
text
9
Enrollmentdt
datetime
10
Cou
Varchar
max
Binary DSC in string format
Enrollment date of DSC in Nregasoft
50
Organisation unit
11
level
char
4
Level i.e I or II signatory (possible values
are Acnt and PO respectively)
12
status
char
1
Active status of DSC
Filename Format of XML file to share DSCs with Bank:
<state_short_name>DSC_<bank_short_name><date_and_time_of_file_generation>.xml
where ‘date_and_time_of_file_generation’ should be in ‘ddmmyyyyhhmmss’ format.
Example:
If the XML file is generated for ‘Allahabad Bank’ of ‘Uttar Pradesh’(UP) State on 17/02/2014
at 11:57:37, then XML filename will be: UPDSC_ALLA17022014115737.xml
AADHAAR SEEDING IN BANKS
Objective
: To seed workers’ Aadhaar numbers in Bank database for the account number
matching cases. (if demographic authentication of worker’s aadhaar number seeded in nregaSoft is
‘success’ and the account number entered in NREGASoft is ‘frozen’, those workers’ details are sent
to respective Banks to seed Aadhaar number in Bank database and map Aadhaar number in NPCI
Mapper . This will enable to credit the payments to the beneficiaries through Aaadhar Based
Payment.
Sender
Receiver
Folder
: MoRD, State Functionaries at Block/GP level
: Banks
: ‘<bank_short_name>\UIDSEED’ in the respective SFTP server.
Eg.: sbi\UIDSEED for ‘State Bank of India’
DSC required?: Yes
(Sample) XML FILE FOR ‘AADHAAR SEEDING’ in Bank
<NREGA>
<worker_uid_ac>
<state_code>33</state_code>
<district_code>3306</district_code>
<tran_date>13/05/2014</tran_date>
<reg_no>CH-06-001-024-001/138 </reg_no>
<applicant_no>5</applicant_no>
<ac_holdner_name>LILAWATI</ac_holdner_name>
<uid_no>543689788883</uid_no>
<ac_no>33680802095</ac_no>
<bank_name>STATE BANK OF INDIA</bank_name>
<ifsc_code>SBIN0006792</ifsc_code>
<npci_map_status />
<err_code />
<err_desc />
<remark />
</worker_uid_ac>
</NREGA>
Filename Format for ‘AADHAAR SEEDING’ in Bank:
S i g n _ < location code>_<bank_short_name>_<creationDate>UIDseed _<serialno>.xml
where ‘creationDate’ should be in ‘ddmmyy’ format.
Example:
If location code is CH9900000001 and bank short-name is SBI and XML is created on
13/05/2014 and serial no. is 24, then FTO filename will be:
Sign_CH9900000001_SBI_130514UIDseed_24.XML
XML TAG Description for ‘Aadhaar Seeding’:
S.No.
Tag Name
Type
Length
Description
1
state_code
char
2
State-Code as per nrega db
2
district_code
char
4
District_code as per nrega db
3
tran_date
char
10
4
reg_no
varchar
34
Date on which XML generated
(dd/mm/yyyy)
Job card no. of nrega worker
5
applicant_no
int
6
ac_holdner_name
varchar
75
Name of worker as in jobcard
7
uid_no
char
12
Aadhaar (UID) No. of worker
8
ac_no
varchar
18*
A/c no. of primary account holder
9
bank_name
varchar
75
Bank name in which primary account
holder is having account
10
ifsc_code
char
11
IFSC Code of the branch in which
primary account holder is having
account
11
npci_map_status
varchar
1
Status of aadhaar seeding in NPCI
mapper (Y/N) (to be provided by Bank)
12
err_code
13
err_desc
varchar
14
remark
varchar
Worker’s applicant no. in nrega jobcard
Error code, if any, provided by Bank
Error description, if any, provided by
Bank
200
Note: Length has been changed to the * marked cases.
Remark, if any (provided by Bank)
RESPONSE FILE TO BE SENT FROM BANK TO MORD AFTER AADHAAR SEEDING IN NPCI MAPPER:
Objective
: To send the NPCI mapper status after workers’ aadhaar numbers seeded in Bank
Database by mapping worker’s ac no. and aadhaar no. in NPCI mapper. NREGAsoft will consume
these responses and will update in the NREGA DB.
Sender
: Banks
Receiver
: NREGAsoft
DSC required?: No
Sample Response file (After Aadhaar seeding in Bank DB):
<NREGA>
<worker_uid_ac>
<state_code>33</state_code>
<district_code>3306</district_code>
<tran_date>13/05/2014</tran_date>
<reg_no>CH-06-001-024-001/138 </reg_no>
<applicant_no>5</applicant_no>
<ac_holdner_name>LILAWATI</ac_holdner_name>
<uid_no>543689788883</uid_no>
<ac_no>33680802095</ac_no>
<bank_name>STATE BANK OF INDIA</bank_name>
<ifsc_code>SBIN0006792</ifsc_code>
<npci_map_status>Y</npci_map_status>
<err_code />
<err_desc />
<remark />
</worker_uid_ac>
</NREGA>
Filename Format for Bank Response File (After Aadhaar seeding in Bank DB):
response_uidseed_<bank_short_name>_<Date>.xml
where ‘Date’ -> Date of Response Generated and should be in ‘ddmmyy’ format.
Bank can add incremental counter at the end of file name if there is more than one response
file.
Banks are requested to share the response only after receiving response from NPCI about
status of mapping.
Example:
If bank is State Bank of India (SBI) and date of response generation is 13/05/2014, then the
response filename will be:
response_uidseed_SBI_130514.xml
Error Codes and Reason for Aadhaar seeding:
S.No.
1
Error Code
AS01
Description
Invalid account number
2
AS02
Different Aadhaar number already seeded in the account
3
AS03
Same Aadhaar number already seeded in the account
4
AS04
Customer name does not match
5
AS05
Joint Account. Customer Aadhaar number cannot be
matched in the request.
6
AS06
Account is in Aadhaar de-link mode
7
AS07
Account closed
8
AS08
Account dormant
9
AS09
Invalid Aadhaar number
10
AS10
Others
If DSC mismatch is found in Aadhaar seeding files, banks are expected to reject the whole
Aadhaar seeding file. Folder with the name “UIDseed_wastebin” has been created on SFTP
server for all banks to put Aadhaar seeding files rejected due to DSC mismatch error.