Budget sequestration

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Budget sequestration is a procedure in United States law that limits the size of the federal budget. Sequestration involves setting a hard cap on the amount of government spending within broadly defined categories; if Congress enacts annual appropriations legislation that exceeds these caps, an across-the-board spending cut is automatically imposed on these categories, affecting all departments and programs by an equal percentage. The amount exceeding the budget limit is held back by the Treasury and not transferred to the agencies specified in the appropriation bills.[1] The word sequestration was derived from a legal term referring to the seizing of property by an agent of the court, to prevent destruction or harm, while any dispute over said property is resolved in court.

The term "budget sequestration" was first used to describe a section of Gramm-Rudman-Hollings Deficit Reduction Act of 1985 (GRHDRA). The hard caps were abandoned and replaced with a PAYGO system by the Budget Enforcement Act of 1990, which was in effect until 2002. Sequestration was later included as part of the Budget Control Act of 2011, which resolved the debt-ceiling crisis; the bill set up a Congressional debt-reduction committee and included the sequestration as a disincentive to be activated only if Congress did not pass deficit reduction legislation. However, the committee did not come to agreement on any plan, activating the sequestration plan. The sequestration was to come into force on January 1, 2013 and was considered part of the fiscal cliff, but the American Taxpayer Relief Act of 2012 delayed it until March 1 of that year.

Gramm–Rudman–Hollings Act

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Budget sequestration was first authorized by the Balanced Budget and Emergency Deficit Control Act of 1985 (BBEDCA, Title II of Pub. L. 99-177). This is known as the Gramm–Rudman–Hollings Act.[2] They provided for automatic spending cuts (called "sequesters") if the deficit exceeded a set of fixed deficit targets. The process for determining the amount of the automatic cuts was found unconstitutional in the case of Bowsher v. Synar, 478 U.S. 714 (1986) and Congress enacted a reworked version of the law in 1987.[3] Gramm-Rudman failed, however, to prevent large budget deficits. The Budget Enforcement Act of 1990 supplanted the fixed deficit targets.

PAYGO era

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

From 1990 until 2002, and again since 2010, Congress has operated under a system called PAYGO, under which any new government spending needs to be offset by savings from (or cuts to) current programs.

