How Does IRS TIN Matching Work? The Process, Results, and Limitations Explained

IRS TIN Matching is the only IRS-run check of a name and TIN pair before you file, and most organizations run it only after a CP2100 arrives. This page covers how a request works, what each code means, and what the service cannot tell you.

Updated October 28, 2026.

How IRS TIN Matching Works

IRS TIN matching is the process of validating a vendor's legal name + Taxpayer Identification Number (TIN) combination against IRS records before that data is used for tax reporting. When the combination matches, the vendor record is confirmed safe for 1099 filing. When it doesn't, you have a mismatch, and fixing it now costs a fraction of what it costs after a CP2100 notice arrives.

The core question TIN matching answers:
Does this vendor's legal name and TIN combination match what the IRS has on file, before I file a 1099 with it?

Why TIN Matching Exists

The IRS requires businesses to file accurate information returns. When a 1099 is submitted with an incorrect vendor name or TIN, the IRS cannot match the payment to the correct taxpayer record. That creates a cascade: CP2100 mismatch notice, B-Notice outreach requirement, potential backup withholding, and 972CG penalty exposure, all traceable back to a vendor record that could have been validated at onboarding.

TIN matching is the proactive checkpoint that stops the cascade before it starts.


Step-by-Step: How TIN Matching Works

Step 1: Collect Vendor Taxpayer Information

The business collects the vendor's legal name and TIN from a signed W-9 form. The critical fields are:

  • Line 1: Legal name (this is what the IRS matches against, not a DBA)
  • Line 2: Business/DBA name (operational use only, never used for IRS reporting)
  • Part I: TIN (EIN or SSN)
Common mistake: Storing the DBA name (Line 2) in the legal name field. The IRS will not match against a DBA, only the legal entity name on Line 1.

Step 2: Submit the Name + TIN for Validation

The legal name and TIN are submitted to a TIN matching service. This can be done three ways depending on your volume and workflow:

Method Best For How It Works
Interactive Small volumes, one-off checks Submit up to 25 pairs per request; results come back immediately
Bulk File Upload Vendor master cleanup, Q4 pre-filing validation Upload a file of up to 100,000 pairs; results usually within 24 hours
API Integration Real-time onboarding automation Validation runs automatically as vendors are added to your system

Step 3: The IRS Checks Their Database

The IRS compares the submitted name and TIN against their taxpayer records. For business entities (EIN), they match the legal entity name registered under that EIN. For individuals (SSN), they match the legal name associated with that Social Security number.

What the IRS checks, and what it doesn't:

The IRS confirms whether the name + TIN combination resolves to a matching taxpayer record. It does not confirm business ownership, active status, or payment history, only whether the name and TIN align.


Step 4: Receive the Result

Every submitted pair returns one of nine result codes:

Code Meaning Action Required
0 Name and TIN match IRS records Safe to use for 1099 filing
1 TIN missing or not nine digits Correct the TIN format; resubmit
2 TIN not currently issued Request a corrected W-9
3 Name and TIN do not match IRS records Request a corrected W-9; revalidate before use
4 Invalid request (bad characters or layout) Fix the request; resubmit
5 Duplicate request Drop the duplicate; the first result stands
6 Matched on SSN when the TIN type was unknown Record the TIN as an SSN
7 Matched on EIN when the TIN type was unknown Record the TIN as an EIN
8 Matched on both SSN and EIN Confirm the TIN type with the payee

Free Tools
Got results back from the IRS? Decode them instantly.

The Bulk TIN Results Analyzer decodes every result code 0 to 8 with plain-English explanations and payee-level action steps. The TIN Format Validator catches structural errors before you submit. Both free, no account required.

All codes 0 to 8 decoded Format errors caught pre-submission No account required

Step 5: Resolve Mismatches Before Filing or Payment

If a mismatch is returned, the standard resolution workflow is:

  1. Check for internal data entry errors first (transposed digits, missing suffix, DBA in legal name field)
  2. If no internal fix, request a corrected signed W-9 from the vendor
  3. Confirm the vendor is using their legal IRS name, not a trade name
  4. Confirm the correct TIN type (EIN vs SSN, especially for sole proprietors)
  5. Resubmit the corrected name + TIN for validation
  6. Only activate the vendor after a confirmed match result

Fixing a mismatch at onboarding takes minutes. Fixing it after a CP2100 notice takes weeks.


Step 6: Store Results for Audit

Validation results should be stored alongside the W-9 and vendor record to support:

  • Internal compliance reviews
  • CP2100 notice response documentation
  • Year-end reporting and audit trails
  • Penalty abatement requests (reasonable cause)
A timestamped validation log is one of the strongest forms of compliance documentation available to businesses that file high volumes of 1099s.

What Causes TIN Matching Failures?

Most mismatches are data quality issues, not fraud. The most common causes:
Cause Why It Fails
DBA name used instead of legal name IRS matches legal entity name, not trade name
Business name abbreviated or reordered The IRS compares a four-character name control (the first four significant characters, leading "The" dropped); "ABC" for "American Business Co" fails
Single transposed or incorrect digit One wrong digit produces no match
Wrong TIN type (EIN vs SSN) Common for sole proprietors and single-member LLCs
Copy/paste errors from ERP systems Truncated names, extra spaces, character substitutions
Outdated vendor record Name or entity changed since the original W-9 was collected

