PRIASOFT-PFMS

INTEGRATION
OBJECTIVE
 Bringing transparency & accountability in management
of finances available to Panchayat under 14th Finance
Commission Grant.
 PFMS portal to be utilized FOR ONLINE Payment to
Vendors/Beneficiaries under FFC Grants
PRE REQUISITES
 Panchayats need to register in PFMS portal as Agency
with a valid Bank Account details(out of 30 DSC
enabled Banks Account to be used for FFC Scheme).
 Unique Agency ID is generated against each Panchayat
in PFMS portal.
 Agency ID is exchanged with PRIASoft through
webservice.
 Agency ID is used as a reference for all the transactions
carried out by Panchayat under FFC Scheme.
NEW MODULES INTRODUCED IN
PRIASOFT
 User Creation & Approval
 DSC Management

 Vendor Registration(Bulk)

 Digitally Signing of Payment File(FTO)

USER CREATION
 Provision to create Scheme Specific users for Online
Payment
 Roles are:
 State Admin
 District Admin
 Block Development Officer (or Equivalent)
 Checker (Panchayat Sarpanch or Equivalent)
 Maker (Panchayat Secretary or Equivalent)

 Hierarchical approach followed for user creation

USER CREATION
USER PROFILE MANAGEMENT - CREATION
 On First Login , each user have to fill profile details as per
following:
 Name of the official
 Organization
 Designation
 Mobile number
 Email Id

 Valid & Unique Email-id and Mobile number should be

used.
 OTP based verification is enabled for validating the profile

 Other transactions are also validated based on OTPs sent to

registered mobile number and email id of the user.
USER PROFILE MANAGEMENT - CREATION
User will fill below mentioned details and click on Update button

User enter OTPs (Received on E-mail & Mobile) and Save the details.
Facilitate to Regenerate OTPs if not received.
USER PROFILE MANAGEMENT -
APPROVAL
 Hierarchy based user profile approval system is in place
 The profile of “Maker” and “Checker” users will be approved
by “BDO” user.
 The profile of “BDO” user will be approved by “District
Admin” user.
 The profile of “District Admin” user will be approved by
“State Admin” user.
 User profile approval system will help in
authenticating/validating the details of users at each
level.
APPROVAL OF REGISTERED USERS
•Each user should register by filling the correct profile details
•Then user will be approved by subsequent higher level user.

State
Admin
Approve/Reject

District
Admin

Approve/Reject

Block
Maker Checker
Admin
Approve/Reject

Approve/Reject
USER PROFILE MANAGEMENT -
APPROVAL
USER PROFILE MANAGEMENT -
APPROVAL
DSC REGISTRATION AND APPROVAL
 Each user has to register with a separate unique DSC
 Hierarchy based DSC approval system is in place
 State Admin register the DSC first
 District Admin register its DSC and will be approved by the State
Admin
 BDO register its DSC and will be approved by District Admin
 Maker and Checker user register their DSC and will be approved by
BDO user
 OTP based registration and approval process is in place to authenticate
about the genuine person is using the system.
 Registered DSCs of “Maker” & “Checker” users are ported in PFMS
through XML to ensure the authenticity of the person while making online
payment transactions.
• Gram Secretary(Maker) & Gram Sarpanch/Pradhan(Checker) will register their DSCs Maker &
• BDO will Approve/Reject and apply digital Signature Checker
• Maker will do entries in PRIASoft and digitally sign it.
• Checker will cross check maker’s entry and apply digital signature
• BDO will register DSC BDO
(Block)
• District Admin will Approve/Reject and apply digital Signature
• BDO will approve/reject registered DSCs of Makers & Checkers (at GP level)
• District Admin will register its DSC District Admin
• State Admin will Approve/Reject and apply digital Signature.
• District Admin will approve/reject registered DSCs of Makers & Checkers (at GP level)
• State Admin will register its DSC State Admin
• No approval is required
• State Admin will approve/reject registered DSCs of District Admin ( Lower Tier)
ROLE OF DSC STAKEHOLDERS
DSC REGISTRATION
User will insert the DSC Token and click on Register your DSC, the DSC will be
registered (Follow the steps of DSC Installation Steps)and sent to respective approver
for approving the file.

User has to enter the token password and click on “OK” button to proceed.
DSC REGISTRATION

• DSC token details will be displayed. Click on “Save DSC”, generate OTP and send on
registered mobile number of the user.
• User will enter the OTP and click on “Submit” button to proceed.
• Click on “Submit” will save the DSC details and sent to respective approver/admin for
approval.
DSC APPROVAL/REJECTION

The approval user will select the respective entity and selecting from drop
down menu to either Approve or Reject the DSC.
DSC APPROVAL/REJECTION

User will select from the radio button and click on the “Apply Digital Signature” button to sign
it.

• User will enter the Token password and click on the “OK” button
• In next screen after clicking on the “Confirm Signing” button the DSC file will be Accepted
or Rejected with digital sign of Admin user.
VENDOR REGISTRATION AND
APPROVAL
 The vendors such as Agency, Employee, Beneficiary etc. registers in
