TC 971: Miscellaneous Transaction (Notice or Other Account Action)
By Forrest Baumhover, CFP®, EA · Last verified September 14, 2026
TC 971 is one of the few codes on a transcript with no fixed meaning of its own — it is a generic wrapper for a companion Action Code that decides what actually happened, from a mailed notice to a frozen refund to nothing more than a stopped direct deposit.
What the code actually does
Document 6209's entire base definition of TC 971 is a single sentence, and it is worth reading literally rather than skimming past: it is a "Miscellaneous Transaction" that "[p]erforms different actions based on the Action Code which are listed separately." Unlike a code such as TC 846, which records a refund the IRS scheduled for release, TC 971 by itself does not describe an event. It describes a category of events, and the three-digit Action Code (AC) that rides along with every TC 971 posting is what actually tells you which one occurred.
Most transcript tools and most transcripts themselves print TC 971 with a generic literal like "Notice issued." That literal is accurate as far as it goes — many Action Codes do correspond to a notice or letter going out — but treating "Notice issued" as the code's meaning skips the one detail that actually matters: which notice, about what, and whether it affects anything you care about.
Two Action Codes about penalty history, not a notice: 995 and 996
Two Action Codes worth knowing by number are the clearest illustration of why a TC 971 has no fixed meaning, because neither one is itself a notice. When AEP posts a 996, the IRS mails a separate notice (a CP95 or CP195B). The codes themselves are not new: IRM 20.1.1.3.3.2.4, Compliance and Administrative Penalty Relief Action Codes, has been live on IRS.gov since 07-05-2024 and has documented TC 971 AC 995 and AC 996 since then, under the older First Time Abate (FTA) program. What is new is the program built on top of the same two codes: IRM Procedural Update SBSE-20-0626-0643 (June 17, 2026) establishes Automatic Exemption from Penalty (AEP), which formally replaces FTA — reusing AC 995 and AC 996 rather than introducing new ones — for eligible original returns due January 1, 2027 and after, with a transition beginning summer 2026 for tax year 2025 and 2026-quarter returns. The AEP rules below come from that update, because the published IRM has no numbered subsection for them yet (the update calls it IRM 20.1.1.3.3.2.5); this page cites the update for AEP and IRM 20.1.1.3.3.2.4 for the two codes. Under ¶11, TC 971 Action Code 995 is the per-year compliance marker in Master File (the IRS’s central account-processing system): it records that one module, for one return type, met the filing-and-paying test for that period. It is not relief, it is not a notice, and by itself it says nothing about the year you are looking at — it is a vote that Master File counts when it processes a later return.
TC 971 Action Code 996 is the one that means relief actually happened. Update ¶12 says an unreversed 996 shows the IRS granted AEP or a prior First-Time Abate. Under ¶14, when the IRS grants AEP, Master File posts it, records the suppressed penalty type and amount in the MISC field, and on a married-filing-joint return posts it to the secondary TIN as well. Per ¶15, an unreversed 996 does more than record history — it blocks future failure-to-file, failure-to-pay, and failure-to-deposit accruals and assessments on that module going forward, to the point that the IRS balance screen (command code INTST) will display $0.00 for accrued, assessed, and total failure-to-pay penalty. The block also reaches manual adjustments that would add those penalties to the module (¶(15) Note), though other penalty types may still apply (¶(16)). If First-Time Abate was granted on an unpaid module, the IRS uses reason code 062 and the failure-to-pay penalty keeps running until you pay (IRM 20.1.1.3.3.2.1 ¶(14)). That is why 995 and 996 are worth telling apart precisely: a 995 on an earlier year helps you qualify; a 996 on an earlier year blocks the next grant (unless the IRS later reverses it with a TC 972 AC 996 because the penalty was not owed, IRM 20.1.1.3.3.2.4 Example 3), because ¶12 says Master File will not grant AEP if any of the three lookback modules carries an unreversed 996, and ¶17 restarts the three-year clock once one posts. For a First-Time Abate grant, IRM 20.1.1.3.3.2.4 describes the code only for tax years 2022 and later on Forms 1040, 940, 941, 943, 944 and 945, so a missing 996 proves nothing for other years or forms.
Two consequences follow that a transcript alone will not spell out. First, per ¶13, a module built from a Substitute for Return or completed under IRC 6020(b) procedures — agreed or unagreed — is not treated as compliant and should not carry a TC 971 A/C 995 at all, so a year the IRS filed for the taxpayer does not count toward the three even though a return technically posted. Second, per the Note to ¶20, the reverse also happens: if a penalty is abated for reasonable cause and no other penalty remains on the module, the module reads as compliant again and Master File should post a subsequent TC 971 A/C 995 — a successful reasonable-cause request can therefore repair a prior year’s eligibility rather than only clearing that year’s bill. Neither of those is visible as a code; both change what the codes mean.
For what a taxpayer actually receives when AEP posts a 996, see CP95 for an individual account. For the case where a return qualified and the 996 never posted because of an IRS processing error, see What Happens if You Qualified for AEP but an IRS Error Blocked It.
Why "Notice Issued" isn’t the whole story
Document 6209's own freeze-code summary table shows just how far apart two TC 971 postings can be. One entry: the "E-" Amended Return freeze (IRM 21.5.6.4.2 calls it the -A freeze) "is also set when a TC 976 is generated from the posting of a TC 971 with action code 10 or 12-15" — tied to duplicate or amended return processing, and it freezes the module from refunding or offsetting. A separate entry, for a completely different Action Code range: the "-O" Disaster freeze, "set by TC971 AC 86 or 87," which "[c]auses unique penalty and interest processing" and "suppresses notices" — notice suppression, not notice issuance, from the same base transaction code.
IRM 21.5.6.4.2 supplies more of the same pattern from day-to-day account activity — and its -A Freeze section shows the Action Code does not always generate the notice. TC 971 AC 010 or AC 012–015 sets the -A freeze tied to amended-return handling, and the IRM is explicit that these Action Codes do not generate a CP 36, and AC 010 generates a CP 193 only in some cases: "Exception: TC 971 AC 010 or AC 012-016 does not generate a CP 36. TC 971 AC 010 generates a CP 193 only in certain situations." The duplicate or amended return actually posting — TC 976 or TC 977 — is what generates the CP 36 (individual) or CP 193 (business) duplicate-filing notice for those codes, and Document 6209 corroborates that split independently: its TC 976 (IMF) entry reads "CP 36, Notice of Duplicate Return is issued," and its TC 976 (BMF) entry reads "CP 193 will be issued unless unreversed TC 420 or 424 posted" — both tied to the TC 976 posting itself, not to the Action Code on the TC 971 that set the freeze ahead of it. TC 971 AC 128 "identifies RICS AQC involvement" — the IRS Return Integrity and Compliance Services (RICS) Automated Questionable Credit review, nothing to do with a routine notice at all.
TC 971 AC 850 is one example of the range: IRM 21.4.1.5.7 labels it "Flip direct deposit to paper," yet it posts when a taxpayer asks to stop a pending direct deposit, when an Online Account user lists a reason a bank account is not an option, when the IRS cannot validate a bank account entered there, and when an IRS employee corrects a deposit that reached the wrong account. That range is the reason this page will not tell you what a TC 971 on your transcript means: it depends on the Action Code attached to it, and sometimes on the circumstance behind that code.
How to actually tell which notice a TC 971 refers to
You usually cannot tell which letter a TC 971 line records by reading your transcript. IRS employees can: for some identity-protection letters sent before November 2022, IRM 21.5.6.4.9.1 says the CC TXMOD screen (an IRS-internal research screen) may show a TC 971 AC 123 with the letter number in the "MISC field," a companion field on the posting. The account transcript you download through your online account, or that is available through e-Services, usually does not show it.
What is practical: match the date. The date next to a TC 971 line on the transcript is the same date the underlying notice or letter was generated, so lining that date up against the notice you actually received in the mail — or against the "Notices and Letters" section of your IRS Online Account, where select notices are available as digital copies — is the reliable way to connect a specific TC 971 to a specific piece of correspondence. If more than one TC 971 posted around the same time, match each one to its own notice by date rather than assuming the most recent notice explains all of them.
Once you know which notice you are actually holding, the IRS Notice Library is where to look it up — what triggered it, the real deadline, and what people mistake it for. There is no separate "identify my TC 971" lookup tool; the notice itself, once identified by date, is the thing to research.
What this means for your refund
A TC 971 by itself does not tell you anything about whether your refund is affected. Some Action Codes freeze a refund; a much larger number have nothing to do with a refund at all — an identity-verification letter, a duplicate-return notice, a stopped direct deposit you requested yourself, or routine correspondence about something already resolved. Seeing "Notice issued" next to a 971 is not, on its own, a reason to expect a delay, and it is not a reason to assume everything is fine either — the only way to know which applies is to find the actual notice tied to that date and read what it says.
If a TC 971 is sitting near other codes on your transcript — a hold, a freeze, or a TC 846 that has not posted when you expected it to — the combination usually tells the real story better than any single code does. Running the whole transcript through the IRS Transcript Decoder is a direct way to see how the codes around a TC 971 fit together, rather than trying to read one line in isolation.
What people mistake TC 971 for
TC 972 leads readers to think it cancelled whatever a TC 971 announced. It is not that broad. Document 6209 defines TC 972 narrowly: it "[r]everses Amended/Duplicate Return" activity and is "[u]sed to reverse TC 971." A TC 972 tells you the miscellaneous transaction itself was reversed — often because it was input in error, or the specific condition it recorded no longer applies — not that the notice named in the original TC 971 was withdrawn, that its deadline moved, or that whatever it warned about went away. Treat a TC 972 as "the marker was corrected," not as "the underlying issue is resolved," unless the actual notice or a follow-up transaction says otherwise. One case helps the client: if First-Time Abate used up the 996 on a penalty that a payment the IRS found later erased, the IRS can post a TC 972 AC 996 to reverse the 996, and First-Time Abate is then available again the next year (IRM 20.1.1.3.3.2.4, Example 3).
TC 976 and TC 977 are also easy to fold into TC 971 because Document 6209's own freeze-code table ties them together procedurally: an amended or duplicate return posting can be created "from the posting of a TC 971 with action code 10 or 12-15." But TC 971 in that sequence is the administrative marker — the notation that duplicate-filing correspondence went out — while TC 976 (or TC 977) is the actual posting of the second return itself, the transaction that puts new figures on the account. Seeing both on the same transcript is normal and expected for a duplicate-filing scenario; reading the 971 as if it were the return posting, or the 976/977 as if it were just paperwork, gets the sequence backward.
What to do next
Do not advise a client based on the word "notice" alone. Pull the date next to the TC 971, match it to the actual notice or letter the client received (or to the Notices and Letters section of their IRS Online Account if the physical copy is missing), and read that document before saying anything about deadlines or next steps. If the client has more than one TC 971 in a short window, match each one individually rather than assuming they all point to the same notice.
If you cannot find the notice and the transcript does not answer it, call the Practitioner Priority Service line (open to any tax professional with a Form 2848, 8821 or 8655 on file) and ask the IRS phone representative what the TC 971 dated that day records, rather than guessing from the transaction code alone. The MISC-field detail, such as the AC 123 letter number on letters sent before November 2022, sits on the IRS-internal CC TXMOD screen this page cites above, and a standard account transcript usually does not show it. The representative may or may not read them to you.
Sources
- IRS Document 6209, Section 8A (Master File Codes) — TC 971, 972, 976/977 freeze-table entries (CP 36/CP 193 tied to the TC 976 posting, not to TC 971)
- IRM 21.5.6 — Freeze Codes (TC 971 Action Code and MISC-field mechanics; 21.5.6.4.2, -A Freeze, states the CP 36/CP 193 exception for AC 010/012-016)
- IRM 21.4.1 — Refund Research (TC 971 AC 850, "Flip direct deposit to paper" — taxpayer-request, taxpayer-selected-waiver, automatic-validation-failure, and employee-correction triggers, 21.4.1.5.7 and 21.4.1.5.8.1)
- IRS.gov — Online Account for Individuals, Frequently Asked Questions (Notices and Letters section)
- IRM 20.1.1.3.3.2.4 — Compliance and Administrative Penalty Relief Action Codes (base TC 971 AC 995/996 mechanics, live on IRS.gov since 07-05-2024, under the First Time Abate program AEP now replaces)
- IRM Procedural Update SBSE-20-0626-0643 (June 17, 2026) — establishes Automatic Exemption from Penalty (AEP) eligibility criteria reusing TC 971 Action Codes 995 and 996; not yet folded into a published IRM subsection