Real-World TIN Matching Examples

Example 1: Valid EIN, Wrong Entity

Submitted: National Distribution, Inc. + EIN 11-2233445 IRS record for that EIN: ND Holdings LLC (the parent company that holds the EIN) Result: Code 3: name control NATI does not match NDHO Fix: collect a W-9 from the entity that holds the EIN, or the subsidiary's own EIN, and revalidate


Example 2: Surname Changed (SSN)

Submitted: Sarah Johnson-Lee + SSN IRS record: Sarah Lee (name updated with the SSA after marriage) Result: Code 3: name control JOHN does not match LEE (a hyphenated surname keeps the hyphen, so Johnson-Lee gives JOHN) Fix: ask for the name exactly as it appears on the Social Security card and revalidate


Submitted: FastFix Plumbing + EIN IRS legal name for that EIN: Robert Taylor Services LLC Result: mismatch: completely different name registered under that EIN Fix: request corrected W-9 with the vendor's actual legal entity name


Example 4: Wrong TIN Type

Submitted: Jane Doe Consulting + EIN IRS expects: Jane Doe + SSN (sole proprietor filing under personal name) Result: mismatch: wrong TIN type for the legal name provided Fix: confirm tax classification; collect corrected W-9 specifying SSN


What Happens Without TIN Matching?

Skipping TIN matching creates a predictable chain of consequences:
Stage What Happens
Filing season Incorrect vendor records submitted on 1099s
Fall after filing IRS issues CP2100 / CP2100A mismatch notices
Within 15 business days B-Notices must be sent to affected vendors
30 business days after B-Notice Vendor must respond with corrected information
Vendor non-response Backup withholding (24%) may apply
Continued non-compliance IRS Notice 972CG penalties assessed per form

TIN Matching at Scale: Choosing the Right Method

Method Volume Speed Best Use Case
Interactive Up to 25 pairs per request Immediate New vendor spot checks
Bulk File Up to 100,000 pairs per file Usually within 24 hours Q4 vendor master cleanup
API Ongoing, as vendors are added Real time Automated onboarding workflows

For most organizations, the most effective strategy is API or bulk validation at onboarding combined with an annual Q4 bulk revalidation of the entire vendor list before filing season.


Best Practices

Organizations with low mismatch rates share these habits:
  • Validate at onboarding, not at year-end
  • Require a signed W-9 before the vendor is activated for payment
  • Store the W-9 legal name (Line 1), not the DBA
  • Revalidate the full vendor list in Q4 before each filing season
  • Revalidate after any W-9 correction: don't assume the fix is right
  • Store validation results with timestamps for audit documentation
  • Automate validation via API inside ERP onboarding workflows

TIN Matching Checklist

  • W-9 collected before first payment is issued
  • Legal name taken from W-9 Line 1, not DBA, not informal name
  • TIN type confirmed (EIN vs SSN vs ITIN)
  • Name + TIN submitted for IRS TIN matching at onboarding
  • Mismatch type documented if validation fails
  • Corrected W-9 requested; vendor revalidated before activation
  • Validation result stored with timestamp in audit log
  • Bulk revalidation run across all vendors in Q4
  • Corrected records revalidated after any W-9 update

Frequently Asked Questions

Is TIN matching legally required?

TIN matching is not always explicitly mandated, but it is considered a best practice and is the most effective control for reducing CP2100 notices and 972CG penalty exposure.

Does TIN matching replace W-9 collection?

No. The W-9 is the required certification document. TIN matching validates what the vendor provided on it. Both are needed.

Can I validate thousands of vendors at once?

Yes. Bulk file processing is commonly used for vendor master cleanup and Q4 pre-filing validation.

Can TIN matching integrate directly into my ERP?

Yes. API-based TIN matching integrates into SAP, Oracle, Workday, NetSuite, Coupa, and similar platforms to validate records automatically at the point of onboarding.

What if the vendor says their information is correct but it still fails?

Recheck whether a DBA is being used, whether a suffix is missing, or whether the wrong TIN type was provided. If the vendor insists their information is correct, ask them to confirm the exact name and TIN on file with the IRS: often the IRS record differs from what the vendor expects.


Conclusion

IRS TIN matching validates the legal name + TIN combination against IRS records and returns a clear match or mismatch result. When built into vendor onboarding and run in bulk before each filing season, it prevents the majority of CP2100 notices, B-Notices, backup withholding exposure, and 972CG penalties before they occur. The W-9 collects the data. TIN matching confirms it's actually correct.


Get Started with TIN Comply

Free Tools

Start Catching Mismatches Before They Reach a 1099

Five free tools cover every stage of the TIN matching workflow from format checking before submission to decoding results after, to triaging CP2100 and 972CG notices if mismatches reach a filed return. No account required on any of them.

  • TIN Format Validator: catch errors before submission
  • CP2100 B-Notice Triage: classify payees and get deadlines
  • Bulk TIN File Validator: pre-flight your submission file
  • 972CG Penalty Response: deadline, abatement letter, W-9 packets
  • Bulk TIN Results Analyzer: decode every result code 0 to 8
  • No account required: everything runs in your browser