Analyses / Public Summary / 119 · S 1991 Public Summary

119-S-1991 Journalist Public Summary

119 · S 1991 Delivering On Government Efficiency in Spending Act

Bill S.1991 would require agencies to attach plain-language purpose details to every federal payment, verify that data yearly, and post it publicly within 30 days, while expanding Treasury’s tools (like Do Not Pay checks, bank-account verification, and limited access to tax, Social Security, and new‑hire data) to prevent improper payments; supporters say it boosts transparency and cuts waste, while critics may raise privacy, data‑security, and burden concerns.

Published
12 Dec 2025
Updated
12 Dec 2025
Tags
public-summary · US-Congress · federal-spending
Unvetted
01 · Section

Headline Summary

Make every federal payment more transparent and double‑check bank and identity details to cut down on mistaken or fraudulent payouts.

02 · Section

What It Does

The bill requires agencies to include a short purpose description, the funding account, and an activity code with each payment sent through Treasury systems—and to confirm that information at least once each fiscal year. Most payment details must be posted for the public within 30 days on the government’s spending website, with exemptions for sensitive law‑enforcement or national‑security operations (those exempt payments still have to be summarized in future budget materials). It also strengthens “Do Not Pay” and related anti‑fraud checks by allowing Treasury to verify bank accounts before paying, and to use limited data from the National Directory of New Hires, consumer reports, IRS records (in a privacy‑preserving way), and Social Security records solely to spot, prevent, or recover improper payments.

Public posting deadline
30days after payment certification
Data re-check frequency
1per fiscal year (minimum)
Minimum tax years for IRS validation
3years
Scope of agencies covered
0Executive agencies, independent regulators, and certain entities (Congress, courts, territories, D.C.) that use Treasury disbursement systems
03 · Section

Why It Matters

  • Transparency: Attaching a plain‑English purpose to each payment—and posting it quickly—helps taxpayers and watchdogs see where money goes.
  • Accuracy and fraud prevention: Bank‑account checks and cross‑database validation aim to reduce wrong payments before money goes out the door.
  • Balance of openness and security: Sensitive operations can be shielded, but agencies must still provide aggregated reporting later, which tries to protect security while maintaining accountability.
04 · Section

Who’s For It

  • Primary sponsor: Sen. Joni Ernst (R‑IA).
  • Cosponsors (Senate): Sens. Tim Sheehy, Cynthia Lummis, Markwayne Mullin, Mike Lee, Jim Risch, Tommy Tuberville, Kevin Cramer, Roger Marshall, Ted Budd, Steve Daines, James Lankford, Katie Britt, Chuck Grassley, and Rick Scott of Florida (all Republicans).
  • Supporter rationale (stated or typical): Increase transparency, deter waste and fraud, and improve trust in federal spending.
05 · Section

Who’s Against It

  • No formal opposition is listed in the bill text. Potential concerns could come from privacy and civil‑liberties advocates about broader data sharing (new‑hire, tax, Social Security, and consumer‑report data).
  • Some agencies or contractors may worry about compliance costs, false positives that delay legitimate payments, or cybersecurity risks from handling more sensitive data.
  • Consumer‑protection voices may scrutinize how credit‑report information is used for pre‑payment checks and how errors are corrected.
06 · Section

What’s Next

Status as of December 12, 2025: The bill was introduced on June 9, 2025, read twice, and referred to the Senate Committee on Homeland Security and Governmental Affairs. A hearing was held on December 10, 2025, in the Senate Committee on Small Business and Entrepreneurship. Next steps would be committee markup and a vote to report the bill to the full Senate; if passed, it would move to the House, and then to the President.

Discussion