SBI PENSION FUND SCHEME - CENTRAL GOVT - 26.0465 as on 22-06-2018 || SBI PENSION FUND SCHEME - STATE GOVT - 22.3578 as on 22-06-2018 || SBI PENSION FUND SCHEME E - TIER I - 24.123 as on 22-06-2018 || SBI PENSION FUND SCHEME C - TIER I - 24.5142 as on 22-06-2018 || SBI PENSION FUND SCHEME G - TIER I - 22.4054 as on 22-06-2018 || SBI PENSION FUND SCHEME E - TIER II - 22.2476 as on 22-06-2018 || SBI PENSION FUND SCHEME C - TIER II - 22.4388 as on 22-06-2018 || SBI PENSION FUND SCHEME G - TIER II - 21.3997 as on 22-06-2018 || NPS TRUST A/C-SBI PENSION FUNDS PRIVATE LIMITED- NPS LITE SCHEME - GOVT. PATTERN - 21.1498 as on 22-06-2018 || SBI PENSION FUNDS PVT. LTD. SCHEME - CORPORATE-CG - 16.5981 as on 22-06-2018 || NPS TRUST - A/C SBI PENSION FUND SCHEME - ATAL PENSION YOJANA (APY) - 12.5506 as on 22-06-2018 || SBI PENSION FUND SCHEME A - TIER I - 11.2367 as on 22-06-2018 || SBI PENSION FUND SCHEME A - TIER II - 20 as on 22-06-2018 || UTI RETIREMENT SOLUTIONS PENSION FUND SCHEME- CENTRAL GOVT - 25.2986 as on 22-06-2018 || UTI RETIREMENT SOLUTIONS PENSION FUND SCHEME- STATE GOVT - 22.518 as on 22-06-2018 || UTI RETIREMENT SOLUTIONS PENSION FUND SCHEME E - TIER I - 28.1948 as on 22-06-2018 || UTI RETIREMENT SOLUTIONS PENSION FUND SCHEME C - TIER I - 22.1833 as on 22-06-2018 || UTI RETIREMENT SOLUTIONS PENSION FUND SCHEME G - TIER I - 20.1855 as on 22-06-2018 || UTI RETIREMENT SOLUTIONS SCHEME E - TIER II - 22.8887 as on 22-06-2018 || UTI RETIREMENT SOLUTIONS SCHEME C - TIER II - 21.2072 as on 22-06-2018 || UTI RETIREMENT SOLUTIONS SCHEME G - TIER II - 20.7241 as on 22-06-2018 || NPS TRUST A/C-UTI RETIREMENT SOLUTIONS LIMITED- NPS LITE SCHEME - GOVT. PATTERN - 21.0025 as on 22-06-2018 || UTI RETIREMENT SOLUTIONS PENSION FUND SCHEME - CORPORATE-CG - 10 as on 22-06-2018 || NPS TRUST - A/C UTI RETIREMENT SOLUTIONS LTD. SCHEME - ATAL PENSION YOJANA (APY) - 12.9093 as on 22-06-2018 || UTI RETIREMENT SOLUTIONS PENSION FUND SCHEME A - TIER I - 11.1623 as on 22-06-2018 || UTI RETIREMENT SOLUTIONS PENSION FUND SCHEME A - TIER II - 10 as on 22-06-2018 || LIC PENSION FUND SCHEME - CENTRAL GOVT - 25.3413 as on 22-06-2018 || LIC PENSION FUND SCHEME - STATE GOVT - 22.6251 as on 22-06-2018 || NPS TRUST A/C-LIC PENSION FUND LIMITED- NPS LITE SCHEME - GOVT. PATTERN - 20.8783 as on 22-06-2018 || LIC PENSION FUND LIMITED SCHEME - CORPORATE-CG - 16.602 as on 22-06-2018 || LIC PENSION FUND SCHEME E - TIER I - 18.2091 as on 22-06-2018 || LIC PENSION FUND SCHEME C - TIER I - 15.8149 as on 22-06-2018 || LIC PENSION FUND SCHEME G - TIER I - 16.286 as on 22-06-2018 || LIC PENSION FUND SCHEME E - TIER II - 15.1242 as on 22-06-2018 || LIC PENSION FUND SCHEME C - TIER II - 14.8195 as on 22-06-2018 || LIC PENSION FUND SCHEME G - TIER II - 16.3398 as on 22-06-2018 || NPS TRUST - A/C LIC PENSION FUND SCHEME - ATAL PENSION YOJANA (APY) - 12.7981 as on 22-06-2018 || LIC PENSION FUND SCHEME A - TIER I - 11.114 as on 22-06-2018 || LIC PENSION FUND SCHEME A - TIER II - 10 as on 22-06-2018 || KOTAK PENSION FUND SCHEME E - TIER I - 25.619 as on 22-06-2018 || KOTAK PENSION FUND SCHEME C - TIER I - 24.3936 as on 22-06-2018 || KOTAK PENSION FUND SCHEME G - TIER I - 20.5802 as on 22-06-2018 || KOTAK PENSION FUND SCHEME E - TIER II - 22.648 as on 22-06-2018 || KOTAK PENSION FUND SCHEME C - TIER II - 20.9323 as on 22-06-2018 || KOTAK PENSION FUND SCHEME G - TIER II - 19.3471 as on 22-06-2018 || NPS TRUST A/C-KOTAK MAHINDRA PENSION FUND LIMITED- NPS LITE SCHEME - GOVT. PATTERN - 18.4049 as on 22-06-2018 || KOTAK PENSION FUND SCHEME A - TIER I - 10.7793 as on 22-06-2018 || KOTAK PENSION FUND SCHEME A - TIER II - 10 as on 22-06-2018 || RELIANCE PENSION FUND SCHEME E - TIER I - 25.6352 as on 22-06-2018 || RELIANCE PENSION FUND SCHEME C - TIER I - 22.0396 as on 22-06-2018 || RELIANCE PENSION FUND SCHEME G - TIER I - 20.1847 as on 22-06-2018 || RELIANCE PENSION FUND SCHEME E - TIER II - 21.9831 as on 22-06-2018 || RELIANCE PENSION FUND SCHEME C - TIER II - 20.524 as on 22-06-2018 || RELIANCE PENSION FUND SCHEME G - TIER II - 19.6077 as on 22-06-2018 || NPS TRUST A/C-RELIANCE CAPITAL PENSION FUND LIMITED- NPS LITE SCHEME - GOVT. PATTERN - 10 as on 22-06-2018 || RELIANCE PENSION FUND SCHEME A - TIER I - 11.0697 as on 22-06-2018 || RELIANCE PENSION FUND SCHEME A - TIER II - 10 as on 22-06-2018 || ICICI PRUDENTIAL PENSION FUND SCHEME E - TIER I - 28.1487 as on 22-06-2018 || ICICI PRUDENTIAL PENSION FUND SCHEME C - TIER I - 24.4868 as on 22-06-2018 || ICICI PRUDENTIAL PENSION FUND SCHEME G - TIER I - 20.7972 as on 22-06-2018 || ICICI PRUDENTIAL PENSION FUND SCHEME E - TIER II - 22.199 as on 22-06-2018 || ICICI PRUDENTIAL PENSION FUND SCHEME C - TIER II - 22.7954 as on 22-06-2018 || ICICI PRUDENTIAL PENSION FUND SCHEME G - TIER II - 19.9424 as on 22-06-2018 || NPS TRUST A/C-ICICI PRUDENTIAL PENSION FUNDS MANAGEMENT COMPANY LIMITED- NPS LITE SCHEME - GOVT. PATTERN - 10 as on 22-06-2018 || ICICI PRUDENTIAL PENSION FUND SCHEME A - TIER I - 10.9356 as on 22-06-2018 || ICICI PRUDENTIAL PENSION FUND SCHEME A - TIER II - 10 as on 22-06-2018 || HDFC PENSION MANAGEMENT COMPANY LIMITED SCHEME E - TIER I - 20.9395 as on 22-06-2018 || HDFC PENSION MANAGEMENT COMPANY LIMITED SCHEME C - TIER I - 15.8939 as on 22-06-2018 || HDFC PENSION MANAGEMENT COMPANY LIMITED SCHEME G - TIER I - 15.3631 as on 22-06-2018 || HDFC PENSION MANAGEMENT COMPANY LIMITED SCHEME E - TIER II - 18.1241 as on 22-06-2018 || HDFC PENSION MANAGEMENT COMPANY LIMITED SCHEME C - TIER II - 15.0057 as on 22-06-2018 || HDFC PENSION MANAGEMENT COMPANY LIMITED SCHEME G - TIER II - 15.6919 as on 22-06-2018 || NPS TRUST A/C-HDFC PENSION MANAGEMENT COMPANY LIMITED SCHEME - NPS LITE SCHEME - GOVT. PATTERN - 10 as on 22-06-2018 || HDFC PENSION MANAGEMENT COMPANY LIMITED SCHEME A - TIER I - 11.1392 as on 22-06-2018 || HDFC PENSION MANAGEMENT COMPANY LIMITED SCHEME A - TIER II - 10 as on 22-06-2018 || BIRLA SUN LIFE PENSION SCHEME E - TIER I - 11.6598 as on 22-06-2018 || BIRLA SUN LIFE PENSION SCHEME C - TIER I - 10.8147 as on 22-06-2018 || BIRLA SUN LIFE PENSION SCHEME G - TIER I - 10.3237 as on 22-06-2018 || BIRLA SUN LIFE PENSION SCHEME A - TIER I - 10.7566 as on 22-06-2018 || BIRLA SUN LIFE PENSION SCHEME E - TIER II - 11.6264 as on 22-06-2018 || BIRLA SUN LIFE PENSION SCHEME C - TIER II - 10.5241 as on 22-06-2018 || BIRLA SUN LIFE PENSION SCHEME G - TIER II - 9.9623 as on 22-06-2018 || BIRLA SUN LIFE PENSION SCHEME A - TIER II - 10 as on 22-06-2018 ||

