14.3 Stock Statements vs. Flow Statements

Stock Statements vs. Flow Statements

A fundamental conceptual distinction tested on public finance examinations is the difference between stock statements and flow statements:

Accounting Periods and Year-End Cutoffs

Accounting periods establish rigid calendar boundaries (typically a 12-month fiscal year, such as July 1 to June 30 for state/local governments, or October 1 to September 30 for the federal government). Accurate financial reporting requires rigorous enforcement of year-end cutoffs:

• Modified Accrual Cutoff (Governmental Funds): Under GASB standards, revenues are recognized only when they become both measurable and available to pay current period liabilities (the "available" period is legally defined as collected within the current period or typically within 60 days after fiscal year-end, such as for property taxes).
• Expenditure Recognition Cutoff: Goods and services delivered on or before the final day of the fiscal year must be accrued as expenditures and accounts payable of that closing fiscal year, even if vendor billing occurs weeks later.
• Year-End Encumbrance Treatment (GASB Statement No. 54): Open encumbrances (outstanding purchase orders) at year-end do not constitute GAAP expenditures or liabilities because the vendor has not yet performed. Under GASB 54, uncompleted purchase orders do not appear as liabilities on the balance sheet; instead, the underlying resources are reported as Committed Fund Balance (if contracted by the highest authority) or Assigned Fund Balance, and re-appropriated into the subsequent fiscal year.

---

Financial Management System Controls

Modern Integrated Financial Management Systems (IFMS) and Enterprise Resource Planning (ERP) databases translate statutory budget rules into automated, systemic internal controls that prevent human error, fraud, and unauthorized spending.

+---------------------------------------------------------------------------------------------------+
|                         AUTOMATED TRANSACTION LIFECYCLE CONTROLS                                  |
+---------------------------------------------------------------------------------------------------+
|  1. REQUISITION   --> System executes automated funds availability check                          |
|                       PASS: Pre-encumbrance recorded; soft reservation of budget                  |
|                       FAIL: "Hard Stop" triggered; transaction blocked completely                 |
|                                                                                                   |
|  2. PURCHASE ORDER--> Vendor contract awarded; pre-encumbrance converted to formal ENCUMBRANCE     |
|                       Legal commitment established; funds locked against other purchases          |
|                                                                                                   |
|  3. RECEIVING     --> Warehouse receives physical goods; inspects count & condition;              |
|                       Receiving Report entered electronically into financial management system    |
|                                                                                                   |
|  4. INVOICE       --> Vendor transmits billing invoice; system performs automated                 |
|                       THREE-WAY MATCH: (Purchase Order == Receiving Report == Vendor Invoice)     |
|                                                                                                   |
|  5. DISBURSEMENT  --> Encumbrance liquidated; general ledger records EXPENDITURE & ACCOUNTS PAYABLE; |
|                       Warrant / electronic EFT payment generated and disbursed to vendor          |
+---------------------------------------------------------------------------------------------------+

Automated Funds Availability Checking

Whenever an employee enters an electronic purchase requisition, the financial management system executes an automated mathematical verification against general ledger balances in real time:

$\text{Available Budgetary Balance} = \text{Appropriation / Allotment} - (\text{Actual Expenditures} + \text{Encumbrances} + \text{Pre-encumbrances})$

• Pre-encumbrance (Requisition): An internal administrative reservation of budget authority. It flags funds as pending, preventing other departmental staff from committing those same dollars while purchase specifications are reviewed.
• Encumbrance (Purchase Order / Contract): An accounting commitment recognizing an executed legal contract with an external vendor. The system places a binding legal hold on the funds, reducing available spending authority.
• Expenditure (Invoice / Receipt): Recognition of a completed transaction where goods have arrived. The encumbrance is liquidated, and an expenditure and liability (Accounts Payable) are recorded.

Hard Stops vs. Soft Warning Flags

ERP systems configure automated budgetary limits through two distinct enforcement protocols:

• Hard Stops (System Rejections): The system strictly blocks transaction posting if available budget is insufficient. The requisition cannot be processed or submitted. The process can move forward only if the budget officer executes an approved budget transfer or the legislature passes a supplemental appropriation. Hard stops are universally applied to personnel compensation, travel, and capital accounts.
• Soft Warning Flags: The system generates an automated alert warning the user and department head that an account is nearing exhaustion or running a minor negative balance, but permits transaction submission subject to secondary managerial review. Soft stops provide operational flexibility for high-volume, low-risk operating consumables (such as road salt or utility bills) where public safety requires immediate procurement.

Three-Way Matching Disbursement Controls

