The Federal Fiscal Year-End IT Buying Playbook: What Actually Ships Before Your Funds Expire

Every August, the same question moves through federal program and IT offices: my funds die September 30 — what can I actually get in time? It is the one buying deadline that is about your calendar, not a compliance rule, and it is unforgiving. This playbook walks the mechanics of the year-end close: what the deadline actually is (it is not the one most people assume), the appropriations law behind it, and the order-readiness moves that decide whether a requirement gets obligated in time or slips into next year's budget fight.

For fiscal year 2026, the wall is September 30, 2026 — the last day of the federal fiscal year, which runs October 1 through September 30.

Most operating money agencies spend on commodity IT is a one-year appropriation: it is available for new obligations only during a single fiscal year. The instant that year closes, the authority to commit that money to a new order is gone. This is why the year-end scramble exists — it is not a policy preference or an internal cutoff, it is the outer edge of the fund's legal life.

Not all money behaves this way. Appropriations come in different "colors," and some carry a multi-year or no-year period of availability that does not slam shut on September 30. If your requirement is funded by one of those, the year-end pressure is different. But the buys that create the August-September rush are almost always one-year funds, and this playbook is written for that case.

When a one-year appropriation reaches the end of its period of availability, the money does not vanish outright — it expires. For the next five years the account stays open in an expired status, where the balance can be used only to make adjustments to obligations that were properly incurred while the fund was still current. No new obligations may be charged against it. After that five-year window, the appropriation is cancelled, and any remaining balance is returned to the general fund of the Treasury — beyond the reach of your program entirely.

The practical takeaway is blunt: a requirement you fail to obligate by September 30 does not "roll over." Its funding starts a one-way trip toward cancellation. If the need survives into next year, you fund it again from next year's money — assuming it is appropriated, and assuming it wins the priority fight all over again.

The single most valuable thing to understand at year-end is that obligation and delivery are two different clocks. The one that must beat September 30 is obligation. Delivery has room to breathe.

Read the table top to bottom and the year-end strategy writes itself: nail down a genuine current-year need, get a clean binding order in place before the deadline, and let delivery land when it lands. The trap is treating the arrival of the hardware as the thing that must beat the clock. It is not — but a purported obligation that is really just a placeholder for a future-year need will not hold up, no matter when it is dated.

Appropriations law recognizes something practical: some things you genuinely need this year cannot physically be delivered before the year ends. A server configured to spec, a batch of endpoints, a networking refresh — these have normal, non-trivial lead times. So the rule lets you obligate current-year funds for an item that will be delivered early in the next fiscal year, provided two things are true. First, the need is genuine and arises in the current year — you need it now, for a this-year purpose, not next year's project you are pre-funding because money is available. Second, the lead time is normal for that item — you are accommodating ordinary production or fulfillment time, not stretching delivery out to disguise a next-year requirement.

Where buyers get into trouble is treating this as a general-purpose loophole — obligating in late September for something the program will not actually need until well into the new year, with delivery pushed out to match. That is not a lead-time accommodation; it is obligating for a future-year need, which the bona fide needs rule prohibits. Keep the file honest: record why the need arises this year and what the item's normal lead time is, and the exception is exactly what it is meant to be.

Use this as a planning cadence, not a set of legal deadlines. The only fixed date here is the September 30 fund-expiration wall; every T-minus window is a working backstop to give award, compliance screening, and fulfillment enough room. Exact order-by cutoffs depend on the item, the fulfillment path, and your contracting shop's workload.

The dollar size of a buy is a switchboard: it determines which procedures apply and how much process stands between you and an award. At year-end, that directly affects speed. Two threshold lines matter most.

Both the MPT and SAT figures above reflect the five-year inflation adjustment (FAC 2025-06) that took effect October 1, 2025, raising the prior $10,000 and $250,000 lines.

Two rules ride these thresholds and are worth stating plainly. Some compliance rules attach only at a dollar level — TAA, for example, applies at or above its acquisition threshold, while below it a different domestic-preference analysis may govern. Threshold-independent screens — banned-maker (§889) and excluded-source (FASCSA) — apply regardless of dollar value, micro-purchases included.

And never split a requirement to duck a threshold: breaking one buy into smaller pieces to stay under the SAT, or to reach for a faster path, is prohibited (FAR 13.003(c)). Size the buy to the real requirement.

Four failure modes account for most funds that lapse unspent. All four are avoidable with the runway this playbook builds in.

Splitting the requirement to dodge a threshold. Carving a $400,000 need into three under-SAT buys to move faster is prohibited under FAR 13.003(c), and it is exactly the kind of thing that surfaces in a year-end review. Structure the buy to the actual requirement and choose the path that fits.

Obligating for a future-year need. An obligation that is really a placeholder for next year's project fails the bona fide needs rule, no matter how it is dated or worded. If the need does not arise this year, this year's money cannot fund it.

Quotes that expire before award. A quote honored on September 5 is no help if it lapses on September 20 and your contracting officer acts on September 28. Lock a validity window that survives to award — and confirm it, in writing, in the final stretch.

A backordered SKU nobody flagged. The requirement everyone assumed was routine turns out to be on allocation with no firm ship date — discovered too late to substitute. This is why availability confirmation moves to the front of the checklist. In-stock, confirmed-for-your-quantity items are the safe bet when the clock is short.

A missed year-end deadline is rarely a paperwork failure — more often it is a sourcing failure discovered too late: a backordered part, an availability that was never confirmed in writing, or a compliance snag that surfaced the week of award. That is the part a stocking sourcing partner exists to solve.

Bring your requirement list and your delivery date. Get back confirmed availability, honest lead time, and a dated quote you can carry to award — with the country-of-origin and banned-maker questions answered up front, so a compliance hold does not become a missed deadline. When the requirement is ready, send it to us as a quote or RFQ.

The screens that most often stall a year-end buy are worth clearing early: banned-maker screening under NDAA §889 — our §889 Covered-Equipment Screening Checklist walks it step by step — plus country-of-origin under the Trade Agreements Act and excluded-source screening under FASCSA on SAM.gov.