What Happens If a Vendor Provides the Wrong SSN? CP2100 Notices, B-Notices, and Next Steps

A wrong SSN from an independent contractor carries the same compliance chain as a wrong EIN from a business vendor — CP2100 notice, B-Notice requirement, backup withholding exposure, potential 972CG penalty — but with one additional layer of complexity: SSN mismatches for individuals are more likely to involve name formatting issues alongside the TIN error. A contractor who submits "Mike Johnson" when the IRS has "Michael A. Johnson" on file, or who transposes two digits in their SSN on a handwritten W-9, creates a mismatch that the payer is accountable for correcting. The payer can't control what the contractor submits. They can control whether it's validated before the first payment or discovered after the first filing.

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, more likely to use informal name variations, and more likely to be unfamiliar with which name the IRS has on file for their SSN.

The two distinct categories of SSN mismatch:
  • TIN mismatch: The SSN digits are wrong — transposed, missing, or copied incorrectly. The number doesn't resolve to any IRS record, or resolves to a different individual entirely.
  • Name mismatch: The SSN is correct, but the name submitted doesn't match the name the IRS has registered for that SSN — nickname instead of legal name, maiden name not updated after marriage, missing middle initial the IRS record includes.

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

What happens at each stage when a wrong SSN reaches a filed 1099:
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 B-Notice to the contractor
Within 30 days Contractor must respond with corrected taxpayer information
If contractor doesn't respond Backup withholding (24%) may apply on future payments
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
Nickname vs. legal name "Mike Johnson" submitted when IRS record is "Michael A. Johnson"
Married/maiden name mismatch Name changed since SSA record was last updated
Missing or extra middle initial IRS record includes middle initial that wasn't provided, or vice versa
Hyphenated last name handled inconsistently "Smith-Jones" vs. "Smith Jones" vs. "SmithJones"
AP team data entry error Correct SSN on W-9, wrong digit entered into payroll or ERP system
Electronic W-9 collection with format validation catches digit errors at submission — confirming nine digits, proper format, no invalid characters. It doesn't eliminate name mismatches, but it eliminates the transposition and truncation errors that are the most common category of SSN digit problems.

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.

Correction at onboarding: one W-9 request, one revalidation, one record update. Total compliance exposure: zero.

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 receiving the CP2100
  • Track the contractor's response within the 30-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
The same SSN error — caught at onboarding — required one correction request and nothing else. Caught after filing: B-Notice workflow, corrected 1099, potential backup withholding, potential 972CG response. The cost of not validating early compounds with every stage of the sequence.

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.

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
For individual contractors, the IRS derives name control from the last name. A last name spelling discrepancy is therefore a more direct mismatch risk than a first name variation — but both should be confirmed against the Social Security card, not the contractor's preferred name.

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

The controls that prevent most wrong SSN situations:
  • 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 will return a mismatch but won't specify which element caused it. 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.

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

TIN Comply validates contractor name and SSN combinations against IRS records in real time — so wrong SSNs are caught at onboarding and in Q4 bulk validation, not discovered on a CP2100 notice after filing.

Real-time IRS TIN/Name matching at contractor setup. Bulk SSN validation across your full 1099-NEC reportable population before filing season. Automated W-9 outreach for mismatches with specific correction guidance. Revalidation after corrections. And a complete audit-ready validation history retained per contractor for CP2100 response and 972CG abatement support.

  • Real-time IRS TIN/Name matching — catches wrong SSNs before first payment
  • Bulk contractor list validation for Q4 pre-filing cleanup
  • Automated W-9 outreach with specific correction detail per mismatch type
  • Revalidation workflow — confirms SSN corrections before contractor record is updated
  • Audit-ready validation history and mismatch resolution logs per contractor
  • API integration with SAP, Oracle, Workday, NetSuite, and more

Start Free Trial Request a Demo