PRIASoft with following details:
 Agency Name
 Address & City
 Bank Name
 IFSC Code
 Bank Account Number
 The XML is generated for registered vendors and digitally signed by both
“Maker” and “Checker” .
 The XML is pushed to SFTP server for verification and validation process of
the vendor details entered.
 PFMS validated at their end with banks and shares details of “Approved” or
“Rejected” vendors with PRIASoft along with “Rejection Reason” (if any).
 The “Approved” vendors(Unique ID) are eligible for transaction while the
“Rejected” vendors have to re-register with correct details and pass through
validation process of PFMS.
VENDOR REGISTRATION
Maker will login in PRIASoft and enter details of vendors
APPROVING VENDOR FILE BY MAKER
Master Entry Agency Approve Agency for PFMS

The Maker will select the respective Agency/Vendors and approve them
for signing digitally and sending to Checker for final approval
 SIGNING VENDOR FILE BY MAKER
Master EntryDSC ManagementSign approved vendor file

• Maker select the unsigned vendor file and Apply Digital signature
• The Maker enter DSC token password and enter OTP received on registered
mobile number to confirm the Digitally Signing of Vendor file
 SIGNING VENDOR FILE BY CHECKER
Master Entry DSC Management Sign Approved vendor file

• Checker select the Maker’s Signed vendor file and Apply Digital
Signature
• Checker enter DSC token password and enter OTP received on
registered mobile number to confirm Signing of Vendor file
PAYMENT VOUCHER BOOKING
 Maker will book a payment voucher for expenditure made
 Transactions Voucher TransactionPayment VoucherOnline
Payment Voucher Add
PAYMENT VOUCHER BOOKING
SCREEN
GENERATION OF PAYMENT FILE (FTO )
 After booking all Payment Voucher for one day, Close day book is must.
 Provision made for scheme wise closure of day book i.e. the schemes mapped for
online payment are having separate interface for closing the day book.
 Period End Procedure  Scheme wise closure  Schemewise close day
book
GENERATION OF PAYMENT FILE (FTO ) ..CONT
 Close day Book Screen

• As soon as user click Close Day book, the XML of Payment file (FTO)
containing all the frozen payment vouchers for all beneficiaries, will be
generated.
SIGNING FTO BY MAKER
 The Maker will go to TransactionsVoucher Transaction  Payment
Voucher Sign FTO
SIGNING FTO BY MAKER
 The details of all payment files fro all beneficiaries would be visible
 Maker have to select the appropriate files are Apply Digital Signature to Sign the
FTO

The signed FTO by Maker will be sent to Checker for verification and approval
SIGNING FTO BY CHECKER
Checker will go to Master Entry DSC Management Sign FTO

• Checker will view all details and approve or reject the digitally signed payment file of
Maker.
• A digitally signed XML file (FTO) containing the information of all Payment vouchers
will be sent to PFMS through SFTP Electronically
• PFMS will send /push the digitally signed payment file to respective bank.
• On successful payment, the Bank account of Panchayat will be debited and beneficiary
bank account will be credited.
• If the Payment is rejected due to any reason then, automatically a payment cancellation
voucher will be booked in PRIASoft.
PFMS VALIDATION OF FTO
• PFMS pick and read the Signed Payment File(FTO) from SFTP
Electronically and verify the DSC of Maker and Checker.

• Then PFMS send /push the digitally signed payment file to respective
bank as per the process of PFMS.

• PFMS also verifies the bank account of Vendor at the moment

• On verification properly, if payment process is successful, the Bank

account of Panchayat will be debited and beneficiary bank account will be
credited.

• If the Payment is rejected due to any reason then, automatically a

payment cancellation voucher will be booked in PRIASoft.
 DIGITALLY SIGNING OF FTO

 The Payment vouchers (Expenditure) are booked by Panchayats for

registered Vendors only.
 The payment to registered vendors under FFC can be done only
through PFMS as mode of payment. The other mode of payments such
as Cash, Cheque, Demand Draft etc. are not available.
 Proper mapping of PRIASoft Account Heads with PFMS Payment
purpose ID as per FFC Components is done.
 Payment File containing the payment details to various vendors is
generated on the closing of Day Book.
 Payment file is digitally signed by “Maker” &“Checker” both by using
their DSCs.
 Signed Payment FTO is pushed to PFMS ( through SFTP server ) to
verify & validate.
DIGITALLY SIGNING OF FTO
 After verification & validation, the digitally signed FTO is pushed
to the DSC enabled integrated banks.
 PFMS shares the details of “Approved” or “Rejected” FTOs with
PRIASoft with “Rejection Reason” (if any).
 Automatic cancellation voucher is booked in PRIASoft for the
rejected vouchers (if any).
 The rejected FTOs need to be booked again with correct details by
Panchayat
 On successful transaction the bank account of GPs will be debited
and Bank account of Vendor will be credited.