TC 186: Computer-Generated Failure to Deposit Penalty

What the code actually does

TC 186 is the systemic failure-to-deposit penalty under IRC 6656. IRS Document 6209, Section 8A marks it a Generated Transaction and defines it as the “computer generated FTD Penalty if taxpayer fails to make timely and sufficient payments as required by regulations on Forms CT-1, 720, 940, 940EZ, 941, 943, 945 and 1042.” It is a business-account code: employment and excise deposits, not income tax.

The IRM organises this family better than most, and the subsection title alone settles a question practitioners often get wrong. IRM 20.1.4.13 is called “Overview of Manual (Restricted TC 180/181) and Systemic (Computer Generated TC 186/187) Deposit Penalty,” and its body gives a four-line map: “TC 186 — Computer generated assessment, TC 187 — Computer generated abatement, TC 180 — Manual assessment (systemic penalty recalculation restricted), TC 181 — Manual abatement (systemic penalty recalculation restricted).” The axis is who acted, and each side has its own assessment and its own abatement.

It can post in two instalments

This is the detail that changes what a practitioner tells a client after the first notice. The deposit penalty runs on a tiered rate structure, and the top tier arrives separately. IRM 20.1.4.14.4 explains that penalty indicator code “1” is “generated with the systemic TC 186 posting in the same cycle as the TC 150 to mark the account module for a potential 15 percent penalty rate on the amount of the unpaid tax,” and warns the caseworker: “if a PIC ‘1’ is present with the initial TC 186 (posted in the cycle to the TC 150), check to be sure that the systemic 15 percent fourth tier penalty amount isn’t pending for posting as a subsequent TC 186 marked with a PIC ‘2’.” That second TC 186 posts five cycles after the first.

So a module can carry two TC 186 entries for one filing period, and the first is a marker that more may be coming rather than a final figure. A client quoted the initial amount, or a practitioner who computes a relief request against it, can be working from a number that is about to grow. Checking for a pending second posting before advising is the whole practical value of knowing the PIC exists.

The averaged penalty nobody chose

A TC 186 can also be the consequence of silence. IRM 20.1.4.18 describes the CP 207 and CP 207L notices, which go out when a return’s deposit record cannot be reconciled, and states the default: “if there is no reply to a CP 207 or CP 207L, or if the reply isn’t resolved and input by the 13th cycle (week) after issuance of the CP 207/CP 207L notice, Master File will systemically assess an averaged penalty (TC186).”

An averaged penalty is computed by spreading the period’s liability evenly rather than against the deposits the taxpayer actually made, which usually produces a worse result than the real facts would. That makes it a distinctive kind of TC 186: not a determination that the client deposited late, but a placeholder assessed because a notice went unanswered. Where the underlying deposit record supports a smaller penalty — or none — the remedy is to supply the record on which a correct computation can be made, and the same IRM subsection contemplates a late reply being treated “as any other reply to an assessed penalty notice.” Establishing whether a TC 186 is an averaged assessment or a computed one is therefore the first diagnostic question, because it decides whether the argument is about relief or about the facts.

What TC 186 gets confused with

TC 186 gets confused with TC 180, the manually assessed version of the identical penalty, and the confusion has a consequence beyond bookkeeping. IRM 20.1.4.13 explains that “manual adjustments (TC 180/181) restrict Master File from systemically recalculating the penalty,” and that credits moved in or out of a restricted module “won’t cause a systemic recalculation of the penalty because the original or corrected ROFTL information isn’t accessible to Master File.” A module carrying a TC 186 is still live and will recompute when the facts change; a module carrying a TC 180 will not. Treating the two as the same code means expecting a correction to flow through automatically on an account where it never will.

It is also mistaken for the deposit itself. The 6X0-series codes record payments; TC 186 records the penalty for those payments having been late or short. A client looking at a transcript often reads any charge near their deposits as a recomputation of the tax, when the deposit penalty is a separate assessment that survives the tax being paid in full.

The practitioner’s actual next step

Determine whether the TC 186 was computed from the deposit record or averaged after an unanswered CP 207 or CP 207L, because only one of those is argued on the facts.

Check for a pending second posting before relying on the amount. A PIC 1 on the initial entry signals a possible fourth-tier addition five cycles later.

Reconcile the actual deposit dates and amounts against the liability before requesting relief, since a rate-tier or date error produces a bigger reduction than an abatement usually will.

Where the facts are not in dispute, run the First-Time Abate and reasonable-cause analysis with the Penalty Abatement Analyzer — the deposit penalty is named in the IRM as First-Time Abate eligible, unlike several penalties it sits near.

Expect any granted relief to post as a manual TC 181 rather than as a systemic TC 187, and note that the manual entry will also stop the module recalculating on its own.