PUBLIC FINANCIAL MANAGEMENT SYSTEM...

IAAA FUNCTIONALITY ON PFMS

1

PUBLIC FINANCIAL MANAGEMENT SYSTEM (PFMS)

USER MANUAL ON

INTER ACCOUNTAL ADJUSTMENT ADVICE (IAAA) FUNCTIONALITY ON

PFMS

CONTROLLER GENERAL OF ACCOUNTS

DEPARTMENT OF EXPENDITURE

MINISTRY OF FINANCE

NEW DELHI

Website: www.pfms.nic.in

May, 2017


2

INTER ACCOUNTAL ADJUSTMENT ADVICE

(IAAA) FUNCTIONALITY ON PFMS

➢ The functionality for transfer of High Value funds form Ministries / Departments to PSUs / Organizations through Inter Accountal Adjustment Advice (IAAA) to CAS, RBI, Nagpur has been developed on PFMS. ➢ All net transactions exceeding Rupees 100 crore will be treated as IAAA (Inter Accountal Adjustment Advice and will be routed through RBI.

➢ Payments under IAAA exceeding Rupees. 100 crore can be made to any party including Non-PSUs.

➢ A single transaction exceeding Rupees 100 crore to a beneficiary/vendor will be treated as IAAA.

➢ IAAA will be treated as e-payment and not an Inter-Government Adjustment Advice (IGAA) and RBI would send the scrolls to the PAO for the payments made through IAAA.

➢ There will not be any substantive change in the process to be followed in PFMS for this purpose. The sanction will be created in same manner as for the payments below Rupees 100 crore. System will display a message “This sanction will be considered as IAAA sanction. Do you want to create the sanction?”

➢ On PFMS, IAAA sanction will be shown with blue coloured background. ➢ If DDO makes some deductions in IAAA sanction due to which the net amount becomes less than Rupees 100 crore, the same will be treated as normal transaction and will be routed through the accredited bank instead of RBI.


3

Contents

1. OPENING OF IAAA ACCOUNT IN RBI ................................................................................... 4

2. CONFIGURATION OF e-FPB ACCOUNT WITH RBI ON PFMS ....................................... 5

3. FUNCTIONS AT PD LEVEL ....................................................................................................... 8

4. FUNCTIONS AT DDO LEVEL ................................................................................................. 18

5. FUNCTIONS AT DH LEVEL .................................................................................................... 27

6. FUNCTIONS AT AAO LEVEL .................................................................................................. 32

7. FUNCTIONS AT PAO LEVEL .................................................................................................. 35

8. DIGITALLY SIGNING E-PAYMENT FILE BY SIGNATORY 1 .......................................... 38

9. DIGITALLY SIGNING E-PAYMENT FILE BY SIGNATORY 2 .......................................... 47

10. ACCOUNTING IN RESPECT OF IAAA .................................................................................. 52


4

1. OPENING OF IAAA ACCOUNT IN RBI

To use the facility of IAAA on PFMS, PAOs have to open an e-FPB account with Reserve

Bank of India for arranging e-payments exceeding Rs. 100 crore under Inter Accountal

Adjustment Advice (IAAA) (in terms of RBD, O/o CGA letter No. S-

11012/1(12)/HLM/2012/RBD/1358-1410 dated 17th August, 2016.)

As per advice received from Reserve Bank of India vide their letter no. DGBAm GAD. No.

386/31 28.001/2016.17 dated August 16, 2016, all PAO’s of Civil Ministries/Departments are requested to address the Account Opening request to “The

Regional Director, Reserve Bank of India, Banking Department, Mumbai Office, Main

Building, Shaheed Bhagat Singh Road, Fort, Mumbai-400001”

SAMPLE REQUEST LETTER FOR OPENING OF AN e-FPB ACCOUNT IN RBI


5

2. CONFIGURATION OF e-FPB ACCOUNT WITH RBI ON PFMS

After PAO has opened an e-FPB account with Reserve Bank of India for arranging e-payments exceeding Rs. 100 crore under Inter Accountal Adjustment Advice (IAAA), this bank account needs to be entered by respective PAO on PFMS. For this, PAO will log in PFMS though his user id and go to: “MASTERS” > “ADD PAO/CDDO BANK ACCOUNT”

“Controller Name” and “PAO Description” will be displayed automatically. User will press the button “ADD NEW”.

After selecting “IAAA” as “Account Type”, user will fill in the relevant information in the given fields.


6

Note: IFSC CODE OF RBI FOR IAAA: RBIS0MBPA04

For identifying the Account Number allotted to them, PAO may kindly refer

to CGA’s O.M. No. C-13015(380)/MFCGA/PFMS-PMIG/2016-17/1320-

1327 dated 26th March, 2017 available on CGA’s website.

Once PAO user clicks the option “ADD ACCOUNT DETAILS”, system will display a message “Record Saved Successfully”. At this stage, the data is stored in the system and will not be available for editing at PAO level. After the account number has been entered by PAO user on PFMS, this needs to be intimated along with relevant details viz. Controller code, PAO Code, Account number etc. to IT Division of CGA office over email to [email protected] for validation of account number configured on PFMS.

mailto:[email protected]


7

Editing in Bank Account details, if any, will be carried out by PFMS HQ only on written request from PAO to Sr.AO (ITD-SPC), IT Division, O/o CGA, Shivaji Stadium Annexe, New Delhi-110001. User can view the details of bank account entered by him using “Search” button.

Once the bank account details are approved by PFMS, “Bank Status” will be shown as “Approved”.


8

3. FUNCTIONS AT PD LEVEL

I.CREATION OF SANCTION

There will not be any substantive change in the process to be followed in PFMS for this purpose. The sanction will be created in same manner as for the payments below Rs. 100 crore. Program Division user will log into PFMS with his user id and password and go to:

“SANCTIONS” > “CREATE SANCTION”

A screen for “CREATE SANCTION” will appear. This screen will be used

by PD user for creating a new Sanction. He will fill in the relevant information in the

following fields: 1. Controller Name is displayed for the respective PD.

2. IFD/HOD File Number: The Integrated Finance Division number will be filled in by

the PD user manually. 3. IFD/HOD File Date: This field has to be filled in by user manually.

4. Sanction Number: This field has to be filled in manually by the user.

5. Sanction Date: - The date of Sanction should be within the financial year.

6. Scheme: The drop down menu will display only those Schemes that have been

mapped to PD User. 7. PAO: The drop down menu will display the PAO to which the PD User has been

mapped. The user will select the PAO for which the Sanction is being created.


9

8. DDO: The drop down menu will display the DDO to which the User has been

mapped. The user will select the DDO for which the Sanction is being created. 9. Sanction Type: PD has to select the appropriate type of sanction out of the

following types of Sanctions available for selection:

a. Transfer

b. Expenditure

c. Intra Governmental Authorization

10. Amount: Fill in the amount (Gross Amount in Actuals) for which the Sanction is

being generated. Amount in words will be displayed automatically by the system. 11. Upload Scanned Sanction: Only PDF Files with size not more than 4 MB are

allowed to be uploaded on PFMS. This field has been provided for uploading the scanned

copy of Sanction which has been created manually. However, uploading of scanned copy

of sanction is not mandatory for ‘Expenditure’ and ‘Inter Governmental Authorization.’

12. Account Head Details: After all the above fields under “SANCTION HEADER”

have been filled in, the user will proceed for filling in the relevant data in “ACCOUNT HEAD

DETAILS” in the following fields by making selection from the drop down menu:

1) Grant


