What Is TIN Matching? A Complete Guide for AP Teams and 1099 Filers

Every 1099 you file carries a name and a TIN, and the IRS checks whether they match. TIN matching checks that pair against IRS records before you file, so mismatches are fixed before they become CP2100 notices, B-Notices and 972CG penalties.

Updated October 28, 2026.

The Basic Concept

A Taxpayer Identification Number (TIN) is the number the IRS uses to track a taxpayer's filing history and payment records. For individuals, it's typically a Social Security Number (SSN). For businesses, it's an Employer Identification Number (EIN). For certain foreign individuals, it may be an Individual Taxpayer Identification Number (ITIN).

When payments to a vendor reach the 1099-NEC or 1099-MISC threshold ($600 for 2025 payments; $2,000 for payments made in 2026 and later, under the One Big Beautiful Bill Act), you're required to file a Form 1099 reporting that payment to the IRS. The 1099 must include the vendor's correct TIN and the name associated with that TIN in IRS records.

TIN matching is the process of verifying, before you file, that the name/TIN combination you have on file for each vendor actually matches what the IRS has in its database. IRS TIN Matching is the only IRS-run check of a name and TIN pair before you file; the IRS offers it free through its e-Services portal. Services like TIN Comply run the same match against IRS records for you, with additional capabilities layered on top.

Key takeaways

The IRS matches on a four-character name control, so a DBA or a married name on the wrong record fails even when the TIN is right.
A mismatch left until filing becomes a CP2100, then B-Notices and 24% backup withholding, then a 972CG at up to $340 per return.
Run the match at onboarding, once mid-year on the full vendor list, and again before filing.
The IRS program is free but capped at 100,000 pairs per file with results in about 24 hours, and it locks the account for 96 hours on suspicious name testing.

Why the Match Has to Be Exact

The IRS doesn't match against the full name string you submit. It uses a name control: typically the first four significant characters of the last name for individuals, or the first four characters of the legal business name for entities. This sounds forgiving, but in practice it catches a wide range of common errors:

A vendor who provides their DBA name instead of their legal name
A sole proprietor whose SSN is registered under their married name but who submits their former name
A business that changed its legal name after a merger but hasn't updated its EIN registration
A single-member LLC that provides the LLC name but whose TIN is the owner's SSN (registered to the owner's personal name)

Any of these produces a mismatch, not because the TIN is wrong, but because the name associated with it in your records doesn't align with what the IRS has on file for that TIN.

What Happens Without TIN Matching

The consequences of filing with incorrect TIN/name combinations follow a predictable sequence:

Step 1: CP2100 notice. The IRS processes your 1099 filings and runs them through its automated matching system. Any TIN/name combinations that don't match IRS records are compiled into a CP2100 notice (or CP2100A for smaller lists) sent to you, typically in the fall of the year after you filed.

Step 2: B-Notice obligations. The CP2100 triggers First B-Notice requirements. Within 15 business days of the notice date or receipt, whichever is later, you must send a First B-Notice to each affected vendor requesting a corrected W-9. Vendors have 30 business days to respond. Non-respondents trigger mandatory backup withholding at 24% on all subsequent payments.

Step 3: Notice 972CG. Roughly 12 to 18 months after you filed, the IRS proposes civil penalties for the mismatches through Notice 972CG. Penalties range from $60 per return (corrected within 30 days of the due date) to $330 per return for returns due in 2025 and $340 for returns due in 2026 or 2027 (not corrected by August 1); the full table is on the 1099 penalties explained page. You have 45 days from the notice date to respond with payment or a reasonable cause argument.

Step 4: Assessed penalties and collection. If you don't respond to the 972CG, penalties are assessed and collection begins. Interest accrues from the date of assessment.

The entire sequence from filing to penalty assessment typically spans two years. TIN matching before filing interrupts it at Step 1, before anything is triggered.

The IRS TIN Matching Program

The IRS offers TIN matching free of charge through its e-Services platform at irs.gov/e-services. Two modes are available:

Interactive TIN Matching: up to 25 name/TIN combinations per session, results returned immediately. Useful for spot-checking individual vendors.

Bulk TIN Matching: upload a file of up to 100,000 name/TIN combinations in a specific semicolon-delimited format, results returned within 24 hours via secure mailbox.

To use the program, you must be registered for IRS e-Services, have filed at least one information return (so you appear in the IRS Payer Account File), and have completed a separate TIN Matching application. Results are available in your secure mailbox for 30 days; once opened, the file is retained for 3 days before being purged.

The result codes the IRS returns:

Code	Meaning
0	Match - TIN and name combination match IRS records
1	TIN missing or not 9-digit numeric
2	TIN not currently issued
3	TIN/name combination does not match
4	Invalid request (file format error)
5	Duplicate request
6	Matched on SSN (TIN type was unknown)
7	Matched on EIN (TIN type was unknown)
8	Matched on both SSN and EIN (TIN type was unknown)

For a detailed breakdown of what each code means and what to do about it, see the TIN matching result codes guide.

Limitations of the IRS Program

The IRS program is authoritative and free. It also has structural constraints that matter at scale:

The 96-hour lockout. The IRS system detects when the same payer EIN researches the same TIN under different names, a pattern that could indicate probing for the name associated with a TIN. When detected, account access is blocked for 96 hours with no early release. This lockout is most dangerous in late January, when AP teams are under deadline pressure to resolve Code 3 mismatches by testing name variations. A team locked out on January 29 may not regain access until after the January 31 1099-NEC deadline.

100,000 record limit per file. Large organizations with vendor populations exceeding 100,000 must split their list into multiple submissions and manage the results across multiple files.

24-hour turnaround. Results aren't immediate for bulk submissions. In a deadline crunch, a 24-hour wait is significant.

TIN matching only. The IRS program validates name/TIN combinations. It doesn't run sanctions screening, look up missing EINs, or provide any resolution path for mismatches beyond the result code.

Strict file format requirements. The bulk file must be a plain text file with semicolon delimiters, specific character restrictions in the name field, and no header row. Files that don't conform exactly produce Code 4 results across affected records. For organizations exporting from ERPs or spreadsheets, format conversion is a common source of errors.

For a complete guide to preparing a valid bulk file, see the IRS TIN matching bulk file format guide.

When and How Often to Run TIN Matching

When	What to run	What it catches
Vendor onboarding, before the first payment	Match the W-9 as it arrives	Errors while the vendor is engaged and willing to correct them; a quick email instead of a November outreach campaign
Mid-year bulk run (Q2 or Q3)	Full active vendor list, once a year outside filing season	Stale records: a vendor who matched last year but returns Code 3 now has changed a name or EIN
Pre-filing validation (December or early January)	Complete 1099 population after payment totals are final	Vendors added since the mid-year run, and proof that earlier corrections are genuinely clean
After major vendor master changes	Any dataset that went through an ERP migration, acquisition, bulk import or data conversion	TIN errors introduced by the transformation itself

TIN Matching in the Broader Compliance Workflow

TIN matching doesn't exist in isolation. It's one component of a vendor compliance workflow that includes:

W-9 collection: gathering the name and TIN information that TIN matching validates. The quality of your W-9 collection process determines the quality of the data you're matching. A W-9 with a DBA name instead of a legal name will produce a Code 3 result no matter how accurately it was entered.

EIN discovery: when TIN matching returns Code 2 (TIN doesn't exist) or Code 3 (name/TIN mismatch), EIN lookup by company name can often identify the correct EIN without requiring vendor cooperation. This resolves mismatches that would otherwise require back-and-forth vendor outreach.

Sanctions screening: verifying that a vendor doesn't appear on OFAC's SDN list or other government watchlists. TIN matching confirms tax identity; sanctions screening confirms legal eligibility to be paid. Both are needed for a complete vendor validation workflow.

B-Notice management: when mismatches survive to the CP2100 stage, the B-Notice workflow is the structured response process. TIN matching pre-filing minimizes the B-Notice population; a well-run B-Notice process manages what remains and builds the reasonable cause documentation that defends against 972CG penalties.

TIN Comply connects all of these in a single platform (validate TINs, look up missing EINs, screen for sanctions, collect W-9s, manage B-Notice workflows, and respond to 972CG notices) so vendor compliance is a coherent process rather than a set of disconnected tools.

The Business Case in Plain Numbers

Consider a mid-sized company filing 1,000 Form 1099-NECs annually with a 5% mismatch rate: 50 mismatched records.

If mismatches are caught pre-filing through TIN matching:

Cost: time to run the match, time to resolve 50 mismatches through W-9 corrections or EIN lookup
IRS penalty: $0
B-Notice workflow: none triggered

If mismatches are discovered via CP2100 after filing:

B-Notice workflow: 50 First B-Notices sent within 15 business days, 30-business-day vendor response tracking, backup withholding calculations for non-respondents, corrected 1099 filings
Staff time: 20 to 40 hours depending on vendor responsiveness
IRS penalty (972CG, assuming corrections after August 1): up to $17,000 at $340 per return for returns due in 2026 or 2027
Additional exposure: backup withholding obligations for non-respondents

The pre-filing path costs staff time. The post-filing path costs staff time plus penalties plus the B-Notice workflow plus the 972CG response. For most organizations with any meaningful vendor population, pre-filing TIN matching pays for itself many times over.

How TIN Comply Works

TIN Comply provides IRS TIN matching against the same underlying IRS database as the e-Services program, with key differences in how the matching is delivered:

No IRS registration required - start immediately without the e-Services registration and TIN Matching application process
No lockout risk - TIN Comply runs the matching for you, so there is no e-Services account of yours to lock; it never gives anyone IRS e-Services access
Real-time results - single pairs return immediately, with no 24-hour wait for bulk submissions
No record limit - upload your full vendor master regardless of size
Upload your own layout - .csv or .xlsx files as exported from your ERP; no IRS fixed format to build
Combined validations - TIN matching, EIN lookup, and sanctions screening in a single file submission
Full audit trail - per-request history with user attribution and timestamps, plus filtered exports for reasonable cause documentation
Request Corrected W-9 - one button on a mismatch starts W-9 collection and tracks it through SENT, OPENED and COMPLETED

Start a free trial - upload your first vendor file and see results in minutes. Or request a demo to see the full workflow.