PFMS Reports and Audit Trails

In the previous chapter, "E-Payment and Accounting in PFMS," we learned how government agencies actually push the button to send money to vendors and beneficiaries. We looked at the mechanics of moving the money. But in government finance, spending the money is only half the job. The other half is proving exactly how, when, and why you spent it.

If you are managing public money, you cannot simply say, "I spent fifty thousand rupees on school supplies; trust me." You need a permanent, unalterable record that proves the money went to the right person, for the right reason, following the right rules. Furthermore, the people sitting in the Ministry of Finance in New Delhi need to be able to see that this transaction happened without having to wait six months for a paper receipt to arrive in the mail.

This is where the reporting and auditing capabilities of the Public Financial Management System (PFMS) come in. PFMS is not just a payment gateway; it is a massive, real-time management information system. In this chapter, we will explore how PFMS turns millions of daily transactions into readable reports, how it creates an unbreakable digital paper trail for every single rupee, and how it has completely revolutionized the way government audits are conducted.

The Power of Real-Time Visibility

To understand why PFMS reports are so powerful, you have to understand the nightmare they replaced.

Before PFMS, government spending was largely a "black box." The Central Government would release funds to a State Government, which would pass it down to a district, which would pass it down to a block, which would finally pass it to a Gram Panchayat or a local school. At every step, the money was withdrawn from the treasury and deposited into a local commercial bank account.

Once the money left the central treasury, the Ministry lost sight of it. The only way the Ministry knew if the money had actually been spent was when the local agency eventually filled out a physical piece of paper called a Utilization Certificate (UC) and mailed it back up the chain. This process took months, sometimes years.

Because of this delay, the government suffered from a massive problem known as the "parking of funds." An agency might receive ₹10 Lakhs for a project, spend only ₹2 Lakhs, and leave the remaining ₹8 Lakhs "parked" in their local bank account. The Ministry, flying blind, might assume the agency needed more money and send another ₹10 Lakhs the next year. Meanwhile, the Central Government was borrowing money from the market and paying interest on it, completely unaware that its own funds were sitting idle in thousands of local bank accounts across the country.

PFMS reports solved this by turning the black box into a glass box. Because PFMS is integrated directly with the core banking systems of commercial banks, every time an agency spends a rupee, the central database updates instantly.

The Daily Bread of Management: Key PFMS Reports

PFMS generates dozens of standard reports designed for different levels of management—from a local Drawing and Disbursing Officer (DDO) checking their daily balance, to a State Finance Secretary monitoring the entire state's budget.

While you do not need to memorize every single report code, you must understand the primary categories of reports and what they are used for.

1. The EAT Reports (Expenditure, Advance, Transfer)

The EAT module is the workhorse of PFMS for lower-level implementing agencies. Whenever an agency spends money, gives an advance to an employee, or transfers funds to a lower-level agency, it is recorded here.

The most famous report in this category is the EAT02 Report.

• What it shows: The EAT02 report provides a detailed view of agency-wise fund flows and, crucially, their unspent balances.
• Why it matters: If a Ministry wants to release the second installment of funds to an agency, they will first pull the EAT02 report. If the report shows that the agency still has 60% of its first installment sitting unspent in its bank account, the Ministry will block the new release. This single report is the primary weapon against the parking of funds.

2. The SNA Reports (Single Nodal Agency)

For Centrally Sponsored Schemes (CSS)—schemes funded jointly by the Centre and the State—the government now uses the Single Nodal Agency (SNA) model. Instead of scattering money across thousands of accounts, each scheme has one central bank account per state.

The SNA01 Report is the critical dashboard for this model.

• What it shows: It tracks the exact balance in the state's central scheme account. More importantly, it tracks whether the State Government has deposited its matching share of the funds.
• Why it matters: By law, when the Central Government sends its share of scheme funds to a state, the State Government has exactly 30 days to add its own matching share into the SNA account. If they delay, they are penalized with interest. The SNA01 report automatically flags which states are late in transferring their shares, allowing the Ministry of Finance to enforce strict financial discipline.

3. Scheme-Wise and Component-Wise Reports

Imagine a massive umbrella scheme like the National Health Mission. This scheme has hundreds of "components"—money for buying ambulances, money for training nurses, money for building clinics.

A Scheme-Wise Expenditure Report allows a manager to filter the data not just by who spent it, but by what it was spent on. A manager can ask the system: "Show me exactly how much money was spent nationwide on the 'Nurse Training' component between April 1st and September 30th." This allows the government to see if their policy priorities are actually translating into ground-level spending.

The Concept of a Digital Audit Trail

Reports give you the big picture. But what happens when an auditor finds a suspicious transaction and wants to investigate the microscopic details? This is where the audit trail comes in.

In the days of manual accounting, a corrupt official could alter a cashbook by using correction fluid, tearing out a page, or simply writing a backdated entry. An auditor looking at the physical book months later might never know the ledger had been tampered with.

PFMS makes this kind of tampering mathematically impossible. Once a transaction is entered into PFMS, it creates a permanent digital footprint that cannot be deleted or altered, even by the system administrators.

Anatomy of a PFMS Transaction Record

When a single rupee is spent through PFMS, the system attaches a massive amount of metadata (data about the data) to that transaction. If an auditor clicks on a specific payment, they will see:

1. 1The Maker-Checker User IDs: PFMS strictly enforces the Maker-Checker rule. The person who enters the payment details (the Data Operator / Maker) cannot be the same person who approves it (the Data Approver / Checker). The audit trail permanently records the unique login IDs of both individuals.
2. 2Exact Timestamps: The system records the exact date, hour, minute, and second the Maker submitted the file, and the exact second the Checker approved it.
3. 3IP Addresses: The system logs the internet IP address from which the users logged in.
4. 4Sanction ID and Voucher Number: Every payment must be tied to an official government sanction order. The system generates a unique Voucher Number linking the payment to this specific approval.
5. 5The UTR Number: This is perhaps the most important piece of the puzzle.

The UTR is the ultimate proof of payment. An agency cannot claim "we sent the cheque but it got lost in the mail." If there is a UTR number in the PFMS audit trail, it is absolute, undeniable proof that the commercial bank successfully deposited the exact amount into the vendor's or beneficiary's account.

Revolutionizing Government Audits

The Comptroller and Auditor General of India (CAG) is the supreme auditing body of the country. Their job is to ensure that every rupee of public money is spent legally and efficiently. PFMS has completely transformed how the CAG and internal departmental auditors do their jobs.

From Physical Vouching to Desk Audits

Historically, an audit meant a team of auditors traveling to a district office, sitting in a dusty room, and manually "vouching"—comparing handwritten cashbook entries against stacks of physical paper receipts and bank passbooks. It was slow, exhausting, and prone to human error. Auditors could only ever check a small random sample of transactions.

Today, auditors conduct "desk audits." Before they ever visit an office, they log into PFMS from their headquarters. They can download the entire year's financial data for an agency in an Excel file. Instead of sampling 5% of transactions, they can use data analytics software to scan 100% of the transactions in seconds.

Automated Anomaly Detection

Because the audit trail is entirely digital, auditors can search for specific patterns that indicate fraud, inefficiency, or rule-breaking.

Using PFMS reports, an auditor can instantly filter for all transactions made in the last 48 hours of March. They can look at the timestamps in the audit trail. If they see that a Maker and a Checker approved fifty massive payments at 11:45 PM on March 31st, and both users logged in from the exact same IP address, the auditor immediately knows something is wrong. It suggests the Maker and Checker were sitting at the same computer, likely sharing passwords to bypass internal controls and push the money out the door before midnight.

Without the digital audit trail, catching this kind of procedural violation would be nearly impossible.

Worked Example: Tracing a Transaction

Let us walk through exactly how an auditor uses these tools in the real world.

Imagine an auditor is reviewing the accounts of a District Health Society. The auditor pulls a Scheme-Wise Expenditure Report for the "National Health Mission" and notices a sudden spike in spending under the component code for "Emergency Medical Equipment."

The auditor decides to drill down into a specific transaction: a payment of ₹5,00,000 made to "Apex Medical Suppliers."

Step 1: Verifying the Approval The auditor clicks on the transaction and looks at the audit trail. They check the Sanction ID. They ask the District Health Officer to produce the physical or digital file matching that Sanction ID to ensure the purchase was actually authorized by the competent authority.

Step 2: Checking the Maker-Checker Logs The auditor looks at the timestamps.

• Maker ID (Clerk): Submitted on Oct 12 at 10:15 AM.
• Checker ID (Chief Medical Officer): Approved on Oct 14 at 2:30 PM.

This shows a healthy gap, indicating the Chief Medical Officer likely took the time to actually review the file before approving it, rather than rubber-stamping it instantly.

Step 3: Confirming the Delivery of Funds The auditor looks for the UTR Number. The presence of the UTR confirms that the ₹5,00,000 didn't just leave the government's account; it successfully landed in the bank account of Apex Medical Suppliers.

Step 4: Closing the Loop Because PFMS proves the money was paid, the auditor's final job is physical verification. They walk into the hospital store-room and say, "PFMS proves you paid Apex Medical Suppliers ₹5,00,000 for emergency equipment on October 14th. Show me the equipment."

PFMS handles the financial truth perfectly, leaving the auditor free to focus on the physical truth on the ground.

Quick Revision

• The Core Problem Solved: PFMS reports eliminate the "black box" of government spending, providing real-time visibility and preventing the idle "parking of funds" in local bank accounts.
• EAT Reports: Stand for Expenditure, Advance, and Transfer. The EAT02 report is crucial for monitoring agency-wise fund flows and unspent balances before releasing new installments.
• SNA Reports: Used for Centrally Sponsored Schemes. The SNA01 report monitors the state's central scheme account and tracks whether the State Government has deposited its matching share within the mandated 30 days.
• Audit Trail: A permanent, unalterable digital footprint of a transaction. It records exactly who did what, and when.
• Maker-Checker Logs: The audit trail permanently records the distinct User IDs and IP addresses of the person who initiated the payment (Maker) and the person who approved it (Checker).
• UTR Number: The Unique Transaction Reference number generated by the bank. It is recorded in the PFMS audit trail as absolute proof that the money successfully reached the payee's account.
• Desk Audits: PFMS allows the CAG and internal auditors to analyze 100% of an agency's transactions remotely, using data analytics to spot anomalies like the "March Rush" or shared passwords.