10

2) Functional Head 3) Object Head 4) Category (NOTE: In case the desired heads of accounts do not appear, the PD user may contact

his PAO to map the relevant head of accounts and enter the budget in same (in case

of budgetary heads).

After selecting the relevant accounting details, PD user will enter the amount and press the button “ADD ACCOUNTS HEADS”. A record showing the selecting account head

details and amount will appear in a grid below. In case of wrong record, same can be removed by using “X”.

13. Now PD user will proceed for “Vendor Details” and key in the data in the following

fields:-

1) Vendor Type: User has to select Type of Vendor out of the eight types available

for selection in drop down menu. 2) Vendor: Select the name of the vendor from the drop down menu. On selection

of vendor’s name, unique code will be displayed automatically.


11

3) Amount: Fill in the amount as shown in Sanction. After filling in the relevant

vendor information, PD user will press “ADD” button. A record showing selected vendor’s

details will appear in a grid below. If required, multiple vendors can be added one by one.

In case of wrong record, same can be deleted by selecting it and pressing the button “REMOVE”.

After all the relevant information have been filled in all the fields, PD user will press the button “CREATE SANCTION”.

A sanction exceeding Rupees One hundred Crores will be considered as IAAA, and

system will display a message: “This sanction will be considered as IAAA sanction. Do you want to create the

