The bill bars Executive agencies from obligating more in each month of the two‑month period immediately before a fiscal‑year end than the agency’s average monthly discretionary obligations across the prior ten months. Agencies must also file an itemized list of discretionary obligations made during that two‑month “covered period” within 60 days after the fiscal year ends and post it on a public website.
The measure is aimed at stopping last‑minute spikes in obligational activity that can undermine congressional control of spending and obscure year‑end reprogramming. It creates a new, quantifiable constraint on agency budget execution and a public reporting requirement, while carving out national security and disaster relief activities from the limit.
At a Glance
What It Does
The bill defines a two‑month "covered period" before a fiscal‑year end and prohibits each month of that period from exceeding the agency’s average monthly discretionary obligations during the prior 10 months. It requires agencies to submit and publish an itemized report of covered‑period obligations within 60 days after year end.
Who It Affects
The rule applies to Executive agencies as defined in 5 U.S.C. 105 and only to discretionary appropriations as defined in section 250(c) of the Balanced Budget and Emergency Deficit Control Act of 1985. National security‑related activities and disaster relief obligations are exempt.
Why It Matters
By engineering a statutory cap on end‑of‑year obligations and mandating public disclosure, the bill reduces the ability of agencies to accelerate spending at year end and gives Congress and the public a clearer view of late‑year obligational behavior — potentially changing procurement timing, reprogramming practices, and budget execution operations.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The statutory text creates three basic building blocks: a definition of the covered period (the two months leading up to the fiscal‑year end), a numerical control on obligations during that period, and an after‑the‑fact reporting requirement. Agencies must measure their discretionary obligations for the ten months immediately before the covered period, calculate the average monthly amount for that window, and then ensure that obligations in each month of the covered period do not exceed that average.
The bill speaks to obligations specifically, not outlays. That matters because agencies obligate funds (commit them to contracts, grants, or orders) before the cash is actually spent.
Changing obligations timing is operational: procurement schedules, grant award timing, and interagency transfers will have to be managed to avoid breaching the per‑month cap. The bill’s reporting requirement forces agencies to produce an itemized list of those discretionary obligations and post it publicly within 60 days after the fiscal year ends, giving Congress and outside monitors line‑level visibility into late‑year commitments.The exemption for "national security‑related activities" and "disaster relief efforts" is broad and will be central to implementation.
The statute does not define those phrases further, nor does it assign an enforcement or adjudicative role to OMB or another agency—so practical effect will depend on follow‑on guidance and congressional oversight. The bill also references statutory definitions for "discretionary appropriations" and "Executive agency," tying scope to preexisting budget law vocabulary rather than creating new categories.Because the text imposes a numerical ceiling but does not attach statutory penalties or an enforcement mechanism beyond the reporting requirement, compliance will rely on internal agency controls, OMB guidance, and Congress’s oversight tools.
Expect agencies to update internal obligation tracking, shift procurement calendars earlier in the fiscal year, or use available exceptions and accounting methods to remain within the cap while continuing mission delivery.
The Five Things You Need to Know
Covered period: the bill defines the covered period as the two months immediately preceding the end of a fiscal year.
Monthly cap: for each month in the covered period, an agency may not obligate more than the average monthly amount of discretionary obligations during the 10 months before the covered period.
Scope: the limit applies only to discretionary appropriations as defined in 2 U.S.C. 900(c) (Balanced Budget and Emergency Deficit Control Act) and to Executive agencies per 5 U.S.C. 105.
Reporting: each Executive agency must submit to Congress and post publicly an itemized list of discretionary appropriations obligated during the covered period not later than 60 days after the fiscal year ends.
Exceptions: obligations for national security‑related activities and disaster relief efforts are explicitly exempt from the cap.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Names the statute the "End‑of‑Year Fiscal Responsibility Act." This is a formal device but signals congressional intent to regulate year‑end obligational behavior rather than to alter substantive program authorities.
Key definitions that set scope
Defines three operative terms: 'covered period' (two months before fiscal‑year end), 'discretionary appropriations' by cross‑reference to section 250(c) of the Balanced Budget Act, and 'Executive agency' by reference to 5 U.S.C. 105. Because the bill uses existing statutory definitions, the practical boundary between covered and uncovered obligations will follow prior budget law practice—chiefly, the discretionary/mandatory distinction—rather than novel categories created by the bill.
Obligation limit during the covered period
Imposes the core operational rule: each month of the covered period cannot exceed the agency’s average monthly discretionary obligations from the preceding 10 months. That arithmetic cap is applied at the monthly level (not as a combined two‑month total), which prevents agencies from concentrating obligations into one of the two months. The provision ties compliance to obligations (commitments) rather than outlays (payments), which affects procurement timing and grant award scheduling.
Congressional and public reporting requirement
Requires agencies to submit an itemized list of discretionary obligations made during the covered period to Congress and to publish that list on a public website within 60 days after the fiscal year ends. The requirement creates line‑item transparency for late‑year obligational activity, but the statute does not prescribe the format, level of detail, or consequences for inaccurate reporting—leaving those operational details to agency practice and oversight.
Exemptions for national security and disaster relief
Exempts obligations for 'national security‑related activities' and 'disaster relief efforts' from the cap. The carve‑outs are broad in wording; the law does not define the terms or set a certification process, so agencies and OMB will likely need to develop guidance about what qualifies for the exemption and how to document it for congressional review.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Congressional appropriations and oversight committees — receive a statutory control and public reporting that make it easier to spot and question late‑year obligational spikes and to hold agencies accountable for year‑end maneuvers.
- Taxpayer watchdogs and transparency advocates — gain access to itemized, line‑level data on late‑year obligations through public postings, improving external monitoring of agency execution.
- Agency program managers who prefer stable monthly funding — benefit from reduced volatility if the cap prevents sudden, large last‑minute obligations that can displace planned work.
- Budget analysts at CBO/GAO and OMB staff — obtain more consistent obligational patterns to forecast year‑end behavior and to integrate into budgetary analyses, assuming the reports are timely and granular.
Who Bears the Cost
- Agency budget, procurement, and grants offices — will bear compliance costs: tracking obligations against a 10‑month average, adjusting procurement timelines, preparing the required itemized reports, and potentially defending exemption claims.
- Vendors and contractors that rely on year‑end award windows — may see reduced opportunities for late fiscal‑year contracts if agencies smooth obligations earlier in the year.
- OMB and central agency staff — likely face an unfunded implementation task of issuing guidance, monitoring compliance, and adjudicating disputes over exemptions or calculation methods.
- Programs that historically used year‑end obligational flexibility to absorb unplanned demands — may experience operational friction even if some relief exists through the disaster and national security exceptions.
Key Issues
The Core Tension
The central dilemma is between curbing rushed, opaque year‑end obligational spikes to restore deliberate congressional control and preserving agencies’ operational flexibility to meet legitimate end‑of‑year needs (including true emergencies). The statute favors predictability and transparency but delegates crucial definitional and enforcement choices to agencies and OMB, creating a trade‑off between a clean numerical rule and the risk of administrative burden, narrow exemptions, and accounting workarounds.
The statute establishes a clear numerical ceiling but leaves multiple operational questions unresolved. It does not define how to treat multi‑year or no‑year appropriations, whether obligations recorded late on the final day count toward a single month or can be dated differently, or how to handle intra‑agency transfers and intra‑governmental orders.
Because it targets obligations, agencies may respond by shifting the timing of commitments earlier in the fiscal year or by accelerating contracting before the covered period, which could simply move rather than reduce year‑end spending behavior.
Enforcement is indirect. The bill mandates reporting and public disclosure but contains no fines, rescissions, or express administrative sanctions for noncompliance.
That design makes the role of OMB guidance and congressional oversight pivotal: without robust guidance and audit‑level review, agencies could exploit the narrow exemptions ("national security‑related" and "disaster relief") or rely on accounting techniques to stay within the letter of the cap while preserving late‑year activity. The balance between clearer congressional control and the potential for workarounds will shape the bill’s real‑world effects more than the statutory cap itself.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.