What Is an IRS B-Notice? First vs. Second B-Notice Requirements Explained
A B-Notice is not a warning — it's a compliance obligation with a deadline attached. When the IRS issues a CP2100 notice listing vendors with name/TIN mismatches, the clock starts immediately: 15 business days to send a B-Notice to each affected vendor, 30 days for the vendor to respond, and backup withholding exposure if they don't. The difference between a First and Second B-Notice isn't just procedural — it changes what documentation the vendor must provide and what constitutes a valid response. Sending a First B-Notice when a Second is required is itself a compliance failure. Tracking which vendors have prior mismatch history is what determines which notice type applies.
What a B-Notice Is — and What It Isn't
A B-Notice is a letter the payer sends to a vendor after receiving an IRS CP2100 or CP2100A notice. It informs the vendor that the IRS has flagged their name/TIN combination as a mismatch on a filed information return, and it requests corrected taxpayer documentation to resolve the mismatch.
- CP2100 / CP2100A — The IRS notice to the payer. Lists vendors whose name/TIN combinations didn't match IRS records on filed 1099s.
- B-Notice — The letter the payer sends to the vendor in response to the CP2100. Informs the vendor of the mismatch; requests corrected taxpayer information.
The CP2100 is the trigger. The B-Notice is the required response. Missing the B-Notice deadline doesn't resolve the mismatch — it creates a separate compliance failure on top of the original filing error.
B-Notices are not optional, and they're not the same for every vendor. The IRS distinguishes between two types based on mismatch history, and the required vendor documentation is different for each.
First B-Notice vs. Second B-Notice — The Critical Distinction
| First B-Notice | Second B-Notice | |
|---|---|---|
| When it applies | First mismatch for this vendor within the IRS lookback period | Second mismatch for the same vendor within three calendar years of the first |
| What the vendor must provide | A new signed Form W-9 | SSA-issued verification (for SSN vendors) or an IRS TIN confirmation letter (for EIN vendors) |
| Is a W-9 sufficient? | Yes — a corrected, signed W-9 satisfies the First B-Notice requirement | No — a W-9 alone is not acceptable for a Second B-Notice |
| Compliance severity | Moderate | High — repeat mismatch indicates a persistent data problem |
| Backup withholding risk | Applies if vendor doesn't respond | Applies if vendor doesn't provide required verification |
The distinction matters in practice: if a vendor appeared on a CP2100 last year and a B-Notice was sent, and the same vendor appears again this year, the second notice must be a Second B-Notice — not a First. Sending a First B-Notice when a Second is required doesn't satisfy the IRS requirement and doesn't protect the payer.
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.
- 1st vs. 2nd B-Notice auto-classified
- Penalty exposure estimated
- Deadlines calculated automatically
- No account required
What a First B-Notice Requires
A First B-Notice is sent when the IRS flags a vendor for the first time within the lookback period. The required action is straightforward: notify the vendor of the mismatch, request a corrected signed W-9, and document the outreach.
The First B-Notice package typically includes:
- The IRS-provided First B-Notice template
- Clear identification of the mismatch: vendor name, TIN, and form year
- Instructions for completing and returning Form W-9
- The payer's contact information for questions
- A stated response deadline
- An explanation of backup withholding and when it applies
After the vendor provides a corrected W-9:
- Confirm the form is complete and signed
- Confirm the legal name is from W-9 Line 1 — not a DBA
- Run IRS TIN matching to confirm the corrected name + TIN resolves
- Update the vendor master only after TIN matching confirms a match
- Document the resolution: W-9 received date, validation result, vendor master updated
A corrected W-9 that still fails TIN matching is not a resolved B-Notice. The mismatch must be confirmed corrected through revalidation.
What a Second B-Notice Requires
A Second B-Notice is sent when the same vendor is flagged again within three calendar years of the first mismatch. The documentation requirement is significantly more stringent.
For SSN vendors (individuals): the vendor must obtain verification from the Social Security Administration confirming the correct name and SSN.
For EIN vendors (businesses): the vendor must obtain an IRS TIN confirmation letter confirming the correct legal name and EIN.
A First B-Notice mismatch could be a simple data entry error — a transposed digit, a missing suffix. The vendor self-certifies the correct information on a W-9. A Second mismatch on the same vendor means either the vendor's W-9 correction was wrong, or the same data problem persists despite prior outreach. At that point, the IRS requires verification from an authoritative external source — the SSA or IRS — not just the vendor's renewed attestation.
The Second B-Notice package typically includes:
- The IRS-provided Second B-Notice template
- Instructions for the vendor to contact the SSA (for SSN vendors) or the IRS (for EIN vendors)
- The specific verification documentation the vendor must obtain and provide
- A stated response deadline
- An explanation that backup withholding will apply if documentation isn't provided
What Happens If the Vendor Doesn't Respond
For both First and Second B-Notices, failure to provide the required documentation within the response window triggers backup withholding requirements.
- Backup withholding at 24% applies to applicable future payments
- Withholding begins after the vendor response window closes without documentation
- Withheld amounts must be remitted to the IRS on schedule
- Withholding continues until the vendor provides valid taxpayer information and a confirmed TIN match
- Documentation of withholding start date, amounts, and remittance must be retained
Backup withholding is not optional when the requirement applies. Continuing to pay a vendor at full value after the backup withholding obligation is triggered creates its own compliance exposure.
B-Notice Scenarios: What Each Looks Like in Practice
Scenario 1 — First B-Notice, Simple Resolution
Vendor filed:
- Name: Apex Consulting
- EIN: 12-3456789
IRS record: Apex Consulting LLC
CP2100 received. First B-Notice sent within 15 business days. Vendor submits corrected W-9 with "Apex Consulting LLC" on Line 1. IRS TIN matching confirms match. Vendor master updated. B-Notice resolved.
Scenario 2 — Second B-Notice Required
Same vendor appeared on last year's CP2100. First B-Notice was sent; vendor submitted a corrected W-9. Vendor appears on this year's CP2100 again — same mismatch persists.
Second B-Notice must be sent. Vendor must obtain IRS TIN confirmation letter (EIN vendor) and provide it to the payer. A corrected W-9 alone does not resolve a Second B-Notice.
Scenario 3 — Vendor Non-Response, Backup Withholding Applied
First B-Notice sent. No response within 30 days. Reminder sent. Still no response.
Backup withholding (24%) initiated on future payments. Date withholding began, amounts withheld per payment, and IRS remittance documentation all retained. Withholding continues until valid taxpayer information is confirmed.
Scenario 4 — Payer Sends Wrong Notice Type
Vendor appeared on CP2100 last year and a First B-Notice was sent. Same vendor appears this year. Payer sends another First B-Notice.
This is a compliance error. A Second B-Notice was required — a W-9 request is not sufficient for a second mismatch. The wrong notice type doesn't satisfy the IRS requirement, and it doesn't start the clock on the correct documentation standard.
B-Notice Compliance Timeline
| Milestone | Deadline / Action |
|---|---|
| CP2100 received | Log receipt date immediately — 15-business-day clock starts |
| First vs. Second determination | Review vendor mismatch history before preparing notices |
| B-Notices sent | Within 15 business days of CP2100 receipt |
| Proof of delivery retained | Certified mail or delivery confirmation per vendor |
| Vendor response window | Generally 30 days from B-Notice receipt |
| Backup withholding begins | If no valid response received after window closes |
| Corrected W-9 or SSA/IRS docs received | Revalidate via IRS TIN matching before clearing |
| Vendor master updated | Only after TIN matching confirms a match |
| Resolution documented | Date, documentation type, validation result, outcome |
Common B-Notice Mistakes
| Mistake | Why It's a Problem |
|---|---|
| Missing the 15-business-day deadline | Mandatory IRS requirement — late delivery is a compliance failure |
| Sending First B-Notice when Second is required | Wrong notice type doesn't satisfy IRS requirements |
| No mismatch history tracked per vendor | Can't make First vs. Second determination without it |
| Accepting a W-9 for a Second B-Notice | W-9 alone is insufficient — SSA or IRS documentation required |
| No proof of mailing retained | Can't demonstrate delivery if vendor claims non-receipt |
| Not revalidating after receiving corrected W-9 | Correction may still fail TIN matching |
| Not starting backup withholding after non-response | Withholding obligation exists regardless of vendor cooperation |
Best Practices
- Log CP2100 receipt date immediately — assign a compliance owner on day one
- Maintain per-vendor mismatch history to support First vs. Second determination
- Send B-Notices within 15 business days — no exceptions
- Use the IRS-provided template for the correct notice type
- Retain proof of delivery (certified mail or confirmed delivery) per vendor
- Send reminders at Day 15 and Day 30 for non-responding vendors
- Enforce Second B-Notice documentation requirements — W-9 not accepted
- Revalidate every corrected W-9 via IRS TIN matching before clearing the vendor
- Start backup withholding promptly for non-responding vendors and document everything
- Retain all outreach, documentation, and validation records per vendor for audit and abatement support
B-Notice Compliance Checklist
- CP2100 receipt date logged; compliance owner assigned
- Per-vendor mismatch history reviewed — First vs. Second B-Notice determined
- Correct IRS template prepared for each notice type
- B-Notices sent within 15 business days of CP2100 receipt
- Proof of mailing retained for every B-Notice sent
- Vendor response tracked — reminder sent at Day 15 and Day 30
- First B-Notice: corrected signed W-9 received and stored
- Second B-Notice: SSA or IRS verification documentation received (W-9 not accepted)
- Received documentation revalidated via IRS TIN matching before vendor is cleared
- Backup withholding started, documented, and remitted for non-responding vendors
- Complete B-Notice record retained per vendor: mismatch, notice type, outreach, response, revalidation, resolution
Frequently Asked Questions
Is a B-Notice the same as a CP2100 notice?
No. They're different documents with different purposes. A CP2100 is the IRS notice to the payer listing vendors with name/TIN mismatches. A B-Notice is the letter the payer is then required to send to each affected vendor. The CP2100 is the trigger; the B-Notice is the required response.
How do I determine whether to send a First or Second B-Notice?
By reviewing your vendor mismatch history. If this is the first time this vendor has been listed on a CP2100 within the lookback period, it's a First B-Notice. If the same vendor was flagged within the prior three calendar years and a B-Notice was sent at that time, it's a Second B-Notice. This determination requires per-vendor mismatch tracking — it can't be made from the CP2100 alone.
Can a First B-Notice be resolved with a W-9?
Yes. A First B-Notice requires the vendor to provide a new signed W-9 with corrected taxpayer information. Once received, the W-9 should be validated via IRS TIN matching to confirm the correction resolves the mismatch before the vendor record is updated.
Can a Second B-Notice be resolved with a W-9?
No. A Second B-Notice requires official verification — SSA-issued documentation for SSN vendors, or an IRS TIN confirmation letter for EIN vendors. A self-certified W-9 is not sufficient to satisfy a Second B-Notice requirement.
What happens if we accidentally send a First B-Notice when a Second is required?
The wrong notice type doesn't satisfy the IRS requirement. If the error is discovered before the response window closes, the correct Second B-Notice should be sent promptly with documentation of the correction. The compliance record should reflect both notices and the reason for the correction.
Conclusion
A B-Notice is a required IRS compliance action triggered by CP2100 mismatch notices — and the type of notice sent matters as much as whether it's sent at all. First B-Notices require a corrected W-9. Second B-Notices require SSA or IRS verification documentation, and a W-9 alone will not suffice. Missing the 15-business-day deadline, sending the wrong notice type, failing to track mismatch history, and skipping revalidation after corrections are the errors that convert a manageable B-Notice workflow into a compounding compliance problem. The organizations that handle B-Notices cleanly are the ones with the process built before the CP2100 arrives — tracking, templates, documentation, and revalidation all in place.
Reduce B-Notice Workload with TIN Comply
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, estimates your IRC §6721 penalty exposure by correction tier, and exports a prioritized action list — all based on IRS Publications 1281 and 1586.
- Classifies every payee as 1st or 2nd B-Notice automatically
- Estimates IRC §6721 penalty exposure by correction tier
- Calculates 15-business-day send deadline and BWH start date
- Detects 2-in-3 year rule — flags payees where no action needed
- Exports prioritized action list as CSV
- No account required — runs entirely in your browser