TC 321: Abatement of the Civil Fraud Penalty

What the code actually does

TC 321 is the abatement side of the IRC 6663 civil fraud penalty. IRS Document 6209, Section 8A gives it two functions rather than one: it “abates a previously posted 320 transaction in whole or in part,” and on both BMF and IMF it “releases restriction on FTP Penalty.” Only the first is in the code’s name.

Partial abatement is the expected shape here rather than an edge case. The fraud penalty reaches only the portion of an underpayment attributable to fraud, so an outcome that narrows that portion — on appeal, in litigation, or on reconsideration — reduces the penalty without eliminating it. A TC 321 is therefore not, by itself, evidence that a fraud determination was withdrawn.

The standard that produces one

IRM 20.1.5.19.8 states the operative rule: “in general, no fraud penalty is imposed on any portion of an underpayment if it is shown (by a preponderance of the evidence) that it is not attributable to fraud.” Two things in that sentence are worth drawing out for a client.

The unit of analysis is a portion of the underpayment, not the return and not the year. Establishing that some items were not fraudulent carves those items out of the penalty base even if others remain, which is why the allocation argument usually matters more than the characterisation argument. And the standard is a preponderance — the ordinary civil balance — which is a different and lower bar than the clear and convincing evidence the government must meet to sustain the penalty in the first place.

There is also a distinct route on a joint return. IRM 20.1.5.19.8 notes that “in the case of a joint return (married filing jointly), the fraud penalty will not apply to a spouse unless some part of the underpayment is due to fraud of such spouse. See IRC 6663(c).” The penalty does not travel to a spouse on the strength of the other spouse’s conduct, and that is a full defence for that spouse rather than a mitigating factor.

The side effect worth checking

Doc 6209’s second clause is the practical trap. Assessing the fraud penalty restricted the failure-to-pay penalty on the module for certain legacy assessments; abating it “releases restriction on FTP Penalty.” Releasing a restriction means the system resumes computing.

So a client who wins a reduction in the fraud penalty may see the account move in an unexpected direction, because a failure-to-pay penalty that had been frozen starts running again on whatever tax remains unpaid. The net effect can be smaller than the headline abatement, and on an old module with a long unpaid balance it can be materially smaller. This is worth modelling before reporting a result, and it is the same mechanic that makes TC 272, the failure-to-pay restriction deletion, a code to think twice about on an unpaid account. Here it happens automatically, as a consequence of the abatement, rather than by anyone choosing it.

What TC 321 gets confused with

TC 321 gets confused with an abatement of the accuracy-related penalty, which is the downstream consequence of the confusion about TC 320 itself. Accuracy-related penalties under IRC 6662 are assessed and abated by penalty reference number rather than under this code, so a TC 321 always concerns the 75 percent fraud penalty. A practitioner reporting a TC 321 as “the accuracy penalty came off” is describing a different and much smaller case than the one in front of them.

It is also read as closing the matter. It does not resolve the tax, which stands on its own; it does not speak to any criminal exposure, which runs under a separate standard; and where it is partial it leaves a fraud determination alive as to the remainder. A TC 321 in whole or in part is a change to one penalty, not a disposition of the case, and the account will usually still show a balance afterwards for reasons that have nothing to do with the abatement.

The practitioner’s actual next step

Read the amount against the original assessment to establish whether the abatement was full or partial, since a partial one leaves the fraud determination standing as to the rest.

Build any further request around allocation — which portions of the underpayment are not attributable to fraud — because that is the unit the standard actually operates on.

On a joint return, test the non-participating spouse’s position separately under IRC 6663(c), where the penalty does not apply absent that spouse’s own conduct.

Model the failure-to-pay consequence before reporting the outcome, since abating the fraud penalty releases a restriction and can restart a frozen penalty on unpaid tax.

Confirm what the account actually looks like afterwards with the IRS Transcript Decoder, and treat the underlying tax and any criminal exposure as separate matters this code does not touch.