A pre-encumbrance in government accounting is an internal reservation of budget funds recorded when a purchase requisition is approved, reducing the available balance in an appropriation before any vendor has been selected or contract signed. It sits at the earliest stage of the spending cycle and carries no legal obligation. Its job is to keep two departments from spending the same dollar and, in federal agencies, to catch a potential overrun before it hardens into a commitment the government cannot legally back out of.
The Three Phases of Government Spending
Government spending moves through three phases, each representing a deeper level of commitment. A pre-encumbrance is the first.
- Pre-encumbrance. A department submits a purchase requisition signaling intent to buy. No vendor has been chosen, no contract exists, no legal obligation has been created. The estimated cost is subtracted from the available budget balance to prevent other spending from claiming those funds.
- Encumbrance. The organization issues a formal purchase order or signs a contract with a vendor. A legal obligation now exists, the reserved amount shifts from planned to committed, and the pre-encumbrance is reversed and replaced with an encumbrance at the actual agreed price.
- Expenditure. The vendor delivers, the invoice is processed, the encumbrance is liquidated, and the payment is recorded against the appropriation.
The distinction that matters most is legal weight. A pre-encumbrance is a purely internal budgetary control. An encumbrance reflects a binding agreement. That difference drives how each phase is treated at year-end, in audits, and in financial reporting.
How a Pre-encumbrance Gets Created
The trigger is a purchase requisition, usually entered through a procurement system or enterprise resource planning platform. What the requester types in determines whether the reservation hits the right budget line and holds the correct amount.
The requisition needs an estimated cost based on catalog pricing, recent vendor quotes, or historical data for similar items. This figure becomes the pre-encumbrance amount, so overestimating ties up funds unnecessarily and underestimating defeats the purpose of the reservation. It needs account coding — the correct general ledger account, fund code, and departmental cost center — because those codes decide which budget line absorbs the reservation. And it needs a description of what is being purchased and why, both for approvers and for the audit trail.
A supervisor then approves the requisition, confirming that the planned purchase is consistent with departmental priorities, falls within budgetary authority, and complies with procurement policy. Many organizations route requisitions above certain dollar thresholds through additional levels of approval. Once the last required signature is captured, the accounting system generates the pre-encumbrance entry automatically.
The Journal Entry
When the approved requisition posts, the system records a paired budgetary entry: a debit to a pre-encumbrance control account and a credit to a reserve-for-pre-encumbrances account. The general ledger stays balanced, and the estimated amount is flagged as no longer available for other spending. Modern ERP systems handle this without manual keying.
The effect on reports is immediate. Financial reports will show three categories against the appropriation: actual expenditures already processed, encumbrances from existing purchase orders, and pre-encumbrances from approved requisitions still awaiting a purchase order. The truly available balance is the appropriation minus all three. Administrators who look only at expenditures and encumbrances are working from a number that overstates what they can actually spend.
One operational detail matters here: a pre-encumbrance does not shrink automatically as invoices are processed. It stays on the books at its original estimated amount until someone converts it, reverses it, or a scheduled reversal date fires. Stale pre-encumbrances that no one cleans up make available balances look artificially low.
Converting a Pre-encumbrance to an Encumbrance
The pre-encumbrance phase ends when the organization issues a purchase order. The system does two things at once: it reverses the original pre-encumbrance entry, and it records a new encumbrance at the purchase order’s actual price. The reversal credits the pre-encumbrance control account and debits the reserve-for-pre-encumbrances account. The new encumbrance debits the encumbrance control account and credits the reserve-for-encumbrances account at the purchase order price.
That price often differs from the estimate on the requisition. When the actual price is lower, the difference flows back into the unencumbered balance. When it is higher, the system checks that sufficient funds remain in the appropriation before the purchase order can post. That budget check is where the encumbrance system earns its keep, catching overruns at the commitment stage rather than after the invoice arrives.
Not every requisition converts cleanly. A single requisition might source items to multiple vendors, with only part going onto a given purchase order. In systems with commitment control features, the platform decreases the pre-encumbrance and increases the encumbrance by only the purchase order amount when budget checking runs.1Oracle Help Center. Using Partial and Final Liquidation The remaining pre-encumbrance stays on the books until another purchase order absorbs it or someone cancels the balance.
If a project shrinks and the requisition will be finalized for less than originally planned, the standard practice is to reduce the quantity or price on the purchase order, finalize the document, and re-run budget checking to release the excess reservation.1Oracle Help Center. Using Partial and Final Liquidation Leaving the unreduced balance sitting as a pre-encumbrance indefinitely artificially constrains available funds.
Canceling a Pre-encumbrance
Some planned purchases never happen. The vendor cannot deliver, the project gets shelved, priorities shift. In each case the pre-encumbrance needs to come off the books so the funds return to the available balance.
There are two common approaches. The first is manual disencumbrance: a new entry references the original pre-encumbrance document number and reverses the accounting lines, keeping the audit trail intact. The second is an automatic reversal driven by a date set when the pre-encumbrance was created. If the requester entered a future reversal date, the system zeros out the reservation on that date without further action.
Reversal dates need to be chosen carefully. Too early, and funds are released before the procurement decision is truly dead. Too far out, and budget capacity sits tied up for no reason. A pre-encumbrance without any reversal date stays on the books until someone manually removes it. Monthly reviews of outstanding pre-encumbrances prevent stale reservations from accumulating.
Fiscal Year-End Treatment
Outstanding pre-encumbrances at year-end are usually treated differently from encumbrances. Because a pre-encumbrance represents only internal intent, many governments and institutions let them lapse when the fiscal year closes. The reasoning is that if the department did not formalize the purchase during the year, the reservation should not automatically carry forward and consume the next year’s appropriation.
Grant-funded and multi-year accounts often work differently. Since the underlying funding does not expire at fiscal year-end, pre-encumbrances on those accounts typically carry forward. For annual operating accounts, a department that still intends to make the purchase must create a new requisition in the new fiscal year, which generates a fresh pre-encumbrance against the new budget.
The practical risk is forgetting to re-establish a needed reservation. If a department lets one lapse and does not re-enter it promptly, other spending can consume the funds before the purchase order gets issued. Finance offices that handle this well send reminders before year-end asking departments to review outstanding pre-encumbrances and flag any that need to be re-created.
Why Federal Agencies Rely on Pre-encumbrances
For federal agencies, pre-encumbrance tracking is a frontline defense against violating the Anti-Deficiency Act. Under 31 U.S.C. § 1341, no federal officer or employee may make or authorize an expenditure or obligation that exceeds the amount available in an appropriation, or commit the government to a contract before an appropriation is made.2Office of the Law Revision Counsel. 31 USC 1341 – Limitations on Expending and Obligating Amounts By reserving funds at the requisition stage, the pre-encumbrance flags a potential overrun while the purchase can still be canceled, before a legal obligation is created.
The consequences are serious. An employee who knowingly and willfully exceeds available appropriations faces a fine of up to $5,000, imprisonment of up to two years, or both.3Office of the Law Revision Counsel. 31 USC 1350 – Criminal Penalties Agency heads must immediately report any violation to the President and Congress, with a copy to the Comptroller General.4Office of the Law Revision Counsel. 31 USC 1517 – Prohibited Obligations and Expenditures Administrative penalties can include suspension without pay, removal from the position, or an unsatisfactory performance rating placed in the employee’s permanent record.
OMB Circular A-11 requires every agency to maintain a funds control system that restricts both obligations and expenditures to the lower of the OMB apportionment or the available appropriation. The circular calls for commitment and obligation tracking that “can be monitored in real time with comparisons to the apportionment, allotment and suballotment, on a fiscal year and quarterly basis.”5The White House. OMB Circular No. A-11 – Preparation, Submission, and Execution of the Budget Pre-encumbrances are the mechanism that makes real-time tracking possible at the earliest stage of spending.
Where Pre-encumbrances Appear in Financial Reports
Pre-encumbrances live in the budgetary accounting world, not the financial statement world. They do not appear on GAAP-basis financial statements. Under GASB guidance, encumbrances for supplies and equipment ordered but not yet received are reported in the year the order is placed for budgetary purposes, but in the year the supplies are received for GAAP reporting.6Governmental Accounting Standards Board. Budgetary Comparison Schedules Pre-encumbrances, an even earlier stage than an encumbrance, fall further outside GAAP recognition.
Where they do show up is in internal budgetary reports and, indirectly, in the budgetary comparison schedules that governments present as required supplementary information in their annual financial reports. Those schedules compare original budget, final amended budget, and actual results on a budgetary basis, and when the government’s budgetary practices differ from GAAP a reconciliation must accompany the schedules.7GASB Codification. 2400 – Budgetary Reporting For fund balance reporting, GASB Statement 54 classifies encumbered amounts as committed or assigned fund balance depending on the process used to encumber the funds, rather than reporting them on a separate line.8Governmental Accounting Standards Board. Statement No. 54 – Fund Balance Reporting and Governmental Fund Type Definitions Pre-encumbrances, lacking any formal commitment, generally do not warrant even assigned classification. They are internal administrative tools, not reportable financial positions.