The IRS Has A $192M Contract Control Problem

IRS & Regulation

The tax agency is leaning on temporary IT deals that are supposed to be short-term fixes. The controls do not look short-term enough.

The IRS has a contract problem that sounds boring until the number shows up. A new inspector general review found 19 information technology bridge contracts totaling $192 million, and the agency did not consistently follow Treasury Department policy while using them.

Bridge contracts are meant to keep critical services moving when an old contract is ending and a replacement is not ready. That can be reasonable. The risk is what happens when temporary stops being temporary and noncompetitive work becomes the easy path.

The 12-Month Line Matters

Treasury policy generally says a bridge contract should not exceed 12 months unless unusual circumstances justify it. If a bridge contract goes past that line, the next-level approving authority is supposed to sign off.

The review found six of the 19 bridge contracts exceeded 12 months. That is 32% of the sample. It also found problems with required justifications being signed, kept in the contract file, and approved by the right authority.

This Is A Controls Story

The dollar figure is only part of the issue. In fiscal 2025, the IRS had $16.5 billion in contract obligations, and more than $8.2 billion related to IT products or services. When IT spending is that large, weak tracking around noncompetitive contracts becomes a real operating risk.

The inspector general warned that weak controls over bridge contracts can increase the risk of overpaying for IT goods or services. That is the point CPA firms should care about. The failure mode is familiar: the organization has a policy, but the evidence trail does not prove the policy was followed.

Five Fixes Are On The Table

The recommendations were practical. The IRS was told to build a process that flags missing justifications, require training for contracting officers, make bridge contracts easier to identify, track extensions more clearly, and make sure contracts over 12 months carry the right next-level approval.

The IRS agreed with all five recommendations. CFO Todd Newnam said the agency recognizes the need to track bridge contracts and keep effective controls around IT asset and service purchases.

The Bigger Lesson For Firms

This is not just a government procurement story. It is a reminder that process gaps usually hide in the handoff moments. Temporary contracts, manual overrides, emergency approvals, side spreadsheets, and informal exceptions are where controls start to loosen.

For accounting firms advising clients, the question is not whether a bridge contract or short-term workaround is allowed. The question is whether the client can prove why it was used, who approved it, when it should end, and whether anyone checked that it did not become the default operating model.

What CPAs Should Watch

Watch for clients with large technology spend, recurring emergency extensions, or procurement files that depend on memory instead of documentation. The IRS review is a clean example of how a compliance issue becomes a cost issue when the control owner cannot quickly identify, support, and approve exceptions.