sanction?”

User will press “OK” button.


12

System will display the following message: Sanction has been saved successfully...!!! Do you want to proceed with payee details? Yes No Press “Yes” button.


13

On pressing “YES”, system will display the “Payee Details”. Here, the system will also display the “Available Budget”. While creating a sanction, PD user must ensure the availability of budget. In case vendor has provided more than one Bank Account Number, user can select the desired one from the list in drop down menu. “Instrument Type”, whether “RTGS” (for e-payment) or “CHEQUE” is also displayed here.

After verifying the payee details, user will press “Next” button.

System will display the e-Payment Details of vendor. If the IFSC code is not automatically shown, it means bank account is not validated. If payment process is urgent, user can key in the correct IFSC code. User has to give some meaningful remarks for kind of payment in the field “PAYEE REMARKS”. User will press “CONFIRM” button. System will display a message for successful submission of sanction. “Payee Details have been submitted successfully”.


14

Note: In above screen, it may be noted in case of IAAA sanction, “Reserve Bank of India” will appear in the column of “Accredited Bank”.

II.EDITING THROUGH MANAGE SANCTION (IF REQUIRED) In case some editing is required in this newly created sanction, same can be carried out using the option “SANCTIONS” > “MANAGE SANCTIONS”. The desired sanction will become available for editing. User will press the button “EDIT SANCTION”. User will carry out the required modifications and press the button “SAVE SANCTION”. Thereafter, user will confirm the payee details.

III.APPROVAL OF SANCTION After the sanction has been created, PD user will proceed to approve the same. For approval of already created sanction, user will click the option “SANCTIONS” > “APPROVE”.


15

A screen for “SEARCH SANCTIONS” will appear.

A list of already created sanctions (but pending for approval) will appear for selection. To

locate a desired sanction, user will key in the desired sanction number or use any other search criteria and press “SEARCH” button. All IAAA sanctions will be displayed with

blue coloured background for easy identification. User will select the sanction by

clicking over the hyperlink of “Sanction Number”.

The sanction details will be displayed on the screen.

Here, user will find following options for selection:

1. Edit Sanction 2. Payee Details 3. Approve/Reject


16

4. Cancel Sanction 5. Print Sanction Order 6. Back 1. EDIT SANCTION: At the time of approval of sanction, in case the PD user wants to modify the details of Sanction, he will click the ”Edit Sanction” button; system will make the sanction available for editing. PD user can make the desired modifications in sanction and again save it by Clicking “Save Sanction” button. 2. PAYEE DETAILS: This field is used to see and confirm the details of Payee viz. Sanction details, accounting details and the details of payee’s bank account, before the user proceeds for confirmation of Sanction. PD user can see the details and confirm the sanction for approval. On confirmation, system will display the message “Payee details have been submitted successfully...!!! 3. APPROVE/REJECT: User after confirming the Payee details, can either “APPROVE” or “REJECT” the sanction (as the case may be). User has to enter remark for action. 4. CANCEL SANCTION: This field is used to cancel an already created sanction. User will click this button, give the remark and press “OK” button to cancel the sanction. (Note: Cancelled sanction also requires approval for cancellation). 5. PRINT SANCTION ORDER: This option is used for taking print out of approved sanction order. 6. BACK: This button will redirect the user to previous page.

