What Is IRS Notice 972CG? Penalty Amounts, Deadlines, and How to Respond

IRS Notice 972CG is a penalty assessment — not a warning, not a preliminary notice, not a request for information. It arrives with a dollar amount, a per-form calculation, and a response deadline. The penalty is for information returns that were filed late, filed with missing or incorrect TINs, filed with mismatched names, or filed using the wrong form type. Because the penalty is per form, organizations that file at volume face exposure that scales with their filing count — not just with the severity of the error. A 2% mismatch rate across 5,000 1099s is 100 penalty assessments, not one. The 972CG isn't the problem itself; it's the IRS's formal accounting of what the filing errors cost. Responding to it correctly reduces or eliminates the penalty. Preventing the errors that trigger it eliminates the notice entirely.

What IRS Notice 972CG Is

Notice 972CG is the IRS's formal penalty assessment notice for failures involving information returns — 1099-NEC, 1099-MISC, 1099-INT, 1099-DIV, W-2, 1042-S, and other required filings. It is issued under Internal Revenue Code Sections 6721 and 6722, which cover failure to file correct information returns and failure to furnish correct payee statements respectively. The notice states the tax year at issue, the number of returns affected, the type of failure identified, the per-form penalty calculated, and the total penalty assessed.

The distinction between CP2100 and Notice 972CG — frequently confused:
CP2100 / CP2100A Notice 972CG
What it is Compliance notification Penalty assessment
What it requires B-Notice outreach to vendors; backup withholding if no response Formal written response before stated deadline; penalty payment or abatement request
When it arrives Shortly after filing — IRS identifies mismatches Later in the compliance cycle — after penalty assessment calculations are complete
Dollar amount included No Yes
Relationship to each other CP2100 is often the precursor 972CG follows unresolved CP2100 issues and other filing failures

A CP2100 notice that isn't handled correctly — B-Notices not sent, backup withholding not applied, corrections not made — is one of the most direct paths to a 972CG penalty assessment. But 972CG can also be triggered by late filing, missing furnishing, or incorrect forms filed independently of any CP2100.

Free Tool
972CG Penalty Response Tool

Skip the manual work on Steps 5–8. Paste your 972CG data and the tool calculates your exact deadline, classifies every payee with required actions, and generates a draft abatement letter based on IRS Publication 1586 — ready to review and send.

Deadline calculated automatically Draft abatement letter included No account required

What Triggers a 972CG Penalty Assessment

The filing failures that produce 972CG penalties:
Trigger What It Means
Missing TIN 1099 filed with no TIN in the payee field — blank or placeholder
Incorrect TIN Wrong digits, transposed numbers, wrong TIN type — anything that fails IRS matching
Name/TIN mismatch Valid TIN paired with a name that doesn't match the IRS record for that TIN
Late filing 1099 filed after the IRS submission deadline — per-form penalty applies from day one
Failure to furnish Vendor copies (Copy B) not delivered by the furnishing deadline — separate penalty track from IRS filing
Wrong form type Services income reported on 1099-MISC instead of 1099-NEC, or other incorrect form selection
Intentional disregard IRS determines the error wasn't accidental — highest penalty tier, no cap reduction available

Most 972CG notices in vendor compliance contexts involve missing TINs, name/TIN mismatches, and late filing — all of which trace back to vendor data quality problems that weren't resolved before the filing deadline.


How the Penalty Calculation Works

The 972CG penalty is assessed per form — each incorrect or late information return carries its own penalty. The per-form amount depends on the category of failure and how quickly it was corrected.

The per-form penalty tiers:
Category Penalty Tier
Corrected within 30 days of deadline Lower per-form penalty
Corrected after 30 days but by August 1 Higher per-form penalty
Not corrected by August 1 Highest per-form penalty
Intentional disregard Maximum penalty — no annual cap reduction

For organizations filing thousands of 1099s, even a small percentage of affected forms produces significant aggregate penalty exposure. A 3% error rate across 4,000 forms is 120 penalty assessments — calculated at whichever per-form tier applies based on when (or whether) the errors were corrected.


