IRS CP2100 and B-Notices: The Complete Step-by-Step Response Workflow
When a CP2100 arrives, the clock starts immediately. Most AP teams treat it as a nuisance — a list of vendor mismatches to clean up when there's time. That's the wrong frame. A CP2100 triggers specific legal obligations with hard deadlines: First B-Notices must go out within 15 business days, vendors have 30 days to respond before backup withholding is required, and every step needs to be documented because the same mismatches will likely generate a Notice 972CG penalty proposal 12 to 18 months later. How you respond to the CP2100 is how you defend against the 972CG.
What Is a CP2100 Notice?
A CP2100 (or CP2100A for smaller lists) is the IRS's formal notification that information returns you filed — typically 1099s — contained TIN/name combinations that didn't match IRS records. The IRS generates these notices after processing your filings through its automated matching system.
CP2100 notices are typically issued in two waves each year: one in the fall covering returns filed in the spring, and one in the spring covering returns filed the prior January. If your notice covers more than 250 mismatched records, the list arrives on CD rather than paper.
CP2100 vs. CP2100A: The CP2100A is issued when the mismatch list is relatively small (generally under 50 records). The response obligations are identical — only the format differs.
The CP2100 B-Notice 972CG Sequence
Understanding how these three notices relate to each other is essential before diving into the response workflow:
CP2100 arrives first. It identifies which payees had TIN/name mismatches on your filed returns and triggers your B-Notice obligations.
B-Notices (First and Second) are what you send to your payees in response to the CP2100. They notify the payee of the mismatch and request a corrected W-9 or IRS TIN certification.
Notice 972CG arrives 12–18 months later and proposes a civil penalty for the mismatches identified on the CP2100. How thoroughly you completed your B-Notice workflow is the primary basis for a reasonable cause argument when responding to the 972CG.
In other words: your CP2100 response today is your 972CG defense tomorrow. Document everything.
First B-Notice vs. Second B-Notice
The IRS distinguishes between two types of B-Notices based on how many times the same payee has appeared on a CP2100:
First B-Notice — issued the first time a payee appears on a CP2100 (or the first time within a three-year window after a clean period). Requires the payee to provide a corrected TIN and name on a new W-9.
Second B-Notice — issued when the same payee appears on a CP2100 for the second time within three calendar years. A Second B-Notice has a higher standard: the payee must obtain IRS TIN certification directly, either through a CP-575 (EIN assignment letter) or by completing Form W-9 with a notation that the TIN has been certified with the IRS. You cannot accept a self-certified W-9 for a Second B-Notice payee.
Tracking which payees are on First vs. Second B-Notice status is an operational requirement, not optional. Most AP teams manage this in a spreadsheet alongside their vendor master.
Upload your CP2100 extract and the tool handles the workflow below automatically — classifying every payee as 1st or 2nd B-Notice, calculating your deadlines, flagging backup withholding triggers, and estimating your IRC §6721 penalty exposure based on your mismatch count and correction timing. Based on IRS Publications 1281 and 1586.
The Response Workflow: Step by Step
Step 1: Process the CP2100 List — Immediately
When the CP2100 arrives, pull the mismatch list and match each record against your vendor master. For each entry, determine:
- Is this a data entry error you can fix internally (wrong digit, name truncation, formatting issue)?
- Does this require a corrected W-9 from the vendor?
- Is this payee a First B-Notice or Second B-Notice situation?
Any mismatches you can resolve internally — for example, you find the correct TIN in your records and the issue was a data entry error on the filed 1099 — should be corrected now and flagged for a corrected 1099 filing.
Step 2: Send First B-Notices Within 15 Business Days
For all remaining mismatches that require vendor action, you must send a First B-Notice within 15 business days of receiving the CP2100. This is a legal deadline, not a guideline.
The First B-Notice must:
- Inform the payee that their TIN/name combination didn't match IRS records
- Request a corrected Form W-9 with their correct legal name and TIN
- Include a blank W-9 for the payee to complete and return
The IRS provides a sample First B-Notice letter. You can use the sample language or draft your own, but the content requirements are specific. Send by mail and retain proof of mailing — a certificate of mailing at minimum, certified mail for high-value vendors.
Start date for the 15-business-day clock: The date printed on the CP2100 notice, not the date you received it. If the notice was delayed in the mail, the clock was already running.
Step 3: Track Responses — 30-Day Vendor Window
After sending First B-Notices, payees have 30 business days to respond with a corrected W-9. Track each vendor's response status in your B-Notice log.
For vendors who respond with a corrected W-9:
- Validate the new TIN/name combination using IRS TIN matching before updating your records
- Update your vendor master with the corrected information
- Document the date received, the corrected TIN, and the TIN matching result
For vendors who do not respond within 30 business days, move to Step 4.
Step 4: Begin Backup Withholding for Non-Respondents
If a payee fails to provide a valid W-9 within 30 business days of your First B-Notice, you are required to begin backup withholding at 24% on all subsequent payments to that payee.
Backup withholding must:
- Be calculated on the gross payment amount
- Be remitted to the IRS on your regular deposit schedule
- Be tracked separately for year-end reconciliation on Form 945
- Be reflected on the payee's 1099 (gross payment in Box 1, backup withholding in Box 4)
Backup withholding continues until the payee provides a valid TIN — either a corrected W-9 (for First B-Notice situations) or IRS-certified TIN documentation (for Second B-Notice situations).
Step 5: Send Second B-Notices Where Required
If this is a payee's second appearance on a CP2100 within three years, send a Second B-Notice instead of a First B-Notice. The Second B-Notice informs the payee that because the mismatch has occurred a second time, a self-certified W-9 is no longer sufficient. The payee must provide one of the following:
- A copy of their CP-575 (EIN assignment notice from the IRS)
- A copy of a Social Security card or SSA letter confirming the SSN
- A letter from the IRS confirming the TIN
Until IRS-certified documentation is received, backup withholding applies to all payments regardless of payment amount.
Step 6: File Corrected 1099s
For mismatches that were corrected — either through your own records correction or through a vendor's corrected W-9 — file corrected 1099s. The sooner corrections are filed, the lower the potential penalty tier if a 972CG is later proposed.
Corrections filed within 30 days of the original filing deadline: $60 per return. Corrections filed between 30 days and August 1: $130 per return. Corrections filed after August 1: $330–$340 per return.
The August 1 cutoff is the most important date to track after receiving a CP2100. Every mismatch corrected before August 1 is at the lower penalty tier if a 972CG follows.
Step 7: Build Your Documentation File
Every step of this workflow should produce documentation:
- Copy of the CP2100 and the mismatch list
- Copy of each First and Second B-Notice sent, with proof of mailing
- Log of vendor responses: date received, corrected TIN, TIN matching result
- Log of non-respondents: dates of follow-up attempts, backup withholding start date, amounts withheld
- Copies of corrected W-9s received
- Record of corrected 1099 filings
This documentation file is your reasonable cause package if a 972CG arrives. The IRS is asking whether you responded to the CP2100 responsibly. This file answers that question.
Common Mistakes That Make CP2100 Response Worse
Waiting to respond. The 15-business-day deadline for First B-Notices is frequently missed by teams that treat the CP2100 as a low-priority item. Missing the deadline weakens your reasonable cause argument later.
Sending B-Notices without proof of mailing. If you can't prove you sent the notice, you can't use the sending as evidence of due diligence. Certified mail or at minimum a certificate of mailing for every First B-Notice.
Not tracking First vs. Second B-Notice status. Sending a First B-Notice to a payee who should receive a Second B-Notice — and accepting a self-certified W-9 — means you're not in compliance with the Second B-Notice requirements.
Starting backup withholding late or not at all. Backup withholding is a legal requirement, not optional. Failure to withhold when required creates a separate compliance exposure.
Not re-validating corrected W-9s through TIN matching. A payee providing a "corrected" W-9 doesn't guarantee the new information is correct. Validate every corrected W-9 through IRS TIN matching before updating your records and stopping backup withholding.
The CP2100 as a Prevention Signal
Every mismatch on a CP2100 represents a vendor whose TIN data was wrong at the time you filed. Most of those mismatches could have been caught and corrected before filing with pre-filing TIN matching — at zero penalty cost.
The practical prevention workflow:
- Run IRS TIN matching on your full vendor population in Q3 or early Q4 — before filing season, when you have time to resolve mismatches calmly
- Collect W-9s proactively from new vendors at onboarding and from existing vendors when TIN matching surfaces a mismatch
- Re-validate after any vendor name change, EIN change, or business structure change
- Keep your vendor master current year-round rather than discovering problems in November
Teams that run pre-filing TIN matching consistently see their CP2100 mismatch counts drop substantially year over year. The B-Notice workflow doesn't disappear — legacy data and unresponsive vendors are a permanent feature of any large vendor population — but the volume becomes manageable rather than overwhelming.
How TIN Comply Supports the Full B-Notice Workflow
CP2100 B-Notice Triage Tool
Upload your CP2100 extract or paste the data directly. The tool classifies every payee as 1st or 2nd B-Notice, calculates your send deadline and backup withholding start date, and estimates your IRC §6721 penalty exposure — showing your gross penalty, the impact of correction timing, and your potential reasonable cause savings. All based on IRS Publications 1281 and 1586.
- Classifies every payee as 1st or 2nd B-Notice automatically
- Calculates 15-business-day send deadline and BWH start date
- Estimates IRC §6721 penalty exposure by correction tier
- Detects 2-in-3 year rule — flags payees where no action needed
- Exports prioritized action list as CSV
- No account required — everything runs in your browser
Quick Reference: CP2100 Response Deadlines
| Action | Deadline |
|---|---|
| Send First B-Notices | Within 15 business days of CP2100 date |
| Vendor response window | 30 business days after First B-Notice |
| Begin backup withholding (non-respondents) | After 30-day vendor window closes |
| File corrected 1099s — lowest penalty tier | Within 30 days of original filing deadline |
| File corrected 1099s — mid penalty tier | By August 1 |
| File corrected 1099s — highest penalty tier | After August 1 |
| Respond to Notice 972CG (if received) | Within 45 days of 972CG date |
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.