EIN Discovery vs. TIN Matching: What's the Difference and When to Use Each
When the IRS flags a vendor's TIN, two questions follow: is the TIN really wrong, and if so, what is the correct one? TIN matching answers the first and EIN discovery answers the second; this post explains when to use each.
Updated October 28, 2026.
The Problem They're Each Solving
TIN matching and EIN discovery are related but distinct. Confusing them, or assuming one replaces the other, leaves gaps in your vendor validation workflow.
TIN matching is a verification tool. You give it a name and TIN, and it checks whether that combination matches IRS records. It returns a result code: match, mismatch, or one of several specific error conditions. It tells you whether the data you have is correct. It does not tell you what the correct data is. IRS TIN Matching is the only IRS-run check of a name and TIN pair before you file.
EIN discovery is a lookup tool. You give it a company name or an EIN, and it searches an independent database of business records to find the corresponding information. It's how you find a correct EIN when you don't have it, or verify that a business and its EIN match what you'd expect. The result is the legal name on record for the EIN, or a ranked list of candidate EINs for a name.
Used together: TIN matching tells you there's a problem; EIN discovery helps you fix it.
Key takeaways
- TIN matching verifies a name and TIN pair against IRS records and returns a code from 0 to 8; it never reveals the correct TIN.
- EIN discovery searches an independent business database for the legal name on record for an EIN, or for candidate EINs by company name.
- TIN matching is required for a defensible 1099 filing; EIN discovery is the tool that unblocks a mismatch when the vendor does not respond.
- The workflow is: match, request a corrected W-9, look up, re-match, document.
When to Use TIN Matching
TIN matching is the right tool any time you need to confirm that a vendor's name and tax ID combination is accurate against IRS records. The primary use cases:
Before filing 1099s Run your full vendor list through TIN matching before filing season. Any mismatches surface before you file incorrect returns, avoiding the penalties that come with CP2100 notices and potential 972CG liability.
At vendor onboarding When a new vendor submits a W-9, validate their TIN before they enter your system. Catching a bad TIN at onboarding is far easier than chasing it down after you've been paying them for two years.
After receiving a CP2100 The IRS sends a CP2100 with a list of mismatched TINs from your prior year's 1099 filings. TIN matching confirms which records are genuinely mismatched versus which may have been flagged due to name formatting differences.
Periodically throughout the year Vendor data changes. Running TIN matching mid-year, not just at filing time, catches name changes, entity restructurings, and stale W-9s before they become a filing problem.
What the result codes mean
The IRS returns one code per name and TIN pair. Interactive requests take up to 25 pairs at a time; a bulk file takes up to 100,000 pairs, with results usually back within 24 hours.
| Code | Meaning | What to do next |
|---|---|---|
| 0 | Name and TIN match IRS records | File as is |
| 1 | TIN missing or not nine digits | Fix the data entry and resubmit |
| 2 | TIN not currently issued | Request a corrected W-9; consider EIN discovery |
| 3 | Name and TIN do not match IRS records | Check name formatting, then request a corrected W-9 or run EIN discovery |
| 4 | Invalid request (bad characters or format) | Correct the record and resubmit |
| 5 | Duplicate request | No action; the pair was already submitted |
| 6 | Matched on SSN when the TIN type was unknown | Record the TIN type as SSN |
| 7 | Matched on EIN when the TIN type was unknown | Record the TIN type as EIN |
| 8 | Matched on both SSN and EIN records | Confirm the entity type with the vendor |
Codes 2 and 3 are the ones that start the mismatch workflow described below. Everything else is either a pass or a formatting fix on your side.
When to Use EIN Discovery
EIN discovery is the right tool when you need to find or verify an EIN independently of what a vendor told you. The primary use cases:
After a TIN mismatch with an unresponsive vendor TIN matching returned a mismatch. You've sent a W-9 request. The vendor hasn't responded. Rather than waiting indefinitely, or applying backup withholding, you can cross-reference an independent EIN database to find the correct TIN and get the record fixed.
Verifying a new vendor before onboarding Before a vendor even submits a W-9, you can use EIN discovery to verify that the business is real, the name matches what you'd expect, and the EIN is associated with an active entity.
Cleaning up a vendor master When working through a vendor master cleanup, EIN discovery fills in missing EINs, corrects name/EIN pairs that were entered incorrectly, and flags records where the business name in your system doesn't match what's on file for that EIN.
When a vendor gives you a name-only Some vendors, particularly smaller contractors, don't always know their own EIN off the top of their head. EIN discovery lets you find it by company name so you can populate the W-9 correctly before validation.
Side by Side
| EIN Discovery | TIN Matching | |
|---|---|---|
| What you provide | Company name or EIN | Name + TIN combination |
| What it checks against | Independent business database | IRS records |
| What it tells you | What EIN is associated with a business name, or what name goes with an EIN | Whether a name/TIN pair matches IRS records |
| Primary use | Finding or verifying an EIN | Confirming accuracy before filing |
| Fixes a mismatch? | Yes: helps you find the correct TIN | No: identifies the problem, not the solution |
| Required for 1099 compliance? | No | Yes |
How They Work Together in Practice
The typical mismatch workflow shows how the two tools complement each other:
- You run TIN matching on your vendor list before filing
- A vendor comes back as a mismatch: the name/TIN combination doesn't match IRS records
- You send a W-9 request to the vendor asking for corrected information
- The vendor doesn't respond within your timeline
- You use EIN discovery to cross-reference the business name against an independent database of millions of business records
- You find the correct EIN, update the record, re-run TIN matching to confirm
- The record passes: you file a correct 1099 and document the resolution for your audit trail
Without EIN discovery at step 5, the workflow stalls. You either apply backup withholding, file with a known-bad TIN, or keep waiting on a vendor who may never respond.
A worked example: your vendor master lists "Harbor Point Consulting" with EIN 12-3456789 and TIN matching returns code 3. An EIN lookup on the name returns a ranked list whose top candidate is "Harbor Point Consulting Group LLC" under a different EIN, 98-7654321. You update the legal name, re-run the match on the new pair, get code 0, and keep both results in the record. If the vendor later sends a corrected W-9, it confirms what you already filed.
How TIN Comply Handles Both
TIN Comply provides both tools in a single platform:
- IRS TIN Matching: validate TIN/name combinations against IRS records individually, in bulk, or via API
- EIN Lookup: search millions of business records by company name for ranked candidate EINs, or by EIN for the legal name on record, to resolve mismatches and confirm business identity before onboarding
- Request Corrected W-9: a mismatch result carries a button that sends the vendor a W-9 request and tracks it through SENT, OPENED and COMPLETED
Every result (match, mismatch, or lookup) is logged with a timestamp and the user who ran it, and the history can be filtered and exported for audit documentation.
Start a free trial and run your vendor list through both tools in one platform.
Bottom Line
TIN matching and EIN discovery are not interchangeable: they answer different questions at different points in the vendor validation workflow. TIN matching is your compliance check before filing. EIN discovery is your resolution tool when something comes back wrong. Having both means a mismatch doesn't have to become a stalled workflow, a backup withholding obligation, or a filing deadline missed.
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.