In the initial PAYGO regimen, enacted in the Omnibus Budget Reconciliation Act of 1990 (OBRA '90), by statutory requirement, if legislation enacted during a session of Congress had the effect of increasing the projected deficit for the following year, a sequestration would be triggered. These rules were in effect from FY1991-FY2002.[4] Enacted in 1990, it was extended in the Omnibus Budget Reconciliation Act of 1993 and the Balanced Budget Act of 1997.

Beginning in 1998, in response to the first federal budget surplus since 1969, Congress started enacting, and the President signing, increases in discretionary spending above the statutory limit using creative means such as advance appropriations, delays in making obligations and payments, emergency designations, and specific directives.[5] While staying within the technical definition of the law, this allowed spending that otherwise would not be allowed. The result was emergency spending of $34 billion in 1999 and $44 billion in 2000.

The PAYGO statute expired at the end of 2002. After this, Congress enacted President George W. Bush's proposed 2003 tax cuts (enacted as the Jobs and Growth Tax Relief Reconciliation Act of 2003), and the Medicare Prescription Drug, Improvement, and Modernization Act.[6] The White House acknowledged that the new Medicare prescription drug benefit plan would not meet the PAYGO requirements.[7] The PAYGO system was reestablished as a standing rule of the House of Representatives (which does not have the force of law) on January 4, 2007 by the Democratic-controlled 110th Congress,[8][9][10] but less than one year later, facing widespread demand to ease looming tax burdens caused by the Alternative Minimum Tax, Congress abandoned its pay-go pledge.[11] The point of order was also waived for the Economic Stimulus Act of 2008 passed during the Bush administration, which included revenue reducing provisions and increases in spending that increased the deficit. At the beginning of the 111th Congress, PAYGO was modified by including an "emergency" exemption, which was provided for the American Recovery and Reinvestment Act of 2009 during the Obama administration.[12]

In 2010 President Obama signed the Statutory Pay-As-You-Go Act into law, making PAYGO again mandatory.[13]

Budget Control Act era

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

In 2011, sequestration was used in the Budget Control Act of 2011 (Pub. L. 112-25) as a tool in federal budget control.[2] This 2011 act authorized an increase in the debt ceiling in exchange for $2.4 trillion in deficit reduction over the following ten years. This total included $1.2 trillion in spending cuts identified specifically in the legislation, with an additional $1.2 trillion in cuts that were to be determined by a bipartisan group of Senators and Representatives known as the "Super Committee" or officially as the United States Congress Joint Select Committee on Deficit Reduction. The Super Committee failed to reach an agreement. In that event, a trigger mechanism in the bill was activated to implement across-the-board reductions in the rate of increase in spending known as "sequestration".[14]

The Sequestration Transparency Act of 2012 (Pub. L. 112-155) requires the president to submit a report to Congress on a potential sequestration which may be triggered by the failure of the "Super Committee" to propose and for Congress to enact, a plan to reduce the U.S. Federal Budget by $1.2 trillion as required by the Budget Control Act.[15] The report – which was issued September 14, 2012, and was close to 400 pages long – provided the warning that "sequestration would be deeply destructive to national security... and core government functions".[16]

The start of the sequestration was delayed from January 2, 2013 to March 1, 2013 by the American Taxpayer Relief Act of 2012, which was passed by both houses of Congress on January 1, 2013 as a partial resolution to the fiscal cliff crisis.[17] The bill also lowered the sequestration cap for 2014 to offset the two-month delay in 2013. Also, for 2013 only, certain "security" funding such as homeland security and international affairs were included in the sequestration cut in order to lessen the cuts to defense.[18]

In December 2013, the Bipartisan Budget Act of 2013 increased the sequestration caps for fiscal years 2014 and 2015 by $45 billion and $18 billion, respectively,[19] in return for extending the imposition of the cuts to mandatory spending into 2022 and 2023, and miscellaneous savings elsewhere in the budget.[20]

Discretionary spending caps

The Budget Control Act of 2011 set limits on discretionary spending, with separate pools for defense and non-defense spending. The act specified one set of caps to be enforced if the Joint Select Committee on Deficit Reduction would produce a plan to reduce deficits by $1.2 trillion over 10 years, and Congress would enact it by January 15, 2012; if this did not happen, "automatic enforcement procedures" would impose a lower set of caps. Because the Joint Select Committee on Deficit Reduction did not come to agreement on any plan, the lower caps went into effect. The values in the table below reflect these lower caps.

The BCA column shows the discretionary caps in the original Budget Control Act, as estimated in 2012. (Some of the automatic spending reductions target mandatory spending, leading to some fluctuation in estimates of the discretionary funding.) The actual caps, as modified by subsequent legislation, are also shown.[21]

Fiscal
year
BCA (billions)[21] Actual (billions)
2012 $1,043 $1,043
2013 $1,047 $1,043 (American Taxpayer Relief Act of 2012)[22]
2014 $973 $1,012 (Bipartisan Budget Act of 2013)[23]
2015 $994 $1,014 (Bipartisan Budget Act of 2013)[23]
2016 $1,016 $1,067 (Bipartisan Budget Act of 2015)[24]
2017 $1,040 $1,070 (Bipartisan Budget Act of 2015)[24]
2018 $1,066 $1,208 (Bipartisan Budget Act of 2018)[25]
2019 $1,093 $1,244 (Bipartisan Budget Act of 2018)[25]
2020 $1,120
2021 $1,146

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 Spar, K. (October 2, 2012). Budget "sequestration" and selected program exemptions and special rules. Retrieved from [1].
  3. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. http://www.cbo.gov/ftpdoc.cfm?index=4032&type=0&sequence=7 The Budget and Economic Outlook: Fiscal Years 2004-2013, Appendix A, The Expiration of Budget Enforcement Procedures: Issues and Options
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. H.R. 4954 - Medicare Modernization and Prescription Drug Act of 2002 sent on 27 June 2002 Archived May 8, 2009, at the Wayback Machine
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. 21.0 21.1 Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found.
  24. 24.0 24.1 Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 Lua error in package.lua at line 80: module 'strict' not found.

External links