IRS TIN Matching Result Codes: What Each Code Means

A complete reference for every IRS TIN matching result code, with plain-language explanations, real-world scenarios, and step-by-step remediation actions.
At a Glance
The IRS returns a single-digit result code (0–8) for every name/TIN pair you submit through the TIN Matching Program. Code 0 means the combination matches IRS records. Codes 1–8 indicate various types of mismatches or issues that require action. This guide explains every code in detail and tells you exactly what to do next.

Understanding IRS TIN Matching Result Codes

When you submit a name and Taxpayer Identification Number (TIN) combination through the IRS TIN Matching Program or a service like TINCorrect, the IRS returns a single-digit code for each record. This code tells you whether the name/TIN pair matches what the IRS has on file, and if not, provides a general indication of what went wrong.

Understanding these codes is critical for 1099 compliance. Each code requires a different response, and acting on mismatches quickly can prevent IRS penalties, CP2100 notices, and mandatory backup withholding.

IRS TIN Matching Result Codes at a Glance 0 Match confirmed Name/TIN matches IRS records ! 1 Missing / invalid TIN TIN blank or not 9 digits ! 2 TIN not issued Number never assigned by IRS 3 Name/TIN mismatch TIN valid, name differs 4 Invalid request Formatting error, not data 5 Duplicate request Already submitted in batch i 6 EIN pending Applied for, not yet issued i 7 EIN now issued EIN assigned, update records i 8 Partial match TIN valid, name mismatch

Complete Result Code Reference Table

Code IRS Description What It Means Action Required
0 Name/TIN combination matches The payee name and TIN you submitted match IRS records exactly. None. File your 1099 with confidence.
1 TIN is missing or not 9 digits The TIN field was blank, contained fewer or more than 9 digits, or included non-numeric characters. Collect a valid TIN from the payee via W-9.
2 TIN not currently issued The 9-digit number you submitted has never been assigned by the IRS or SSA. It is not a valid TIN. The payee may have provided a fabricated or transposed number. Solicit a corrected W-9.
3 Name/TIN combination does not match The TIN is valid and currently issued, but it belongs to a different name than the one you submitted. Solicit a corrected W-9. Verify you are using the legal name, not a DBA.
4 Invalid TIN matching request The request itself was malformed. This is a formatting error, not a data error. Check your submission format and resubmit. Does not count against the payee.
5 Duplicate TIN matching request This exact name/TIN combination was already submitted in the same session or batch. No further action needed. Use the result from the first submission.
6 TIN matched; EIN applied for but not yet issued The SSN or ITIN matches, but the payee has applied for a separate EIN that has not yet been assigned. Follow up with the payee in 2-4 weeks to obtain the issued EIN.
7 TIN matched; EIN applied for and issued An EIN has been assigned to this payee since the matching request. The record may need updating. Request the new EIN from the payee and update your records.
8 TIN matched; name/TIN combination does not match The TIN is valid, but the name paired with it in IRS records differs from what you submitted. This is similar to Code 3 but may arise in specific EIN scenarios. Solicit a corrected W-9 with the exact legal name on file with the IRS.

Result Code 0: Match Confirmed

Code 0 is the result you want to see. It means the name and TIN you submitted match what the IRS has in its records. No further action is required for this vendor.

When you receive Code 0, document the match date in your records. This creates an audit trail showing that you performed due diligence before filing. If the IRS later questions the return, you can point to the confirmed match as evidence of reasonable cause.

Keep in mind that a Code 0 match is a point-in-time confirmation. If the payee later changes their legal name or obtains a new TIN, a previously confirmed match can become stale. This is why annual re-verification as part of your 1099 compliance checklist is important.

Result Code 1: Missing or Invalid TIN Format

Code 1 indicates a data quality problem in your submission, not necessarily a problem with the payee's actual TIN. Common causes include:

  • The TIN field was left blank when exporting from your system
  • The TIN contains dashes, spaces, or letters (e.g., "12-3456789" instead of "123456789")
  • Excel stripped a leading zero, turning a 9-digit number into 8 digits
  • The field contains a placeholder like "APPLIED FOR" or "000000000"

What to do: First, check your data. If the TIN is present in your system but was malformatted during export, fix the formatting and resubmit. If you truly do not have a valid TIN on file, send a W-9 request to the payee immediately. Until you have a valid TIN, you may need to begin backup withholding on payments.

