Picture two things happening at the same time. The agency responsible for reviewing your tax return is understaffed and buried under a backlog, and the software that the agency uses to catch filing errors just keeps getting better.

That combination should give any taxpayer pause this season. Not because an audit is necessarily coming, but because if something does go wrong, the window for getting it resolved quickly has shrunk considerably.

The IRS Is Running Lean, But It’s Technology Isn’t

The agency lost more than a quarter of its workforce in 2025. The National Taxpayer Advocate’s most recent annual report to Congress documented the drop: from roughly 102,000 employees to about 74,000. Those departures, through a mix of voluntary exits and layoffs, spread across nearly every division.

Funding took a hit at the same time. Congress reversed a significant portion of the IRS budget boost approved through the Inflation Reduction Act, pulling back billions earmarked for enforcement and technology investment. A government shutdown that stretched across October and November of last year piled further delays onto an already strained system. The Treasury Inspector General for Tax Administration confirmed in a January report what tax practitioners were already seeing firsthand: a serious backlog in the processing of amended returns and taxpayer correspondence.

Here’s the part that catches people off guard. None of that has slowed the IRS’s ability to spot problems on your return. The agency’s systems cross-reference what you report against data received independently from employers, brokers, and financial institutions. Artificial intelligence and expanded automation have made error detection faster and more precise, staffing levels notwithstanding.

Fewer people are available to handle problems once they surface. But the technology responsible for finding those problems is running better than ever.

What This Looks Like in Practice

Tax professionals working with real clients are the best window into what this means day to day. Advisors report receiving IRS notices today that are resolving matters dating back to 2023, showing a multi-year lag on what should be routine correspondence. The practical response among preparers has been to tighten processes and leave less to chance.

Some advisors have added specific safeguards, such as obtaining power of attorney to monitor clients’ IRS online accounts directly rather than waiting for slow paper notices. Others describe the current environment plainly: the cost of needing to amend a return has gone up, not necessarily in dollars, but in time and uncertainty.

A poll of tax and financial advisors conducted during a recent industry webinar found that every respondent is maintaining at least the same level of care they applied when IRS staffing was at full strength. Nearly half said they are actively raising the bar this season.

What You Should Do Differently

Here are a few practical steps worth taking seriously this year:

• Give your preparer complete and accurate information. Incomplete or inconsistent reporting is where most errors begin, and those errors are exactly what the IRS’ matching systems are built to catch.
• If you are claiming something new on your return, ask your preparer to walk you through the basis for it. Understanding what you are filing and why is reasonable.
• Set up an IRS online account at IRS.gov if you haven’t already. You can monitor your filing status, review transcripts, and spot potential issues before they become formal notices.
• And if something does go sideways, respond early. Letting a notice sit without a response doesn’t slow the IRS down. It just costs you time you don’t have.

Conclusion

The agency may be a smaller operation than it was a few years ago. But the part of it designed to find mistakes on your return is still very much running.

---

"; return; } var url = block.dataset.restUrl + "?post_id=" + encodeURIComponent(block.dataset.postId) + "&keyword=" + encodeURIComponent(keyword); output.innerHTML = ""; submit.disabled = true; output.setAttribute("aria-busy", "true"); fetch(url, { headers: { "X-WP-Nonce": block.dataset.nonce } }) .then(function(r){ return r.json().then(function(data){ return { status: r.status, data: data }; }); }) .then(function(resp){ if (resp.status === 200 && resp.data && resp.data.success) { dpSimilarRender(output, keyword, resp.data); } else if (resp.status === 403) { output.innerHTML = ""; } else if (resp.status === 429) { output.innerHTML = "" + dpSimilarCta(output, -1); } else { output.innerHTML = "" + dpSimilarCta(output, -1); } }) .catch(function(){ output.innerHTML = "" + dpSimilarCta(output, -1); }) .then(function(){ submit.disabled = false; output.removeAttribute("aria-busy"); }); } function dpAskGrokSend(block) { var input = block.querySelector(".dp-ask-grok-input"); var result = block.querySelector(".dp-ask-grok-result"); var send = block.querySelector(".dp-ask-grok-send"); var form = block.querySelector(".dp-ask-grok-form"); var button = block.querySelector(".dp-ask-grok-button"); var intro = block.querySelector(".dp-ask-grok-intro"); var question = (input.value || "").trim(); if (question.length Please ask a question of at least 10 characters."; return; } if (question.length > 500) { result.innerHTML = ""; return; } result.innerHTML = ""; send.disabled = true; result.setAttribute("aria-busy", "true"); fetch(block.dataset.restUrlAskGrok, { method: "POST", headers: { "Content-Type": "application/json", "X-WP-Nonce": block.dataset.nonce }, body: JSON.stringify({ post_id: parseInt(block.dataset.postId, 10), question: question }) }) .then(function(r){ return r.json().then(function(data){ return { status: r.status, data: data }; }); }) .then(function(resp){ if (resp.status === 429) { if (form) form.style.display = "none"; if (intro) intro.style.display = ""; if (button) { button.style.display = ""; button.disabled = true; button.setAttribute("title", "Daily limit reached. Try again tomorrow."); button.textContent = "Daily limit reached"; } var rateMsg = (resp.data && resp.data.message) ? resp.data.message : "You\u2019ve reached today\u2019s question limit. Please try again tomorrow."; result.innerHTML = ""; return; } if (resp.status === 403) { result.innerHTML = ""; return; } if (resp.status === 200 && resp.data && resp.data.success) { var safeAnswer = dpSimilarEscape(resp.data.answer || ""); var safeDisclaimer = dpSimilarEscape(resp.data.disclaimer || ""); var answerHtml = ""; result.innerHTML = answerHtml; if (form) form.style.display = "none"; if (intro) intro.style.display = ""; if (button) { button.style.display = ""; button.disabled = true; button.setAttribute("title", "Daily limit reached. Try again tomorrow."); button.textContent = "Daily limit reached"; } return; } if (resp.status === 200 && resp.data && !resp.data.success) { var msg = dpSimilarEscape(resp.data.message || "Could not process your question right now."); result.innerHTML = ""; return; } result.innerHTML = ""; }) .catch(function(){ result.innerHTML = ""; }) .then(function(){ if (send) send.disabled = false; result.removeAttribute("aria-busy"); }); } function dpSimilarRender(output, keyword, data) { var html = ""; if (data.count === 0) { html += ""; } else { html += "

Articles matching “" + dpSimilarEscape(keyword) + "”

"; html += "

"; data.results.forEach(function(r){ html += "
• "; html += "" + r.title + ""; html += "" + r.date + ""; html += "
"; }); html += "

"; } html += dpSimilarCta(output, data.count); output.innerHTML = html; } function dpSimilarCta(output, count) { var block = output.closest(".dp-similar-block"); var contactUrl = block ? block.dataset.contactUrl : ""; if (!contactUrl) { return ""; } var ctaText; if (count === -1) { ctaText = "While you wait, here are some other ways to get help:"; } else if (count === 0) { ctaText = "Couldn\u2019t find what you needed? Speak with a professional for personalized help."; } else { ctaText = "Need more help with this topic? Speak with a professional."; } var html = ""; return html; } function dpSimilarEscape(s) { var div = document.createElement("div"); div.textContent = s; return div.innerHTML; }})();