Toll Free Number -1800-110-069 of Atal Pension Yojana                  Submission of FATCA Self Declaration                 Go Paperless Opt for an Email Annual Transaction Statement                 Join Atal Pension Yojana Online with Aadhaar


Steps for upload of Subscriber contribution files:

  • Consolidation of DDO wise Subscriber contribution records.
  • Digitization of records through FPU or own back office.
  • Validation of the contribution file using File Validation Utility (FVU)
  • Upload of contribution file in the NPSCAN by PAO.
  • Transfer of funds to the Trustee Bank along with Contribution Submission form (CSF).

At the end of every month, the DDO shall forward the contribution details of the Subscribers to the PAO. The PAO shall consolidate the data and prepare a Subscriber contribution file using File Preparation Utility (FPU) provided by CRA. PAO may also use any equivalent software for preparation of SCF. However, the file so prepared should be as per file formats of CRA.

Alternatively, the respective DDO can create the SCF using the FPU. PAO can consolidate the DDO wise files using a File Merger Utility (FMU). After consolidating the files through FMU, PAO shall open the file in FPU for creation of final SCF to be run through FVU.

SCF is the file containing the details of the contributions of Subscriber (Own and Government contribution) towards the pension fund. PAO shall prepare the Subscribers contribution file to be uploaded to the NPSCAN.

