Para 2.3.9 — CAM
Original Rule Text
2.3.9 Miscellaneous procedure to be adopted by stakeholders:
i. In case of transfer of an official to other offices, DDO while issuing LPC shall attach employee payment details as available in PFMS. The formats of Pay Bill Register (PBR: Part II) and Last Pay Certificate have been revised.
ii. Claimant shall check the bank account details as appearing in PFMS while submitting the eclaim.
iii. In case of any discrepancy in e-sanction or e-claim, provision shall be made for return of esanction and e-claim by DDO or HoO user as the case may be.
iv. In the case of e-bill, DDO shall complete the registration of HoO user as authorised officer for conveying the sanction to Pay and Accounts Officer in terms of DFPR or as per orders issued from time to time in consultation with PAO/CDDO concerned.
v. Sanctioning Authority Code details: For viewing the details of sanctioning authority code generated by the system, the following report may be used;
CAM Reports-Master-MST-04-Sanctioning Authority Code details.
vi. HoD authorised users (Sanction Maker and Sanction Checker) and DDOs shall keep a close watch on the entire process of the e-bill module and it should be ensured that the same claim is not duplicated e.g. by processing both through ‘normal bill’ and ‘e-bill’ module’. Two radio buttons naming “normal bill” & “e-bill” are being provided in the existing two reports available in PFMS under ‘CAM Reports’ viz. “PAY-02: Sanction E-payment Status details” and “MIS-01: Bill status details.” This is to facilitate the users to filter and verify the details of bills separately. PAY01-Sanction Status Details report has also been provided through which payments drawn earlier can be verified.
vii. Any discrepancies noticed, in the PFMS-CAM reports must be taken up promptly with GIFMIS (PFMS) for its rectification.
What This Means
This paragraph outlines miscellaneous procedures for various PFMS stakeholders. When an employee transfers, the DDO must attach PFMS payment details with the LPC. Claimants should verify their bank account details in PFMS before submitting e-claims. If discrepancies arise in e-sanctions or e-claims, there are provisions for returning them to the relevant authority. DDOs must complete the e-bill process within prescribed timelines, and all stakeholders must use the system's built-in safeguards to maintain accuracy and prevent payment errors.
This explanation was generated with AI assistance for educational purposes. Always refer to the official gazette notification for authoritative text.
Key Points
- 1DDO must attach PFMS payment details with Last Pay Certificate (LPC) on employee transfer
- 2Claimants must verify bank account details in PFMS before submitting e-claims
- 3Provisions exist for returning e-sanctions and e-claims when discrepancies are found
- 4DDOs must complete e-bill processing within prescribed timelines
- 5Pay Bill Register (PBR: Part II) and LPC formats have been revised for PFMS compatibility
Practical Example
An Assistant Section Officer is transferred from the Ministry of Finance to the Ministry of Commerce. The DDO at the Finance Ministry issues an LPC with a printout of the employee's PFMS payment history attached, showing last salary drawn, GPF deductions, TDS details, and bank account on record. The new DDO at the Commerce Ministry can immediately verify the employee's pay details in PFMS without waiting for physical records, ensuring the first salary at the new office is processed correctly and on time.
This explanation was generated with AI assistance for educational purposes. Always refer to the official gazette notification for authoritative text.
Frequently Asked Questions
Why must bank details be verified before submitting an e-claim?▼
What happens if there is a discrepancy in an e-sanction?▼
How do revised PBR and LPC formats help in the PFMS environment?▼
This explanation was generated with AI assistance for educational purposes. Always refer to the official gazette notification for authoritative text.