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 (the IRS’s reference guide to its data-processing codes) 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. Once the IRS establishes fraud on any portion, the taxpayer must show by a preponderance of the evidence which items were not fraudulent (IRC 6663(b)), which is why the allocation argument usually matters more than the characterization 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 defense for that spouse rather than a mitigating factor.

The side effect that needs a date check

Doc 6209 gives TC 321 a second clause, and its scope is narrower than it first appears — though Doc 6209 itself is not perfectly consistent about how narrow. The transaction-code entries state that TC 321 “releases restriction on FTP Penalty” and that TC 320 restricts it for “Fraud Penalties assessed under IRC 6653(b) for returns due before 1/1/1989.” IRC 6653(b) is the predecessor fraud statute IRC 6663 replaced, so on that description a TC 320 assessing today’s civil fraud penalty — the one TC 320 and this page both describe — was never subject to the restriction, and a TC 321 abating it has no restriction left to release.

A separate table in the same Doc 6209 publication, the Freeze Code File, describes the identical restricted-failure-to-pay freeze differently: on IMF it lists “TC 320 (with significant amount)” as one of the transactions that sets it, with no date qualifier at all, and on BMF it gives the cutoff as “TC 320 (RDD is prior to 1-1-87)” — two years earlier than the date in the code’s own entry. That is a genuine inconsistency inside the primary source, not a settled fact this page can silently pick a side on. Practically, the cutoff matters only on an old return the IRS can still collect on. A return due in the late 1980s is far past the ordinary three-year assessment period, but a fraud return has no assessment limit under IRC §6501(c)(1), and the ten-year collection period under IRC §6502(a)(1) runs from the assessment date, not the return date. So an old return can still carry a live balance, and a practitioner who sees an actual restricted-FTP indicator on a current-looking module (the record for one tax type and period) should confirm it against the account itself — the IRS Transcript Decoder reads what is actually there — rather than rule the mechanic out on the strength of a date in Doc 6209 that Doc 6209 does not state consistently. The underlying idea is the same one that makes TC 272, the failure-to-pay restriction deletion, worth checking on an account where a restriction is actually live.

What people mistake TC 321 for

People confuse TC 321 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 a civil fraud penalty: the 75 percent penalty under IRC 6663, or IRC 6653(b) on a return due on or before 12/31/1989. 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.

What to do next

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 and the taxpayer carries the burden on it.

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.

Do not budget real time modeling a failure-to-pay restart on a routine current case. The date cutoffs Doc 6209 gives for the restriction (returns due before 1/1/1989 in the TC 320 entry; return due date before 1-1-87 in the BMF freeze table; the IMF freeze table gives no date and sets the restriction on a TC 320 “with significant amount”) matter mainly when two things are true. First, the IRS assessed late, which IRC §6501(c)(1) allows for fraud. Second, the ten-year collection period that runs from that assessment under IRC §6502(a)(1) is still open. If a restricted-FTP indicator does show up on a module that looks current, verify it against the account rather than ruling it out by date; Doc 6209’s own tables disagree on the cutoff.

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.