Result Code 2: TIN Not Currently Issued

Code 2 is more concerning than Code 1. It means the 9-digit number you submitted has never been assigned by the IRS (for EINs and ITINs) or the SSA (for SSNs). The number simply does not exist in government records.

Common scenarios that produce Code 2:

  • Transposed digits (e.g., "12-3456798" instead of "12-3456789")
  • The payee provided a fabricated number
  • A data entry error introduced an incorrect TIN
  • The payee confused their SSN with their EIN or ITIN

What to do: Contact the payee and request a corrected W-9. Emphasize that the TIN they provided does not appear in IRS records. If the payee cannot provide a valid TIN, you must begin backup withholding at 24% on future payments and should not file a 1099 with the invalid number.

Result Code 3: Name/TIN Mismatch

Code 3 is the most common mismatch result. The TIN exists and is currently issued, but the name you submitted does not match the name the IRS has on file for that TIN. This is the same type of mismatch that triggers CP2100 notices after filing.

Code 3 frequently occurs because of:

  • DBA vs. legal name: You submitted "Joe's Plumbing" but the EIN is registered to "Joseph Smith" or "Smith Plumbing LLC"
  • Name changes: A person changed their legal name (e.g., after marriage) but the W-9 on file still has the old name
  • Entity restructuring: A business changed its legal structure (sole proprietorship to LLC) and got a new name on file with the IRS
  • Spelling variations: "Mcdonalds" vs. "McDonald's" or "Int'l" vs. "International"
  • Wrong line on the W-9: The payee filled in Line 2 (business name) but left Line 1 (legal name) blank, and your system captured the wrong field

What to do: Solicit a new W-9 from the payee. Ask them to provide their name exactly as it appears on their tax return or the documentation they received when their TIN was issued. Re-verify after updating your records. If the mismatch persists after multiple attempts, consult IRS Publication 1281 for backup withholding guidance.

Handling Code 3: Name/TIN Mismatch Code 3 Received DBA vs. legal name issue? Yes Update to legal name from W-9 Line 1 No Solicit new W-9 from the payee Re-verify TIN Still Code 3? Yes Consider backup withholding (24%) No Matched! Update records Code 3 Remediation Flowchart

Result Code 4: Invalid Request

Code 4 means your TIN matching request itself was malformed. This is not a problem with the payee's data but with how the request was submitted. In the IRS bulk matching context, this typically means a record in your file did not conform to the required fixed-width format.

What to do: Review the specific record that returned Code 4. Check for formatting issues such as incorrect field lengths, non-printable characters, or encoding problems. Fix the formatting and resubmit. If you are using TINCorrect, Code 4 results are rare because the platform handles format translation automatically.

Result Code 5: Duplicate Request

Code 5 indicates that you submitted the same name/TIN combination more than once in the same batch. The IRS only processes the first occurrence and marks subsequent duplicates with Code 5.

What to do: Use the result from the first submission of this name/TIN pair. To avoid Code 5 in the future, deduplicate your file before submitting. TINCorrect handles deduplication automatically during bulk processing, so you will not see Code 5 when using the platform.

Result Codes 6 and 7: EIN Application Status

Codes 6 and 7 relate to sole proprietors who have applied for an EIN in addition to their SSN. These codes are less common but important to understand:

  • Code 6: The payee's SSN or ITIN matched, and the IRS shows that an EIN application is pending but has not yet been issued. The payee is in a transitional state.
  • Code 7: The payee's SSN or ITIN matched, and the IRS has since issued an EIN. Your records may need updating to reflect the new EIN.

What to do: For Code 6, follow up with the payee in 2-4 weeks to check if their EIN has been issued. For Code 7, request the new EIN and update your records. In both cases, you can file your 1099 using the SSN/ITIN that matched, but transitioning to the payee's preferred TIN is good practice. See our guide on EIN lookup vs. TIN matching for more context on EIN-specific scenarios.

Result Code 8: Partial Match

Code 8 is similar to Code 3 but carries a slightly different nuance. It indicates that the TIN is valid and matched to a record, but the name associated with the TIN in IRS records does not match the name you submitted. Some practitioners consider Code 8 to be a "soft" mismatch compared to Code 3, though the practical response is the same.

What to do: Treat Code 8 the same way you would treat Code 3. Solicit a corrected W-9, update your records with the legal name, and re-verify. If this is a business EIN, confirm you are using the entity name as registered with the IRS, not a trade name.