After the user has confirmed the payee details, he will click the button “Approve/Reject”,

and give a remark for approval of sanction, which is a mandatory field. After writing the remark, user will press “APPROVE” button.


17

On pressing “APPROVE” button, following screen will appear showing the message

“Sanction approved successfully”. At this stage, budget will be updated accordingly.


18

Now after the sanction has been approved by the PD user, it will be electronically

transmitted and will be available at DDO level user for generation of bill.

IV.ACTION ON SANCTION RETURNED BY DDO/PAO

Once a sanction has been approved by PD user, it will no more be available with him for

carrying out further modifications or cancellation. Though the same sanction will be available under “Manage Sanction” option, but only for viewing. In case approved

sanction needs to be edited/cancelled, DDO will return the sanction to PD and same will

be available at PD level for further action i.e. editing/cancellation under the option: “SANCTIONS” > “MANAGE SANCTION”.

4. FUNCTIONS AT DDO LEVEL

I. SANCTION RECEIVE The sanction as “Approved” by all PD users will appear at DDO under the option: “SANCTION” > “RECEIVE”.


19

To generate bill, DDO has to first receive the sanction. The sanctions can be received in bulk or one by one.

The DDO user can put in information in search field(s) and trace a particular sanction against which bill is to be generated. Before receiving a sanction, its details can be viewed and checked by clicking the hyperlink of sanction number indicated in blue colour in the grid. The sanction submitted by PD user will be shown as ‘approved’ in sanction status field. To view payee details click “Payee Details” button. Select the desired sanction and press the button “‘Receive Sanction” to receive it or “Return Sanction to PD” in case it is to be returned to PD.

The user can also receive a sanction directly. Tick the box given against Sanction No. and

press “Receive Sanction” button below. The sanctions can also be received in bulk. To

receive sanctions in bulk tick box “All” or select multiple sanctions and then press the

button “Receive Sanction” button at the bottom. Click “Return sanction to PD” button, if

sanction is to be returned. The sanctions received by DDO will be available for generation

of bills.


20

Before receiving a sanction, user can view the details of sanction by clicking its hyperlink.


21

II. GENERATE BILLS:

The received sanction will appear for bill generation at DDO user level under the option “SANCTION” > “GENERATE BILLS”.

The sanction received by DDO will be shown as ‘DDO received’ in sanction status field. The DDO can put information in search field and find out desired sanction received by him


22

and against which bill is to be generated. There are two different ways for generating bills. One is for bill without any deduction and another is for bill with deduction(s).

Generation of Bill without Deduction

For bills to be generated without deduction click on check box given against desired sanction and then click on “GENERATE BILLS”. System will display a message to confirm

whether the bill has to be generated without deductions? User will press the button “OK”.

A message “bill(s) has been generated successfully” will appear in above grid. A bill

number will be allotted by system itself in arithmetic series.


23

Print out of generated bill can be taken by user.


24

(a) Generation of Bill with Deduction

For bills to be generated with deduction click on sanction number to open the sanction and then on “GENERATE BILL” number to add deduction(s). Field for adding deduction will

appear. Select favouring of vendor given at left side. Some of the standard deduction

codes have been provided in drop down list. User may choose from them; other details

viz. grant number, function head, object head and category will automatically appear in the

respective box. Enter the amount to be deducted from the bill in amount column and click ‘ADD DEDUCTION’. The details of deduction added will appear in grid below with a

message ‘DEDUCTION ADDED SUCCESSFULLY’. Similar steps may be repeated for

more deductions. The net effect of deductions will be shown below the grid. In case of any error in deductions, tick the box and press “REMOVE” button. The added deduction will

