What Is IRS TIN Matching and How Does It Work?

IRS TIN Matching is the only IRS-run check of a name and TIN pair before you file. Format validation tells you a TIN has nine digits; TIN Matching tells you whether the IRS has that name registered to that TIN.

Updated October 28, 2026.

What IRS TIN Matching Does, and What It Doesn't

IRS TIN matching validates a name + TIN combination against IRS taxpayer records. It applies the same name control logic the IRS uses when processing filed returns: deriving a matching identifier from the submitted legal name and comparing it against the record registered for that TIN. The result tells the payer whether the combination will resolve correctly when a 1099 is filed with those values.

What TIN matching confirms, and what it doesn't:
TIN Matching Confirms TIN Matching Does Not Confirm
The TIN exists in IRS records The vendor's payment or tax classification
The submitted name resolves correctly with that TIN The vendor's address or contact information
The combination will pass IRS matching when the 1099 is filed Whether the vendor is exempt from 1099 reporting
The TIN type (EIN/SSN) is consistent with the name's registration Whether the vendor's W-9 is signed

TIN matching is not a substitute for collecting a signed W-9. It's the validation step that confirms the information on the W-9 is correct, applied after the W-9 is received and before the vendor record is created. The two work together: the W-9 is the certified source document; TIN matching is the IRS confirmation that the certification is accurate.


Why TIN Matching Is Different from Format Validation

Format validation checks whether a TIN is structurally valid: nine digits, no invalid characters, correct dash placement. It catches structural errors: a TIN with eight digits, a letter where a number should be, an extra space. What it doesn't catch is a structurally valid TIN that belongs to the wrong entity, resolves to a different legal name, or is the wrong TIN type for the vendor's registration.

A nine-digit EIN that passes format validation can still fail IRS TIN matching if it belongs to a different entity, or if the legal name submitted doesn't match the legal name on record for that EIN. Format validation says the number is structurally possible. TIN matching says whether it actually resolves, which is the only determination that matters for 1099 compliance.

The Three TIN Matching Result Categories

The IRS returns one of nine result codes for each pair. Codes 0 to 3 and 6 to 8 describe the vendor's record and fall into three categories; codes 4 and 5 describe the submission itself.

Code What It Means Category Required Action
0 Name and TIN match IRS records Match Create or clear the vendor record; document the result
1 TIN missing or not nine digits Invalid TIN Fix the format internally and resubmit
2 TIN not currently issued Invalid TIN Request corrected W-9; confirm TIN type (EIN vs. SSN) against entity structure
3 Name and TIN do not match IRS records Mismatch Request corrected W-9 with specific detail; revalidate after correction
4 Invalid request Submission error Correct the formatting of the request and resubmit
5 Duplicate request Submission error No action; the pair was already submitted
6 Matched on SSN when the TIN type was unknown Match Record the TIN type as SSN
7 Matched on EIN when the TIN type was unknown Match Record the TIN type as EIN
8 Matched on both SSN and EIN when the TIN type was unknown Match Confirm which TIN type the vendor uses for federal reporting

A mismatch and an invalid TIN require different correction approaches. A mismatch means the TIN may be correct but the legal name is wrong, or vice versa. An invalid TIN means the number itself doesn't exist in IRS records and the vendor needs to confirm their correct TIN from their IRS registration documentation.


Free Tools
Validate your vendor list before you submit

The TIN Format Validator catches structural errors before submission. The Bulk TIN Results Analyzer decodes every IRS result code with plain-English action steps after results come back. Both free, no account required.

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

When TIN Matching Should Be Run


At Vendor Onboarding: Before the First Payment

This is the highest-leverage point in the compliance process. A mismatch caught at onboarding is a W-9 correction request and a revalidation, resolved before any payment is made, before any 1099 is filed. The same mismatch discovered after filing is a CP2100 notice, a B-Notice deadline, and potential 972CG penalty exposure.

Onboarding is when the mismatch is cheapest to fix. It requires one outreach, one corrected W-9, one revalidation. Nothing has been filed, no deadlines have run, no penalties have been assessed. Every other point in the compliance cycle where the same mismatch surfaces is more expensive.