How to Respond to a 972CG Notice

The 972CG penalty is not final until the response period closes. A documented, timely response is the primary opportunity to reduce or eliminate the assessment.


Step 1 — Read the Notice Completely Before Acting

The 972CG specifies the tax year, form type, number of returns at issue, failure categories, per-form penalty amounts, total assessed, and the response deadline. Confirm each of these before preparing a response. A response addressing the wrong tax year or wrong form type wastes the response window.


Step 2 — Reconstruct the Filing Record for the Tax Year at Issue

Pull the complete compliance record for the filing year the notice references: what was filed, when it was filed, what W-9s were on file at the time of filing, what TIN matching was run, what outreach was completed for missing or mismatched vendors, and what corrections were made. This record is the foundation of the abatement argument.


Step 3 — Evaluate Penalty Abatement Options

Two primary abatement paths exist:

Reasonable Cause Abatement — The IRS may waive or reduce penalties when the filer demonstrates that the failure resulted from circumstances outside normal operational control and that the organization acted in good faith. Supporting documentation: W-9 collection records showing outreach efforts, TIN matching results showing validation was attempted, vendor non-response documentation, system failure records if applicable. The stronger and more complete the documentation, the stronger the abatement case.

First-Time Abatement (FTA) — Available to organizations with a clean prior three-year compliance history for the same type of penalty. FTA doesn't require documenting reasonable cause — it's based on prior compliance record. If this is the first 972CG assessment, FTA should be evaluated alongside reasonable cause before responding.

FTA and reasonable cause abatement can sometimes be combined — FTA for the portion of the penalty that qualifies, reasonable cause for the remainder. Review both options before submitting the response.

Step 4 — Prepare a Formal Written Response

The 972CG response must be submitted in writing before the stated deadline. It should include: the notice date and reference number, the tax year and form type at issue, a clear statement of the relief requested (full abatement, partial abatement, or penalty reduction), the factual narrative supporting the request, and all supporting documentation attached and organized.


Step 5 — Correct the Underlying Filing Errors

Even if abatement is granted for the current penalty, filing the same errors in the next cycle will produce another 972CG — potentially without FTA availability because the first notice broke the clean compliance record. Correct the vendor master, update W-9 records, validate via IRS TIN matching, and implement the controls that prevent the same errors from reaching the next filing.


Step 6 — If Abatement Is Denied, Consider Appeals

A denied abatement request can be appealed within the IRS Office of Appeals. The appeals process gives a second opportunity to present the documentation record. If the denial appears incorrect, consulting a tax professional who handles IRS penalty abatement is appropriate at this stage.


The Documentation That Makes or Breaks an Abatement Request

The documentation most valuable for 972CG abatement:
Documentation Type Why It Matters
W-9 collection records with dates Demonstrates proactive collection effort — not waiting until January
IRS TIN matching results per vendor Shows validation was attempted before filing
Vendor outreach records for missing/mismatched TINs Demonstrates repeated, documented attempts to obtain correct information
B-Notice send confirmations with proof of delivery Shows CP2100 compliance process was followed
Corrected W-9s with revalidation results Demonstrates corrections were verified, not just accepted
System records of format validation at submission Shows technical controls were in place at the point of collection
Timeline of corrective action relative to filing deadline Demonstrates good-faith effort within the compliance window available

The IRS's standard for reasonable cause is whether the filer exercised ordinary business care and prudence. A compliance record that shows W-9 collection at onboarding, TIN matching, structured outreach for exceptions, and Q4 bulk validation is evidence of exactly that — regardless of whether some errors still reached the filing.


How to Prevent Future 972CG Notices

