TC 291: Abatement of Prior Tax Assessment

What the code actually does

TC 291 reduces assessed tax. IRS Document 6209, Section 8A defines it in one sentence that is wider than the code’s reputation: it "abates a previously posted 150 and/or 290 or 300 in whole or in part." Three different assessments are in scope, and only one of them is the adjustment code TC 291 is usually paired with.

Like its counterpart it is keyed rather than generated, on the same adjustment command code, and Doc 6209 records that it "may need priority and/or hold codes" and that on individual accounts it "needs reason and source codes." Those codes are where the explanation lives; the transaction itself carries only the money.

It can reach the taxpayer’s own original return

The ability to abate a TC 150 is what makes this code worth a page rather than a footnote on TC 290. A TC 150 is the liability the taxpayer reported on the return they filed. When a TC 291 reduces it, the Service is not undoing something it did — it is accepting that the original self-assessment was too high.

That happens more often than practitioners expect: an amended return allowed, a claim substantiated, a math-error assessment reversed on protest, a duplicate filing resolved in the client’s favour. In every one of those the client’s question is "did they accept it?" and a TC 291 against the original assessment is a large part of the answer.

It also means the size of a TC 291 cannot be checked against a single prior transaction. A TC 291 larger than any individual TC 290 on the module is not necessarily an error; it may simply be reaching the original return as well.

The interest abatement rides along automatically

Doc 6209 records that a TC 291 "generates abatements (TC 197) of computer-generated interest where applicable." The interest that accrued on tax now abated comes off by a separate generated transaction rather than as part of the TC 291 amount, and TC 197 is where to look for it.

This matters when reconciling a client’s balance after a successful claim. The tax abatement and the interest abatement are two lines, they can post in different cycles, and a client reading only the first will think the correction was incomplete. Where the interest was restricted rather than computer-generated, the automatic abatement will not fire at all and the interest has to be addressed on its own terms.

Doc 6209 also records that a TC 291 "releases same freezes and holds as TC 290," which is a long list — so, as with its counterpart, a TC 291 often appears immediately before money finally moves on a module that had been stuck.

One practical consequence of the reason and source codes Doc 6209 requires on individual accounts is that the explanation a client receives is generated from them rather than written by anyone. The adjustment notice language is produced by the code combination, which is why two abatements granted for quite different reasons can produce near-identical letters — and why the letter is a poor guide to what was actually decided when the transcript is available instead.

What TC 291 gets confused with

It gets confused with a refund. An abatement reduces what is assessed; it does not by itself send anything. If the abatement takes the module into overpayment, a refund or offset follows as its own transaction with its own date, and the gap between the two is where most client anxiety about "the abatement that never arrived" actually sits.

It is also confused with the examination-side abatement. TC 301 does the equivalent job for an examination or Appeals adjustment and carries an explicit cap the IRM states outright. The two codes have overlapping reach — both can abate a TC 150 or a TC 290 — so which one posted tells a practitioner which function made the decision, and therefore who to talk to about it.

One narrow trap is worth knowing: Doc 6209 records that TC 291s on MFT 10 in blocking series 500-519 "have been designated for FUTA use only," with generated reference codes carrying a state code. A TC 291 in that series on an employment tax account is a FUTA state-credit adjustment, not a general abatement, and reading it as the latter will not reconcile.

The practitioner’s actual next step

Establish which assessment the abatement reached — the original return, a prior adjustment, or an examination deficiency — before describing to a client what was conceded.

Look for the matching interest abatement, and check whether interest on the module was restricted, in which case it will not come off automatically.

Read the reason and source codes rather than the amount; the amount says how much and the codes say why.

If the module is now in overpayment, expect the refund as a separate later transaction and say so before the client asks.

On employment tax accounts, rule out the FUTA blocking series before treating the transaction as an ordinary abatement, and confirm the sequence against the module with the IRS Transcript Decoder.