Prior to issuing a payment warrant or electronic funds transfer (EFT) to an external supplier, the financial management system enforces a mandatory three-way match across three separate documents originated by three distinct individuals (enforcing strict segregation of duties):

1. Purchase Order (PO): Originated by the Purchasing / Procurement Department; confirms authorized items, approved quantities, and contracted unit prices.
2. Receiving Report: Originated by the Receiving Warehouse / Field Staff; certifies physical delivery, date received, quantity accepted, and confirmation that items were undamaged and meet specifications.
3. Vendor Invoice: Originated by the external supplier; details itemized billing charges, payment terms, and vendor remittance address.

The system validates that the quantities, unit prices, and descriptions across all three records match within tight automated tolerance thresholds (e.g., matching within 1% or $50). If quantities disagree (e.g., invoice bills for 100 laptops but the receiving report confirms only 85 delivered), the system places an automated payment hold on the unverified variance, preventing overpayments, duplicate disbursements, or payment for fictitious services.

Comparative Matrix: Budgetary Control Stages

| Procurement Stage | Primary Triggering Document | Operational Purpose | General Ledger Impact | System Validation Protocol | | :--- | :--- | :--- | :--- | :--- | :--- | | 1. Requisition | Electronic Purchase Requisition | Internal request by departmental staff to buy goods | Debits Pre-encumbrances; credits Pre-encumbrance Reserve | Automated Funds Availability Check (Hard Stop or Soft Warning) | | 2. Commitment | Approved Purchase Order / Contract | Executed legal contract binding government to vendor | Liquidates Pre-encumbrance; debits Encumbrances; credits Encumbrance Reserve | Validates against Allotment ceiling; locks funds from reallocation | | 3. Receiving | Electronic Receiving Report | Physical confirmation of delivery and inspection | No direct GAAP journal entry in most governmental systems | Matches received quantities against Purchase Order specifications | | 4. Invoicing | Itemized Vendor Billing Invoice | Supplier demands payment for delivered items | Liquidates Encumbrance; debits Expenditures; credits Accounts Payable | Automated Three-Way Match (Purchase Order vs. Receiving Report vs. Invoice) | | 5. Disbursement | Payment Voucher / Check / EFT | Treasury disburses cash; satisfies accounts payable liability | Debits Accounts Payable; credits Cash / Treasury General Account | Verifies positive vendor master file status; cancels invoice to prevent duplicate payment |

---

Practical Public Finance Scenario: Managing Emergency Procurement and Budget Overruns

To observe the interaction of operational budgetary controls, personnel systems, and automated ERP workflows, examine the following case:

Scenario: During a severe winter ice storm in February, the County Department of Public Works (DPW) mobilizes round-the-clock road clearing operations. By March 5, the DPW's Object 0430 (Road De-icing Salt) line has zero available balance, having exhausted its $600,000 appropriation due to unprecedented salt consumption. A late-season blizzard is forecast, requiring an emergency order of 2,500 tons of salt costing $175,000. When the procurement clerk attempts to issue an emergency purchase order, the county's financial management system triggers an automated Hard Stop, rejecting the transaction for insufficient funds.

Professional Financial Analysis and Resolution Steps

1. Overriding the Hard Stop via Budgetary Reallocation: The procurement clerk cannot unilaterally bypass the ERP hard stop. To resolve the emergency, the DPW director reviews the department's general ledger allotments. The director identifies $210,000 in surplus uncommitted funding within Object 0110 (Full-Time Regular Salaries) resulting from a higher-than-budgeted vacancy lag (three senior highway engineers retired in November and replacements have not yet been onboarded).
2. Executing an Administrative Budget Transfer: Under the county financial management code, the DPW director submits an electronic budget transfer request to shift $175,000 from the Personnel Services Allotment to the Supplies and Materials Allotment. The central budget office validates that the salary savings are genuine and non-recurring, approves the journal entry, and re-allocates the budget authority in the general ledger database.
3. Transaction Flow and Encumbrance: With budget authority restored to Object 0430, the purchasing agent inputs the purchase order. The system's automated funds check passes, recording an immediate $175,000 encumbrance. This locks the funds, preventing any other department from spending the newly transferred dollars.
4. Three-Way Matching and Final Disbursement: The salt vendor delivers the 2,500 tons to the central county depot. The warehouse supervisor inspects the weigh-scale tickets and inputs an electronic receiving report confirming 2,500 accepted tons. When the vendor's invoice arrives billing for 2,500 tons at the contracted $70 per ton ($175,000), the ERP system executes an automated three-way match. The encumbrance is liquidated, an expenditure and accounts payable liability are recorded, and the treasury issues an electronic payment, fully preserving statutory budgetary control under emergency conditions.