Gotham Government Services logo
Course Catalog
Contact Us

Obligating Year-End Funds: A Practical Guide for Program Offices

By Gotham Government Services

Every program office feels the calendar tighten as the fiscal year closes. That pressure has produced a familiar but wrong piece of advice: spend it before you lose it. That framing is backwards, and acting on it produces exactly the kind of acquisition that draws an Inspector General's attention. The goal at fiscal year end is not to spend remaining balances — it is to obligate funds correctly, against a genuine need, with documentation that holds up under audit. Spending pressure is a known driver of bad acquisitions: rushed requirements, thin justification files, obligations that do not survive review. This guide lays out what the law requires, so your program office can move fast in the fourth quarter without creating exposure.

What an Obligation Actually Requires

An obligation is not a plan to spend money, a purchase request in a queue, or a verbal commitment from a contracting officer. Under 31 U.S.C. § 1501, an amount may be recorded as an obligation only when supported by documentary evidence of a binding agreement — in writing, in a form and for a purpose authorized by law — executed before the appropriation's period of availability ends. For a contract action, that means a signed contract, exercised option, or issued order for specific goods or services. A requisition sitting in a contracting office or a verbal commitment does not satisfy the statute, even if dated September 30.

The Bona Fide Needs Rule

The bona fide needs rule, codified at 31 U.S.C. § 1502(a), is the foundation of year-end obligation decisions. A fixed-period appropriation is available only to meet a genuine need that arises during its period of availability. An agency cannot obligate this year's funds against next year's requirement, and cannot obligate funds merely because a balance is about to expire. GAO's Principles of Federal Appropriations Law (the "Red Book") treats this as a bedrock principle, not a technicality: the test is whether a real, current need exists, not whether unobligated balance remains. A requirement that exists only because money is available is not a bona fide need — it is the exact pattern auditors are trained to find.

Annual, Multi-Year, and No-Year Funds

The type of appropriation you hold determines how much room you have. An annual appropriation is available for obligation only during the fiscal year Congress provided it, and expires at year end. A multi-year appropriation is available over a defined period longer than one fiscal year, as specified in the appropriations act. A no-year appropriation — typically identified by language such as "to remain available until expended" — carries no fixed expiration for obligation purposes. Program offices sometimes conflate these under year-end pressure, treating a no-year balance with the urgency of an expiring annual account. Confirm the appropriation type with your budget office before building a year-end plan; everything that follows depends on it.

Severable vs. Non-Severable Services — and the Authority to Cross Fiscal Years

Whether a service contract is severable or non-severable changes what you can fund and when. A severable service is recurring or measured in level of effort, and the government receives value as it is performed — routine IT help desk support or facilities maintenance, for example. A non-severable (entire) service produces a specific end product, and the government receives value only when that product is complete, such as a final research report or a system delivered whole.

Because a non-severable service is a single, indivisible undertaking, FAR 32.703-3(a) generally prohibits an annually funded contract for that work from crossing fiscal years unless the requirement cannot feasibly be subdivided or specific statutory authority applies. Severable services get a narrow exception. Under 10 U.S.C. § 3133 and 41 U.S.C. § 3902, implemented at FAR 32.703-3(b), the head of an executive agency (other than NASA) may enter a contract, exercise an option, or place an order for severable services for a period that begins in one fiscal year and ends in the next, provided the period does not exceed one year — and may obligate the full amount against the fiscal year in which the action is entered into. This is a different authority from the Federal Acquisition Streamlining Act's multiyear contracting provision at 41 U.S.C. § 3903, which lets an agency obligate current-year funds for the bona fide needs of both severable and non-severable services over as many as five fiscal years, but only where the agency has separately established a multiyear contract under that authority. Confirm with your contracting officer and counsel which authority applies to a specific action — they are not interchangeable.

Realistic Lead Times by Acquisition Path

The most common cause of a failed year-end obligation is starting too late for the acquisition path chosen. Procurement administrative lead time (PALT) — the span between soliciting offers and award — varies widely by dollar value, competition type, and vehicle. GAO's review of DOD contract data found lead times moving in different directions across acquisition tiers over the same period, with the largest, most complex actions taking longer, not less (GAO-24-106528). As a general rule, a task order against an existing GSA Schedule or IDIQ vehicle with a ready statement of work moves fastest; a simplified acquisition takes longer to plan and evaluate; a new full-and-open award takes the longest, especially where a Justification and Approval is required. Your contracting office maintains its own PALT benchmarks by acquisition type — request them early in the fourth quarter, not in September.

What Auditors and Inspectors General Look For

Audit and IG reviews of year-end obligations follow a consistent pattern. They look for a documented bona fide need that predates the obligation, not one written to justify it after the fact. They look for the file required by 31 U.S.C. § 1501 — a signed, dated agreement for specific goods or services, executed within the period of availability. They check whether severable-services funding followed FAR 32.703-3 rather than an assumption that "services always cross years." And they check for Antideficiency Act exposure under 31 U.S.C. §§ 1341 and 1517 — obligations exceeding available appropriations or apportionments, which agencies must report to the President and Congress if confirmed. GAO's own work on year-end spending notes that a surge in obligations is not automatically improper; the determining question is always whether the obligation reflects a genuine, current need, not the calendar.

The Traps

  • Banking funds. Placing money on a contract, grant, or interagency agreement to preserve it, with no genuine near-term requirement behind it, is a bona fide needs violation regardless of the paperwork's polish.
  • Vague requirements. A statement of work drafted to be signed quickly rather than to describe what the government actually needs produces a weak documentation trail and an obligation that will not survive an audit test.
  • Backdating. Dating a document to make it appear executed within the period of availability, when it was not, is not a technical fix — it is a false record and a potential violation with personal and criminal exposure for those who sign it.
  • Obligating without a bona fide need. An obligation made solely because the money is expiring, absent a genuine current requirement, is the single fact pattern GAO and agency IGs are trained to isolate.

Building a Defensible Year-End Plan

Start the fourth quarter by confirming, with your budget office, the appropriation type and its expiration date for obligation. Confirm with your contracting officer, early, which acquisition path fits the timeline you actually have, not the one you wish you had. Write requirements that describe a real, present need, not ones sized to consume a balance. Route anything crossing fiscal years, or relying on multiyear contracting authority, through your contracting officer and counsel before assuming it applies. And keep the documentary record — requirement, justification, signed agreement, all dated to the actual sequence of events — because that record, not the obligation total, is what determines whether the year-end obligation holds up.

This article provides general information about federal fiscal law and is not legal advice. Obligation decisions depend on the specific appropriation, statutory authority, and facts involved. Program offices should consult their servicing contracting officer and agency counsel before acting on any of the guidance above.

Sources