Stop Saving Expiring Funds: It's Causing Your Next-Year ADA Risk

Every September, a quiet ritual unfolds across federal agencies. Program managers race to obligate expiring funds before the fiscal year clock runs out. The instinct is understandable: returning money looks like poor stewardship, and losing budget authority this year often means smaller allocations next year. So teams default to what feels safe: obligating dollars on low-risk buys, existing contracts, or task orders that seem easy to execute.

But here is the problem. That defensive move does not eliminate risk. It transfers it. And when the calendar flips to October, those September obligations often become fiscal time bombs. What looked prudent in the final weeks of the fiscal year can quietly mutate into Anti-Deficiency Act exposure by the following spring.

This is not about criticizing end-of-year execution. It is about understanding a specific, widespread behavior pattern that turns obligation speed into obligation liability. When teams prioritize getting money out the door over ensuring the obligation reflects genuine need and realistic execution windows, they set up a dangerous collision between budget metrics and fiscal law.

This article walks through that collision. It explains why the September reflex creates next-year problems, how those problems trigger fiscal law violations, and what program managers can do to break the cycle.

The September Reflex – Why Teams Default to Defensive Obligations

Federal acquisition professionals are conditioned to see unobligated funds as a problem. Execution rates are tracked, reported, and scrutinized. Leaders ask pointed questions when dollars sit idle. The implicit message is clear: obligate or explain why you did not.

This creates institutional pressure that peaks in September. Program managers face a choice between returning funds or finding something to buy. Returning money is not just embarrassing. It can erode future budget credibility and shrink next year's allocation.

So teams default to what feels defensible. They obligate on low-complexity actions. They add task orders to existing IDIQ vehicles. They extend service contracts or stockpile supplies. These moves check the obligation box without demanding heavy procurement lift or lengthy approval chains.

Underneath this behavior is an unspoken agreement: park the money now, work out the details later. The obligation becomes a placeholder. The assumption is that future modifications, descopes, or realignments will clean up any mismatch between the original action and actual need.

This reflex is widespread, but it is rarely discussed openly in training or guidance documents. Everyone knows it happens. Few people name it. And because it is not named, the fiscal law risks embedded in the behavior remain invisible until they surface as violations.

The Hidden Mechanics of Risk Transfer

Obligating expiring funds feels like closing a loop. The budget execution dashboard turns green. Leadership stops asking questions. The fiscal year ends cleanly. But obligation is not the same as fiscal soundness.

When a program manager obligates money in September without tight alignment to actual need timing or realistic execution capacity, the risk does not disappear. It shifts forward. The next program manager, or the same manager in a different budget cycle, inherits an obligation with unclear justification and mismatched timelines.

The fiscal year boundary is not just an administrative marker. It is a legal tripwire. Fiscal law treats each year's appropriation as distinct. Money appropriated for one fiscal year cannot be used to satisfy needs that arose in a different year unless specific statutory authority exists.

During September's high-pressure window, obligation speed substitutes for obligation discipline. Teams focus on getting contracts signed, purchase orders issued, or task orders awarded before the clock runs out. The question of whether the obligation reflects a bona fide need at the time it was made gets less attention.

By the time the following year's Q1 or Q2 rolls around, institutional memory fades. The original rationale for the obligation is buried in email threads or absent altogether. When execution problems surface, the team must reverse-engineer a justification that may not hold up under scrutiny.

The Fiscal Law Collision – Where Bona Fide Need, Severability, and Modifications Meet

Three fiscal law principles govern how federal dollars can be obligated and spent. Separately, they are straightforward. Together, during post-obligation cleanup, they collide.

The bona fide need rule states that an appropriation can only be used for needs that arise during the period of availability for that appropriation. For one-year money, the need must arise during that fiscal year. This is not about when you sign the contract. It is about when the government's need for the good or service actually emerged.

Severability rules distinguish between supplies and services that are naturally divisible over time and those that are not. A monthly grounds maintenance contract is severable: each month is a distinct need. A single training event is not severable: the whole service must be delivered as one unit. This distinction determines which fiscal year's funds can be used.