be removed. If there is more than one payee in sanction id generated by PD, the DDO

can add deduction for each payee. In such case select favouring one by one and add

deduction as explained above.

In case the desired deduction type is not available in list of standard deduction codes, DDO has to select ‘other’ from standard code list and then provide grant number, function


25

head, object head, category and amount in the respective columns and follow the steps

explained above in order to add deduction.

After adding all the deductions, click on “GENERATE BILLS” button given at bottom. The

bill will be generated with bill number and a message “bill(s) has been generated

successfully” will appear in above grid. A bill number will be allotted by system itself in

arithmetic series.

User can print the bill from the link ‘to print click here’. The generated bill will appear at

DH level in Pay & Accounts Office with status ‘generated bill’.

(In case, the deductions have been added but the bill is to be prepared without deduction, user can press “CANCEL” button to remove all deductions and press the button

“Generate Bill Number” to generate it without deductions.)

The generated bill will appear at DH level in Pay & Accounts Office with status ‘generated

bill’.

NOTE: - In case a sanction with amount exceeding One Hundred Crores has been created as IAAA sanction at PD level, but DDO makes some deduction(s) in it due to which net amount becomes less than or equal to Rs. 100 crore, then it won’t be treated as IAAA sanction. The same will be treated as normal transaction and will be routed through the accredited bank instead of RBI. For example in following case, a sanction with amount exceeding Rupees One Hundred

Crores was treated as IAAA sanction at the time of creation. The system displayed a

message that this sanction will be considered as IAAA sanction.


26

➢ However, at the time of bill generation DDO added some deduction(s) due to which net amount of sanction became less than or equal to Rupees One Hundred Crores. In such case, before generation of bill, system will display a message that this sanction will not be considered as IAAA sanction. ➢ All net transactions less than or equal to Rs. 100 crores will not be treated as IAAA and thus will be routed through Accredited Bank instead of RBI.


27

5. FUNCTIONS AT DH LEVEL

The bill generated by DDO will appear at DH level in Pay & Accounts Office. The status of bill will be shown as “generated”. DH user will log into PFMS portal with his/her user id and password. To receive a sanction from DDO, DH user will click the option “SANCTION” > “RECEIVE”


28

A screen, showing a list of all the sanctions available for receiving at DH level, will appear. DH has the option to select one, multiple or all sanctions in one go. All IAAA sanctions will be displayed with blue coloured background for easy identification. DH user can open the sanction by clicking the box in front of Sanction Number and view its details. In case the desired sanction is not visible in this list, DH can make use of “Search” options to trace it. By clicking “Vendor Details”, DH can view the details of vendor. DH will click the box given against the desired sanction number and receive it by clicking the button “RECEIVE SANCTION”.

The following screen will appear showing the system generated Token Number and displaying the message: “Bill has been received and token number ___generated”.


29

Now DH user will go to “SANCTIONS” > “PASS BILL”

A screen, showing a list of all the sanctions which have been received by DH user and are available for “Pass/Return” (as the case may be) will appear. If the desired sanction is available in the list, DH user can directly open it by clicking on hyperlink of sanction number. Otherwise, DH user can trace the same by using search options.


30

The desired sanction with the status “Received by DH” will appear. User will open the sanction by clicking over its hyperlink. On clicking hyperlink of sanction number, a screen will appear showing the Sanction Details, Account Details, Bill Details, Bill deduction details, Budget Details and Vendor Details. Before passing the bill, DH user can see the “Payee Details”. DH user has two options available; he can either “Forward to AAO (Pass)” or “Forward to AAO (Return)”. If he opts for “Return Bill to AAO”, he will have to give the remark for same. DH user will write the Remark and press “OK” button to “Forward to AAO (Return)”.


31

If he opts to pass the bill, he will click the option “Forward to AAO (Pass)”. User can also view the details of vendor by clicking the button “Vendor Details”.

