Codify — Article

Get Your Money Back Act directs Treasury to keep and expand IRS Direct File

Requires the Treasury (via the IRS) to continue a free Direct File e‑file system and compels state participation for tax years after Dec. 31, 2025 — a potential pivot point for the tax‑prep market and state revenue systems.

The Brief

The Get Your Money Back Act instructs the Secretary of the Treasury to continue implementing the Internal Revenue Service’s free direct electronic filing program commonly called Direct File. It also directs the Secretary (or a delegate) to require state tax authorities to participate in that free federal Direct File system.

The measure matters because it converts a pilot or discretionary IRS service into a statutory obligation for the Treasury and forces state-level integration. That raises immediate operational, funding, and legal questions for the IRS, state tax agencies, private tax‑prep vendors, and taxpayers who currently use commercial software or paid preparers.

At a Glance

What It Does

The bill uses an explicit 'notwithstanding any other provision of law' clause to prioritize continued deployment of the IRS’s free Direct File e‑file system and instructs the Secretary (or delegate) to require state participation. It sets a clear implementation trigger tied to taxable years beginning after December 31, 2025.

Who It Affects

The directive touches the IRS’s operations, state tax authorities (50 states and the District of Columbia), commercial tax‑preparation vendors and software platforms, paid preparers, and low‑ and moderate‑income taxpayers who would be most likely to use a free filing option.

Why It Matters

By elevating Direct File to a statutory direction, the bill could reshape market share between the IRS and private tax‑prep firms, influence state IT integration and data flows, and change end‑user options for filing returns. It also creates practical questions about funding, technical standards, and enforcement that the text does not resolve.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

The bill is short and narrowly focused: it tells the Treasury Department to keep running the IRS’s Direct File—a no‑cost electronic tax‑return filing system—and it directs Treasury to make states participate. The language is framed broadly enough to override conflicting laws, and it vests the duty in the Secretary or a delegated official, which preserves administrative flexibility about how to operate and enforce the requirement.

Operationally, the statute stops short of dictating design details. It does not prescribe technical standards, authentication methods, verification flows, or how state returns will be routed, validated, or reconciled with federal filings.

It similarly does not create a grant program or appropriate funds; the text imposes an obligation without specifying a funding source or additional staffing for the IRS or for state tax agencies.For states, the bill converts participation from an optional coordination exercise into a compelled requirement. The text does not define what 'participation' means in practice—whether states must accept returns transmitted directly by the IRS, host joint filing screens, or simply coordinate on data exchange.

That vagueness will require follow‑on rulemaking or intergovernmental agreements to translate the statutory duty into interoperable systems.Finally, the bill is silent on enforcement and penalties if a state declines or fails to implement the required participation. It also does not address how the Direct File program will coexist with commercial e‑file providers that currently handle most individual returns, nor does it address consumer privacy standards or procurement rules that typically govern state IT integrations.

The Five Things You Need to Know

1

The bill directs the Secretary of the Treasury (or the Secretary’s delegate) to continue implementing the IRS program commonly called 'Direct File'—a free direct e‑file option run by the IRS.

2

It contains a 'notwithstanding any other provision of law' clause, which elevates the directive above other statutory conflicts rather than leaving it to discretionary agency policy.

3

For each taxable year beginning after December 31, 2025, the Secretary must require each of the 50 States and the District of Columbia to participate in the free Direct File system.

4

The statutory text identifies no appropriation, grant, or dedicated funding stream to support IRS operations or state integration work tied to this mandate.

5

The bill does not specify enforcement mechanisms, penalties, or consequences if a state fails to participate, nor does it define technical or data‑security standards for participation.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section 1

Short title

Designates the act as the 'Get Your Money Back Act.' This is purely nominal but signals the bill's framing for legislative and public discussion.

Section 2(a)

Continued implementation of Direct File

Directs the Secretary of the Treasury (or a delegate) to continue implementing the IRS’s free direct electronic filing system. The provision expressly prioritizes continuation of the program, using language that removes agency discretion to discontinue on the basis of conflicting statutes or policies unless Congress amends the law.

Section 2(b)

Mandatory state participation for tax years after 2025

Requires the Secretary (or delegate) to require every state and the District of Columbia to participate in the Direct File system for taxable years beginning after December 31, 2025. The text does not define 'participate' or provide criteria, leaving open whether participation means technical integration, data exchange agreements, or acceptance of returns transmitted by the federal system. That gap delegates significant implementation detail to the Treasury/IRS and to intergovernmental negotiation.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Finance across all five countries.

Explore Finance 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

  • Lower‑income and cost‑sensitive taxpayers — They gain access to a free federal e‑file option that could reduce or eliminate the need to pay commercial preparers for simple returns.
  • IRS and federal policymakers focused on access — A statutory mandate stabilizes the agency’s ability to offer a public filing alternative and strengthens arguments for sustained investment in taxpayer‑facing IT.
  • Taxpayer advocacy organizations — The law gives advocates a clear statutory basis to press for accessible design, reduced fees for filers, and transparency in how Direct File operates.

Who Bears the Cost

  • State tax agencies — They must undertake whatever technical, legal, and operational work 'participation' requires without an explicit federal funding stream in the bill, increasing budgetary and project management burdens.
  • Commercial tax‑preparation firms and software vendors — A free federal filing option could reduce market share and revenues for companies that rely on paid e‑file services, particularly for simple returns.
  • The IRS — The agency is tasked with continuing and scaling Direct File and coordinating with all states; absent new appropriations, this imposes resource and staffing pressure on an agency already managing complex systems.

Key Issues

The Core Tension

The bill forces a choice between two legitimate goals: expanding free, public access to tax filing (promoting equity and lower costs for filers) versus the practical costs and risks of imposing a rapid, nationwide technical integration on state systems and the IRS without dedicated funding or detailed technical and legal guardrails.

The bill resolves an access question—make Direct File persistent—but leaves crucial implementation levers blank. It compels an outcome without specifying how to get there: no funding, no technical or security standards, no interoperability definitions, and no enforcement mechanism against non‑compliant states.

That combination risks uneven implementation: some states may rapidly interconnect using existing APIs and staff, while others face delays or functional limitations because of legacy systems, procurement cycles, or statutory constraints at the state level.

Another unresolved issue is market and legal friction with private providers and existing e‑file rules. The statute’s 'notwithstanding' language may invite legal challenges from stakeholders who argue federal overreach into state tax administration or who claim preemption issues with state procurement and privacy laws.

Finally, by specifying a start tied to taxable years after December 31, 2025, the bill compresses the timeline for complex multi‑jurisdictional IT projects, creating risk that a minimally viable but functionally limited solution will be deployed instead of a robust, secure system.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.