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

Notice 972CG arrives 12 to 18 months after filing with a dollar amount, a per-return calculation, and 45 days to respond. This page explains what triggers it, what each return costs by the year it was due, and how to answer it.

Updated October 28, 2026.

What IRS Notice 972CG Is

Notice 972CG is the IRS's proposed penalty notice for failures involving information returns: 1099-NEC, 1099-MISC, 1099-INT, 1099-DIV, 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. The notice states the tax year, the number of returns affected, the type of failure, the per-return penalty, and the total proposed, and it gives you 45 days from the notice date to respond.

The distinction between CP2100 and Notice 972CG, frequently confused:
CP2100 / CP2100A Notice 972CG
What it is Compliance notification Proposed penalty
What it requires B-Notice to each listed payee within 15 business days; backup withholding if no response in 30 business days Written response within 45 days of the notice date: payment, dispute, or reasonable cause request
When it arrives In the months after filing, as the IRS identifies mismatches 12 to 18 months after filing; a notice in fall 2026 covers tax year 2024 returns due in 2025
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. 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, a 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 return: each incorrect or late information return carries its own penalty. The amount depends on how quickly the correct return was filed and on the year the return was due, because the IRS indexes the figures each year.

Per-return penalty by correction timing and the year the return was due:
Correction timing Returns due in 2025 (tax year 2024) Returns due in 2026 (tax year 2025)
Corrected within 30 days of the due date $60 $60
Corrected after 30 days but by August 1 $130 $130
Not corrected by August 1 $330 $340
Intentional disregard $660, no annual cap $680, no annual cap
Annual cap for large filers $3,987,000 $4,098,500

A 972CG arriving in fall 2026 covers tax year 2024 returns that were due in 2025, so the first column applies. For organizations filing thousands of 1099s, even a small percentage of affected returns produces significant exposure: a 3% error rate across 4,000 forms is 120 penalties, or $39,600 at the after-August-1 tier for returns due in 2025. The full table, including returns due in 2027 and the small-filer caps, is on the 1099 penalties page.


How to Respond to a 972CG Notice

The 972CG penalty is not final until the 45-day response period closes. A documented, timely response is the primary opportunity to reduce or eliminate the proposed amount.


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: Build the Reasonable Cause Case

Two paths are often mentioned; only one applies to these penalties.

Reasonable cause under Treas. Reg. 301.6724-1: The IRS waives the penalty when the filer shows an event beyond its control (such as a payee who certified wrong information) or significant mitigating factors (a first-time filer, an established history of correct filing), plus responsible conduct, which for TIN failures means the solicitation rules were followed: a W-9 requested before the first payment and an annual solicitation after each notice. Supporting documentation: W-9 request records, TIN matching results, B-Notice send confirmations, vendor non-response records, system failure records if applicable.

First-Time Abatement (FTA): Not available. FTA covers failure-to-file, failure-to-pay, and failure-to-deposit penalties; information return penalties under IRC 6721 and 6722 are outside it. A clean compliance history still helps, but as a mitigating factor inside the reasonable cause request.

Pull the solicitation dates first: when the W-9 was requested for each payee on the notice, and when each B-Notice or annual solicitation went out. Those dates are the proof of responsible conduct, and the IRS reads them before it reads the narrative.

Step 4: Prepare a Formal Written Response

The 972CG response must be submitted in writing within 45 days of the notice date. 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 the penalty is waived this time, filing the same errors in the next cycle will produce another 972CG, and a second notice weakens the mitigating factor that an established history of compliance provides. 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 on these penalties is Treas. Reg. 301.6724-1: an event beyond your control or significant mitigating factors, plus responsible conduct. A compliance record that shows W-9 collection at onboarding, TIN matching, B-Notices after each CP2100, 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: an established history of correct filing is a mitigating factor
  • Reasonable cause documentation assembled: W-9 records, TIN matching results, outreach history, B-Notice compliance
  • Solicitation dates confirmed per payee: initial W-9 request and each annual solicitation
  • Formal written response prepared and submitted within 45 days of the notice date
  • 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. A reasonable cause waiver under Treas. Reg. 301.6724-1 is available when the filer shows an event beyond its control or significant mitigating factors, plus responsible conduct (the W-9 solicitation rules were followed). First-time abatement does not apply to information return penalties.

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

45 days from the date on the notice. 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 the penalty is waived this year, does that affect future relief?

There is no first-time abatement clock to protect, because FTA does not cover these penalties. What a second 972CG does cost you is the mitigating factor of an established history of compliance, and the IRS will expect to see that the solicitation rules were followed after the first notice. That is one more reason to fix the underlying controls now.

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, building the reasonable cause case under Treas. Reg. 301.6724-1, assembling the documentation record, and submitting a formal response within 45 days) 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