Q4 Bulk Validation: Before Every Filing Season

Vendor records that passed TIN matching at onboarding can become mismatches if the vendor's IRS registration changes (entity restructuring, legal name change, merger, conversion from one entity type to another) without the payer being notified. Q4 bulk validation identifies these stale records before they appear on a filed 1099.

The Q4 window, October through December, provides enough time to complete the full correction cycle: identify mismatches, initiate outreach, collect corrected W-9s, revalidate, and update vendor records before January filing deadlines.


After Receiving a Corrected W-9

A corrected W-9 is the vendor's new attestation. It is not confirmation that the correction is right. A vendor who provides a corrected W-9 with a second error produces another CP2100 at the next filing cycle. Revalidating every corrected W-9 before updating the vendor master is the control that prevents corrections from creating their own mismatch cycle.


After a CP2100 Notice or B-Notice Response

When a vendor provides corrected taxpayer information in response to a B-Notice, that information must be validated via TIN matching before the vendor record is cleared. The correction resolves the mismatch when TIN matching confirms it, not when the vendor provides the documentation.


After System Migrations or ERP Changes

Vendor data that travels through system migrations, ERP upgrades, or integrations is vulnerable to truncation, formatting changes, and encoding errors that can alter names and TINs. Post-migration bulk TIN matching validates the entire vendor population against IRS records after the migration, catching data quality issues introduced by the technical process before they reach filed returns.


How TIN Matching Works at Different Scales

Method Best For How It Works
Manual / Single-record One-off validation, exception handling Submit one name + TIN at a time; result returned immediately
Bulk file upload Q4 pre-filing cleanup, vendor master audits, post-migration validation Upload a file of name + TIN pairs; batch results returned; mismatches identified for outreach
API integration Real-time onboarding workflows, ERP-embedded validation TIN matching called programmatically at vendor setup; result returned in the workflow before record is created

API integration is the approach that closes the onboarding gap most completely, because it means TIN matching happens automatically at the point of vendor creation, without requiring a separate manual step that AP teams might skip under time pressure. Bulk processing is what makes Q4 validation practical at scale across thousands of vendor records.


How IRS Name Control Logic Works

The IRS doesn't compare full name strings directly the way a human would. It derives a name control, a four-character identifier, from the submitted name and compares it against the registered name control for that TIN. Understanding how name controls are derived explains why certain name differences produce mismatches:

IRS name control derivation, simplified:
  • Business entities: Name control derived from the first four significant characters of the registered legal name: "Brightline Solutions LLC" derives "BRIG"
  • Individuals: Name control derived from the last name: "John Smith" derives "SMIT"
  • Sole proprietors: Name control derived from the individual's legal last name, matched against the TIN type (SSN, not EIN)
  • Articles and special characters: The IRS ignores leading articles ("The", "A", "An") and handles certain punctuation consistently, but apostrophes, hyphens, and ampersands can affect name control derivation
  • DBA names: Name controls are derived from the registered legal name, not any trade name, which is why DBA names in the legal name field consistently fail

The name control is the mechanism that turns a full legal name into a matchable identifier. TIN matching is the only IRS-run check, before you file, of whether the name control derived from a vendor's submitted name matches the one registered for their TIN at the IRS.


Common Mismatch Scenarios and Their Causes

Submitted IRS Record Why It Mismatches
BrightLine Consulting BrightLine Consulting LLC Missing suffix: name control may differ
Mike's Plumbing Michael Carter Services LLC DBA filed instead of legal name
John A. Smith John Smith Middle initial handling
ABC Holdings ABC Holdings, Inc. Missing suffix
Apex Logistics (EIN: 12-3456789) Apex Logistics (EIN: 12-3456788) Transposed digit: invalid TIN
John Smith (EIN provided) John Smith (IRS expects SSN) Wrong TIN type: sole proprietor

Every scenario in this table is detectable via IRS TIN matching at onboarding. None of them require waiting until a CP2100 notice arrives.


Best Practices