The timelines are specified in OM No 1 (7) 2003 / TA / Partfile/ 279 Dt 2/9/2008 issued by Department of Expenditure, Office of CGA, Ministry of Finance; applicable to Civil Ministries only.

PAO shall login to NPSCAN and upload the SCF, which is successfully validated by FVU. On acceptance of the file, a transaction ID will be generated along with a Contribution Submission Form, which will contain the details of the SCF. PAO will then transfer the funds to the Trustee Bank.

File Preparation Utility (FPU) is a stand-alone utility provided by CRA to enable PAO to prepare the monthly Subscribers' contribution file as per the file formats of CRA. It will contain details such as PAO Registration number, DDO Registration number, Subscriber PRAN, amount of Government contribution is equal to Subscriber contribution, Pay month etc. In case of any incorrect data format inserted, FPU provides error prompt to enable the PAO to rectify the same. FPU has excel type features such as copy, paste, insert/delete rows etc.

If DDO prepares the SCF then File Merger Utility (FMU) will provide PAO with the option of merging all the .fpu files prepared by individual DDOs. FMU will generate a single consolidated file in the fpu format. This merged file has to be opened by PAO using File Preparation Utility (FPU) for preparing a final text file.

File validation utility (FVU) is a stand-alone utility provided by CRA to validate the contribution file prepared using FPU or the uploading Nodal Office's own software, against a set of validation rules. On successful validation, an output file with extension .fvu along with a control total html file will be generated, which can be uploaded in the NPSCAN/CRA system. If any of the validations fail, then the file will be rejected and an error file will be generated.

