TC 810: Refund Freeze — the -E Freeze

What the code actually does

TC 810 sets the -E freeze on an individual (IMF) account. Per IRM 21.5.6.4.10, "Transaction Code (TC) 810 is placed on an IMF account by Compliance or Return Integrity and Compliance Services (RICS)," and "a -E freeze prevents generated offsets into the module" in addition to blocking a straight refund. Document 6209 states the scope even more broadly: TC 810 acts "to freeze the module from refunds, offsets and credit elect" — all three ways an overpayment could otherwise leave the module are stopped at once.

Unlike TC 570's -R freeze, which IRM 21.5.6.4.35 ties to a specific module-level pending item, TC 810 comes from Compliance or RICS review — a different part of the IRS's process, and one the IRM's own resolution table treats as effectively out of an ordinary caseworker's hands. IRM 21.5.6.4.10 states this directly for a phone assistor working the case: "Master File account has a TC 810[:] You cannot resolve it." The freeze only comes off through the function that put it on.

The Responsibility Code framework — RC 1 through RC 4

TC 810 always carries a Responsibility Code (what Document 6209 calls a "Code," same field, different name), and that code is what tells a practitioner which of several very different reviews is actually holding the refund. Per IRM 21.5.6.4.10, verbatim: "TC 810 RC 1 indicates pre-filing notification. Refer to IRM 21.5.10.4.1.2, Compliance Refund Hold Projects." The IRM does not rank the four Responsibility Codes by severity, and this page does not either — RC 1's own cross-referenced subsection covers a distinct compliance project this page did not independently verify, so what "pre-filing notification" specifically entails procedurally is outside its scope.

"TC 810 RC 2 indicates an Abusive Tax Shelter Detection (ATSDT) freeze" — a hold connected to the IRS's abusive-shelter enforcement program. "TC 810 RC 3" covers a cluster of credit-specific fact patterns the IRM lists together: an Earned Income Tax Credit freeze accompanied by TC 424, an EITC-plus-Additional-Child-Tax-Credit combination, several Premium Tax Credit variations tied to specific TC 570 blocking series, and an American Opportunity Tax Credit freeze — each one built around a particular refundable-credit claim under review rather than a blanket "the whole return is suspect" hold.

RC 4 is its own subsection. Per IRM 21.5.6.4.10.1, "Transaction Code (TC) 810 Responsibility Code (RC) 4 is a preventative freeze in Return Integrity Verification Operations (RIVO) to screen for potential frivolous return criteria." Once RIVO makes a frivolous determination, the taxpayer gets Letter 3176C, Frivolous Returns Response — the point at which the freeze finally has a stated reason attached to it, per the same subsection. The current IRM text also defines additional Responsibility Codes beyond RC 4 (an entity-fabrication review code and a general RICS preventative-freeze code); this page covers only RC 1 through RC 4, per its own scope, and does not claim that list is exhaustive.

How long RC 4 cases actually run

This is the one place worth citing real-world figures rather than IRM procedure alone, because the gap between what the IRM says and what actually happens is large and TAS has measured it directly. Per the Taxpayer Advocate Service's 2024 Annual Report to Congress, "Transaction code (TC) 810-4 is only used if a return meets potentially frivolous return criteria," and refund volume frozen under that code "increased tenfold from 2020 to 2021" — from roughly 61,000 returns for tax year 2020 to almost 620,000 for tax year 2021. TAS reports that, as of the end of FY 2024, "approximately 739,000 taxpayers were still waiting for resolution of their frozen refund," and for the first tax year this specific code was used, "taxpayers waited an average of 570 days (more than 1.5 years) for the IRS to release their refund."

These are IRS-reported figures about a specific historical cohort, not a rule about how long any individual RC 4 case will take, and this page does not treat them as one. What they do establish is that RC 4 is not a routine hold that clears in a few weeks — it is the freeze most worth setting realistic expectations around before promising a client anything about timing.

What TC 810 gets confused with

TC 810 is most often confused with TC 570, and the confusion is understandable — both stop a refund cold and both sit on a transcript without much explanation. The real difference is who set the freeze and why. TC 570's -R freeze usually traces to a specific, module-level pending item — a missing document, a payment mismatch, an open TDI — and IRM 21.5.6.4.35.2 documents a resolution table an ordinary caseworker can act on. TC 810's -E freeze traces to Compliance or RICS review, and per IRM 21.5.6.4.10 itself, an ordinary caseworker "cannot resolve" a TC 810 at all — only Responsibility Code research and the right referral path move it forward. See TC 570 for that freeze's own release mechanism.

TC 810 is also worth distinguishing from TC 130, the V- freeze covered elsewhere in this library. TC 130 freezes an entire account because of a liability the IRS says exists on a different account entirely — a debt somewhere else on record. TC 810 freezes a module because of a compliance question about the return itself — the shelter, the credit combination, or the frivolous-return screen tied to the specific Responsibility Code. Both stop refunds; the underlying question each one is actually asking is different.

Finally, TC 420 and TC 424 are real IRM-documented Examination-referral codes — per IRM 21.5.6.4.10's own text, "TC 424 or TC 420 identifies Exam involvement" on a -E freeze module, and they appear directly in the RC 3 credit-combination patterns above. But TC 420/424 sets a separate freeze of its own, the -L (Open Examination Indicator) freeze, which IRM 21.5.6.4.24 states "does not freeze the account" the way -E or -R do — it is an examination flag that can accompany a TC 810, not a substitute for one.

The practitioner's actual next step

Pull the Responsibility Code before advising a client on anything — timing, next steps, or how serious the hold actually is. RC 1 and RC 2 point toward compliance-project or shelter-detection research; RC 3 points toward a specific refundable-credit combination worth reviewing on the return itself; RC 4 points toward RIVO's frivolous-return screen, where the taxpayer should be watching for Letter 3176C rather than expecting the freeze to lift on a normal processing timeline.

Because an ordinary caseworker cannot resolve a TC 810 directly, the practical next step is almost always identifying the right referral path for the specific Responsibility Code rather than requesting a routine account adjustment — a TC 290 that would clear a TC 570 does nothing to a TC 810.

If an RC 4 hold is causing the client genuine hardship — a threatened eviction, a shutoff notice, an inability to cover basic living expenses — the Taxpayer Advocate Service is a parallel option even while the RIVO review is still pending: file Form 911, Request for Taxpayer Advocate Service Assistance, describing the hardship. TAS can act on significant hardship independent of how the underlying frivolous-return review eventually resolves.

What this means for your refund

A TC 810 on your transcript means a specific part of the IRS — not the general processing pipeline — is holding your refund for review, and it is not something that resolves through the usual "wait 21 days" refund timeline. Which reason code is attached (you may not be able to see this directly on your own transcript, but a practitioner can research it) tells you which kind of review is actually happening.

If your hold is tied to a frivolous-return screen, the Taxpayer Advocate Service has reported that these cases can run well over a year to resolve, so it is worth watching for any IRS letter closely rather than assuming a quick turnaround. The IRS Transcript Decoder can help you see exactly what a TC 810 and any codes around it mean for your account.