What organizations with the strongest TIN matching programs do consistently:
  • Run TIN matching at vendor onboarding: before the first payment, triggered at W-9 submission
  • Integrate TIN matching into the ERP via API, which makes it automatic, not optional
  • Use legal name from W-9 Line 1 as the submitted name for matching, never DBA
  • Run Q4 bulk TIN matching starting in October, which gives time for correction before filing
  • Revalidate every corrected W-9 before updating the vendor master
  • Store every validation result per vendor: match, mismatch, invalid, correction, revalidation
  • Combine TIN matching with OFAC screening in the onboarding workflow, validating both compliance dimensions at setup
  • Run post-migration bulk validation after any ERP change affecting vendor data

TIN Matching Implementation Checklist

  • TIN matching integrated into onboarding workflow: runs at W-9 submission before vendor activation
  • Legal name from W-9 Line 1 used as matching input: DBA not submitted as legal name
  • TIN type confirmed: EIN vs. SSN consistent with entity structure before submitting
  • Mismatch results trigger automated W-9 outreach with specific correction detail
  • Q4 bulk TIN matching run annually: October start, completed before filing deadline
  • All corrected W-9s revalidated before vendor master is updated
  • Post-migration validation run after any ERP change affecting vendor records
  • All validation results retained per vendor: match, mismatch, correction, revalidation
  • Validation history accessible for CP2100 response and 972CG abatement documentation

Frequently Asked Questions

Is IRS TIN matching legally required?

TIN matching is not a statutory requirement in the way that filing a 1099 is. But the IRS holds payers accountable for the accuracy of information returns, and documented TIN matching is the primary evidence that a payer exercised due diligence before filing. In practice, running TIN matching and not running it produce very different outcomes when CP2100 notices arrive and abatement requests need to be supported.

What's the difference between IRS TIN matching and the IRS's own e-Services TIN matching system?

The IRS offers TIN matching to authorized payers through its e-Services portal: up to 25 pairs per interactive request, and bulk files of up to 100,000 pairs with results usually within 24 hours. TIN Comply runs the matching for the payer, so nobody on your team needs an e-Services account, and it adds the workflow around the result: mismatch categorization, a Request Corrected W-9 button on a mismatch, per-request history with user attribution, bulk .csv and .xlsx files, and a REST API.

How long does TIN matching take?

For real-time API-based matching, results are typically returned in seconds. For bulk file submissions, results are usually available within 24 hours.

Can TIN matching be run on ITIN vendors?

Yes. IRS TIN matching validates EIN, SSN, and ITIN combinations. ITINs follow the same name + TIN combination matching logic as other TIN types, with the additional consideration that ITINs expire if not used on a U.S. tax return for three consecutive years, so ITIN validation should also confirm the ITIN is current.

Does a TIN match result guarantee no CP2100 will be issued?

A confirmed TIN match at onboarding significantly reduces CP2100 risk. But a vendor whose IRS record changes after validation (name change, entity restructuring, merger) may still produce a mismatch at the next filing cycle if Q4 bulk revalidation isn't run to catch the change. TIN matching at a point in time is accurate at that point in time; annual revalidation keeps it current.


Conclusion

IRS TIN matching is the verification step that converts a vendor's self-certified W-9 into a confirmed IRS-validated record. It catches the mismatches (wrong TINs, wrong legal names, wrong TIN types) that format validation misses entirely, and it catches them at the point where correction is cheapest: before any payment is made and before any 1099 is filed. Run at onboarding via API integration, run annually in Q4 via bulk processing, and run after every corrected W-9 is received, TIN matching is what stands between vendor data quality problems and the CP2100 notices, B-Notice deadlines, backup withholding obligations, and 972CG penalties they produce when they reach filed returns unchecked.


The Free Tools That Cover the Full TIN Matching Workflow

Free Tools

Two tools for the TIN matching workflow

Use the Format Validator before submission to catch structural errors. Use the Results Analyzer after IRS results come back to decode every code and get a prioritized action list. Both free, both run entirely in your browser.

  • TIN Format Validator: catch Code 1 and Code 4 errors pre-submission
  • All result codes 0 to 8 decoded with plain-English explanations
  • Bulk TIN File Validator: pre-flight your submission file
  • Payee-level action steps and prioritized remediation export
  • No account required: everything runs in your browser