PAO can download the FPU, FMU, FVU and the file formats from www.npscra.nsdl.co.in

If the format level validation is successful at FVU, then an output file with extension .fvu along with a control total html file will be generated in the specified path. The .fvu file will contain the contribution details, FVU version and FVU generated hash value (digital lock to prevent the file being tampered) which has to be uploaded to NPSCAN. This control total file in html form would be for record purpose of the PAO.

If the SCF validation is not successful, FVU will generate a error report containing details of the errors. The PAO shall rectify the errors in the original file and again pass it through the FVU until all records are rectified and SCF is successfully validated through FVU.

If any of the validations fail in FVU, FVU will generate an error file in the specified folder indicating the details of the errors such as contribution month is a future month etc.

FVU will validate whether the file is as per the format specified by CRA. Some of the errors which FVU may show are - Sum total of Subscriber contribution and Government contribution are not matching, contribution year is a future year etc.

PAO can use its own software for preparation of the file. However, the file should confirm to the file formats of CRA. The output file should be in ASCII Format with ".txt" as filename extension. However, it is mandatory for the PAO to validate the output file through FVU, irrespective of whether it has been created through FPU or own back office. Unless the file is successfully validated by FVU, it cannot be uploaded to the NPSCAN system. Therefore, in nutshell, the usage of FVU is mandatory, but usage of FPU is optional.

PAO can reuse the contribution file prepared initially through the FPU by modifying the required details such as month of contribution etc.. When creating the final SCF file, FPU will create two files - a .fpu file for future use and a .txt file for upload to NPSCAN. For next month SCF, PAO can open the .fpu file of the previous month using the FPU and make the necessary modifications. For the record of PAO, the final file may be saved with the name of the month and year.

Error files will be generated at two levels:

  • FVU
  • NPSCAN

If any of the validations fail in FVU, FVU will generate an error file in the specified folder indicating the details of the errors such as contribution month is a future month etc.

In case of validation failure in NPSCAN, an error file will be generated indicating the details of the error such as Duplicate files having same batch id, invalid PAO-DDO mapping, invalid PAO id, invalid PRAN. In case of rejection by NPSCAN, the error file will be available for download through the Contribution File Status View. On the basis of the File Reference Number generated at the time of uploading the contribution file, the PAO can check the status of the file.

FVU is a standalone utility and checks only the format level validations. However, database level validations such as whether PAO, DDO registration number and PRAN is valid etc. will be carried out at CRA system. Hence, in such cases file which is successfully validated by FVU can be rejected at NPSCAN.

The utilities can be executed on any of the following windows platform: Win 95/Win 98/Win 2K Professional/Win 2K Server/Win NT 4.0 Server/Win XP Professional. Further, Java (JRE 1.5 or any higher version) has to be installed to run FPU, FVU and FMU. The above said software can be freely downloaded from http://java.com.

Online FPU is a functionality provided by CRA to the uploading offices to facilitate preparation of contribution files online. However, this facility can be availed by uploading offices for preparing files of 50 or lesser number of subscribers only.

There is a facility provided to the Nodal Offices to check the status of the contribution file. User can enquire about the status of a particular file by entering the upload period (from and to date) or batch ID /file reference number or Transaction ID.

PAO can upload multiple contributions for the same PRAN in one SCF provided any one of the below mentioned fields are different for both the instances:

  1. DDO Registration Number
  2. Month of Contribution
  3. Year of Contribution
  4. Type of Contribution

PAO can upload contribution for a Subscriber who has been tranferred to a different sector and the shifting request of the Subscriber has been executed in the CRA System. e.g If a Subscriber previously mapped to a Central Government (CG) employee has shifted to State Government (SG) and the CG office wishes to upload the pending contribution of the Subscriber, the PAO can do so even though the subscriber is currently mapped to the SG office. In this situation the PAO can use the functionality of Contribution Upload for Shifted Subscriber available under the PAO login in the CRA system. Once the request has been successfully authorised by the PrAO, the PAO can upload the contribution within seven calender days after authorisation of the request by PrAO.

It is not mandatory for a PAO to upload a consolidated SCF. PAO can carry out multiple uploads of SCF as and when the data is consolidated or as and when it is received from the respective DDOs.

