Para 2.3.5 — CAM
Original Rule Text
2.3.5 Procedure for generation of e-sanction by Sanctioning authority
i. Authorized Sanction Maker (SnM) users in PFMS will be able to receive e-claim and shall scrutinise the claims thoroughly. SnM users will ensure that the unique e-Claim Reference Number as shown by PFMS in the e-claim tallies with the Claim Reference Number in the
uploaded supporting documents. On receipt of e-claim from the claimant, it should be ensured that the said e-claim have not been earlier processed for payment.
ii. In case of cutting or overwriting of figures in the supporting documents or inconsistency of details in supporting documents with the details mentioned in the e-claim, the e-claim should be returned to the claimant.
iii. The SnM in PFMS will generate e-Sanction in PFMS after obtaining necessary financial sanction of the competent authority. At the time of creation of e-Sanction, SnM can upload two documents viz. Budget Overriding Assurance (size 2 MB) if any, and a scanned copy of approval note of the financial sanction (Size 4 MB). PFMS will also provide SnM an option to attach a copy of the terms and conditions (size 2 MB) in case of sanction of grants-in-aid/loans etc. e-Sanction will be generated as per the uniform format with editing facility for the user. The Sanction Checker (SnC) user in PFMS who must be the gazetted officer authorized to convey the sanction of the Head of Department (HoD) or Head of Office (HoO) in terms of Delegation of Financial Power Rules (DFPR). e-Sanction will be issued with the Sanction Checker (SnC)'s digital signature.
iv. Multiple e-claims of same nature/sub category can be attached to a sanction to generate eSanction.
What This Means
The e-sanction process in PFMS works through two roles: the Sanction Maker (SnM) who scrutinizes the claim and prepares the sanction, and the Sanction Checker (SnC) who reviews and digitally signs it. The SnM must verify that the e-claim reference number in PFMS matches the reference in uploaded supporting documents and that the claim has not been previously processed. If there are any discrepancies in supporting documents (like overwriting or inconsistencies), the SnM must return the e-claim to the claimant rather than processing it further.
This explanation was generated with AI assistance for educational purposes. Always refer to the official gazette notification for authoritative text.
Key Points
- 1Two roles: Sanction Maker (SnM) prepares the sanction, Sanction Checker (SnC) approves with digital signature
- 2SnM must verify e-claim reference numbers match between PFMS and uploaded supporting documents
- 3SnM must check that the claim has not been previously processed for payment
- 4Discrepancies like overwriting or inconsistencies in documents require return to claimant
- 5The SnC reviews and digitally signs the e-sanction using DSC (Digital Signature Certificate)
Practical Example
A government employee submits an e-claim for Rs.50,000 medical reimbursement through PFMS. The Sanction Maker receives the claim, verifies that the e-claim reference number (e.g., ECL-2026-MHA-00542) appears on both the PFMS record and the uploaded hospital bill scan. Noticing that the hospital bill has an amount overwritten from Rs.45,000 to Rs.50,000, the SnM returns the e-claim to the employee requesting a fresh bill from the hospital. Only a clean, unaltered claim proceeds to the Sanction Checker for DSC approval.
This explanation was generated with AI assistance for educational purposes. Always refer to the official gazette notification for authoritative text.
Frequently Asked Questions
What is the difference between a Sanction Maker and a Sanction Checker?▼
Why must the e-claim reference number be verified against supporting documents?▼
What happens if a previously processed claim is submitted again?▼
This explanation was generated with AI assistance for educational purposes. Always refer to the official gazette notification for authoritative text.