|2||Failure Transactions handling for the month of March 2018||The central team of CFMS sends the payment file to RBI for payment to payees’ accounts. The RBI shall communicate the unsuccessful payments list from time to time in the form of Return Notifications. The central team has to re-initiate payment after the DDO furnishes correct the bank account details of payees. Since it is difficult to reach out the DDOs, This office is communicating the RNs to respective DTOs and requesting them to furnish consolidated list of corrected bank details. Upon receipt of such details, the central team of CFMS shall re-initiate the payment to respective payees.|
|3||Failure Transactions handling in CFMS going forward||
When a payment is processed in CFMS, it will be submitted to eKuber @ RBI to process the same and remit the payment to the beneficiary account. In this process, sometimes there could be failures due to many reasons like incorrect bank account details, inoperative accounts etc. Such transactions need to be reviewed for re-processing and the following diagram illustrates the same.
|@ DDO Level:-
HOO shall configure the workflow to authorise one person for failed payment request access in OTHERS tab under BLM Submitter Workflow. This configuration is pre-requisite to get the display of failure transactions.
In case of regular vendors i.e. employees / DDO vendors / some third party vendors who were registered, the corrections to the Bank Account number and IFSC code are to be carried out first in Beneficiary Master through Beneficiary creation request and Master Records have to be updated first. In case of Other one time vendors who were not registered, e.g. Scholarship Beneficiaries, corrections can be made in the screen available to
|authorised person who has access to failed payment request function.
Once Bank account number and IFSC code details are updated, authorised person will submit these details to the treasury.
@ Treasury Level:-
HOO of the treasury will configure workflow for Failed Payment Bill creation and submission by assigning Maker – Checker (Optional) – Submitter to his/her own treasury DDO code and 8658 HOA and He/ She also configure the workflow for Bill Approval by assigning Auditor – Verifier (Optional) – Approver. These steps are pre-requisites to start failure transactions paymentprocess.
Once workflow is configured, Maker will have access to the creation of Failed Payment Bill under Non HR Bill category.
Maker will create a bill for all the available line items related to failure transactions submitted by DDOs in the jurisdiction of that treasury on that day and the bill will go through the process of Bill submission and Bill approval as usual.
|4||Corporations - DDO||In reference to the U.O. Note No. 43027/199/2017, Fin Dept. Dt.15.09.2017, No DDO Code shall be assigned to the Corporations as these corporations are not supposed to draw the funds directly from Consolidated fund.
In the past, there has been a practice that HoDs distribute the budget to the corporations and these organisations preferred the bills and directly tapped the consolidated fund which is irregular and on no. of occasions, AG has raised objections to that effect. Consequent to this and in compliance with the orders issued by Finance department, DDO codes assigned to theCorporations are hereby withdrawn.
However various corporations are rendering service to the government departments, for this the government departments either been providing funds as Grant in Aid or entering into 3rdparty agreement to deliver the services .Since the practice of assigning DDO codes is withdrawn and to facilitate the departments to continue
to engage corporations, the following process is proposed in CFMS.
Grant in Aid: The Government departments who are the budget owners have to draw the funds on their DDO code as per the needs of the work / activities and adjust to PD Account of respective offices, such funds will be maintained in deposit works.
Funds related to expenditure other than works will be adjusted to existing PD account of the Corporations.
Funds related to works are adjusted to 8443 – Deposit Works and the government has granted permission to treat deposit work accounts as PD Accounts in Memo No. 21025/2/E-File/CM/2018 of Fin. Dept Dt.29.03.2018.
In case of 3rd party agreement with the institutions – shall be treated as any other third party vendors.
|5||Beneficiary Creation||Employees and Pensioners bank details obtained from the Legacy system and registered as beneficiaries in CFMS system.
To register third party / Non-employee beneficiaries provision has been made in CFMS.
HOO shall configure the workflow for Beneficiary creation by clicking on Authorised Beneficiary create request access which can be found in OTHERS tab under Workflow configurator Bill Submit.
The authorized person will get access to the Beneficiary Create Request tile, through which HOO can make request for 3rd party / Non – employee beneficiaries’ registration by providing beneficiary basic details and bank details and beneficiary create request number shall be generated and later beneficiary vendor code is created in CFMS.