What Happens If a Vendor Provides the Wrong SSN? CP2100 Notices, B-Notices, and Next Steps
A wrong SSN runs the same course as a wrong EIN, with one twist: under an SSN the IRS matches the surname, so a trade name or an outdated married name fails like a transposed digit. This page covers each stage and the six-step fix.
Updated October 28, 2026.
Why Wrong SSN Situations Are Common for Individual Contractors
SSN mismatches for individuals occur more frequently than EIN mismatches for business entities, for a straightforward reason: individuals are more likely to complete W-9 forms by hand, to put a trade name where their own name belongs, and to be unsure which surname the SSA holds for their SSN.
- TIN mismatch: The SSN digits are wrong: transposed, missing, or copied incorrectly. The number doesn't resolve to any IRS record (TIN Matching code 2), or resolves to a different individual entirely (code 3).
- Name mismatch: The SSN is correct, but the surname submitted doesn't derive the four-character name control the IRS holds for that SSN: a trade name in the name field, a married or maiden name the SSA record doesn't yet show, or a hyphenated surname entered without its hyphen (code 3).
Both produce the same CP2100 result at filing. But the correction process is different: a digit error in the SSN requires a corrected W-9 with the right number confirmed; a name mismatch requires confirming the exact legal name registered with the SSA and IRS, which is the name on the contractor's Social Security card, not the name they use day-to-day.
The Compliance Sequence Triggered by a Wrong SSN
| Stage | What Happens |
|---|---|
| At filing | 1099-NEC filed with incorrect SSN: IRS name + TIN match fails |
| Post-filing | IRS issues CP2100 / CP2100A listing the contractor as a mismatch |
| Within 15 business days | Payer must send the B-Notice (counted from the CP2100 notice date or receipt, whichever is later) |
| Within 30 business days | Contractor must return a signed W-9 (or an SSA printout on a second B-Notice) |
| If contractor doesn't respond | Backup withholding at 24% must begin on payments made after the 30 business days |
| If unresolved | IRS Notice 972CG: formal penalty assessment |
| Corrected filings | Payer may need to file corrected 1099-NEC with the right SSN |
The payer is responsible for this sequence regardless of whether the contractor caused the error. Documented good-faith effort (collecting the W-9, running TIN matching, requesting correction when a mismatch is identified) is the primary defense available. But the compliance obligations exist independent of fault.
Common Reasons Contractors Provide Wrong SSNs
| Cause | What's Actually Happening |
|---|---|
| Transposed digits | Two digits written in wrong order on a handwritten W-9, extremely common |
| Misremembered number | Contractor recalls SSN incorrectly, rare but happens |
| Uses ITIN when SSN expected | Foreign-born contractor with both an ITIN and SSN provides wrong one |
| Spouse's SSN submitted | Joint filer accidentally provides spouse's number |
| Trade name in the name field | "Mike's Plumbing" submitted with the SSN of Michael Johnson: MIKE does not match JOHN |
| Married/maiden name mismatch | Surname changed since SSA record was last updated |
| Name change not yet filed with the SSA | New married name used on the W-9 while the SSA still holds the prior surname |
| Hyphenated last name handled inconsistently | "Smith-Jones" vs. "Smith Jones" vs. "SmithJones": the IRS keeps the hyphen in the name control |
| AP team data entry error | Correct SSN on W-9, wrong digit entered into payroll or ERP system |
What Happens at Each Stage If the Wrong SSN Isn't Caught
Caught at Onboarding: Best Case
IRS TIN matching run before the first payment returns a mismatch. The contractor is contacted with specific correction detail: whether the issue is the SSN digits, the legal name format, or both. A corrected W-9 is received, revalidated, and the contractor record is updated before any payment is made. The wrong SSN never appears on a filed 1099-NEC.
Caught During Q4 Bulk Validation
The wrong SSN has been on file since onboarding but no 1099 has been filed yet. Q4 bulk TIN matching identifies the mismatch. The contractor outreach is initiated with the specific correction detail. Corrected W-9 is received and revalidated before filing deadlines. The wrong SSN still doesn't reach a filed 1099-NEC.
Discovered After a 1099-NEC Is Filed
The wrong SSN was used on a filed 1099-NEC. The IRS issues a CP2100 notice. The payer must:
- Send a B-Notice to the contractor within 15 business days of the CP2100 notice date or receipt, whichever is later
- Track the contractor's response within the 30-business-day window
- Collect a corrected W-9, validate it, and update the contractor record
- File a corrected 1099-NEC using the accurate SSN
- Apply backup withholding (24%) if the contractor doesn't respond
- Document the entire process for potential 972CG penalty response
Step-by-Step: How to Fix a Wrong SSN From a Contractor
Step 1: Request a Corrected W-9 With Specific Detail
Don't send a generic W-9 request. Tell the contractor specifically what the problem is: the SSN provided doesn't match IRS records for their name. Ask them to confirm both their legal name as it appears on their Social Security card and their correct SSN, and to reference their Social Security card directly if there's any uncertainty.
Step 2: Confirm the Legal Name Alongside the SSN
SSN mismatches often involve both a digit error and a name format issue. When requesting a corrected W-9, ask the contractor to confirm:
- Their legal first name as registered with the SSA (not a nickname)
- Middle name or middle initial if the IRS record includes it
- Last name exactly as spelled on their Social Security card, including hyphens if applicable
- Whether they have had a name change since their SSA record was last updated
Step 3: Run IRS TIN Matching on the Corrected Information
A corrected W-9 is the contractor's new attestation, not confirmation that the correction is right. Revalidate via IRS TIN matching before updating the contractor record. This is the step most often skipped, and it's how a corrected record with a second error produces another CP2100 at the next filing cycle.
Step 4: Update the Contractor Record and Document the Change
Update the SSN in your payroll or AP system with a notation of the change, the date, the corrected W-9 received, and the TIN matching validation result. This documentation supports audit defense and, if a 972CG notice arrives, reasonable-cause abatement.
Step 5: File a Corrected 1099-NEC If the Wrong SSN Was Already Filed
If a 1099-NEC was filed using the incorrect SSN, a corrected filing may be required. The corrected return should use the accurate SSN confirmed through revalidation. Retain documentation of both the original filing and the correction.
Step 6: Respond to CP2100 and 972CG Notices With Full Documentation
If the wrong SSN triggered IRS notices before it was corrected, respond with the complete correction record: the original W-9 showing the wrong SSN, the outreach record requesting correction, the corrected W-9 received, the TIN matching confirmation, and the corrected 1099-NEC. This record demonstrates good-faith compliance effort and supports penalty abatement.
Best Practices for Preventing Wrong SSN Problems
- Collect a signed W-9 before contractor activation: no payment without certified taxpayer documentation
- Use electronic W-9 collection with format validation: catches digit errors at source before they reach the vendor master
- Explicitly ask for legal name as it appears on the contractor's Social Security card, not their preferred or informal name
- Run IRS TIN matching at onboarding, before the first payment
- Confirm TIN type (SSN vs. EIN vs. ITIN) and confirm it's consistent with the contractor's entity structure
- Run Q4 bulk TIN matching annually across all 1099-NEC reportable contractors
- Request an updated W-9 after any contractor name change (marriage, divorce, legal name change)
- Revalidate every corrected SSN via TIN matching before marking the contractor as filing-ready
- Restrict manual SSN entry in payroll and AP systems where possible: import from validated W-9 data instead
Wrong SSN Prevention and Response Checklist
- W-9 collected and signed before contractor activation
- Legal name confirmed from Social Security card, not nickname or informal name
- SSN format validated: 9 digits, correct structure (XXX-XX-XXXX)
- TIN type confirmed: SSN (vs. EIN or ITIN) consistent with contractor status
- IRS TIN matching run at onboarding: name + SSN confirmed against IRS records
- Q4 bulk TIN matching run annually before filing season
- Wrong SSN identified: corrected W-9 requested with specific correction detail
- Corrected W-9 received, stored, and revalidated via TIN matching
- Contractor record updated with confirmed-match SSN and change documented
- Corrected 1099-NEC filed if original used wrong SSN
- CP2100 / B-Notice / 972CG response documentation retained per contractor
Frequently Asked Questions
Can the IRS penalize a business for a wrong SSN that the contractor provided?
Yes. The payer is responsible for the accuracy of information returns regardless of where the error originated. Documented good-faith outreach (W-9 collection, TIN matching, correction request when a mismatch is found) is the primary defense, but it doesn't eliminate the obligation to report correctly.
Is it illegal for a contractor to provide the wrong SSN?
Unintentional errors (transposed digits, nickname vs. legal name) are not illegal. A contractor who knowingly provides a false SSN on a W-9, which is signed under penalty of perjury, is a different situation. Most wrong SSN cases are accidental and correctable with a new W-9.
How do I tell if the mismatch is a digit error or a name format issue?
IRS TIN matching gives a partial answer: code 2 means the SSN itself is not currently issued, so the digits are wrong; code 3 means the SSN exists but the name does not pair with it, which points to the surname or to a different person's number. Request a corrected W-9 asking the contractor to confirm both their SSN and their legal name as it appears on their Social Security card. Then revalidate. If the corrected W-9 still mismatches, the issue may be that the IRS record hasn't been updated for a name change, which requires the contractor to contact the SSA directly.
What if the contractor insists their SSN is correct but TIN matching still fails?
Ask them to confirm their SSN from their Social Security card directly, not from memory. Also ask them to confirm their IRS-registered legal name. If both appear correct and TIN matching still fails, the contractor may need to contact the SSA to verify that their SSA and IRS records are consistent and up to date.
Should the SSN be re-validated after a contractor changes their legal name?
Yes. A legal name change (from marriage, divorce, or other reason) requires an updated W-9 with the new legal name, and the new name + SSN combination should be revalidated via IRS TIN matching to confirm the SSA record has been updated to reflect the change.
Conclusion
A wrong SSN from a contractor creates the same compliance accountability chain as any other information return error: the payer is responsible for what was filed, regardless of where the error originated. Caught at onboarding via IRS TIN matching, a wrong SSN is a W-9 correction request and a revalidation. Caught after a 1099-NEC is filed, it becomes a B-Notice workflow, a corrected return, potential backup withholding, and potential 972CG exposure. The controls that prevent it are consistent: collect a signed W-9 before activation, validate the name + SSN combination via IRS TIN matching before the first payment, run Q4 bulk validation before every filing season, and revalidate every correction before updating the contractor record.
Validate Contractor SSNs with TIN Comply
Real-time IRS TIN Matching at contractor setup. Bulk files (.csv and .xlsx) across your full 1099-NEC reportable population before filing season. A Request Corrected W-9 button on every mismatch. Revalidation after corrections. And per-request history with user attribution and timestamps for CP2100 response and 972CG relief.
- Real-time IRS TIN Matching: catches wrong SSNs before first payment
- Bulk contractor list validation (.csv and .xlsx) for Q4 pre-filing cleanup
- Request Corrected W-9 on any mismatch, tracked as SENT, OPENED and COMPLETED with a signed PDF
- Address validation (USPS standardization, ZIP+4) so the corrected 1099-NEC copy reaches the contractor
- Per-request history with user attribution, timestamps and filtered exports
- REST API for ERP and AP system integration