The Most Common W-9 Errors That Cause IRS Mismatches - and How to Fix Each One

A W-9 that looks complete is not the same as a W-9 that's correct. A vendor can fill out every field, sign the form, and return it promptly - and you can still end up with a TIN mismatch, a B-Notice, and a backup withholding obligation. The problems are usually specific and predictable: wrong name format, wrong entity classification, a TIN that belongs to the owner rather than the business, or a W-9 that was accurate three years ago but isn't anymore. Knowing which mistakes to look for - and how to catch them before they hit the IRS - is most of the job.

Why W-9 Errors Matter Beyond the Form Itself

The W-9 is not just paperwork - it's the source of the name and TIN you'll put on a 1099. Whatever the vendor writes on that form is what you file with the IRS. If the W-9 has the wrong name, your 1099 has the wrong name. If the TIN doesn't match what the IRS has on file for that name, you get a Code 3 on TIN matching, and eventually a CP2100 and a B-Notice.

The time to catch W-9 errors is when you receive the form, not after filing. Every W-9 that comes in should be validated through IRS TIN matching before being entered into your vendor master. That one step eliminates the vast majority of problems before they become mismatch issues at filing time.

Here are the specific errors that come up most often and what to do about each.

Headache 1: DBA Name Instead of Legal Name

What happens: A sole proprietor or single-member LLC operates under a trade name and fills in that name on Line 1 of the W-9 instead of their legal name. "Sunrise Landscaping" instead of "John Martinez." Their TIN is their SSN, which is registered to their legal name - not their DBA.

Why it causes a mismatch: The IRS matches against the legal name on the SSN record. "Sunrise Landscaping" won't match "John Martinez" regardless of whether the TIN is correct. You'll get a Code 3 on TIN matching.

How to fix it:

Line 1 of the W-9 is for legal name. For sole proprietors and single-member LLCs, that's the owner's full legal name as it appears on their Social Security card or prior-year tax return.
Line 2 is for business name / DBA - that's where "Sunrise Landscaping" goes.
If a vendor has already submitted a W-9 with a DBA on Line 1, send it back with a note explaining the distinction and requesting a corrected form.
When TIN matching returns Code 3 for a sole proprietor, try the owner's name before requesting a new W-9 - this is frequently the cause.

Headache 2: Wrong Entity Classification

What happens: The vendor checks the wrong box in Part I of the W-9. The most common version: a single-member LLC checks "LLC" and writes "S" or "C" as the tax classification, when they should check "Individual/sole proprietor or single-member LLC" because the LLC is disregarded for tax purposes and their TIN is their SSN.

Other common versions:

A two-member LLC (taxed as a partnership) checks "individual" instead of "LLC" with classification "P"
A C-corporation checks "S corporation"
A vendor selects "exempt payee" when they aren't actually exempt

Why it causes a problem: The wrong entity classification affects which 1099 form applies, whether the corporate exemption applies (exempting them from 1099 reporting entirely), and which TIN to use. A disregarded single-member LLC should provide the owner's SSN - if they provide an EIN instead, TIN matching may fail because the EIN is registered under the LLC name, not the owner's name.

How to fix it:

The W-9 instructions distinguish between entity types clearly but the form itself is confusing, especially for LLCs. Here's a quick reference to include when sending W-9 requests:

Entity Type	Line 1	TIN to Use	1099 Required?
Individual / sole proprietor	Owner's legal name	SSN	Yes (if threshold met)
Single-member LLC (disregarded)	Owner's legal name	Owner's SSN (or EIN if applicable)	Yes (if threshold met)
Multi-member LLC (partnership)	LLC legal name	LLC EIN	Yes (if threshold met)
LLC taxed as S or C corp	LLC legal name	LLC EIN	Generally no (corporate exemption)
S corporation	Company legal name	Company EIN	Generally no (corporate exemption)
C corporation	Company legal name	Company EIN	Generally no (corporate exemption, except legal services)
Partnership	Partnership legal name	Partnership EIN	Yes (if threshold met)

When a vendor's entity classification is unclear, run TIN matching with TIN type 3 (unknown) - the result code (6 for SSN match, 7 for EIN match) tells you which database the TIN is registered in and helps confirm entity type.

Headache 3: EIN Belongs to a Different Legal Entity

What happens: A vendor provides an EIN that is technically valid but belongs to a predecessor entity, a parent company, or an old entity that was dissolved. This comes up frequently after acquisitions, mergers, restructurings, or when a vendor reorganized their business structure without getting a new EIN assignment.

Why it causes a mismatch: TIN matching will return Code 3 - the EIN exists in IRS records but is registered to a different legal name than what the vendor wrote on Line 1.

How to fix it:

Ask the vendor to confirm their EIN from their CP-575 (the original IRS EIN assignment letter) or a recent tax return.
Use EIN lookup by company name to cross-reference what EIN the IRS has on file for that business name. This often surfaces the correct EIN without requiring further vendor cooperation.
If the vendor has recently gone through a merger or acquisition, they may need a new EIN or may be operating under the acquiring company's EIN. Clarify before updating records.

Headache 4: Blank or Incomplete TIN Field