The system will ask to confirm the action by displaying a message: “Are you sure you want to pass the sanction further?”


32

DH user will press “OK” button. A screen will display the message “Bill has been passed to AAO successfully.”

Now this Bill (Sanction) will be electronically transmitted and will be available at AAO level user for further action.

6. FUNCTIONS AT AAO LEVEL

AAO user will log into PFMS portal with his user id and password and go to: “SANCTIONS” > “PASS BILL”


33

All the Bills (Sanctions) passed (or Returned) by DH user will appear on the screen. If the desired sanction is available in the list, AAO user can directly open it by clicking the hyperlink of sanction number. Otherwise, AAO user can trace the same by using search criteria.

On clicking the hyperlink of Sanction Number, Screen showing the Sanction Details, Account Details, Bill Details, Bill deduction details, Budget Details and Vendor Details, will appear. AAO user has two options available; he can either “Forward to PAO (Pass)” or “Forward to PAO (Return)”.

If he opts for the option “Forward to PAO (Return)”, he will have to give the remark(s) for same. In case, DH has already submitted some remark(s) for return, AAO has the


34

option to agree with same and go ahead, or if required AAO can delete the remark(s) submitted by DH and add some other remark(s) for return.

AAO user will write the Remark and press “OK” button to “Return the Bill to PAO”.

If AAO has to pass the bill, he will click the option “Forward to PAO (Pass)”.

The system will ask to confirm the action by displaying a message: “Are you sure you want to pass the sanction/Bill further?” AAO user will press “OK” button.

Screen will display a message:


35

“Bill has been passed to PAO successfully.”

Bill (Sanction) passed by AAO will be transmitted electronically and will be available at PAO level user for further action.

7. FUNCTIONS AT PAO LEVEL

PAO user will login PFMS portal with his user id and password and go to: “SANCTIONS” > “PASS BILL”.

All the bills (Sanctions) which have been passed/returned by AAO, will be available at PAO user. If the desired sanction is not visible in the list, user can trace it by using search option. PAO user will open the desired sanction by clicking the hyperlink of Sanction Number.


36

On clicking the Sanction Number, a Screen showing the Sanction Details, Account Details, Bill Details, Bill deduction details, Budget Details and Vendor Details, will appear. Here, two options are available. PAO user can either pass the bill for payment or return the bill to DDO. If the bill is to be returned, PAO user will press the button “Return Bill to DDO”. He will give the reason for return of bill in the remark field and press “OK” button. Bill will be returned to DDO. IF user has to pass the bill for payment, he will click the option “Pass Bill”.

System will ask for confirmation of action. PAO user will press the button “OK”.


37

System will display a message: “Bill has been passed successfully”.

The status of this sanction can be viewed as “Passed by PAO” through the option “SANCTION” > “MANAGE SANCTION”.


38

8. DIGITALLY SIGNING E-PAYMENT FILE BY SIGNATORY 1

All the sanctions for e-payment, passed by PAO user, will appear at Signatory 1 user for

digital signing. Sanctions amounting to Rupees below 10 lakhs will be digitally signed by

Signatory 1 only. However, the sanctions, amounting to Rupees 10 lakhs and above, will

require to be digitally signed by both signatory 1 and signatory 2.

User needs to open PFMS in Internet Explorer for successful digital signatures.

Since IAAA payment is exceeding Rupees One Hundred Crores, therefore it will be

signed by both Signatory 1 and 2.

In order to sign multiple e-payment files in one go, payment batch file needs to be

generated. User will go to:

“SANCTIONS” > “DIGITALLY SIGN PAY FILES”


39

A screen for “DIGITAL SIGN ON BILLS”, showing all e-payment sanctions passed by

PAO, will appear. User can trace a particular sanction by making use of search criteria.

In above screen, you can see that even after the bill has been passed by PAO, still the

PAO has the option not to sign it digitally and return the sanction to DDO. For this, user

