Technical corrections only. The diff between v2 and v3 primarily addresses grammatical errors, typos, and formatting inconsistencies in several sections, including updates to cross-references. No substantive policy changes were introduced.
Stop Secret Spending Act of 2025
- Sponsor
- Sen. Ernst, Joni [R-IA]
- Committees
- Homeland Security and Governmental Affairs Committee (primary), Small Business and Entrepreneurship Committee
- Last action
- Jun 15, 2026
Bottom line
The bill significantly expands federal spending transparency by requiring the disclosure of 'other transaction agreements' on USAspending.gov and enhancing overall data quality and accountability for federal award reporting.
What it actually does
This bill mandates that 'other transaction agreements' (OTAs), a type of federal award often used for research and development, be reported to USAspending.gov. It requires the Secretary of the Treasury to ensure automatic data transmission and a centralized view of OTA data within three years. Additionally, the bill establishes new requirements for federal agencies to ensure the completeness and accuracy of data posted to USAspending.gov and mandates an annual report on all federal spending that has not been posted to the website, including reasons for non-disclosure.
Proponents argue
Proponents argue that the bill closes a significant loophole in federal spending transparency, bringing a growing category of federal awards—other transaction agreements—under public scrutiny. They contend that increased transparency will enhance accountability, reduce waste, and improve public trust in government spending by allowing citizens and oversight bodies to track how billions of taxpayer dollars are spent, particularly in areas like defense research and development.
Opponents contend
Opponents might argue that while transparency is important, the expanded reporting requirements could impose significant administrative burdens and costs on federal agencies and their partners, potentially slowing down critical research and development projects. Concerns could also be raised about the potential disclosure of sensitive or proprietary information related to certain OTAs, particularly those involving national security, despite provisions allowing for non-reporting of classified data.
The bill is concise and relatively easy to read, allowing for a quick understanding of its core objectives and provisions.
Section 2(a) and 2(b)
Mandatory Reporting of Other Transaction Agreements (OTAs) to USAspending.gov
This provision amends the Federal Funding Accountability and Transparency Act of 2006 (FFATA) to explicitly include 'other transaction agreements' (OTAs) within the definition of federal awards that must be reported. It further requires the Secretary of the Treasury to ensure that data related to OTAs is automatically transmitted to USAspending.gov and made available in a centralized, searchable view on the website within three years of the bill's enactment.
Supporters argue
Supporters argue that this provision closes a critical gap in federal spending transparency, as OTAs represent a substantial and growing portion of federal awards that have historically lacked comprehensive public reporting. They contend it will ensure greater accountability for taxpayer dollars, particularly in areas involving innovative technologies and defense contracting.
Critics contend
Critics may argue that integrating OTA data into USAspending.gov could be technically complex and costly, potentially diverting resources from other critical agency functions. Some may also raise concerns that detailed public disclosure of certain OTAs, especially those related to sensitive research or national security, could inadvertently reveal strategic information or proprietary data.
Tradeoffs
The provision balances the public's right to know how federal funds are spent against the administrative burden on agencies and the potential for disclosing sensitive information related to certain types of federal awards.
Section 2(c)
Annual Report on Unreported Federal Spending
This section mandates that the Secretary of the Treasury, in consultation with the Director of OMB, publish an annual report on USAspending.gov. This report must detail the total amount of federal spending for which data has not been posted to the website and provide specific reasons for non-disclosure, such as national security classifications, awards by legislative or judicial branch agencies, or subawards below a primary subaward.
Section 2(d)
Implementation Plan and Interim Reporting for OTAs
This section establishes a phased implementation approach for OTA reporting. If the Secretary has not fully complied with the automatic OTA data transmission requirement within one year of enactment, an initial report listing all OTAs from the preceding fiscal year must be published. If compliance is not met within two years, the Secretary must submit a detailed plan to Congress outlining actions to ensure full incorporation of OTA data into USAspending.gov by the three-year deadline.
Section 3(a)
Inspector General Reporting Amendments
This section amends FFATA to clarify which agencies' Inspector Generals (IGs) are required to submit reports on data quality and compliance. It specifies that IGs of agencies described in paragraphs (1) or (2) of section 901(b) of title 31, United States Code, must submit these reports. It also updates the deadlines, requiring the first report one year after enactment and subsequent reports at least every two years for ten years.
Section 3(b)
Enhanced Data Quality and Agency Reporting Determination
This section introduces new requirements for data quality and agency accountability. It mandates the Secretary and Director of OMB to establish requirements for complete and accurate information posted to USAspending.gov, making federal agencies responsible for their data's quality, and granting the Secretary and Director authority to verify accuracy. It also requires the Secretary and Director to assess and publish a list of federal agencies and components required to post information, providing written notice to those included.
Section 4
GAO Report on Federal Acquisition Regulation (FAR) Updates
This section directs the Comptroller General of the United States (head of the Government Accountability Office, GAO) to make recommendations for updating clause 52.204-10 of the Federal Acquisition Regulation (FAR). These recommendations are intended to incorporate requirements under FFATA, ensuring that federal contractors comply with transparency mandates. The report is due one year after the bill's enactment.
The effective date for the amendments made by Section 3(b)(1)(A) (which modifies how agencies are identified for reporting under FFATA Section 3(b)) is delayed until the Secretary publishes the first list of required reporting agencies under the new Section 3(e)(2).
Section 3(b)(2)
Why it matters:This is standard legislative practice to ensure that new requirements only take effect once the necessary administrative groundwork (like compiling and publishing a list of agencies) has been completed. It prevents agencies from being out of compliance before they are formally notified of their obligations.
Case for: Supporters would argue this phased effective date is practical and necessary for orderly implementation. It ensures that agencies are not held accountable for new reporting requirements before the Secretary has formally determined their obligations and published the necessary guidance.
Case against: Critics might argue that delaying the effective date, even for practical reasons, could prolong the period during which some agencies might not be fully compliant with the spirit of the transparency law. It could be seen as allowing a grace period that delays full accountability.
Estimated impact: The impact is primarily on the timeline for full implementation of the new agency reporting determination process, potentially delaying it by up to a year or more depending on how quickly the Secretary and Director can publish the initial list.
The bill amends the Inspector General reporting requirements by specifying that reports are required from 'each agency described in paragraph (1) or (2) of section 901(b) of title 31, United States Code,' rather than 'each Federal agency.'
Section 3(a)(1)(A) and 3(a)(2)
Why it matters:This is common legislative drafting practice to avoid redundancy and ensure consistency with existing statutory definitions. Referencing an established list of agencies in the U.S. Code is more efficient than reproducing it or creating a new, potentially conflicting, definition.
Case for: Supporters would argue that using an existing statutory reference ensures clarity and consistency in defining the scope of agencies subject to IG reporting. It leverages established legal frameworks, avoiding ambiguity and potential conflicts with other statutes.
Case against: Critics might argue that relying on external legal citations makes the bill less accessible to the general public and requires specialized legal knowledge to fully understand its scope. This could hinder public oversight by obscuring which specific agencies are covered.
Estimated impact: The impact is on the precise scope of federal agencies whose Inspector Generals are mandated to submit regular reports on data quality and compliance. It ensures that a specific, legally defined set of agencies are consistently covered.