PAO can correct the details of the file already uploaded in the NPSCAN/CRA system by preparing and uploading a correction file along with the transaction id of the original file. The PAO will have to upload the entire file with the corrected records. PAO can upload the correction file only if the status of original file is not 'Matched and Booked" at CRA system. The file will go into "Matched & Booked" status once the information of receipt of payment is uploaded by Trustee bank & the records provided their in match with the records provided by PAO. If the original file is already matched and booked in CRA, PAO cannot upload a correction file. PAO can adjust the short/excess payment in the next months contribution record to be uploaded to CRA.

The contribution arising out of arrears can be uploaded to CRA along with the regular contribution. At the time of preparing the SCF, PAO shall enter the contribution type as Arrears and mention the period of arrears in the Remarks column.

PAO shall transfer the funds to the Trustee Bank through electronic transfer such as RTGS or NEFT (Type R-41) (For detailed instructions regarding fund transfer viz. account number and PAO string please refer footnote on the CSF generated for the transaction). The Trustee Bank shall confirm to CRA the funds transferred by the respective PAO against the respective transaction ID.

The below mentioned instructions should be followed while transferring funds:

  • Remittances (RTGS/ NEFT) should be done by R-41 RTGS format only.
  • 26 digit PAOFIN no. should be written in “Sender to Receiver Information” ( Field 7495 only)
  • Amount transferred to the Trustee Bank should match amount of SCF uploaded.
  • The above details are critical since unless the above data reaches the Trustee Bank along with the funds, it will not be in a position to identify the PAO and the SCF for which funds are received for transmitting the fund confirmation receipt to CRA.

PAO can check the status of the file in NPSCAN. In case the funds have not been identified by the Trustee Bank in the CRA system, the funds are remitted back to the originating account on T+1 day. The PAO may check status of refund with their accredited bank in case the file is not matched and booked after T+2 days in the CRA system. In case the funds are identified correctly by the Trustee Bank the Subscriber Contribution File is matched and booked in the CRA system.

Funds not identified by Trustee Bank shall be returned by the Trustee Bank to the source Bank account by T + 1 day.

No. PAO cannot make a consolidated payment for multiple contribution files. Since each contribution file has a separate transaction ID, the amount transferred should match the amount uploaded in each transaction ID individually.

Since, a Susbscriber Contribution File (SCF) is valid for a period of 15 working days from the date of upload, fund should be transferred to the Trustee Bank within the same period (i.e. 15 days). SCF pending for Matching and Booking for more than 15 working days are automatically cancelled/deleted from the CRA System and the respective uploading office shall have to upload a new SCF in this scenario.

Various reports which are available to the PrAOs are:

  • Contribution file status
  • Verification Pending Request
  • Pending Contribution files
  • PAO Performance for Contribution Upload
  • Exception report for PAO Performance for Subscriber Registration
  • Subscriber Registration Report
  • Status of SCF (Subscriber contribution file) upload
  • Comparison of the monthly contribution upload
  • Credit Analysis
  • Performance Tracker
  • Subscriber Recruitment Monitoring
  • Subscriber PAO List
  • Registered Subscriber List
  • Transaction Statement
  • Rejection Memo
  • Statement of Contribution
  • S1 Form View

Various reports which are available to the PAOs are:

  • Pending Contribution files
  • Statement of Holding of Subscriber.
  • Transaction Statement of Subscriber.
  • Subscriber Retirement Details
  • Subscriber Registration
  • Status of SCF (Subscriber contribution file) upload
  • Comparison of the monthly contribution upload
  • Credit Analysis
  • Performance Tracker
  • Subscriber DDO List
  • List Registered Subscribers
  • Transaction Statement
  • Statement of Contribution
  • Rejection Memo
  • S1 Form View

Various information / alerts, which are sent by CRA to PAO:

  • on successful registration of PAO in CRA system
  • on successful registration of DDO in CRA system
  • on successful registration of Subscriber in CRA system
  • on rejection of Subscriber application for registration
  • Contribution file which has been uploaded by PAO and the corresponding Fund Receipt Confirmation is not uploaded by Trustee Bank to CRA within 3 business days
  • When the status of contribution file is 'Match Failed'.
  • When the PAO contribution file is rejected by the NPSCAN
  • Subscriber request for modification is rejected by CRA
  • Subscriber request for modification is accepted by CRA
  • In case a grievance is raised against a PAO
  • In case a PAO raises a grievance for a Subscriber/himself
  • In case a Subscriber is shifted