IRS Notice 972CG: What It Means, How to Respond Within 45 Days, and How to Prevent It
Notice 972CG is a proposed penalty, not an assessed one. You have 45 days from the notice date to pay or to request abatement for reasonable cause, and filers who do nothing pay penalties they often did not have to.
Updated October 28, 2026.
What Is IRS Notice 972CG?
Notice 972CG, sometimes called a "P-Notice" or proposed penalty notice, is the IRS's formal notice to a payer that information returns were filed with errors. It proposes civil penalties under IRC Section 6721 (failure to file correct information returns) and IRC Section 6722 (failure to furnish correct payee statements).
The notice is generated from the IRS Payer Master File, which tracks all information returns filed by a given EIN. The 972CG is typically issued 12 to 18 months after the returns were filed, so tax year 2024 returns filed in early 2025 generate notices through the second half of 2026.
The errors that trigger a 972CG include:
- TIN/name combinations that don't match IRS records
- Missing TINs (blank fields or invalid characters)
- Information returns filed late
- Returns filed on paper when electronic filing was required (organizations filing 10 or more information returns must e-file)
The notice includes a list of the affected payee records, the proposed penalty amount, and instructions for responding. If the notice covers more than 250 records, the IRS provides the list on CD.
Key takeaways
- A 972CG is proposed, not assessed: respond within 45 days of the notice date and nothing is owed until the IRS rules.
- A notice arriving in fall 2026 covers tax year 2024 returns that were due in 2025, proposed at $330 per return.
- Reasonable cause under Treas. Reg. 301.6724-1 needs mitigating factors or events beyond your control plus proof you followed the solicitation rules.
- Your CP2100 and B-Notice file is the evidence; without it, abatement is unlikely.
- Pre-filing IRS TIN Matching removes most of the mismatches before they can be penalized.
Free Tool: 972CG Penalty Response Tool
Just received a 972CG? Use our free analyzer to calculate your exact 45-day response deadline, get a payee-by-payee action list, and generate a draft reasonable cause abatement letter in minutes, based on IRS Publication 1586.
Open the free 972CG Penalty Response Tool
The Penalty Structure
Penalties under Section 6721 are tiered based on how quickly errors are corrected:
| Timing | Penalty per return (tax year 2024 returns, due in 2025) |
|---|---|
| Corrected within 30 days of filing deadline | $60 |
| Corrected after 30 days but by August 1 | $130 |
| Not corrected by August 1 | $330 |
| Intentional disregard | $660 (minimum) |
Returns due in 2026 (tax year 2025) carry $340 after August 1, $680 for intentional disregard and a $4,098,500 cap ($1,366,000 for small filers). Returns due in 2027 keep $340, with $690 for intentional disregard and a $4,191,500 cap. The full table by year is on the 1099 penalties explained page.
The 972CG proposes penalties at the highest standard tier, meaning mismatches identified through the IRS matching cycle and not corrected before August 1 are proposed at $330 per return for tax year 2024 returns that were due in 2025.
Annual caps apply. For large businesses, the cap is $3,987,000 per error category for returns due in 2025. For small businesses with average gross receipts of $5 million or less in the three preceding years, lower caps apply.
If a single return has more than one type of error, the IRS imposes only the highest applicable penalty for that return. They don't stack penalties per error.
The Relationship Between CP2100 and 972CG
These two notices are part of the same sequence and are often confused.
CP2100 (the B-Notice) arrives first. It notifies a payer that specific TIN/name combinations on filed 1099s didn't match IRS records. CP2100 triggers B-Notice obligations: you must send First B-Notices to affected payees within 15 business days, track responses, and begin backup withholding for non-respondents.
Notice 972CG arrives later, typically several months to a year after CP2100, and proposes a penalty for the mismatches that were identified. The 972CG doesn't necessarily cover the same mismatches as the most recent CP2100. It reflects the IRS's matching cycle for an earlier filing period.
How you responded to the CP2100 is directly relevant to your 972CG response. Documented evidence that you sent B-Notices promptly, followed up with payees, and corrected W-9s as they came in is the foundation of a reasonable cause argument when the 972CG arrives.
The 45-Day Response Window
Once you receive a 972CG, you have 45 calendar days from the notice date to respond (60 days for foreign filers). If you need more time, you can submit a written extension request. It must arrive before the deadline expires.
If you don't respond, the proposed penalties are manually input as assessed civil penalties and the IRS begins issuing balance-due notices (CP15 or CP215), followed by collection activity. Interest accrues from the CP15/CP215 date until paid.
You can still request abatement after the 45-day window closes, but it's harder: you're now dealing with an assessed penalty, not a proposed one, and collection activity may already be in motion.
How to Respond: Reasonable Cause
The most important tool in a 972CG response is reasonable cause. Under Treasury Regulation Section 301.6724-1, the IRS will waive or reduce penalties if the filer can demonstrate:
- Significant mitigating factors: for example, no prior history of information return penalties, or a steadily improving error rate over time
- Events beyond the filer's control: system failures, data conversion errors, a vendor who refused to provide a correct TIN despite documented solicitation, or errors inherited through an acquisition
"Significant mitigating factors" specifically includes having no prior filing history with the form in question, and having an established track record of compliance. The regulations are explicit that even filers with prior errors may qualify for abatement if they can show a year-over-year improvement in their error rate.
The IRS also requires responsible conduct before and after the failure, which in practice means the annual solicitation rules were followed: the initial W-9 request, the B-Notice solicitations, and backup withholding when a payee did not respond. A response that shows only that errors occurred, without explaining what steps were taken to prevent or correct them, is unlikely to succeed.
What a reasonable cause response must contain:
- The specific regulatory provision under which you're requesting a waiver (Reg. Section 301.6724-1)
- A full statement of all facts supporting your argument, including timeline and supporting documentation
- Evidence of B-Notice compliance: copies of First and Second B-Notices sent, proof of mailing, W-9 collection records, backup withholding calculations for non-respondents
- Your organization's compliance history: prior years with few or no errors strengthen the case considerably
- Signature of the person responsible for filing the returns
- A declaration under penalties of perjury
The statement is submitted to the address listed on the 972CG notice.
Common Scenarios and How They Affect Abatement
| Scenario | Why it supports abatement | What the IRS will look for |
|---|---|---|
| Vendor refused to provide a TIN | Events beyond your control, provided you acted responsibly | The initial request, the annual solicitations required by Publication 1586, and proof backup withholding began when the vendor stayed silent. Asking once is not enough. |
| Errors inherited through an acquisition | Beyond your control at the time the returns were filed | The acquisition timeline, when the errors in the acquired vendor master were discovered, and the remediation steps taken. The free 972CG tool's draft letter covers this scenario. |
| System conversion errors | ERP migrations and accounting system changes that corrupt TIN data qualify if documented | Evidence that you corrected the errors once discovered, not just that the conversion happened |
| No prior compliance issues | Significant mitigating factor | Your filing history: years of 1099 filings without a 972CG, stated explicitly in the response |
What Happens If Abatement Is Denied
If the IRS denies the abatement request, it issues Letter 854C explaining the basis for denial and your appeal rights. You then have the option to appeal through the IRS Independent Office of Appeals.
The appeals process allows you to present additional documentation or arguments. Many penalties that are initially denied at the campus level are reduced or eliminated on appeal, particularly when the filer can provide additional evidence of compliance efforts.
Prevention: The B-Notice Workflow Is Your Best Defense
The evidence that supports a successful 972CG abatement is largely the same as the evidence produced by a well-run B-Notice compliance process. This isn't a coincidence: the IRS's reasonable cause standard is essentially asking whether you treated the CP2100 seriously and responded properly.
For organizations that want to avoid the 972CG entirely rather than respond to it:
- Run IRS TIN matching on your full vendor population before filing season: mismatches found before filing can be corrected at zero penalty cost
- Collect W-9s proactively, before payment rather than at year-end
- Respond to CP2100 notices promptly and document everything: B-Notice letters sent, responses received, backup withholding calculated
- Re-validate vendor TINs after name changes, mergers, or EIN updates
The path from TIN mismatch to 972CG takes 12 to 18 months. Every step in that sequence is either evidence of due diligence or evidence of neglect.
How TIN Comply Can Help
Start free. Use the tool yourself:
Our free 972CG Penalty Response Tool walks you through the full response workflow:
- Calculates your exact 45-day deadline from your notice date
- Classifies every payee on the notice with required actions
- Generates a draft reasonable cause abatement letter ready to review and send
No account required. Upload your 972CG extract or paste the data directly. Everything runs in your browser and nothing is uploaded to any server.
Need hands-on help?
If you're dealing with a large notice, a tight deadline, or want a professional to build and submit the response package for you, TIN Comply's 972CG Penalty Support managed service handles the full workflow.
Start a free trial · Request a demo
Quick Reference
| Question | Answer |
|---|---|
| What is Notice 972CG? | A proposed civil penalty for information return errors: TIN mismatches, missing TINs, late filing, wrong filing method |
| When does it arrive? | Typically 12 to 18 months after the returns were filed |
| How long do I have to respond? | 45 days (60 for foreign filers) |
| What happens if I don't respond? | Penalty is assessed and collection begins |
| Can I still respond after 45 days? | Yes, but it's harder: the penalty is now assessed |
| What's the max per-return penalty? | $330 for standard failures; $660 for intentional disregard (tax year 2024 returns, due in 2025) |
| What is reasonable cause? | Significant mitigating factors or circumstances beyond your control, documented |
| What's the key publication? | IRS Publication 1586: Reasonable Cause Regulations for Missing and Incorrect Name/TINs |
This article is for informational purposes only and does not constitute legal or tax advice. Consult a qualified professional for guidance specific to your organization.