How to Read an IRS Account Transcript: A Practitioner’s Walkthrough
IRS transcript is the record most resolution decisions actually get made from, and it’s also the one most likely to get misread. The codes aren’t self-explanatory, the layout doesn’t tell you what matters, and a missed freeze code or a misunderstood reversal can send a case down the wrong path before the client ever sees a resolution option. This is a section-by-section read of what’s actually on the page and what each part means for the case you’re working on.
What an Account Transcript Actually Tells You (and What It Doesn’t)
Of the transcript types practitioners pull, the account transcript is the one that shows the account’s live status, not just what was filed. A return transcript confirms what the client reported. A wage and income transcript confirms what third parties reported. The account transcript is the only one that shows balance history, penalty and interest accrual, collection activity, and the transaction codes that reveal what the IRS has actually done, or is currently doing, with the account.
That distinction matters for resolution work specifically. You can know exactly what a client filed and still have no idea whether the account is in currently-not-collectible status, sitting under an active bankruptcy freeze, or approaching a CSED that’s been tolled twice. All of that lives in the account transcript.
The Header Block: Confirming You’re Looking at the Right Account
Before reading a single transaction code, check the header. It carries the tax period, a partial taxpayer ID reference, filing status, and a tracking number. This sounds obvious, but pulling the wrong year, or misreading a joint account as a separate one, is a common source of downstream errors. Confirm the header matches the case you’re working on before drawing any conclusions from what follows.
Reading the Transaction Code Section Line by Line
This is the core of the transcript. Each entry follows the same structure: a three-digit transaction code, a plain-language explanation, a cycle date, and a dollar amount where applicable. Several of these codes have a manually assessed version and a systemically generated version; the table below flags the pair where it matters, since the systemic version is usually the one you’ll actually see on a transcript.
| Transcript Code | What It Means | Why It Matters for the Case |
| TC 150 | Return filed and liability assessed | Confirms the base assessment exists and starts the clock on the original CSED |
| TC 160/166 | Failure-to-file penalty | 160 is the manually assessed version; 166 is what typically posts on an account transcript, with 167 as its reversal if the penalty is later abated |
| TC 170 | Estimated tax penalty | Confirms an ES penalty was computed; compare against what the client reports paying quarterly |
| TC 190/196 | Interest assessed | 190 is the manual version used on quick or prompt assessments; 196 is the systemic version most practitioners will actually see |
| TC 270/276 | Failure-to-pay penalty | 270 is the manual version; 276 is the systemic version that typically posts, relevant to any FTA or penalty abatement review |
| TC 290 | Additional tax assessed | A multi-use code. A dollar amount next to it is a real new assessment; a $0 entry is often a verification marker or a rejected abatement request, not new liability. Check for a nearby explanatory code (like a return amendment or income review marker) before assuming an audit |
| TC 420/424 | Examination indicator/examination request | Signals the account is or was under audit review, which can affect resolution timing |
| TC 460 | Extension of time to file | Carries the extended due date; check before flagging a return as late, and note it can interact with statute dates |
| TC 480 | Offer in compromise pending | Account is under OIC review; collection activity is generally suspended during this period |
| TC 520 | Bankruptcy or litigation freeze | Collection is frozen; the CSED is tolled for the duration plus additional time depending on the filing |
| TC 530 | Currently not collectible | Account has been marked CNC; no active collection, but the balance and CSED clock continue |
| TC 570/571 | Additional liability hold/hold released | 570 freezes the account pending review; 571 shows the hold has been lifted; don’t treat a 570 as resolved until a 571 appears |
| TC 582 | Notice of federal tax lien filed | Confirms a lien is on record, relevant for negotiating any resolution option |
| TC 971 | Miscellaneous transaction, notice issued | A placeholder code with no fixed meaning on its own; it always carries an Action Code that defines what actually happened, so don’t treat the bare code as informative by itself |
Read codes in cycle-date order, not the order they happen to appear on the page layout. A code that looks current may have already been reversed by a later entry.
Where CSED-Relevant Dates Actually Live
Don’t assume a standard 10-year collection statute from the original assessment date. Several events on the transcript toll or extend the CSED, and each one has to be read off the transcript directly rather than calculated from memory:
- A pending installment agreement request tolls the CSED for the entire time the request is pending, not just when it’s rejected. If the IA is later rejected, the CSED is suspended an additional 30 days; if the client defaults and the IRS proposes termination, that adds another 30-day suspension; and if the client appeals either the rejection or the termination, the CSED stays tolled through the appeal. This is one of the most common tolling events in resolution work and one of the easiest to undercount, since it applies even when the IA is eventually approved, not only when it falls through.
- A bankruptcy freeze (TC 520) tolls the CSED for the entire time the bankruptcy is pending, from petition to discharge, dismissal, or closing, plus an additional 6 months after the case concludes.
- A pending offer in compromise (TC 480) tolls the CSED from the date the offer is pending to the date it’s accepted, returned, withdrawn, or rejected. If rejected, add another 30 days; if the client appeals the rejection, the CSED stays tolled through the appeal.
- A CDP hearing request tolls the CSED from the date the IRS receives the request to the date the client withdraws it or the determination becomes final, including any court appeals. If fewer than 90 days remain on the CSED when the determination becomes final, the CSED is extended out to a full 90 days from that date.
- An innocent spouse claim tolls the requesting spouse’s CSED from the date the claim is filed until the earlier of a filed waiver or the expiration of the 90-day Tax Court petition window (or, if petitioned, the date the Tax Court decision becomes final), plus an additional 60 days in each case.
Common Misreads That Lead to Bad Case Decisions
Treating a pending code as resolved. TC 480 (OIC pending) and TC 530 (CNC) are both statuses, not endpoints. A case isn’t closed just because one of these codes appears; the resolution has to actually process through to a final code before you build the rest of the case around it.
Reacting to every TC 290 as a new liability
A TC 290 with a dollar amount is a real assessment. A TC 290 at $0 is frequently just a verification marker or a rejected abatement request. Check the amount, and check for a nearby explanatory code, before telling a client their balance changed.
Missing a freeze code entirely
A 570 buried mid-transcript is easy to skip if you’re scanning for the “interesting” codes. Any freeze code changes what collection actions are actually available right now, regardless of what the rest of the transcript suggests.
Misreading a reversal
IRS transcripts don’t delete entries; they reverse them with a new transaction. If you only read the original code and miss the reversal further down, such as a 166 without checking for a 167, you’ll misstate the account’s actual status to the client.
Assuming the CSED from the assessment date alone
Covered above, but worth repeating as its own failure mode: this is the single most common transcript misread in resolution practice, and it’s the one most likely to produce a wrong recommendation to a client.
Where This Fits Into Your Case Workflow
A manual line-by-line read like this is still the right instinct, but it doesn’t need to be the entire job every time. Once transcripts are pulled through TaxVero, Taxometrics surfaces the transaction codes, freeze indicators, and CSED-relevant dates directly, so the manual read becomes a verification step on top of the analysis rather than the only place that analysis happens. That matters most on multi-year accounts, where tracing every tolling event and penalty pairing by hand across a decade of transcript history is exactly the kind of work most prone to the misreads above.
Stop tracing transaction codes and CSED tolling events by hand. See how Taxometrics surfaces them automatically from every transcript pull.
FAQs
What does TC 570 mean on an account transcript?
TC 570 places a hold on additional liability or a pending action on the account. Look for a corresponding TC 571 later in the transcript to confirm the hold has been released.
How do you find the CSED on an IRS account transcript?
Start with the original assessment date from TC 150, then trace every tolling event on the transcript, including bankruptcy freezes, pending offers in compromise, and CDP hearing requests. Each of these can extend the collection statute beyond the standard 10-year period.
What’s the difference between an account transcript and a return transcript?
A return transcript shows what the client originally filed. An account transcript shows the account’s live status, including balance history, transaction codes, and collection activity, which is what practitioners need for resolution work.
Does a TC 290 always mean the client was audited?
No. TC 290 is a multi-use code that can reflect a real additional assessment, a verification marker, or a rejected penalty abatement request. Whether it means an audit depends on the dollar amount and any nearby explanatory codes, not the code alone.
Why would a transaction code appear and then get reversed?
The IRS doesn’t delete transcript entries. When a status changes, a new transaction code is added to reverse or update the prior one. Reading only the original code without checking for a later reversal is a common source of errors.
Can a case be marked currently not collectible and still have collection risk later?
Yes. CNC status (TC 530) pauses active collection, but the balance remains, and the CSED clock continues to run. The account can move out of CNC status if financial circumstances change.