will select the desired sanction by checking the box given against it and press the button “Return to DDO”. He will enter “Return Remarks” and press “SUBMIT” button. System

will display a message “Successfully Returned”.


40

User can click hyperlink of sanction to view its details. Sanction status will be shown as “XML Generated”. In case user opts to digitally sign the sanction, he will select the

desired sanctions by clicking the check box given against each sanction and then press the button “GENERATE PAYMENT BATCH FILE”.

A Payment batch file will be generated for the selected records.


41

After generation of batch, user can view the status of sanction as “DSC Batch Generated” through the option “SANCTIONS” > “MANAGE SANCTIONS”.

Now user will proceed to digitally sign e-payment file using his DSC. He will insert his DSC onto system and go to “SANCTIONS” > “DIGITAL SIGN BATCH”


42

A screen for “DIGITAL SIGN ON BILLS”, showing all the payment batch files pending for

digital signatures of Signatory 1, will appear. User can click the hyperlink of batch number

to view the sanction(s) it contains. Here also, user has the option for not to sign the

sanction and return it to DDO. For this, he will select the batch and press the button “Delete Batch for Recreation”. The sanctions contained in the deleted batch will again

be available under the option “Digitally Sign Pay File” and can be returned to DDO by

using the button “Return to DDO” as explained above.

System will ask for confirmation of action.


43

User will enter “Remarks for Return” and press “SUBMIT” button.

In case user opts to digitally sign e-Payment file, he will insert his DSC into system and click the button “DIGITAL SIGN”.

A screen for “Security Warning” will appear. User has to press “Continue” to proceed

further.


44

Select the box for “I accept the risk and want to run this application” and press “RUN”

button.

Press the button “Don’t Block”.

Press “RUN” to allow it to continue.


45

System will prompt user to enter PIN of DSC.

Enter PIN of DSC and press “OK”.

A Screen, showing Progress Bar, will appear.

System will display a message” Digitally signed successfully”. Press “OK”.


46

Digitally signed sanction will no more be available in the displayed list of sanctions pending for digital signatures.

User can view the status through the option “SANCTIONS” > “MANAGE SANCTION”. The status of sanction is still being shown as “DSC Batch Generated”, because being sanction exceeding Rupees One hundred crore rupees, it is yet pending for the digital signatures of signatory 2.


47

9. DIGITALLY SIGNING E-PAYMENT FILE BY SIGNATORY 2

Since the payment amount in case of IAAA is exceeding Rupees one hundred crores, it will be required to be signed both by signatory 1 and signatory 2.

In the similar manner, as already explained above in case of signatory 1, e-payment file will be digitally signed by signatory 2.


48


49


50


51

After the digital signatures of signatory 2, sanction will no more be available for digital signatures.

Status of sanction can be view through the option “SANCTIONS” > “MANAGE SANCTIONS”. It will be shown as “Digital Signatory Last”.

Hyperlink of sanction can be clicked to view its details.


52

10. ACCOUNTING IN RESPECT OF IAAA

IAAA will be treated as e-payment and not an Inter-Government Adjustment Advice (IGAA). The Reserve Bank of India will provide e-scrolls to PAOs in PFMS. The processing of the said e-scroll and its accounting will be done automatically in PFMS as is being done in case of normal e-payment scroll.

At the time of issue of IAAA Debit or (-Cr.) The functional Head selected by user. Cr. 8658-00-110-00-00-Reserve Bank Suspense-CAO At the time of scroll entry of IAAA received from RBI (-) Cr. 8658-00-110-00-00-Reserve Bank Suspense-CAO Cr. 8675-00-101-01-00-Reserve Bank-Central Accounts Office This completes the procedure for processing of IAAA sanctions on PFMS. “Suggestions from users are welcome to improve the functionality and

make it more user friendly”. ******

Date post:	19-Mar-2018
Category:	Documents
Upload:	leminh
View:	286 times
Download:	18 times

PUBLIC FINANCIAL MANAGEMENT SYSTEM...

Documents