TC 150: Return Filed and Tax Liability Assessed

What the code actually does

TC 150 is the transaction that posts the return itself. Document 6209 files it under the title "Return Filed & Tax Liability Assessed" and states its function in one sentence: "A tax liability assessed from the original return establishes a tax module." Everything that follows on a transcript — a withholding credit, a refundable credit, a refund, an audit adjustment — posts against a module that TC 150 is usually the transaction that creates. It is coded as a debit, which is the detail worth holding onto: TC 150 records what the taxpayer reported owing, not a payment or a credit. The credits that follow it, including TC 806, TC 766, and TC 768, exist to offset that debit — which is why those four codes tend to appear together near the top of almost every individual transcript.

A second, less obvious job belongs to the same code. Where a taxpayer has never filed before, Doc 6209 states that TC 150, "when posted to the Entity Transaction Section... indicates the Master File Entity was created from the posting of the return." In other words, TC 150 is not only how an existing account gets its return; for a first-time filer, it is also the transaction that brings the account itself into existence. And because TC 150 posts the numbers exactly as the taxpayer self-reported them, it says nothing yet about whether the IRS agrees with those numbers — that is a separate question, answered later by codes like TC 290 or TC 300 if the return is examined or adjusted, not by TC 150 itself.

When TC 150 hasn't posted

The absence of TC 150 is itself the finding, and it means exactly what it looks like: the IRS has no record of an original return for that module. IRM 21.5.1.4.3.1.1, Missing Returns, is direct about what an employee does next: "Research to see if the original return posted elsewhere, such as a different TIN or tax period. Contact the taxpayer by telephone or correspondence to determine where, when, and how the return was filed. Request a signed copy of the return, if necessary. Allow the taxpayer 40 days to reply (70 days if taxpayer is overseas)." A practitioner staring at a blank space where TC 150 should be is looking at the same research problem the IRS itself works through — confirm the return actually reached the IRS, under the right identifying number and tax period, before assuming anything about penalties or nonfiling.

The dedicated research procedure for exactly this problem, IRM 21.6.7.4.2, Locate an Original Return (TC 150), lists the IDRS command codes that answer the "did it actually post somewhere" question — CC FFINQ for a return still in processing, CC SUMRY, CC TRDBV, CC RTVUE, CC IMFOL, and CC ENMOD for current-year account data, and CC NAMES, CC INOLE, and CC ATINQ for a return that may have posted under a different identifying number entirely. That same subsection adds a filing-season caveat worth remembering before assuming the worst: "If TC 610 (remittance with return) posted, the return may be in-house awaiting processing" — a payment on the module with no TC 150 yet can simply mean the return hasn't finished processing, not that it never arrived.

Why TC 150's date doesn't answer both statute questions

TC 150 is the event that starts the collection clock. Because Doc 6209 defines TC 150 itself as the transaction that assesses the tax liability, its posting date functions as the assessment date, and IRC §6502 runs the ten-year Collection Statute Expiration Date — the CSED, the deadline by which the IRS must collect an already-assessed balance — from that same assessment. Read the TC 150 date off the transcript, and that is the date the CSED clock actually started.

The Assessment Statute Expiration Date (ASED) works differently, and conflating the two is the mistake worth avoiding. IRC §6501(a) ties the general three-year assessment window to when "the return was filed" — not to when TC 150 happens to post weeks later once the return finishes processing. IRM 25.6.1.6.14, Criteria for Establishing a Statute of Limitations Period, states the distinction the IRS itself works from: "The Received Date does not necessarily establish the filing date. The filing date is established after applying IRC rules." For a normally processed return the filing date and the TC 150 posting date usually sit close together, but they are two different events in the source, and the ASED calculation belongs to the filing date, not to whatever date happens to print next to TC 150 on the transcript. "General" is doing real work in that first sentence: the same statute removes the limit entirely where IRC §6501(c) applies — "a false or fraudulent return with the intent to evade tax" or "failure to file a return" — and extends it to six years under IRC §6501(e) for a gross income omission "in excess of 25 percent of the amount of gross income stated in the return." A TC 150 on the transcript confirms a return posted; it says nothing about which of these windows actually governs the account, and that determination has to come from the underlying facts, not from the transaction code.

What this means for your refund

Think of TC 150 as the on-ramp. Until it posts, a module generally has nowhere for a withholding credit, a refundable credit, or a refund to land — which is why a transcript pulled too early in the season, before TC 150 shows up, can look empty even though a return was filed weeks earlier and a W-2's withholding is sitting in IRS records waiting to be credited. Once TC 150 posts, the credits that offset it — the withholding amount, any refundable credits like the Earned Income Credit — post in the same general window, and only then does a refund transaction have a completed liability to net against. If a transcript is confusing to read on its own, the IRS Transcript Decoder walks through what each line, including TC 150, actually means for a specific account.

What TC 150 gets confused with

A second return hitting an already-established module does not post as a second TC 150 — it posts as TC 976. Doc 6209's own entry is specific: "Identifies the input return which causes a duplicate posting condition. TC 150 is replaced with TC 976 by computer... Tax module is frozen from offsetting and refunding until released by an Examination (TC 30X) or DP Tax (TC 29X) Adjustment." A practitioner who sees TC 976 and expects it to behave like a second original return will be surprised: the module freezes from offset and refund the moment TC 976 posts, and stays frozen until an examination or adjustment transaction releases it — a materially different posture than the one a fresh TC 150 creates on its own.

TC 150 is also easy to read as a statement about correctness rather than what it actually is — a posting of the taxpayer's own self-reported numbers. A zero-balance TC 150 does not mean the IRS reviewed the return and found nothing wrong; it means the return as filed produced no additional liability. Whether the IRS later disagrees is an entirely separate question, answered by later transaction codes on the same module, not by TC 150 itself.

The practitioner's actual next step

If TC 150 is missing, confirm the return actually reached the IRS — under the correct TIN and tax period — before advising a client on nonfiling exposure or drafting a late-filing penalty argument that may not even apply to a return the IRS never received. The IRM's own 40-day (70-day overseas) reply window is a useful benchmark for how long that confirmation reasonably takes.

The one-line version worth repeating to a client or a colleague without notes: TC 150 starts the clock to collect what's already assessed, not the clock to assess anything more. If TC 150 is present, use its date for the CSED and confirm the actual filing date separately before relying on it for the ASED — the two statutes are not reading the same number off the transcript. And if a TC 976 shows up instead of a fresh TC 150, don't treat it as routine: the automatic offset/refund freeze it carries needs a TC 30X or TC 29X to release, which is worth flagging to a client expecting a refund on schedule.

If this distinction changes a CSED or ASED already calculated for an existing or former client's file, treat it as a potential claim circumstance, not just a data correction — most claims-made E&O policies require prompt notice to the carrier once a practitioner becomes aware of a possible error, independent of whether the client has complained; terms vary by carrier, so confirm the specific notice trigger in the practitioner's own policy.