The Taxpayer Experience Improvement Act directs the Secretary of the Treasury to modernize how the IRS communicates operational status and taxpayer-specific information. It requires the IRS to publish real-time call-center metrics (with an embedded tool and an API), detect and screen automated calls, expand online taxpayer accounts to display returns and correspondence for a rolling six-year window, and create controls for authorized representatives and qualified reporting agents.
This is a practical, operational bill: it mandates new public-facing data streams and user-facing features that will improve transparency for taxpayers and third-party tools but also creates immediate IT, privacy, and oversight obligations for the IRS and contractors. Compliance officers, tax professionals, and software developers should plan for new APIs, access-control requirements, and potential audits of authorized-designee activity.
At a Glance
What It Does
The bill requires the IRS to post, in real time where practical, call metrics by phone extension (callers connected, waiting, longest wait, callback availability), provide an embedded wait-time estimator and a public API for that data, screen automated calls, and publish monthly summaries. It also expands individualized online accounts so taxpayers and authorized representatives can view returns, refund routing (partial account and routing numbers or mailed‑check address), suspended-processing reasons, and respond electronically.
Who It Affects
The IRS and any contractors who operate its call lines; taxpayers (including those living abroad); tax return preparers, representatives authorized under 31 U.S.C. 330, and qualified reporting agents; tax-software and third-party developers that may use the new API; and financial institutions that receive refund deposits.
Why It Matters
The act creates a new transparency standard for federal tax administration by making performance and individualized case data publicly accessible and machine-readable. That improves taxpayer visibility but transfers substantial technical, privacy-control, and oversight work to the IRS — and opens new attack surfaces and compliance obligations for third parties.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
Section 2 focuses on call-center transparency. It requires the IRS to post, in real time to the extent practical, per ‘‘applicable phone number extension’’ a set of metrics: how many callers are connected to live representatives or automated systems, how many are waiting, the longest current wait, and whether callback service is available (and when it will be available if not).
The bill also requires an embedded web tool that shows those metrics and estimates wait times, plus a public application programming interface (API) so outside sites and apps can retrieve the same data programmatically. For the prior month, the IRS must publish averages and medians for call length and hold time, percentages of calls routed to automation, disconnect rates, transfer counts and post-transfer hold times, and a measure of whether callers felt their issue was resolved.
Section 2 further directs the IRS to deploy technology to detect and screen out automated (robocalls). It defines ‘‘significant delay’’ for processing categories of returns and other filings as failure to process items received at least 21 days before the week in question and requires the IRS to publish, for any week with significant delays, the earliest receipt dates for items processed in that week.
The effective date for these dashboard requirements is 12 months after enactment.Section 3 expands individualized electronic access. By a statutory deadline (the first January 1 that begins more than 12 months after enactment), the IRS must provide taxpayers via web and mobile app with up‑to‑date status on whether returns and amended returns were received and entered, whether processing is complete, refund issuance dates or estimates, and the destination of refunds (partial/full account number with routing for EFTs or mailing address for paper checks).
If processing is suspended, the system must show the reason and any information the IRS requested plus the form, manner, and due date for submission.Section 4 expresses the sense of Congress that taxpayers should be offered a callback option and sets a target that, by calendar year 2028, the IRS should allow any taxpayer — including those abroad — to request a callback if their call to an ‘‘applicable phone number extension’’ remains unanswered after five minutes. That provision is hortatory rather than a binding mandate.Section 5 expands online account capabilities and designee access.
By the first January 1 beginning more than 18 months after enactment, the IRS must provide a website or app letting taxpayers (and, when authorized, representatives, enrolled preparers with identifying numbers, and ‘‘qualified reporting agents’’) view returns, documents, notices, and letters from the prior six years (but not earlier than enactment), respond by uploading documents, and permit authorized persons to access multiple taxpayer accounts without separate logins for each client. The Secretary must establish vetting and suspension procedures for qualified reporting agents and create a program to investigate and report annual statistics on unauthorized use or overbroad access by designees.
The bill also requires user-focused design work via focus groups before rollout.
The Five Things You Need to Know
The dashboard requirement applies per ‘‘applicable phone number extension,’’ a category that includes contractor‑staffed lines and any extension that received at least 200,000 calls in the prior calendar year.
The bill mandates a public API exposing the real‑time call‑center metrics so third parties can embed wait‑time displays or build applications using IRS operational data.
For monthly summaries the IRS must publish averages and medians for call length and hold times, percentages of automated‑system calls, disconnect rates, transfer counts, post‑transfer hold times, and the percent of callers reporting they received the service they sought.
The expanded online account must surface refund routing: if the IRS will issue an EFT refund it must show the (partial or full) account number and routing number, or the mailed address if paying by paper check.
The bill defines a ‘‘significant delay’’ as failure to process items received at least 21 days before the week and requires the IRS to publish the earliest receipt date for items processed during any such delayed week.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Real‑time call metrics, embedded tool, and API
This subsection specifies the precise operational metrics the IRS must publish for each applicable phone extension: counts of callers connected to representatives or automated systems, callers waiting, the longest waiting time, and callback availability. It also requires an embedded web app that displays the same metrics and estimates wait times, plus an API so outside developers and websites can pull the data. Practically, this moves the IRS from static service notices to a streaming, machine‑readable operations feed and creates expectations for near‑real‑time accuracy and uptime.
Robocall screening, delay reporting, and definitions
The bill requires technology to detect and screen automated calls and establishes rules for reporting weeks with ‘‘significant delays’’ (items received at least 21 days before the week). For such weeks, the IRS must publish, during the following week, the earliest receipt dates for items processed. The definitional subsection clarifies which phone extensions are covered (accounts management, automated collection, the Joint Operations Center, contractor‑staffed lines, or any extension with ≥200,000 calls in the prior year), which affects the scope of dashboarding and API output.
Individualized return and refund tracking
This section requires the IRS to provide taxpayers with specific, up‑to‑date status on their filed and amended returns through web and mobile channels: receipt and entry status, processing completion, refund issue date and estimated arrival, and refund destination (EFT account partial/ routing or mailed address). It also requires showing suspension reasons and any requested information and deadlines — turning what has often been opaque casework into discrete data elements available to taxpayers and authorized agents.
Callback technology (sense of Congress)
The provision is framed as a congressional expression of expectation rather than a binding requirement: it states taxpayers should have a callback option and sets a target that, by 2028, the IRS ‘‘should’’ offer callbacks to any caller (including those abroad) waiting more than five minutes on applicable extensions. Because it’s non‑mandatory language, it signals intent and sets political pressure but does not, by itself, create an enforceable deadline.
Expanded online accounts and multi‑client access
This portion requires a new website or app enabling taxpayers and authorized representatives to view returns, notices, letters, and documents from the preceding six years (but not before enactment), respond electronically, and allow approved preparers, practitioners, and qualified reporting agents to access multiple client accounts without individual logins. It includes definitions of qualified reporting agents, describes the employment‑tax returns they may handle, and tasks the Secretary with regulations establishing availability and timing.
Oversight, vetting, and user testing
The bill directs the Secretary to create a program to detect and investigate unauthorized or overbroad access by designees, report annually on investigative actions (complaints investigated, access revocations, etc.), and to convene taxpayer and practitioner focus groups before deployment. Those provisions create both compliance and transparency obligations for the IRS in policing designee misconduct while requiring pre‑launch usability work.
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
- Individual taxpayers, including those living abroad — gain clearer, near‑real‑time visibility into call wait times, their return status, suspension reasons, and refund routing, reducing uncertainty and the need for repeated calls.
- Tax professionals and enrolled preparers — can access multiple client accounts (with taxpayer authorization) and receive the same granular status data, speeding casework and reducing time spent on routine status inquiries.
- Third‑party developers and tax‑software providers — can incorporate the IRS’s public API and embedded wait‑time tool into portals and apps to surface operational data and client-specific status in their products.
- Consumer advocates and oversight bodies — receive standardized monthly performance statistics and publishable enforcement metrics on designee misuse, improving external accountability for IRS service levels.
Who Bears the Cost
- The Internal Revenue Service — must design, implement, secure, and operate real‑time dashboards, a public API, expanded account capabilities, and a designee‑monitoring program, all of which require funding, staffing, and sustained cybersecurity work.
- IRS contractors running phone lines — face new reporting obligations and technical integration to feed the dashboard and may be audited or have access revoked if they fail to meet standards.
- Financial institutions and refund processors — may see increased inquiries and potential liability questions because the system will surface partial account numbers and routing info, creating privacy and verification issues.
- Qualified reporting agents and authorized designees — will be subject to vetting, suspension procedures, and public statistics about misuse, increasing administrative compliance and reputational risk.
Key Issues
The Core Tension
The central dilemma is between transparency and usability on one hand, and privacy, security, and administrative capacity on the other: the bill pushes the IRS to surface more operational and client‑specific data to reduce taxpayer friction, but doing so safely and reliably requires substantial IT modernization, robust access controls, and sustained funding — requirements that the statute signals but does not directly fund or fully specify.
The bill trades greater transparency for increased operational and security burdens. Publishing real‑time, per‑extension metrics and exposing them via API is useful for taxpayers and third parties, but it creates additional attack surfaces: unauthenticated or poorly authenticated endpoints risk data scraping, spoofing of service metrics, or amplification of denial‑of‑service vectors against specific phone extensions.
The statute requires the Secretary to produce a public API and embedded tool but leaves many security and performance design choices to Treasury regulations and IRS implementation, which will determine the ultimate risk profile.
The privacy implications of displaying refund destination information (even partial account numbers and routing) are unevenly addressed. Showing refund routing helps taxpayers confirm payment destinations, but it also may reveal sensitive banking details to anyone who gains authorized access to accounts or to systems that fail to enforce strict authentication and session management.
Likewise, the requirement to let authorized preparers access multiple clients through single interfaces eases workflow for firms but concentrates privilege — making vetting, logging, and rapid revocation critical. Finally, the ‘‘sense of Congress’’ on callback capability sets political expectations without funding or a binding deadline; whether the IRS can meet the 2028 target depends on internal prioritization and appropriations.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.