The controls that prevent the most common 972CG triggers:
  • W-9 required before vendor activation — eliminates missing TIN filings
  • IRS TIN matching at onboarding — catches name/TIN mismatches before first payment
  • Q4 bulk TIN matching starting in October — provides time to resolve issues before filing deadlines
  • Payment hold for vendors without valid W-9 — makes the collection requirement operational
  • Legal name from W-9 Line 1 exactly — prevents name/TIN mismatches from DBA usage
  • Corrected 1099s filed promptly when errors are discovered — moves the filing into a lower penalty tier
  • USPS address validation before furnishing — reduces failure-to-furnish penalties
  • Complete B-Notice process when CP2100 is received — prevents CP2100 from escalating to 972CG
  • Per-vendor mismatch history maintained — ensures correct B-Notice type and complete response documentation

972CG Response and Prevention Checklist

  • 972CG notice reviewed completely — tax year, form type, records at issue, penalty amount, response deadline confirmed
  • Filing record reconstructed for the tax year at issue
  • Prior compliance history reviewed — FTA eligibility assessed
  • Reasonable cause documentation assembled — W-9 records, TIN matching results, outreach history, B-Notice compliance
  • FTA and reasonable cause abatement both evaluated before response submitted
  • Formal written response prepared and submitted before response deadline
  • Underlying filing errors corrected — vendor master updated, W-9s revalidated, controls improved
  • If denied — appeals process evaluated; tax professional consulted if appropriate
  • Prevention controls implemented: W-9 gate at onboarding, TIN matching, Q4 bulk validation, complete B-Notice process

Frequently Asked Questions

Does receiving a 972CG notice mean the organization did something illegal?

No. The overwhelming majority of 972CG notices result from filing errors — missing TINs, name/TIN mismatches, late filing — not intentional misconduct. The intentional disregard penalty tier exists for cases where the IRS determines the error was knowing and deliberate. Most vendor compliance-related 972CG notices fall under the standard penalty tiers and are addressable through abatement.

Can 972CG penalties be reduced or eliminated?

Yes, in many cases. Reasonable cause abatement is available when the filer demonstrates good-faith compliance effort and circumstances outside normal control. First-time abatement is available for organizations with a clean three-year prior compliance history for the same penalty type. Both should be evaluated before responding to the notice.

How long does the organization have to respond to a 972CG?

The notice specifies the response deadline. Missing it significantly reduces abatement options. Respond before the deadline regardless of whether the abatement case is fully prepared — a timely but incomplete response is better than a complete response submitted after the deadline closes.

If abatement is granted this year, does that affect future abatement eligibility?

Yes. First-time abatement is available once per three-year compliance period for each penalty type. If FTA is used for a 972CG in the current year, FTA won't be available for the same penalty type in the next three years. This is one more reason to address the underlying controls — a second 972CG in the following year has fewer abatement options available.

Is the 972CG penalty for the IRS filing, the vendor furnishing, or both?

Both can generate 972CG penalties — they are separate penalty tracks under IRC 6721 (information return failures) and IRC 6722 (payee statement furnishing failures). A single filing error can trigger both if the vendor copy was also incorrect or not delivered. The notice will specify which failures are included in the assessment.


Conclusion

IRS Notice 972CG is a formal per-form penalty assessment for information return failures — missing TINs, name/TIN mismatches, late filing, failure to furnish, and wrong form type. Because the penalty scales with the number of affected forms, it can produce significant financial exposure for organizations filing at volume. The response process — reviewing the notice carefully, evaluating FTA and reasonable cause abatement, assembling the documentation record, and submitting a formal response before the deadline — determines whether the penalty is paid in full, reduced, or eliminated. The prevention infrastructure — W-9 at onboarding, IRS TIN matching before first payment, Q4 bulk validation, complete B-Notice compliance — is what keeps the 972CG from arriving in the first place.


Prevent 972CG Penalties with TIN Comply

Free Tool

972CG Penalty Response Tool

Upload your 972CG extract or paste the data directly. The tool calculates your exact response deadline, classifies every payee with required actions, and generates a draft abatement letter ready to review — all based on IRS Publication 1586 reasonable cause rules.

  • Calculates your exact 45-day deadline from the notice date
  • Generates a draft reasonable cause abatement letter
  • Classifies every payee on the notice with required actions
  • Produces W-9 solicitation packets for all affected payees
  • No account required — runs entirely in your browser