Modification authority limits define when and how contracts can be changed. If a modification adds scope, accelerates delivery, or extends performance, the government must use appropriations that are valid for the new requirement. Current-year funds cannot always fix prior-year obligations, especially if the original obligation did not reflect a legitimate need or if the modification creates a new bona fide need.

These three principles are usually taught in isolation. But they interact during the exact moment when September obligations start to unravel. A severable service obligated in September with an artificially long period of performance hits a wall when the program office tries to descope it in March using current-year funds. A supplies purchase with vague delivery terms becomes a bona fide need problem when items arrive in the wrong fiscal year. A task order modification that realigns scope can trigger a Purpose Statute violation if the change reflects a need that did not exist when the original obligation was made.

Violations do not announce themselves. They surface quietly during budget reviews, audits, or legal consultations. By then, the damage is done.

Anatomy of Common September Obligation Traps

Trap 1: The Severable Service with an Artificially Extended Period of Performance

Picture this. A program manager has leftover funds in September and obligates a twelve-month support service contract using expiring fiscal year dollars. The contract period of performance runs from October through September of the following year. On paper, it looks clean.

But the program office only needs six months of support. The extended period of performance was not based on mission requirements. It was based on the need to obligate the full amount before the fiscal year expired.

Six months in, the program shifts priorities. The service is no longer needed, or funding constraints require descoping. The contracting officer must modify the contract to reduce scope and deobligate funds. But which year's funds are being deobligated? And which year's funds can be used to pay for any close-out costs or early termination expenses?

If the modification uses current-year funds to address a prior-year obligation that was never tied to a legitimate twelve-month need, the agency may have a bona fide need problem and a potential Anti-Deficiency Act violation. The obligation was not fiscally sound when it was made, and the modification exposes that fact.

Trap 2: The Supplies Buy with No Delivery Discipline

Supplies are generally governed by the bona fide need rule based on when the government will accept delivery. If you obligate fiscal year 2024 funds for office supplies, those supplies should be delivered and accepted during fiscal year 2024.

But September obligations often involve supply purchases with vague or unrealistic delivery dates. The goal is to get the purchase order issued, not to manage the delivery timeline tightly. Vendors are told to deliver "as soon as possible" or given delivery windows that stretch across fiscal years.

When supplies arrive in November or December, well into the next fiscal year, the question arises: did the bona fide need exist in the prior fiscal year, or does it exist now? If the purchase was speculative or made to park funds rather than satisfy an immediate, documented need, the obligation may not have been valid.

Even if the obligation was initially valid, accepting delivery in the wrong fiscal year can create administrative headaches and audit exposure. If the acceptance happens after the appropriation has expired, additional scrutiny follows. The lack of delivery discipline in September turns into a fiscal law puzzle months later.

Trap 3: The IDIQ Task Order Issued to Preserve Ceiling

IDIQ contracts are popular end-of-year vehicles. They are already competed and in place. Issuing a task order feels lower-risk than starting a new procurement. Program managers use them to obligate quickly.

But not all task orders reflect genuine program office need. Some are issued to keep the IDIQ vehicle active, preserve contract ceiling, or maintain vendor relationships. The task order obligates funds, but the program office lacks the capacity, resources, or timeline to execute the work as written.

When the following fiscal year begins, the mismatch becomes obvious. The task order sits unexecuted or underexecuted. The program office needs to descope, cancel, or reallocate funds. But deobligating a task order is not always clean, especially if the original award was not tied to a well-documented, time-sensitive requirement.

If the task order modification or cancellation requires current-year funding decisions or reallocates prior-year obligations in ways that do not align with the original need, the action can trigger fiscal law violations. What looked like a safe obligation in September becomes a liability in the spring.

The Funding-Sound Obligation Test – A Two-Part Framework

Before obligating expiring funds in September, program managers should apply a simple two-part test. This is not about perfect documentation or exhaustive legal review. It is about ensuring the obligation reflects execution reality, not just budget pressure.

Part 1: Does this obligation reflect actual need timing?

