IRS Transaction Code 290 records an additional tax assessment on a module that already carries a TC 150 original assessment. Zero-dollar entries also occur. The IRS Master File code definitions distinguish this entry from TC 291, which abates a prior assessment.
Definition and scope
Transaction Code 290 is a Master File entry that adjusts an existing tax module. A positive amount records additional tax assessed on that entry; a zero-dollar entry adds no tax amount on that line. TC 291 separately records an abatement of a prior assessment. A zero-dollar 290 does not mean your account balance is zero, that an examination is closed, that all freezes are released, that a penalty abatement was granted or that a refund is guaranteed. When a zero-dollar 290 carries a specific blocking code—such as 96X—it may record a penalty abatement request that the IRS considered and denied, so zero is never a safe all-clear signal on its own.
Transaction Code 291 abates a prior 150, 290 or 300 assessment in whole or in part. It is not necessarily a refund or a reversal of all penalties. A positive 290 is not automatically a current unpaid bill; later payments, credits and adjustments affect the balance. The actual notice and full account context determine the reason, the required response and any deadlines.
Transaction Code 150 posts the original assessment and serves a different purpose. IRS Code 810 is a refund freeze and a separate control. Some 290 entries can release particular freezes under certain conditions, but they do not universally release TC 810. You cannot predict a refund date, decode processing cycles or confirm an amendment request from codes alone.
Recording transcript observations
When you pull a Record of Account transcript or a business tax transcript and see Code 290, create a table that compares the transaction date, the dollar amount, any blocking codes visible on the transcript and the running balance after that line:
| Transaction code | Posted date | Amount | Balance after |
|---|---|---|---|
Add rows for every 290, 291, 150 and payment or credit entry that falls within the period you are reviewing. Note which entries carry the same transaction date, because multiple codes posted on the same day may represent a single adjustment package rather than separate events.
Check the transcript for correspondence codes and notice dates. If the IRS issued a formal notice—CP 2000, statutory notice of deficiency or another letter—that document explains the proposed or final adjustment and states your deadline to respond or appeal. Follow the instructions in the actual notice promptly, rather than inferring deadlines from transaction codes.
Compare the 290 amount to any estimated payments, withholding credits and prior-year overpayment credits listed on the same module. If the adjustment affects credits, the transcript will show separate entries for those changes. Record each discrepancy or question you cannot resolve from the transcript text:
- [ ] Locate the IRS notice that corresponds to the 290 transaction date
- [ ] Confirm whether the 290 reflects an amended return, an IRS correction or an examination adjustment
- [ ] Identify any blocking codes and check whether a freeze remains active
- [ ] Compare the running balance to payments and credits posted after the 290 date
- [ ] Note unresolved questions about penalty or interest calculations for follow-up
Workflow for unresolved questions
If the transcript shows a 290 entry but you have not received a notice, or if the amount does not match the explanation you were given, document the observation and the questions it raises. Do not assume the code alone tells you why the adjustment occurred, whether it is correct or what action is required.
Hypothetical illustration: Imagine a transcript line labeled TC 290 with a zero-dollar amount and a blocking series you have not seen before. You note the date, check for a corresponding letter in the client's records and find none. You record the question: Why did the IRS post a zero-dollar 290 on this date, and does the blocking code indicate a pending action or a completed review? You record the missing explanation and use an appropriate authorized IRS contact route. A Form 4506-T request is not a way to bypass transcript masking, and the entry does not establish case closure or an imminent refund.
When a 290 carries a dollar amount that increases tax, compare it to the original 150 assessment and to any amendments the taxpayer filed. If the IRS adjusted income, check whether the change matches a known information-return mismatch—Form W-2, 1099-INT, 1099-DIV or Schedule K-1 discrepancies—and whether the taxpayer has documentation to support the originally reported figure. Write down each unresolved item and the evidence needed to address it, rather than attempting to decode penalty or interest from the 290 line alone.
Track the IRS Collection Statute Expiration Date for each assessment, because a new 290 may start a separate ten-year collection period if it creates additional liability. The CSED clock does not restart for every adjustment; it depends on the actual assessment and any events that suspend or extend its collection period.
FAQ
Does IRS Code 290 always mean I owe additional tax?
A positive amount records additional tax on that entry, and zero-dollar entries also exist. Neither alone establishes what remains unpaid. Check the complete account, notices and payment evidence; TC 291 has the separate abatement function.
Can a zero-dollar Code 290 confirm that my penalty abatement was approved?
Not on its own. A zero-dollar 290 with certain blocking codes may show that the IRS considered and rejected a penalty abatement request. Other zero-dollar entries record administrative updates unrelated to penalties. Always review the corresponding notice and the penalty line on the transcript to confirm whether the abatement posted.
How do I know whether Code 290 came from my amended return or an IRS examination?
Do not assign a source from TC 290 alone. Compare the transaction with the return copies, actual notices and dates in the file. If the relationship is not established, preserve that question and ask the IRS for an explanation rather than concluding an audit or amended return was accepted.
For tax firms
Record each Code 290 observation in your case notes, match it to client correspondence and track unresolved questions in a central worksheet. When multiple adjustments span several modules or tax years, a unified workflow prevents duplicate requests and ensures you capture every penalty, interest and credit change that affects the Collection Statute Expiration Date or a pending business tax transcript review.
Discuss your firm’s authorization, transcript and CRM workflow in a 26T1 demo.