Stop Use-It-or-Lose-It Buying: It's a Fiscal Law Trap

Every September, the same ritual plays out across federal agencies. Program offices suddenly discover urgent needs. Emails fly. Contracting officers work late, racing to get purchase orders and task orders signed before the fiscal year clock runs out. The goal is simple: obligate the money before it expires.

But here's the trap no one talks about. Getting money on contract by September 30 doesn't mean you're safe. It only counts if the obligation was legally proper when you made it. And six months later, when an internal review or IG audit takes a hard look at your September buys, a questionable obligation can unravel fast.

The real problem isn't expiring funds. It's poor-quality obligations that don't survive post-award scrutiny. This article reframes year-end spending pressure as what it actually is: a contracting quality problem disguised as a budget execution problem.

The Hidden Trap in Year-End Obligations

Most people believe that once you get money on contract, the hard part is over. You beat the deadline. The funds are safe. Leadership is happy. You move on.

This belief is dangerous. An obligation only counts if it was legally proper when you made it. That means the purchase had to meet a real need that existed in the fiscal year you charged, and the contract structure had to match the rules for that type of money.

What actually happens after September 30? Your contract doesn't disappear into a filing cabinet. Internal reviews happen. IG audits spot-check obligations. Finance offices reconcile invoices against periods of performance. And if something doesn't line up, the defect surfaces—often months later, often with your signature on it.

There are three failure modes that turn September awards into compliance bombs. First, the bona fide need doesn't actually exist in the fiscal year you obligated. Second, the contract is severable—meaning it could be broken into chunks—but you funded it as if it were one single non-severable thing. Third, the period of performance crosses fiscal years without the right contract line item structure or appropriation to support it.

These aren't obscure technical violations. They're fiscal law trip wires, and they're everywhere in year-end buys.

How Defective Obligations Unravel

Let's follow a flawed year-end buy through its lifecycle. In September, a program office asks you to award a contract for IT support services starting October 1. They hand you current-year operations and maintenance funds. You're busy, they're insistent, and the requirement looks routine. You award it.

In December, a finance reviewer notices the period of performance starts in the new fiscal year. They flag it. Now you have to explain why current-year money is paying for next-year services. If you can't document a bona fide need that existed before September 30—like advance planning, procurement lead time, or an administrative necessity—you have a problem.

Think of it like paying for a gym membership. You can't use your January budget to pay for a February membership unless you can prove you needed to lock in the rate, reserve the spot, or avoid a gap in service. The need has to exist now, even if the benefit comes later.

When a defect gets discovered, consequences cascade. You may be forced to modify the contract, deobligate the funds, and scramble to find new-year money. In severe cases, you risk an Anti-Deficiency Act violation, which is a career-ending federal offense. Even if it doesn't go that far, the rework is costly: vendor confusion, strained relationships, lost time, and leadership scrutiny.

And here's the hardest part. The contracting officer who signed the award now owns the cleanup. That psychological burden—knowing you approved something that's now under investigation—is heavy. It's also avoidable.

The Obligation Quality Mental Model

The solution is not to slow everything down or refuse to obligate funds. It's to reframe year-end as a quality checkpoint, not a speed test. You're not just moving money. You're creating obligations that need to survive scrutiny six months from now.

Here's a three-part diagnostic framework you can apply under pressure.

First: Verify bona fide need. Is the requirement documentable and tied to the current fiscal year? Can you write a clear sentence explaining why this purchase is needed now, even if performance happens later? If the answer is vague or sounds like "we need to spend the money," stop.

Second: Match appropriation to vehicle. Does the contract type and scope align with the appropriation's life and restrictions? Operations and maintenance funds are one-year money. If your contract spans multiple years of severable services, you need to structure it that way—base period plus options, or separate contract line items for each fiscal year.

Third: Structure contract line items correctly. Does the period of performance cleanly map to the appropriation type and fiscal year boundaries? If you're using current-year funds, the work tied to those funds should generally happen in the current year. If it doesn't, you need documentation showing why the need existed in advance.

This model protects both the Government and you. It gives you a rational, defensible framework to evaluate requests under pressure. And it produces obligations that hold up under audit.

Common Year-End Scenarios and Where the Trip Wires Sit

Scenario 1: Buying annual software licenses in September for an October start date.

This is one of the most common year-end purchases, and it's also one of the most misunderstood. Can you use current-year funds to buy a license that starts next fiscal year? Sometimes yes, sometimes no.

