What Is a CP2100 Notice? What It Means and What to Do Next

What a CP2100 Notice Is

A CP2100 notice is an IRS notice sent to a payer — a business that filed 1099 information returns — informing them that one or more of those returns contained a name/TIN combination that didn't match IRS records. It lists each affected vendor with the submitted name and TIN. It is not a penalty notice — it doesn't assess a dollar amount. But it is a compliance trigger: it starts a mandatory response process with defined deadlines, and failure to complete that process creates penalty exposure that the CP2100 itself does not.

What Causes a CP2100 Notice

The CP2100 is the result of the IRS's post-filing name/TIN matching process. After 1099 returns are processed, the IRS validates each payee's submitted name and TIN against its taxpayer records. When the combination doesn't resolve — regardless of the reason — it appears on the CP2100.

Most CP2100 mismatches are data quality problems, not vendor fraud. The vendor is typically legitimate — the name or TIN in the vendor master is just wrong relative to what the IRS has on file.

The Compliance Sequence a CP2100 Starts

Missing the 15-business-day B-Notice deadline doesn't resolve the mismatch — it creates a second compliance failure on top of the original filing error. The clock runs from the date the CP2100 is received, not the date it's opened or reviewed.

First B-Notice vs. Second B-Notice

The CP2100 notice does not specify whether the required B-Notice is a First or Second — that determination belongs to the payer, based on their vendor mismatch history. Getting it right matters because the two notice types require different documentation from the vendor.

Organizations that don't track per-vendor mismatch history can't make the First vs. Second determination. A vendor history log — showing every prior CP2100 listing and B-Notice sent — is required infrastructure for compliant CP2100 response.

What Backup Withholding Means in Practice

If a vendor doesn't provide the required documentation within the response window after receiving a B-Notice, backup withholding applies to future payments at 24%. Withholding begins after the window closes, amounts withheld must be remitted to the IRS on schedule, and withholding continues until valid documentation is provided and confirmed via TIN matching.

What Happens If the CP2100 Process Isn't Completed

If the B-Notice requirement is missed, backup withholding isn't applied when required, or documentation isn't retained, the IRS may assess penalties via Notice 972CG — a formal penalty notice for information return failures. Penalties are assessed per form. An organization with 75 vendors on a CP2100 that doesn't complete the B-Notice process correctly has penalty exposure across all 75 records, not just the ones where outreach was missed.

The 972CG requires a written response before its stated deadline, and the penalty is not final until that window closes. A documented CP2100 response record — showing B-Notices sent, vendor responses tracked, withholding applied where required, and corrections validated — is the foundation of a penalty abatement request.

How to Reduce Future CP2100 Notices

CP2100 notices are a trailing indicator of vendor data quality. They arrive months after the problem was created. The controls that prevent them work at the point where the data problem originates: vendor onboarding and annual revalidation.

Organizations that implement these controls consistently see CP2100 volume decline each filing cycle. The vendors that appear on CP2100 notices repeatedly are almost always the ones where one of these controls was skipped at onboarding or never applied retroactively.

Best Practices

CP2100 Response Checklist

• CP2100 receipt date logged; compliance owner assigned day of receipt
• Full vendor mismatch list reviewed; count of affected records confirmed
• Per-vendor mismatch history reviewed — First vs. Second B-Notice determined for each vendor
• Correct IRS template prepared for each notice type
• All B-Notices sent within 15 business days of CP2100 receipt
• Proof of delivery retained per vendor (certified mail or confirmed delivery)
• Vendor response tracked — reminder sent at Day 15 and Day 30
• Corrected W-9 or SSA/IRS documentation received and stored per vendor
• Received documentation revalidated via IRS TIN matching
• Vendor master updated only after TIN matching confirms a match
• Backup withholding started for non-responding vendors — amounts and dates documented
• Full CP2100 response record retained per vendor for 972CG abatement support

Frequently Asked Questions

Is a CP2100 notice the same as a B-Notice?

No — they're different documents at different stages of the same process. A CP2100 is the IRS notice to the payer listing vendors with name/TIN mismatches. A B-Notice is the letter the payer must then send to each affected vendor. The CP2100 triggers the B-Notice obligation; the two are related but distinct.

Does receiving a CP2100 mean our vendors are fraudulent?

Rarely. The overwhelming majority of CP2100 mismatches are data quality problems — DBA names in the legal name field, missing suffixes, transposed digits, stale records after entity changes. Fraud-related mismatches exist but represent a small fraction of typical CP2100 lists.

Do we need to respond to a CP2100 if we've already corrected the vendor's data?

Yes. The CP2100 response process — B-Notice, documentation, revalidation — is required regardless of whether the underlying data has been corrected in the vendor master. The B-Notice notifies the vendor of the historical mismatch and requests documentation; it runs parallel to, not instead of, vendor master updates.

What happens if we miss the 15-business-day B-Notice deadline?

Missing the B-Notice deadline is a compliance failure independent of the original mismatch. Send the B-Notices as soon as the deadline is identified as missed — late delivery is better than non-delivery. Document the circumstances and retain the record, as this context may be relevant if a 972CG penalty response is needed.

Can CP2100 notices be prevented entirely?

Not with certainty — but volume can be reduced significantly. Organizations that run IRS TIN matching at onboarding and Q4 bulk revalidation annually see CP2100 volumes decline year over year because most mismatches are caught and corrected before any 1099 is filed.

Conclusion

A CP2100 notice is the IRS's notification that vendor name/TIN combinations on filed 1099 returns didn't match its records — and it starts a mandatory compliance sequence with hard deadlines. The required response: B-Notices sent within 15 business days, First vs. Second type determined by vendor mismatch history, backup withholding applied for non-responders, corrections revalidated via TIN matching, and the full record retained per vendor. What determines whether a CP2100 is a manageable annual process or a compounding compliance problem is whether the response infrastructure exists before the notice arrives — and whether the prevention controls at onboarding and Q4 are reducing the list that next year's CP2100 contains.

Reduce CP2100 Notices with TIN Comply