11.1 Statement of Receipts and Expenditures (SRE) Structure and Components
Key Takeaways
- The SRE organizes cash receipts and expenditures by prescribed categories and must reconcile to treasury, accounting, and bank evidence.
- eSRE cash-basis reports are uploaded through the LIFT System under current BLGF reporting rules.
- RA 7160 Section 315 requires the local treasurer’s certified detailed statement to the local chief executive by July 15—not September.
- The Section 315 budget input and recurring LIFT submissions are distinct requirements and should not be conflated.
- Section 352 separately requires annual posting of a summary of revenues, funds received, appropriations, and disbursements.
Statement of Receipts and Expenditures Structure and Components
Purpose and basis
The Statement of Receipts and Expenditures (SRE) is a standardized fiscal report used to show an LGU's cash receipts and cash expenditures by prescribed source and economic or functional category. Current BLGF reporting refers to eSRE cash-basis reports uploaded through the LIFT System. The report supports fiscal monitoring and analysis, but it does not replace the books, bank records, collection reports, vouchers, or statutory budget documents from which it is prepared.
Start with complete source evidence: reports of collections and deposits, validated deposits, bank statements, allotment and obligation records where relevant, disbursement vouchers, check and electronic-payment registers, journal entries, interfund transfers, and closing balances. Map each transaction to the prescribed classification without netting unrelated receipts and expenditures.
Core structure
A report ordinarily distinguishes local-source receipts, national transfers, inter-local or other transfers, grants, borrowing proceeds, and other financing receipts. Expenditure categories distinguish operating uses, capital outlays, debt service, transfers, and other prescribed objects. Fund and special-purpose classifications must remain traceable. A trust receipt does not become local revenue, and a transfer between LGU funds should not be double-counted as new consolidated income.
Use the cash basis required for the LIFT report: recognize cash receipts when received and cash expenditures when paid, applying the current reporting instructions. Do not import accrual revenue or unpaid obligations merely to improve a ratio. Reconcile opening cash plus receipts minus expenditures and transfers to closing cash, with documented treatment of reconciling items.
Section 315 budget statement
RA 7160 Section 315 is a separate, precise requirement. On or before July 15 of each year, the local treasurer submits to the local chief executive a certified statement covering:
- income and expenditures of the preceding fiscal year;
- actual income and expenditures for the first two quarters of the current year; and
- estimated income and expenditures for the last two quarters of the current year.
This certified statement feeds the local budget process. It should not be misstated as a September 5 or September 15 deadline, and it should not be treated as identical to the quarterly and year-end LIFT submissions. Section 317 separately gives department heads a July 15 deadline for budget proposals; Section 318 then uses the treasurer's statement, office proposals, and local finance committee estimates in preparing the executive budget.
Reconciliation and disclosure
Before submission, compare treasury cash reports, accounting ledgers, bank balances, and LIFT classifications. Explain timing differences, returned payments, cancelled checks, interfund items, and prior-period adjustments. Review totals vertically and horizontally and compare unusual movements with source schedules.
RA 7160 Section 352 adds a transparency duty: within thirty days after fiscal year-end, local treasurers, accountants, budget officers, and other accountable officers post in at least three publicly accessible and conspicuous places a summary of revenues collected and funds received, including appropriations and disbursements during the preceding year.
A strong examination answer identifies the report, accounting basis, recipient or system, reporting period, deadline, and reconciliation evidence. Similar names do not make statutory reports interchangeable.
Practical tie-out
As a final check, trace a sample of large receipts from official receipt or electronic settlement through deposit, treasury report, ledger, and LIFT category, then trace large expenditures from appropriation and voucher through payment and bank clearing. This two-direction test helps detect omitted, duplicated, misclassified, or wrong-period transactions.
A crosswalk from source record to SRE line
Treat every SRE amount as the end of an evidence chain. Start with the chart of accounts and fund, identify the cash transaction and period, map the account to the prescribed SRE line, and reconcile the line to the ledger and supporting collection or disbursement report. Maintain a crosswalk for local taxes, regulatory fees, service and business income, national transfers, financing receipts, personnel services, maintenance and operating expense, capital outlay, and other required categories. A convenient label used by an office is not enough if it maps to the wrong statutory or reporting classification.
Use cash-basis timing consistently for the eSRE framework identified by BLGF. Do not report a receivable as a cash collection or move a late deposit backward merely to improve a quarter. At the same time, investigate cutoff differences so collected cash is not omitted. Eliminate duplicate imports and keep reversals, refunds, and interfund movements visible in the reconciliation. Opening cash, receipts, disbursements, transfers, and ending cash should connect arithmetically by fund.
Before certification, run reasonableness comparisons against the prior quarter, prior year, approved budget, and collection target. Large changes require documentary explanations, not arbitrary smoothing. The preparer, reviewer, and certifying official should retain the system-generated submission record, validation messages, signed schedules, and reconciliations. A portal acceptance message proves transmission; it does not prove that the classification or amount is correct.
What is the principal basis used for current eSRE reports uploaded through LIFT?
By what date does RA 7160 Section 315 require the local treasurer’s certified detailed statement to the local chief executive?
Which treatment is proper in a consolidated SRE?
What is a core pre-submission control?