Fund accounting, encumbrances, and budgetary control in a government ERP

Reference article · 6 min read

Commercial accounting packages are built around a single reporting entity that measures profit. Governmental accounting is built around a set of separate fiscal and accounting entities called funds, each with its own self-balancing set of accounts, and around a legally adopted budget that constrains what may be spent and on what. Software that handles the first case well can still fail the second, and the failure rarely shows up in a demo. It shows up in the first close, in the audit, or when the finance director tries to produce a budgetary comparison schedule and finds the system cannot reconcile the budgetary basis to the basis used in the financial statements.

This page describes the accounting behavior a state or local government should confirm before buying or accepting a financial system, whether the product is marketed as a government ERP or is a commercial package being pushed onto the finance office by IT, a parent organization, or a hosting decision. Commercial products are not automatically wrong. The requirements are simply specific, they come from state law, local ordinance, and standards issued by the Governmental Accounting Standards Board rather than from preference, and a buyer should test them directly instead of inferring them from a feature list.

Funds are the accounting entity

A fund is not a department, a project code, or a segment of the chart of accounts. It is a separate fiscal entity with its own trial balance, and the system has to treat it that way.

• Self-balancing by fund. Every posting must keep each fund in balance on its own, with automatic offsets generated when a single transaction touches two funds.
• Mixed measurement focus. Governmental funds are reported on the current financial resources measurement focus and the modified accrual basis. Proprietary and fiduciary funds, and the government-wide statements, use the economic resources focus and full accrual. A system should either maintain both views or support a controlled, repeatable conversion with a documented audit trail.
• Fund types and major fund analysis. General, special revenue, capital projects, debt service, and permanent funds, plus enterprise, internal service, and fiduciary funds, each need correct classification, and the system should help identify major funds rather than requiring a spreadsheet.
• Interfund activity. Due to and due from accounts for short-term balances, advances for long-term ones, transfers, and reimbursements all behave differently in reporting. Ask how each is recorded, how both sides post together, and how they are eliminated for government-wide presentation.

Budgetary control at the level the governing body adopted

The legal level of budgetary control varies. Some bodies appropriate by fund, some by department, some by program, some by object or line item. Control has to be configurable independent of how detailed the chart of accounts is, and it must be enforceable at the point of commitment, not discovered at month end.

• Choose the control behavior per level: hard stop, warning with override and logging, or record and report only.
• Budget amendments and transfers need workflow, effective dating, and a permanent record of who approved what, because those records support the budgetary schedules and the audit.
• Capital projects and grants usually need project-length or multi-year budgets running alongside the annual operating budget, with balances that persist across fiscal years.
• The budgetary basis often differs from the basis used in the audited statements. The system should produce the reconciliation, not leave it as a manual schedule.

Encumbrance accounting through the purchasing cycle

Encumbrance accounting is the mechanism that keeps commitments from consuming appropriations twice. A requisition creates a pre-encumbrance, a purchase order converts it to an encumbrance, and an invoice liquidates the encumbrance and records the expenditure.

• Available balance should be reported as appropriation less expenditures, less encumbrances, less pre-encumbrances, visible to the requester before submission.
• Partial receipts, quantity and price variances, change orders, and cancellations each need defined liquidation behavior.
• Year-end handling matters most. Confirm whether open encumbrances lapse, carry forward against the prior appropriation, or are reappropriated in the new year, and confirm the system can do whichever your policy and state law require.
• Encumbrances are not expenditures under generally accepted accounting principles. They are budgetary charges, and under current fund balance guidance they are disclosed within the appropriate classification rather than reported as a separate one.

Fund balance, net position, and restrictions

Governmental funds report fund balance in classifications commonly described as nonspendable, restricted, committed, assigned, and unassigned, with commitments requiring formal action by the government's highest level of decision-making authority. Proprietary funds report net position in categories including net investment in capital assets, restricted, and unrestricted. A system should let you tag balances to these classifications, apply a spending order consistent with your adopted policy, and show restricted resources by the source that restricted them. Grant and bond proceeds especially need restriction tracking that survives across fiscal years.

What to ask and what to put in the contract

Run a scripted demonstration using your own chart of accounts and your own scenarios rather than the vendor's sample data.

1. Post a transaction that splits across two funds and show both sides, then show the elimination.
2. Attempt a purchase requisition that exceeds the appropriation at your legal control level, then process a budget amendment and retry.
3. Take a purchase order through partial receipt, price variance, and year-end rollover.
4. Produce a budgetary comparison schedule and the reconciliation to the GAAP basis.
5. Produce a grant expenditure report with period of performance, match, and indirect cost, and show how it feeds a schedule of expenditures of federal awards.

In the contract, require acceptance criteria tied to those scenarios, a defined conversion of the chart of accounts and opening balances, vendor cooperation with your external auditors at no separate charge, retention of audit trails for your record retention period, and a data extraction right that returns your full ledger detail in a documented, non-proprietary format on termination. Standards and federal award requirements change over time, so confirm current specifics with the official source or your auditor rather than relying on a vendor summary.

HQT builds and integrates enterprise software for state and local government agencies, including financial and administrative systems.

Frequently asked questions