The VAMOSA Act adds a new section to title 38 requiring the Secretary of Veterans Affairs to ensure the Chief Information Officer, working with other relevant officials, establishes and implements a department-wide software asset management policy. The statute prescribes minimum elements — an agency-wide inventory, license and interoperability assessments, steps to identify and eliminate redundant or unauthorized spending, coordination on significant acquisitions, enterprise licensing strategies, and enforcement of license terms — plus periodic reviews and annual training for staff who acquire or manage software.
The bill aims to reduce duplication and untracked SaaS spending across the Department, improve negotiation leverage with vendors, and provide Congress with reporting on policy changes and realized savings. It requires implementation using existing personnel and funds, terminates the new authorities after five years, and directs the GAO to evaluate implementation and contractor independence three years after enactment.
At a Glance
What It Does
Creates a new statutory duty for the VA to adopt a comprehensive software asset management policy that includes a complete inventory of software assets, license and interoperability assessments, coordination on acquisitions, and compliance measurement. The policy must be reviewed at least once every three years, and employees who handle software acquisitions must receive annual training on contract negotiation and licensing models.
Who It Affects
Directly affects the VA Chief Information Officer, Chief Financial Officer, procurement and IT acquisition teams, program offices that buy or manage software, and third-party vendors and contractors who provide SaaS, platform services, or inventory reconciliation. Congress and taxpayers are indirect stakeholders because the law requires annual reporting on substantive policy updates and cost savings.
Why It Matters
Large agencies often lose visibility into decentralized SaaS spending; this bill legally centralizes inventory and license oversight inside the VA and demands measurable cost-savings reporting. Because it prohibits new appropriations and includes a five-year sunset, the law pressures the VA to implement changes quickly within existing budgets — shifting the practical problem from policy design to resourcing and execution.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The heart of the VAMOSA Act is a new, departmental rule: the VA must have and carry out a single, comprehensive approach to software assets. That means the CIO must coordinate with finance and program leaders to build and maintain a living inventory that goes beyond named contracts to capture accounts, subscriptions, tenants, deployments, and associated entitlements (licenses, seats, capacity or consumption rights).
The statute defines ‘‘software asset’’ broadly to include SaaS, platform services, APIs, and any software for which the VA pays to acquire, operate, or maintain, regardless of whether it runs on government or vendor infrastructure.
The policy must lay out how the Department assesses interoperability and license restrictions, and how it finds and removes waste, fraud, and abuse. Concretely, the law expects reconciliation between the inventory and purchase, subscription, billing, and contract records to spot discrepancies like over-procurement, under-utilized licenses, or unauthorized use.
It also requires the CIO to coordinate with relevant officials before any ‘‘significant acquisition’’ of software and to adopt cost-effective licensing strategies — for example, pursuing enterprise agreements where feasible and measuring compliance with license terms.To make the policy durable, the bill requires the CIO (in consultation with the CFO and other officials) to review and update the policy at least every three years, and it requires targeted annual training for employees who buy, manage, or implement software. The training topics listed in the bill include contract negotiation to limit vendor-imposed deployment or data restrictions, the differences between commercial off-the-shelf and custom development, and how to evaluate seat-based versus consumption-based license models.Implementation is constrained: the statute explicitly directs the VA to use existing personnel, systems, and funds and disclaims any new appropriation or new office.
The law also requires the Secretary to report in the VA’s annual report to Congress any substantive policy updates and an estimate of cost savings realized. Finally, the statute sunsets after five years and instructs the Government Accountability Office to deliver an independent evaluation three years after enactment that assesses implementation, savings and duplication reductions, and whether contractor support used for inventory or entitlement reconciliation preserved operational independence and avoided conflicts of interest.
The Five Things You Need to Know
The policy must maintain a comprehensive inventory that reflects accounts, subscriptions, tenants, deployments, and corresponding license or usage entitlements.
Employees who acquire, manage, or implement software must receive annual training on contract negotiation limits, differences between commercial and custom development, and evaluating seat-based versus consumption-based licensing.
The Chief Information Officer must coordinate with relevant Department officials on any significant software acquisition and must review and update the policy at least once every three years in consultation with the CFO.
The statute requires implementation using current personnel and funds (no new appropriations or new office) and sets a five-year statutory sunset for the section's authorities.
The Comptroller General must report to the House and Senate Veterans’ Affairs Committees three years after enactment on implementation, cost savings and duplication reduced, and the independence of any contractor support used for inventory or entitlement reconciliation.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Act name: VAMOSA Act of 2025
A short title clause that identifies the statute as the Veterans Affairs Management and Oversight of Software Assets Act of 2025. This is administrative but signals the bill’s narrow focus on software asset governance within title 38.
Establishment and coordination of policy
Requires the Secretary to ensure coordination between the Chief Information Officer and other appropriate officials to establish and implement a comprehensive software asset management policy. Practically, this elevates software inventory and license governance to a departmental priority and places primary operational responsibility with the CIO while keeping other officials in the loop for cross-functional buy-in.
Minimum elements: inventory, assessments, and acquisition coordination
Specifies the policy's minimum components: a comprehensive inventory, interoperability and license restriction assessments, procedures to identify and eliminate waste/fraud/abuse through reconciliation with purchase and billing records, CIO coordination for significant acquisitions, enterprise licensing strategies where practicable, and mechanisms to measure and enforce license compliance. These clauses create concrete operational tasks (inventory reconciliation, entitlement reconciliation, compliance monitoring) rather than high-level guidance, which will require process changes inside procurement, finance, and IT units.
Governance cadence, training, resource limits, and reporting
Mandates that the CIO review and update the policy at least every three years with CFO input, and require annual training for staff responsible for software lifecycle duties on listed topics. It also instructs that the requirements be met using existing personnel, systems, and funds (no additional appropriations or new office), and compels the Secretary to include policy updates and estimated cost savings in the annual report to Congress under section 529. Those operational constraints will shape how aggressively the VA can staff and roll out new tooling or centralized procurement functions.
Definitions, sunset, clerical amendment, and GAO evaluation
Defines 'software asset' broadly to include SaaS, platform services, APIs, and any paid software entitlements and clarifies inventory scope to include accounts, subscriptions, tenants, deployments and entitlements. Establishes a five-year statutory sunset for these authorities. The bill also adds a clerical amendment to the table of sections and directs the GAO to produce an implementation report three years after enactment assessing realized savings, duplication reduction, and whether contractor support preserved operational independence. The definitions and GAO mandate will be focal points in measuring success and constructing the inventory standard across the Department.
This bill is one of many.
Codify tracks hundreds of bills on Technology across all five countries.
Explore Technology 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
- Veterans who rely on VA IT services — improved inventory and license oversight can reduce service interruptions caused by untracked subscriptions and improve interoperability across VA systems, yielding more consistent access to digital benefits and records.
- VA leadership (CIO and CFO) — gains centralized visibility into software spend and licensing entitlements, which strengthens negotiating leverage with vendors and supports budgetary planning and audit defense.
- Congressional oversight committees and taxpayers — receive annual reporting on substantive policy updates and estimated savings, plus a GAO evaluation, which increases transparency into Departmental IT spending and potential cost reductions.
- Program offices that depend on widely used enterprise tools — stand to benefit from consolidated enterprise agreements and standardized licensing that can lower per-user costs and simplify procurement.
Who Bears the Cost
- VA procurement and IT acquisition teams — must perform inventory reconciliation, license entitlement audits, and take on new reporting and compliance duties without additional appropriations.
- Line program offices that currently procure specialized or niche software — may lose some autonomy as the Department centralizes acquisition strategy and pushes for enterprise agreements.
- Commercial vendors using seat-based or fragmented licensing models — could face harder negotiations and pressure to shift to enterprise or consumption models that may reduce legacy revenue streams.
- Contractors hired to perform inventory or entitlement reconciliation — face heightened scrutiny about operational independence and conflicts of interest, since the GAO will evaluate contractor support.
- The VA CIO/CFO and their staff — will carry implementation accountability and likely see workload increases to meet the policy, training, review cadence, and reporting requirements within existing resource constraints.
Key Issues
The Core Tension
The central dilemma is between centralizing control to eliminate waste and preserve negotiating leverage, and preserving program-level flexibility and capacity: the bill pushes the VA to consolidate inventories, licensing strategy, and acquisition coordination to save money, but it does so without additional resources and with a limited five-year window, risking rushed or uneven implementation that could constrain mission-tailored software choices.
The bill forces a trade-off between urgency and resources: it mandates an agency-wide program and annual training while simultaneously prohibiting new appropriations and forbidding the creation of a new office. That tension creates several implementation risks — uneven rollouts across administrations, reliance on manual reconciliations that consume scarce staff hours, or superficial compliance that checks boxes without fixing root causes of duplication.
Operationally, the statute’s broad definition of software assets and the inventory requirement (accounts, subscriptions, tenants, entitlements) will surface technical and contractual complexity. Reconciling consumption-based entitlements, multi-tenant cloud deployments, and vendor-managed infrastructure against purchase and billing records is technically demanding and may require tooling the bill does not fund.
Measurement of ‘‘cost savings realized’’ is also likely to be contested: savings can be front-loaded (avoided renewals) or realized over time (lower per-user costs), and the bill gives no standard for how savings should be calculated or independently verified. Finally, the GAO’s mandated inquiry into contractor independence signals concern about outsourcing inventory duties to firms that may also sell licensing services — an ambiguity the VA must navigate when contracting for reconciliation work.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.