What Happens If a Vendor Provides the Wrong EIN? Mismatches, Notices, and Next Steps

A vendor gave you an EIN that does not match IRS records, and the payer, not the vendor, answers for what gets filed. This page covers what happens at each stage and the six steps that fix it, from corrected W-9 to 972CG response.

Updated October 28, 2026.

Why a Wrong EIN Creates Payer Liability

When a 1099 is filed, the IRS cross-references the vendor name and TIN against its taxpayer records. If the EIN is wrong (whether by one transposed digit, a parent company's EIN used instead of the subsidiary's, or a sole proprietor's EIN submitted where the IRS expects their SSN), the name + EIN combination fails to resolve. The result is treated as an incorrect information return, and the penalty exposure belongs to the payer.

The compliance sequence triggered by a wrong EIN:
Stage What Happens
At filing 1099 filed with incorrect EIN, so the IRS name + TIN match fails
Post-filing IRS issues CP2100 / CP2100A listing the vendor 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 Vendor must return a signed W-9 (or IRS Letter 147C on a second B-Notice)
If vendor 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 for incorrect information return
Corrected filings Payer may need to file corrected 1099 with the right EIN

Every step in that sequence (the B-Notice, the withholding application, the corrected filing, the penalty response) is work that could have been avoided with IRS TIN matching at onboarding. The wrong EIN was always fixable. The question is whether it gets fixed before filing or after.


Why Vendors Provide Wrong EINs

Understanding the source of the error determines the correct fix, and informs what documentation to request.

Common wrong EIN scenarios and what causes them:
Cause What's Actually Happening
Transposed digits on W-9 Vendor wrote or typed digits in wrong order (very common with handwritten forms)
Outdated EIN from prior entity Vendor underwent restructuring; old EIN provided from habit or prior records
Parent company EIN with subsidiary name Vendor has multiple entities and cross-referenced the wrong one
Sole proprietor EIN/SSN confusion Vendor has both an EIN and an SSN; provided the one the IRS doesn't associate with their name
AP team data entry error Correct EIN on W-9, but wrong digit entered into ERP during manual keying
EIN from accounting firm Vendor provided their accountant's EIN or a test EIN instead of their own
DBA name with EIN from different entity Vendor filed under a trade name with a TIN registered to a different legal entity

Many wrong EIN situations are vendor-caused, but the payer's compliance exposure exists regardless. That's why validation at onboarding is the correct control, not trust in the vendor's self-reported accuracy.


What Happens at Each Stage If the Wrong EIN Isn't Caught


If Caught at Onboarding (Best Case)

IRS TIN matching run before the first payment returns a mismatch result. The vendor is contacted with specific correction detail. A corrected W-9 is received, revalidated, and the vendor master is updated before any payment is made. The wrong EIN never appears on a filed 1099.

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

If Caught During Q4 Bulk Validation

The wrong EIN has been on file since onboarding but no 1099 has been filed yet. Q4 bulk TIN matching identifies the mismatch. Vendor outreach is initiated. Corrected W-9 is received and revalidated before filing season begins. The wrong EIN still doesn't reach a filed 1099.

Correction at Q4 validation: W-9 outreach and revalidation under a reasonable timeline. Exposure: minimal if completed before filing.


If Discovered After a 1099 Is Filed

The wrong EIN was filed on a 1099. The IRS issues a CP2100 notice. The payer must:

  • Send a B-Notice to the affected vendor within 15 business days of the CP2100 notice date or receipt, whichever is later
  • Track the vendor's response within the 30-business-day window
  • Collect a corrected W-9, validate it, and update the vendor master
  • File a corrected 1099 if the original was filed with the wrong EIN
  • Apply backup withholding if the vendor doesn't respond
  • Document the entire process for potential 972CG penalty response
Correction after filing: B-Notice workflow, corrected 1099, potential backup withholding, potential 972CG response. The same EIN error, caught three months earlier at onboarding, required one correction request and nothing else.

If the Same Wrong EIN Is Filed Again the Following Year

Without a corrected vendor master update, the wrong EIN will appear on the next year's 1099, producing another CP2100 and, because the same payee is listed twice within three years, a Second B-Notice, which requires IRS Letter 147C for an EIN (or an SSA printout for an SSN) rather than a new W-9. Repeat mismatches build a fact pattern of continued noncompliance that supports elevated penalty assessment.


Step-by-Step: How to Fix a Wrong EIN From a Vendor


Step 1: Request a Corrected W-9 With Specific Detail

Don't send a generic W-9 request. Tell the vendor specifically what the problem is: the EIN provided doesn't match IRS records for their entity. Ask them to confirm their legal name as registered with the IRS and their correct EIN, and to reference their IRS EIN confirmation letter (CP 575), or request Letter 147C from the IRS if they no longer have it, when there's any uncertainty about the right number.


A wrong EIN sometimes signals a deeper mismatch: the vendor may have provided an EIN registered to a different legal entity, or an EIN that goes with a different name than what's in your system. Confirm both the EIN and the IRS-registered legal name associated with it are consistent before accepting the corrected W-9.


Step 3: Run IRS TIN Matching on the Corrected Information

A corrected W-9 is the vendor's new attestation, not confirmation that the correction is right. Revalidate via IRS TIN matching before updating the vendor master. This is the step most organizations skip, and it's how corrected records sometimes contain a second error that produces another mismatch at the next filing.

Step 4: Update the Vendor Master and Document the Change

Update the EIN in your ERP with a notation of the change, the date, the corrected W-9 received, and the TIN matching validation result. All of this documentation supports audit defense and, if a 972CG penalty notice arrives, reasonable-cause abatement.


Step 5: File a Corrected 1099 If the Wrong EIN Was Already Filed

If a 1099 was filed using the incorrect EIN, a corrected 1099 may be required. The corrected filing should use the accurate EIN confirmed through revalidation. Retain documentation of both the original filing and the correction.


Step 6: Respond to Any CP2100 or 972CG Notices With Documentation

If the wrong EIN triggered IRS notices before it was corrected, respond to those notices with the full correction documentation: the original W-9 showing the wrong EIN, the outreach record requesting correction, the corrected W-9 received, the TIN matching confirmation, and the corrected 1099 filing. This record demonstrates good-faith compliance effort and supports penalty abatement.


How to Prevent Wrong EIN Problems

The prevention controls that eliminate most wrong EIN exposure:
  • Collect a signed W-9 before vendor activation: no payment without certified taxpayer documentation
  • Run IRS TIN matching at onboarding, before the first payment, not at year-end
  • Use electronic W-9 collection with format validation: nine-digit EIN enforcement prevents transposition errors at source
  • Confirm TIN type at onboarding: EIN vs. SSN vs. ITIN confirmed against entity structure
  • Run Q4 bulk TIN matching annually: catches EINs that have become stale since onboarding
  • Request updated W-9 after any vendor entity restructuring, merger, or name change
  • Restrict manual EIN entry in ERP: require W-9 upload and field population from the form, not manual keying
  • Revalidate every corrected EIN before moving vendor to filing-ready status

Wrong EIN Prevention and Response Checklist

  • W-9 collected and signed before vendor activation
  • EIN format validated: 9 digits, correct structure (XX-XXXXXXX for EIN)
  • TIN type confirmed (EIN vs. SSN) consistent with vendor entity structure
  • IRS TIN matching run at onboarding: name + EIN confirmed against IRS records
  • Q4 bulk TIN matching run annually before filing season
  • Wrong EIN identified: corrected W-9 requested with specific correction detail
  • Corrected W-9 received, stored, and revalidated via TIN matching
  • Vendor master updated with confirmed-match EIN and change documented
  • Corrected 1099 filed if original used wrong EIN
  • CP2100 / B-Notice / 972CG response documentation retained per vendor

Frequently Asked Questions

Can the IRS penalize a business for a wrong EIN that the vendor provided?

Yes. The payer is responsible for the accuracy of information returns regardless of where the error originated. Documented good-faith outreach (collecting a W-9, running TIN matching, requesting correction when a mismatch is found) is the primary defense available, but it doesn't eliminate the filing obligation to report correctly.

Does a wrong EIN always trigger a CP2100 notice?

Almost always. The IRS pairs the EIN with the first four characters of the name, so a wrong EIN escapes notice only in the rare case where it belongs to another taxpayer whose name starts with the same four characters. Expect the CP2100 12 to 18 months after filing.

How can I tell if the wrong EIN is a typo vs. a structural mismatch?

Run IRS TIN matching. A transposed digit usually returns code 2 (TIN not currently issued) or code 3 (name and TIN do not match IRS records). A wrong entity EIN (parent instead of subsidiary) returns code 3 when the two legal names start differently. TIN matching tells you what the IRS sees, which is the only determination that matters for compliance purposes.

What if the vendor insists their EIN is correct but TIN matching still returns a mismatch?

Ask the vendor to reference their IRS-issued EIN confirmation letter (CP 575). This document shows the exact legal name and EIN as registered with the IRS and is the definitive source for resolving disagreements. If the vendor's CP 575 matches what they submitted and TIN matching still fails, the IRS may need to update their records, which requires the vendor to contact the IRS directly.

Is a corrected 1099 always required when a wrong EIN is discovered after filing?

It depends on when the error is discovered and what was filed. If the 1099 was filed with a wrong EIN that resulted in income being reported under the wrong taxpayer record, a corrected filing is generally appropriate. Consulting with a tax advisor on the specific situation is recommended for errors discovered after filing.


Conclusion

A wrong EIN from a vendor creates a compliance chain that belongs entirely to the payer: from the CP2100 notice to the B-Notice deadline to the backup withholding obligation to the potential 972CG penalty assessment. The vendor may have made the error, but the payer is accountable for what was filed. The correction process is straightforward when the error is caught before filing: request a corrected W-9, revalidate via TIN matching, update the vendor master. The same process becomes significantly more expensive when it happens after a 1099 is filed, a notice is received, and deadlines are already running. IRS TIN matching at onboarding and Q4 bulk validation before filing season are the two controls that prevent most wrong EIN situations from ever becoming compliance events.


Validate Vendor EINs with TIN Comply

TIN Comply validates vendor EINs against IRS records in real time, so wrong EINs are caught at onboarding and in Q4 bulk validation, not discovered on a CP2100 notice after filing.

Real-time IRS TIN Matching at vendor setup. Bulk files (.csv and .xlsx) across your full reportable vendor list 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 abatement support.

  • Real-time IRS TIN Matching: catches wrong EINs before first payment
  • Bulk vendor 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
  • EIN and company lookup returns the legal name on record for the EIN
  • Per-request history with user attribution, timestamps and filtered exports
  • REST API for ERP and AP system integration

Start Free Trial Request a Demo