TC 971: Miscellaneous Transaction (Notice or Other Account Action)

By Forrest Baumhover, CFP®, EA · Last verified August 28, 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 always means the same thing — a refund was released — 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.

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 "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, suppresses notices, TDA/BAL DUE, TDI/DEL RET" — notice suppression, not notice issuance, from the same base transaction code.

IRM 21.5.6 supplies more of the same pattern from day-to-day account activity. TC 971 AC 010 or AC 012–016 is tied to duplicate-return handling and, in some circumstances, generates a CP 36 or CP 193 notice. TC 971 AC 128 "identifies RICS AQC involvement" — an Automated Questionable Credit review, nothing to do with a routine notice at all. And per IRM 21.4.1.5.7, a taxpayer who asks to cancel a direct deposit before it releases gets a TC 971 AC 850, which "stop[s] the direct deposit" — a transaction code that, in that instance, has nothing to do with a mailed notice whatsoever. Four Action Codes, four unrelated outcomes: a freeze, a duplicate-return notice, a credit-fraud review flag, and a stopped deposit. That range is the reason this page will not tell you what a TC 971 on your transcript means — it depends entirely on the Action Code attached to it, and that code is not something this page, or any general reference, can guess.

How to actually tell which notice a TC 971 refers to

The honest answer is narrower than "read the transcript." IRM 21.5.6 documents the mechanism IRS itself uses internally: a TC 971 posting carries its Action Code, and for at least Action Code 123 (correspondence sent), the specific letter number is recorded in a companion field, verbatim, "TC 971 AC 123 with the letter number in the MISC field" — with a worked example reading "TC 971 AC 123 MISC XXXXC Sent." That is a real, documented answer to "how does the system know which letter this was." It is also, per the same IRM language, a field that shows up "on the CC TXMOD" — an IRS-internal research screen, not the account transcript a taxpayer downloads through their online account or a practitioner pulls through e-Services. In practice, the AC and MISC detail behind a given TC 971 usually is not something you can read directly off the transcript in front of you.

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 it gets confused with. There is no separate "identify my TC 971" lookup tool, in this library or anywhere else verified for this page; 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 the fastest way to see how the codes around a TC 971 fit together, rather than trying to read one line in isolation.

What TC 971 gets confused with

TC 972 is easy to mistake for evidence that whatever a TC 971 announced got undone. 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.

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.

The practitioner’s actual next step

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 the notice itself cannot be located and the transcript alone will not resolve it, that is the point to call the Practitioner Priority Service line (the IRS's dedicated phone line for credentialed representatives, reachable only with a valid power of attorney on file) and ask specifically for a CC TXMOD pull on the module — the same command code this page cites above as where the Action Code and MISC-field detail actually live — rather than guessing from the transaction code alone. That detail lives on IRS-internal screens this page does not have access to, and neither does a standard account transcript, but an authorized representative calling in can ask an assistor to read it directly.

Sources