Submit Your TIN Data

Upload names and TIN/EIN combinations via spreadsheet, single entry, or API. We support up to 100,000 records per batch.

Verify Against the IRS

TINCorrect validates each name/TIN pair directly against the IRS TIN Matching Program. Real-time results in seconds.

Get Your Results

Download match results with detailed IRS codes. Export to CSV, PDF, or Excel for your records and audit trail.

How TINCorrect Enhances Result Code Handling

The raw IRS result codes are terse. "Code 3: Name/TIN combination does not match" leaves a lot of interpretation to the user. TINCorrect adds value on top of the IRS codes in several ways:

  • Plain-language explanations: Each result includes a human-readable description of what the code means and why it might have occurred.
  • Suggested next steps: TINCorrect recommends specific actions based on the code, such as "Solicit a new W-9" or "Check for DBA vs. legal name."
  • Batch-level analytics: See how many records matched (Code 0) vs. mismatched across your entire bulk file, helping you gauge the health of your vendor database.
  • Historical tracking: TINCorrect stores match results over time, so you can see whether a vendor's status has changed since your last verification.
  • Export-ready reports: Download results with code explanations in CSV, Excel, or PDF format for your 1099 compliance records.

Common Scenarios and What Codes to Expect

Scenario: New Vendor Onboarding

You collect a W-9 from a new vendor and immediately run a TIN match. Expected outcomes:

  • Code 0: The vendor provided correct information. Proceed with payments.
  • Code 1: The TIN field on the W-9 was illegible or incomplete. Request a clean copy.
  • Code 3: The vendor may have used a trade name instead of their legal name on the W-9. Ask them to resubmit with the name exactly as it appears on their tax return.

Scenario: Year-End Bulk Verification

You export all active vendors and run a bulk TIN match before filing 1099s. Common results:

  • Mostly Code 0: Your vendor database is in good shape. Focus remediation on the exceptions.
  • Several Code 3s: Some vendors have changed names or were entered with DBAs. Run a vendor master file cleanup.
  • A few Code 2s: These need immediate attention. You cannot file a 1099 with a non-existent TIN.

Scenario: Post-CP2100 Re-verification

You received CP2100 notices for several vendors and need to determine if the corrected information resolves the issue. Expected results:

  • Code 0: The corrected W-9 resolved the mismatch. Update your records and document the resolution.
  • Code 3 again: The vendor provided incorrect information again. This may trigger a second B-Notice and require you to begin backup withholding.

Reducing Mismatch Rates

Consistently high mismatch rates indicate systemic data quality issues. Here are strategies to reduce the number of non-zero result codes in your TIN matching batches:

  • Verify at onboarding: Match TINs during vendor onboarding rather than waiting until year-end. This gives you months to resolve issues.
  • Use legal names consistently: Train staff to enter Line 1 (name) from the W-9, not Line 2 (business name/DBA).
  • Automate with the API: Embed TIN matching into your vendor onboarding workflow via API so mismatches are caught in real time.
  • Audit periodically: Do not wait for year-end. Run quarterly bulk matches on active vendors to catch issues early.
  • Keep W-9s current: Request updated W-9s every three years, or whenever you learn of a name or entity change.

Frequently Asked Questions

Can I get more detail than the single-digit IRS code?

The IRS only returns the code itself. TINCorrect adds context by providing explanations, suggested actions, and batch-level analytics alongside the raw code.

What if I get different codes for the same vendor over time?

This is normal. A vendor who returned Code 0 last year might return Code 3 this year if they changed their legal name. Conversely, a Code 3 from last year might become Code 0 after you collected a corrected W-9. Always use the most recent result.

Does Code 0 guarantee my 1099 will not be rejected?

Code 0 means the name/TIN matched at the time of your request. It does not guarantee that the payee's information will not change before you file. It also does not validate other fields on the 1099 (amounts, address, etc.). However, a documented Code 0 is strong evidence of due diligence.

How do I handle a vendor who repeatedly returns Code 3?

If a vendor's TIN keeps returning Code 3 despite multiple W-9 solicitations, consult IRS Publication 1281 and consider beginning backup withholding. Document every attempt to collect correct information to establish reasonable cause. See our full guide on what happens when a TIN doesn't match.

Ken Ham
Author
Ken Ham
Founder at TINCorrect

Passionate about making tax identity verification simple so businesses can focus on what matters.

   Help