The key is bona fide need. If the vendor requires advance purchase, if the license needs time to provision, or if waiting until October would create a gap in service, you can document a current-year need. But if you're only buying it now because the money expires, that's not a bona fide need. It's a convenience, and it won't survive an audit.

Scenario 2: Obligating multi-year training on a single-year appropriation.

Training services are almost always severable. That means each training session is a separate thing. If you fund a year's worth of training with one-year money, and some of that training happens in the next fiscal year, you've created a mismatch.

The fix is to structure your contract line items by fiscal year. Base period covers training in the current year. Option period covers training in the next year, funded with next-year money. This aligns your contract structure with appropriation law and makes the obligation defensible.

Scenario 3: Awarding task orders under indefinite delivery, indefinite quantity contracts without current-year need documentation.

Just because you have an IDIQ in place doesn't mean bona fide need disappears at the task order level. Each task order is a separate obligation, and each one must meet a need that exists in the fiscal year being charged.

Even under time pressure, document why this task order is needed now. A one-paragraph memo in the file explaining the current-year need is enough. Skipping it is not worth the risk.

Scenario 4: Funding operations and maintenance requirements that span fiscal years.

Operations and maintenance appropriations are one-year money. They expire for new obligations at the end of the fiscal year. If you're buying services that cross fiscal years—like facility maintenance from October through March—you need to split the contract appropriately.

Use a base-plus-option structure, or use separate contract line items with different appropriations. Don't try to fund six months of next-year services with current-year money unless you have rock-solid documentation of a current-year need.

Practical Tactics for Defending Year-End Buys

Build your contract file as if an inspector general is going to read it in six months. Because they might.

Key documentation to include: a written justification of current-year need, an appropriation-match memo explaining which funds you're using and why, and a contract line item and period-of-performance alignment rationale. These don't have to be long. A single page is often enough. But they have to exist.

Avoid red flag language in your acquisition planning memos and justifications. Phrases like "use available funds," "spend down the budget," or "avoid losing money" are poison. They signal that you're obligating for budget reasons, not mission reasons. If an auditor sees that, your obligation is indefensible.

When program offices pressure you to move fast, push back with fiscal law grounding. You're not being difficult. You're protecting them and the mission. Explain that a defective obligation is worse than expired funds because it creates rework, audit risk, and potential legal exposure.

Before you sign, ask yourself three questions. Can I defend this need as arising in the current fiscal year? Does the period of performance match the appropriation? Are my contract line items structured to prevent severable service violations? If you can't confidently answer yes to all three, don't sign.

What This Means for Your September Workflow

Shift from reactive scramble to deliberate triage. Not every year-end request deserves the same level of urgency. Some are clearly defensible. Some need documentation work before you can proceed. And some are too risky to touch.

Sort incoming requests into three buckets. Bucket one: clearly defensible buys with documented current-year need, appropriate appropriation, and clean contract structure. Move these fast. Bucket two: requests that could work but need documentation. Assign these to your team for quick file-building. Bucket three: requests that violate bona fide need, mismatch appropriation type, or cross fiscal years without a fix. Decline these or defer them to next-year funds.

Communicate risk clearly to leadership without becoming the bottleneck. Your job is not to say no. It's to explain what makes an obligation defensible and what doesn't. Give leadership the information they need to make informed decisions. If they choose to proceed over your objection, document that conversation.

Use the three-part diagnostic—verify need, match appropriation, structure contract line items—as a go or no-go filter for every year-end action. It's fast enough to apply under pressure and rigorous enough to protect you in an audit.

This approach protects you and the Government simultaneously by building quality into the obligation decision, not retrofitting it months later when a reviewer asks questions you can't answer.

Why This Matters

Year-end pressure is not going away. Leadership will always want to execute the budget. Program offices will always have last-minute needs. The fiscal year will always end on September 30.

But fiscal law risk is avoidable. The cost of a defective obligation—rework, audit exposure, reputational damage, vendor frustration—is always higher than the cost of letting questionable money expire. Always.

Obligation quality protects mission continuity, vendor relationships, and your credibility as a contracting officer. It's not about being cautious. It's about being correct. And in federal acquisition, being correct under pressure is what separates good contracting officers from great ones.

This mental model transforms September from a compliance minefield into a strategic quality gate. It gives you a framework to operate confidently when everyone around you is panicking. And it ensures that the obligations you create in September are still defensible in March.