What happens: Vendor returns the W-9 with the TIN field blank, or with only part of the number filled in. Sometimes deliberate (vendor doesn't want to provide their SSN), sometimes a simple oversight.

Why it matters: You cannot file a 1099 without a TIN. If you pay a vendor without a TIN on file and they cross the reporting threshold, you're required to begin backup withholding at 24% immediately - you can't wait until year-end.

What to do:

Return the W-9 immediately with a clear request to complete the TIN field. Explain that without a TIN, payments are subject to 24% backup withholding.
If the vendor is a business, offer to look up their EIN through public records and confirm it with them rather than waiting for them to locate it.
If the vendor is unresponsive, begin backup withholding on all payments and document your solicitation attempts. Two documented solicitation attempts are required for reasonable cause purposes.
Never start payments to a vendor without a TIN on file unless you're already withholding.

Headache 5: Stale W-9s That Are No Longer Accurate

What happens: You collected a W-9 from a vendor three years ago. Since then, they've changed their legal name, been acquired, changed their EIN, or converted from a sole proprietorship to an LLC. The W-9 in your file still shows the old information. You've been filing 1099s with the old name and TIN, generating mismatches on every return.

Why it's underdetected: Most AP teams don't proactively re-request W-9s from existing vendors. The stale W-9 stays in the system and produces quiet mismatch errors year after year until a CP2100 surfaces them.

Events that should trigger a W-9 re-request:

Vendor name change
Vendor notifies you of a merger, acquisition, or restructuring
Vendor requests a bank account change (also a sanctions re-screening trigger)
TIN matching on the existing record returns Code 3 after previously returning Code 0
Vendor's address changes to a different state (sometimes indicates a business restructuring)
More than three years since the last W-9 was collected for an active vendor

How to fix it: Build W-9 re-request triggers into your vendor management process. The specific events above are the ones that most reliably indicate the underlying information has changed. Running annual TIN matching on your full vendor population also surfaces stale records that need updating - a vendor who used to match but now returns Code 3 is a strong signal that something changed.

Headache 6: The Vendor Who Won't Respond

What happens: You've sent a W-9 request. Then a follow-up. The vendor isn't responding. This is especially common with very large vendors who have bureaucratic AP processes, very small vendors who operate informally, and international vendors who may not understand what a W-9 is.

What your obligations are: Under IRS rules, you are required to make two solicitations for a missing TIN - the initial request and one annual follow-up. If you've made both solicitations and the vendor still hasn't provided a TIN, you are required to begin backup withholding at 24%. You are not required to continue soliciting indefinitely.

What to do:

First solicitation: send with the initial onboarding packet or at the time of first payment request. Include a blank W-9 and clear instructions.
Second solicitation: send by December 31 of the same year the first solicitation was made (or January 31 of the following year for vendors added in the fourth quarter).
Document both solicitations with proof of sending (email delivery confirmation, certified mail receipt).
If no response after the second solicitation, begin backup withholding and document the non-response.
For large vendors where you have a relationship, a phone call explaining the backup withholding consequence is often more effective than additional W-9 request emails.

Headache 7: Second B-Notice - When a W-9 Isn't Enough

What happens: You've received a CP2100 that includes a vendor for the second time within three calendar years. You send them a W-9 request. They send back a completed W-9. Problem solved - right?

Not for Second B-Notice situations. When the same vendor appears on a CP2100 for the second time within three years, a self-certified W-9 is no longer sufficient. The vendor must provide IRS-certified documentation confirming their TIN:

For businesses: a copy of their CP-575 (IRS EIN assignment letter) or an IRS letter confirming their EIN
For individuals: a copy of their Social Security card, or an SSA letter confirming their SSN

This requirement catches many AP teams by surprise. If you accept a self-certified W-9 for a Second B-Notice payee and continue paying them without collecting certified documentation, you remain in violation of the B-Notice requirements.

How to manage it: Track which vendors are on First vs. Second B-Notice status in your vendor master or B-Notice log. When a CP2100 arrives, cross-reference the mismatch list against your B-Notice history before deciding which notice to send.

Building a W-9 Process That Prevents These Problems

Most W-9 headaches are preventable with a process that catches errors at collection rather than at filing. The key steps:

Collect W-9 before first payment - not at year-end, not after crossing the threshold. Before the first check goes out.
Validate through TIN matching immediately - run every new W-9 through IRS TIN matching before entering the data into your vendor master. This catches name and TIN errors while the vendor is still engaged and willing to correct them.
Use digital W-9 collection - an online W-9 portal with field validation catches obvious errors (blank TIN, wrong number of digits) at submission rather than after the fact.
Re-request on trigger events - name changes, bank account changes, acquisitions, and annual TIN matching failures all signal that the W-9 on file may no longer be accurate.
Track B-Notice status - know which vendors are on First vs. Second B-Notice status so you send the right notice and require the right documentation.

How TIN Comply Handles W-9 Collection

TIN Comply's W-9 Management sends digital W-9 requests to vendors, validates submissions in real time against IRS records, and tracks response status without manual follow-up management. Combined with IRS TIN Matching and EIN Lookup, it closes the loop between W-9 collection and TIN validation in a single workflow.

For vendors who won't respond despite multiple requests, Full-Service W-9 Outreach handles the entire campaign: sending requests, following up, tracking responses, and documenting the solicitation trail you need for reasonable cause purposes.

Start a free trial or request a demo.

Quick Reference: W-9 Error Diagnosis

TIN Matching Result	Most Likely W-9 Error	First Step
Code 1 (TIN format error)	TIN entered with hyphens or as 8 digits	Check and reformat before re-validating
Code 2 (TIN not issued)	Wrong TIN, transposed digits, or fabricated number	Request new W-9; try EIN lookup
Code 3 (name/TIN mismatch)	DBA instead of legal name, wrong entity type, old EIN	Try name variations first; request corrected W-9 if unresolved
Code 3 (was previously Code 0)	Vendor name change, acquisition, or restructuring	Re-request W-9; check for EIN change
Blank TIN field	Vendor didn't provide TIN	Solicit immediately; begin backup withholding if unresponsive

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.