This bill amends the Federal Funding Accountability and Transparency Act (FFATA) to require agencies to report other transaction agreements (OTAs) to USAspending.gov and to adopt data and display standards so OTA data is automatically transmitted and centrally visible. It also creates new reporting duties for the Treasury Secretary and OMB Director, requires public lists of which agencies must post award data, and mandates annual disclosure of federal awards that remain off the portal and why.
For compliance officers, contractors, and agency program offices, the bill turns a historically opaque procurement vehicle into a public data set over a three-year rollout. The law pairs deadlines (initial compilation, a two-year plan, and a three-year full integration) with inspector general and GAO actions to improve verification and alignment with the Federal Acquisition Regulation clause that governs reporting requirements.
At a Glance
What It Does
Adds OTAs to the kinds of federal awards that must be recorded on USAspending.gov, requires automatic transmission and a centralized display of OTA data within three years, and mandates periodic agency lists and annual reports on funds not posted and the reasons why.
Who It Affects
Federal agencies that enter OTAs (for example, DoD components, DARPA, and other agencies that use other transaction authorities), Treasury and OMB (who must implement standards and lists), federal award recipients and prime contractors, and auditors and transparency stakeholders who use USAspending.gov.
Why It Matters
OTAs have been a persistent transparency gap because they sit outside traditional procurement reporting. Closing that gap changes oversight dynamics, creates new data-management work for agencies and contractors, and exposes previously opaque federal spending to public and congressional scrutiny.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill amends FFATA to treat other transaction agreements as reportable federal awards. Rather than leaving OTAs off the public ledger, it directs the Treasury Secretary, in cooperation with OMB, to ensure OTA data flows to USAspending.gov and to present that information in a centralized, searchable view.
The statute builds in a phased schedule: an initial compilation if full automation is not yet in place within one year, a formal plan to Congress within two years, and full automatic inclusion within three years.
To make the data usable, the bill requires data standards and display rules. Treasury and OMB must set requirements to ensure completeness and accuracy and may verify agency submissions.
The agencies that actually post the data remain responsible for ensuring the data are complete and accurate; Treasury and OMB have backstop authority to check consistency and to publish display standards the agencies must follow. The bill also changes FFATA’s agency-list mechanics: the Secretary must determine and publish which agencies and components are required to post award data, and update that list at least every two years.Accountability hooks are built into reporting and oversight.
The Secretary must publish an annual report that quantifies federal award dollars not posted to the portal and explain why — listing whether exclusions are due to national security/classification, awards by legislative or judicial branch entities, or subaward thresholds. Inspectors general of covered agencies must produce public reports on agency compliance on a one-year timetable and then at least every two years until ten years have passed.
Separately, the GAO must recommend updates to the Federal Acquisition Regulation clause governing award reporting within one year.Operationally the bill anticipates implementation friction and provides concrete steps to surface existing OTAs quickly if full automation is delayed: the ‘‘initial compilation’’ requires a public list and descriptions of OTAs entered in the prior fiscal year; the ‘‘plan’’ requires milestones and actions to reach the three-year target. By combining standards, publication requirements, and oversight workstreams, the statute converts a previously discretionary transparency practice into a structured, time-bound program.
The Five Things You Need to Know
The bill explicitly adds 'other transaction agreements' to the set of award types agencies must report under FFATA.
Treasury must ensure OTA data is automatically transmitted to USAspending.gov and presented as a centralized view within 3 years of enactment.
If automatic inclusion hasn't occurred within 1 year, Treasury must publish an initial compilation of OTAs from the prior fiscal year; if not done within 2 years, Treasury must submit a plan to Congress describing steps to finish integration by year three.
The Secretary must post an annual report quantifying federal award dollars not posted to USAspending.gov and categorize why (national security/classified, legislative or judicial branch awards, or subawards below a primary subaward).
Treasury, in coordination with OMB, must publish a list within 1 year (and update every 2 years) specifying which agencies and components are required to post award data; IG reporting deadlines and GAO recommendations on FAR clause updates are also mandated.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Designates the bill as the "Stop Secret Spending Act of 2025." This is purely formal but signals congressional intent to target opaque contracting practices.
Make OTAs reportable under FFATA
Amends FFATA’s definitional provisions to include 'other transaction agreements' among the award types to be reported. Practically, this removes any statutory ambiguity that allowed OTAs to be excluded from USAspending.gov reporting and triggers downstream obligations in FFATA for agencies that use OTAs.
Automatic transmission and centralized display requirement
Requires Treasury (the Secretary) to ensure OTA-related data is automatically transmitted to USAspending.gov and that the site provides a centralized view of OTAs within three years. This provision creates a technical mandate rather than leaving data submission to manual uploads, which has implications for agency IT systems and vendor award-management platforms.
Annual disclosure of unposted award dollars and reasons
Creates an annual public report listing the total federal spending on awards not posted to the website and requires categorizing the reason for non-posting (classified/national security, legislative/judicial branch awards, or subaward thresholds). That forces agencies to inventory and justify omissions rather than relying on opaque administrative practices.
Phased compliance milestones, definitions, and agency coordination
Sets definitions (Director = OMB Director, relevant agencies = agencies with OTA authority) and establishes a three-step implementation path: if Treasury has not implemented automatic reporting within one year, publish an initial compilation of OTAs for the prior fiscal year; if not implemented within two years, submit a formal plan to Congress describing actions to meet the three-year integration deadline. This section operationalizes the timeline and assigns coordination duties to Treasury and OMB.
Inspector General reporting, data quality, and agency-list mechanics
Revises IG reporting targets—expanding the agency categories subject to IG reports and setting firm submission timelines (first report within one year, then at least every two years until year ten). It also adds statutory obligations for data quality and display: agencies posting data must ensure it is complete and accurate, while Treasury and OMB can verify submissions and publish display standards. Finally, Treasury must assess which agencies/components must post, publish that list within a year, and update it biennially, creating a clear roster of reporting obligations.
GAO review of FAR reporting clause
Directs GAO to recommend updates to the FAR clause that governs contractor reporting to align procurement rules with the enhanced FFATA requirements. This ties administrative procurement rules to the statute and signals potential downstream changes for contracting officers and clauses in solicitations.
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 oversight committees — gain clearer, standardized visibility into OTAs and a statutory basis for asking questions and holding agencies accountable.
- Inspectors General and GAO — receive mandated reports, data access, and a statutory timeline that strengthens audit and investigative work on previously opaque award types.
- Transparency organizations, journalists, and watchdogs — obtain a centralized, searchable dataset on OTAs that improves public scrutiny of how federal dollars flow outside traditional contracts and grants.
- Nontraditional contractors and potential market entrants — benefit from increased public information about OTA opportunities and award recipients, which can level the playing field in niche innovation procurement markets.
Who Bears the Cost
- Agencies that use OTAs (notably DoD components, defense research entities like DARPA, and other operational offices) — must build or adapt IT systems to export OTA data in prescribed formats, inventory legacy OTAs for the initial compilation, and allocate staff time for data quality checks.
- Treasury and OMB — assume coordination, standard-setting, verification authority, and publication duties, which require personnel and technical resources to implement the automatic transmission and centralized display.
- Award recipients and primes — may need to provide more granular reporting data or respond to agency requests to complete fields, increasing administrative burden for vendors that previously faced limited disclosure requirements.
- National-security and classified program offices — face the operational tension and potential incremental workload involved in redacting or explaining why certain awards cannot be posted without degrading program effectiveness.
Key Issues
The Core Tension
The central dilemma is transparency versus operational secrecy and administrative burden: the bill aims to pull previously hidden federal spending into the public glare, which improves oversight and market visibility, but doing so risks exposing sensitive national-security work, imposes nontrivial technical and staffing costs on agencies and contractors, and raises hard questions about how to present redacted or classified data in a meaningful centralized format.
The bill confronts a classic transparency problem but leaves several implementation questions open. First, it mandates automatic transmission and centralized display but does not appropriate funds or specify technical standards in detail; agencies will need to map heterogeneous OTA management systems to the USAspending data model.
That technical work — particularly for legacy OTAs and classified programs — can be time-consuming and expensive. Second, while the statute requires the Secretary and Director to set quality and display standards and gives them authority to verify data, it does not establish specific penalties or enforcement mechanisms for agencies that fail to post accurate or complete data beyond the public and IG reporting requirements.
Another unresolved area is boundary-setting: OTAs vary widely in form and purpose across agencies. The act requires Treasury to publish a list of agencies and components that must post, but it does not create clear criteria for deciding whether a particular agreement or subaward is reportable, nor does it spell out how redactions for classified content will be handled while still meeting the statute’s 'centralized view' requirement.
Finally, the bill asks GAO to recommend FAR updates but does not lock timing between FAR changes and agency implementation, which could leave conflicting expectations between procurement contracting officers and statutory reporting deadlines.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.