NOW DBT Payments in POSB Acount Operating Procedure

                                  Operating Procedure – APBS

Aadhaar Payment Bridge System

APBS’s Aadhaar Payment Bridge (APB) System, developed by NPCI has been helping the Government and Government Agencies in making the Direct Benefit Transfer scheme a success. APB System has been successfully channelizing the Government subsidies and benefits to the intended beneficiaries using the Aadhaar numbers. APBS System can be used for making bulk transactions towards distribution of subsidies, dividends, interest, salary, pension etc. The APB System links the Government Departments and their sponsor banks on one side and beneficiary banks (India Post) and beneficiary on the other hand. Chennai GPO is nodal office for DBT Payments

.

Process flow

Implementing Department/Ministries (State/Central) will share the files for credit to Public Financial Management System(PFMS)/Sponsor Bank

If the files are routed through PFMS, it will push the data to Sponsor Bank (Nodal Bank)

Sponsor Bank/Nodal Bank will process the files and send these files to National Payment Corporation of India(NPCI), within the clearing window of NPCI.

Chennai GPO is the Nodal office for processing the DBT/Electronic credits. NPCI will push the files to Destination Bank (Based on IIN code allotted to DOP for Account Based and AADHAR based credits). NPCI will debit the amount pertaining to files from Sponsor Bank account and will credit the destination Bank account (Chennai GPO account).

Credit files will be available in NPCI’s destined folder for CHENNAI GPO (being nodal office). Files to Chennai GPO will be pushed according to slots. Scripts which are getting executed in regular intervals will pick files pertaining to CHENNAI GPO and will be made 

ready for processing in FINACLE

Chennai GPO will check the availability of files in Finacle for processing.

If files are available, Chennai GPO will invoke a menu in Finacle for crediting funds to beneficiaries account available across circles. 

Process of Seeding AADHAR Number with CIF (CMRC MENU)

Valid AADHAR ID is added as ID Proof or Address Prof under Document Details

Preferred flag to be made as YES( refer Screen Shot)

Valid SBGEN/SBCHQ/SBBAS number to be added under Aadhaar Linked account number field

AADHAR MANDATE AVAILABLE flag to be made as YES if physical AADHAR MANDATE/Consent form is collected from the customer. (AADHAR MANDATE/CONSENT form circulated by RB Division to be obtained during SEEDING and maintained at PO)

Following validations have been built

Closed account /Silent/Frozen /TDA type of accounts cannot be filled as Aadhaar Linked Account Number

When AADHAR MANDATE AVAILABLE flag is changed as YES, Aadhaar Number and Aadhaar Linked account number fields are mandatory

Aadhaar Number linked as either ID Proof or Address Proof cannot be DELETED. It can only be modified.

Same Aadhaar Number cannot be linked to MULTIPLE CIFs

In case if multiple CIFs are available for same customer, it is recommended to merge CIFs before enabling AADHAR MANDATE FLAG 

CMRC – Inquiry function can be used to find list of CIF IDs linked to same AADHAR NUMBER.

Process of Mapper File Generation

Aadhaar based Inward file can flow only for ACTIVE AADHAR records. The Aadhaar status need to be active in NPCI (National Payment Corporation of India) and linked to DOP IIN (unique ID). This will happen through MAPPER file generation.

Once the CIF IS seeded with AADHAR Number, Valid Credit Account Number and ‘Aadhaar mandate available’ field is filled as YES in CMRC menu, batch file will generate MAPPER file at specified time after DC closure.

Mapper file will include accounts which are CLOSED, FREEZED in addition to new SEEDING.

This Mapper file will be sent to NPCI for checking the status of AADHAR and updating DOP IIN.

Acknowledgement file will be provided by NPCI instantly.

Sl. 3,4 and 5 are automated.

This report can be viewed through scheduled reports option and failed records can be corrected at PO end.

Inward file generation

Once the Mapper file is generated, Implementing Departments (Central/State Govt) can start sending Aadhaar Based Input file for active Aadhaar linked accounts.

Once Input file is routed to NPCI through sponsor bank, Inward file will be generated and pushed to DOP file path.

DOP need to confirm the receiving of funds at SBI settlement account opened for the purpose at Chennai.

These files will be automatically pushed to Finacle for crediting concerned customer accounts in Finacle. All inward files will be posted at CHENNAI GPO (Inward file Amount will be credited by sponsor bank to Chennai GPO Bank account)

The return settlement file will enable the net settlement at SBI Settlement account.

DOP need to check the net amount settlement at SBI settlement account. After return cycle is over, DOP may instruct the SBI to make the net settlement entry in their SBI Chennai account.

Example of the process cycle

DoP receives an inward file of 100 transactions of Rs. 50 each. Total amount credited in SBI settlement account after presentment cycle is over will be Rs. 5000. DoP finds that 3 transactions could not be processed and needs to be returned after processing the same in their CBS.  The return settlement would debit the SBI settlement account by Rs.150/-. Thus net amount to be credited to DoP SBI Chennai account will be 5000-150=4850/-

The list of return reason codes provided by the NPCI is attached to this SoP as Annexure 1. it should be mapped with the CBS return codes.

DOP should tally their transaction entries with the report available in ABPS system after the session closure. This will be done by the Chief Postmaster, Chennai GPO.

REPORTS

SOLs can generate APBS detailed report SOL wise/BO wise in HFINRPT after posting of Inward file.