Ask when the government's need for this requirement actually arose or will arise. If the need is emerging in the current fiscal year and will be satisfied during the period of performance, the obligation is likely sound. If the need is speculative, future-oriented, or disconnected from current mission requirements, the obligation carries fiscal law risk.

Think of it like booking a hotel room. If you book a room for a work trip that is confirmed and scheduled, the reservation reflects actual need. If you book a room just because you might travel someday, the reservation is speculative. Fiscal law treats speculative obligations as violations of the bona fide need rule.

Document the need timing in simple terms. When did the requirement emerge? What mission or operational need does it satisfy? Why does it need to be obligated now? This does not require a legal memo. It requires a clear, honest answer that will hold up if questioned later.

Part 2: Can this requirement realistically be executed as written within fiscal law constraints?

Ask whether the contract period of performance, delivery timeline, and scope align with the program office's actual capacity to manage and execute the work. If the answer is no, the obligation is a placeholder, not a sound action.

Evaluate vendor capability and delivery timelines. If the vendor cannot deliver within the specified period, or if delivery dates are vague, the obligation is structurally unsound. Evaluate program office readiness. If the team cannot accept, manage, or consume what is being bought within the contracted timeline, the obligation will likely require modifications that carry fiscal law risk.

Consider whether future-year funds will be available if the requirement continues or needs adjustment. If modification or continuation is likely and future funding is uncertain, the obligation shifts risk instead of managing it.

Practical Application – How to Use This Framework in Real Time

The two-part test is most useful when applied in the moment, not in hindsight. Here is how to use it during the September pressure window.

Before signing any obligation action, ask yourself: can I explain the need timing and execution realism to an auditor in two sentences? If the explanation requires caveats, assumptions, or future events that have not happened yet, pause.

Document the funding-sound obligation test in the contract file or procurement package. This does not need to be formal. A short memo or email that answers both parts of the test provides audit defense and institutional memory. If the obligation is later questioned, the documentation shows that the decision was deliberate, not reactive.

When leadership or resource managers pressure you to obligate funds that do not meet the test, use clear language. Say: "This obligation does not reflect actual need timing, and it is likely to require modifications next year that could create fiscal law exposure." Reframe the conversation from budget execution metrics to fiscal law risk.

If you inherit an obligation that seems misaligned, diagnose it using the same two-part test. Does the original obligation reflect genuine need timing? Can it be executed as written? If the answer to either question is no, involve your legal counsel, finance office, or comptroller early. Do not wait until modification pressure forces a decision.

Early involvement is not about slowing things down. It is about identifying fiscal law landmines before they detonate. Lawyers and comptrollers can help structure modifications, deobligations, or reallocations in ways that minimize ADA risk. But they need to be brought in before the action is signed, not after.

Why This Matters – Reframing Risk in the Budget Execution Window

Program managers are taught to see the risk as losing budget authority. That is a real concern. But it is not the greatest risk.

The greater risk is incurring Anti-Deficiency Act liability and triggering operational disruption. ADA violations are serious. They require reporting to Congress, investigations, and potential personnel consequences. Even when violations are unintentional, they damage credibility and consume organizational resources.

Post-obligation rework is expensive. It takes time, attention, and coordination across contracting, legal, and finance functions. It delays mission execution. It creates friction with vendors. And it erodes trust, both within the acquisition team and with program leadership.

Obligation soundness is a leading indicator of execution success. When obligations are tied to real needs and realistic timelines, execution tends to be smoother. When obligations are defensive placeholders, execution tends to stall, require rework, or fail.

Reframing risk empowers program managers to make defensible decisions under pressure. It gives them the language to explain why certain September actions should not be taken. It protects both the individual and the organization from inheriting future problems that could have been avoided with a two-question test.

The September reflex is powerful. But it is not inevitable. Program managers who understand the fiscal law collision, apply the funding-sound obligation test, and reframe risk from budget loss to ADA exposure can break the cycle. They can obligate with confidence, execute with clarity, and avoid the next-year traps that turn defensive obligations into fiscal liabilities.