Your IRS Notices Are Telling You Whether You Are Ready for IRIS
This year's notices describe last year's filing. With IRIS, they also describe the data you are about to submit.
If you are treating this year's IRS Notices 972CG and CP2100/CP2100A as routine year-end compliance matters, you may need to rethink your strategy.
These notices should also be viewed as insight into the quality of the data you will soon be submitting through the IRS's Information Returns Intake System (IRIS). With FIRE being retired, organizations that have historically dealt with information-reporting problems after filing should consider whether those same problems can be identified and resolved before the next filing season.
That matters because IRIS does more than receive an electronic file. It applies schemas and business rules to the information being submitted. As a result, problems sitting within vendor and payee data can become visible much earlier in the filing process. The IRS has specifically stated that an IRIS Accepted with Errors result for a Name/TIN mismatch is a "pre-check" prior to a CP2100 or CP2100A notice.
CP2100 and CP2100A: Look Beyond the B-Notice
A CP2100 or CP2100A tells a payer that information returns contained missing or incorrect TINs or Name/TIN combinations that did not match IRS records. The distinction between the two notices is primarily volume: CP2100 generally applies when 50 or more erroneous information returns are identified, while CP2100A applies when fewer than 50 are identified.
The immediate response remains important. Depending upon the circumstances, the payer may need to issue a First or Second "B" Notice, solicit corrected information and begin backup withholding. The current backup-withholding rate is 24%.
But don't stop there.
The payee listing accompanying the notice is also a data-quality report.
🔍 If Your Organization Received 40, 400 or 4,000 Name/TIN Mismatches, Ask Why
- Were Forms W-9 completed incorrectly?
- Were sole proprietors loaded under a business name rather than the appropriate tax name?
- Were TINs entered incorrectly?
- Is vendor-master data being changed after the Form W-9 is collected?
- Are acquisitions, decentralized accounts-payable functions or multiple ERP systems contributing to the problem?
Resolving the individual B-Notices addresses today's compliance obligation. Resolving the process that created those mismatches helps address tomorrow's IRIS problem.
The IRS itself recommends TIN Matching as a way for eligible payers to validate Name/TIN combinations before filing and notes that organizations that validate this information in advance should receive fewer CP2100 and penalty notices.
Notice 972CG: Your Penalty Notice Is Also Telling You Something
Notice 972CG presents a different issue. It is a proposed information-return penalty notice.
An organization receiving a 972CG should, of course, determine whether the proposed penalty is correct and whether reasonable-cause relief is available. The IRS currently provides 45 days to respond, or 60 days for foreign filers, before assessing the proposed penalty.
But again, the analysis should not end with getting the penalty reduced or abated.
Ask what caused the notice.
❓ What Produced the Penalty Population?
- Was information missing?
- Was the return filed late?
- Was information incorrect?
- Were corrections not completed promptly?
- Was the organization unable to obtain proper documentation from the payee?
Those answers identify weaknesses in the reporting process.
This is particularly important because reasonable cause itself looks at the organization's behavior. The IRS considers whether the filer acted responsibly before and after the failure, including whether it tried to prevent a foreseeable failure and corrected the problem as quickly as possible.
A successful penalty response therefore shouldn't simply close the notice. It should generate a list of process improvements for the next filing season.
IRIS Changes the Timing of the Conversation
Historically, an organization might file its Forms 1099, receive an IRS notice months later, resolve the notice and move on.
IRIS provides an opportunity — and, increasingly, a reason — to move that analysis forward.
As discussed above, a recipient Name/TIN mismatch can now appear as an Accepted with Errors result. The submission has been accepted, but the error has already been identified. The IRS has said these records are considered accepted but should be corrected, and certain Accepted with Errors situations may ultimately result in proposed penalties.
That changes the question from:
"How do we respond to this IRS notice?"
to:
"Why did our data create the error in the first place, and can we fix it before we submit next year's returns?"
Use 2026 Notices as a Readiness Test
Organizations receiving CP2100, CP2100A or 972CG notices this year should consider conducting a simple look-back before beginning their next information-reporting cycle:
- Identify every error population appearing on the notices.
- Trace those errors back to the underlying Form W-9, vendor record and payment data.
- Determine whether the issue resulted from documentation, data entry, system configuration or reporting logic.
- Correct the current records rather than merely correcting the prior-year return.
- Use IRS TIN Matching where appropriate.
- Determine whether the same issue could trigger an IRIS error when the next information returns are submitted.
- For foreign-payee populations, perform the same exercise with Forms W-8 and the data feeding Form 1042-S.
The last point is particularly important. The transition to IRIS is not limited to Forms 1099. Organizations making reportable payments to foreign persons may have significantly more complex Form 1042-S data, including country, TIN, Chapter 3 and Chapter 4 status, exemption codes and treaty-related information.
Don't Waste the Notice
A CP2100, CP2100A or 972CG notice tells you what went wrong with a prior filing.
With IRIS, that information has another use.
It tells you where to look before you file again.
Organizations that use this year's notices simply to correct last year's problems may find themselves addressing many of the same data issues during the next filing season. Organizations that use the notices to identify weaknesses in documentation, vendor onboarding, TIN validation, withholding and reporting processes have an opportunity to correct those problems before their data reaches IRIS.
The notice may relate to last year's return.
The lesson should be applied to next year's filing.
Turn this year's notices into next year's readiness plan
We trace CP2100, CP2100A and 972CG error populations back to the Form W-9, vendor record and reporting logic that produced them — and correct the process before the data reaches IRIS.