Skip to main content

Run IRS TIN Matching Before 1099 Season: Catch Name/TIN Mismatches While They're Still Free to Fix

Published 10 min readMike ThriftMike Thrift
Run IRS TIN Matching Before 1099 Season: Catch Name/TIN Mismatches While They're Still Free to Fix
On this page

Every January, thousands of small businesses discover the same expensive surprise: the vendor names and tax IDs sitting in their accounting software don't match what the IRS has on file. By then, the 1099s are already due, the mismatch notices are already in the mail, and each bad return can cost up to $340 in penalties — on top of the backup withholding mess you now have to administer.

Here's the good news: the IRS gives you a free tool to catch every one of those mismatches months before you file. It's called TIN Matching, it runs through IRS e-Services, and if you've filed 1099s in either of the last two years, you're almost certainly eligible to use it. September is the ideal time to run it — close enough to year-end that your vendor list is nearly final, with enough runway left to chase down corrected W-9s before the January crunch.

What TIN Matching Actually Is

TIN Matching is a free pre-filing validation service the IRS offers to payers who file information returns. You submit the name and Taxpayer Identification Number (TIN) combinations from your vendor records, and the IRS tells you whether each pair matches its records — before you put those combinations on a 1099 and file it.

It covers the information returns subject to backup withholding: Forms 1099-B, 1099-DIV, 1099-INT, 1099-K, 1099-MISC, 1099-OID, and 1099-PATR. For most small businesses, that means your contractor payments (1099-NEC is not in the matchable list, but the W-9 data behind it is the same data you're validating) and any rents, royalties, or interest you report.

Who can use it

An "authorized payer" is simply a payer that has filed information returns with the IRS in at least one of the two past tax years. If you filed 1099s last January, you qualify. Your authorized agent — your CPA or bookkeeper — can run matches on your behalf under your account as well.

To use the service, you'll need an IRS online account and you'll complete a short application agreeing to the program's terms. First-time enrollment can take a few days to process, which is another reason to start now rather than in mid-January.

The two ways to match

Interactive TIN Matching lets you check up to 25 name/TIN combinations at a time, typed directly on screen, with results back in seconds. The IRS caps usage at 999 such requests in a 24-hour period — far more than any small business will ever need. This is the right option when you're onboarding a new vendor and want to verify the W-9 before the first payment goes out.

Bulk TIN Matching lets you upload a plain-text file with up to 100,000 name/TIN combinations and get results back within 24 hours. This is the year-end play: export your whole vendor list, upload it once, and get a complete mismatch report to work through in October and November.

Why a Mismatch Costs So Much More Than a Correction

A name/TIN mismatch is never just a typo to fix later. It triggers a cascade with three separate costs.

1. The CP2100 notice and the B-notice treadmill

When the IRS finds mismatched name/TIN combinations on your filed returns, it sends you a CP2100 (or CP2100A for smaller filers) notice listing every bad payee. You're then required to send each affected payee a "B notice" — a formal solicitation for a corrected TIN — within 15 business days of the IRS notice date.

If the payee doesn't respond with a valid certified TIN, you must begin backup withholding at 24% on future reportable payments to that vendor, deposit it, and report it on Form 945. Try explaining to a contractor why their next check is 24% lighter because of paperwork. And if the same payee mismatches again within three years, the second B notice requires them to get their TIN certified directly by the IRS or the Social Security Administration — a process neither of you will enjoy.

2. Penalties under Section 6721

Separately from the withholding headache, each return filed with incorrect payee information can draw a penalty under Internal Revenue Code Section 6721. For returns due in 2026, the per-return penalty is $60 if you correct within 30 days, $130 if you correct by August 1, and $340 after that — with higher annual maximums for larger businesses. Intentional disregard carries at least $680 per return with no maximum at all, and the amounts adjust for inflation every year.

One sloppy vendor file with twenty bad TINs can therefore cost thousands of dollars — for errors a free tool would have flagged in seconds.

3. The relationship cost

The penalty math gets the attention, but the operational cost is worse. Backup withholding turns you into a tax collector for your own vendors. It generates confused phone calls, delayed projects, amended filings, and in some cases lost contractors who decide you're too difficult to work with. All of it is avoidable.

How to Run Your Pre-Season TIN Match

Here's a practical workflow that fits into a week of normal operations.

Step 1: Clean your vendor master file first

TIN Matching compares exactly what you submit against IRS records, so garbage in means false mismatches out. Before you upload anything:

  • Collect missing W-9s now. Any vendor you've paid $600 or more this year without a signed W-9 on file is a gap. Request them in September while vendors still answer email promptly.
  • Enter names exactly as the payee entered them on the W-9. The most common mismatch cause isn't fraud — it's data entry. "Robert Smith" vs. "Bob Smith," a missing middle initial, or a DBA line entered in the legal-name field will all fail.
  • Watch the sole-proprietor trap. For individuals and sole proprietors, the name on line 1 of the W-9 must pair with the SSN (or the EIN, if they provided one and it's registered to that name). Entering the business name from line 2 with the SSN from line 1 is one of the most common reasons matches fail.
  • Strip formatting from TINs. Dashes, spaces, and leading-zero truncation from spreadsheet imports cause preventable failures. Store TINs as text, not numbers.

Step 2: Run the match

Log in to IRS e-Services, open the TIN Matching application, and either type in small batches (interactive) or upload your vendor file (bulk). For the bulk file, each line follows a simple delimited format of TIN type, TIN, name, and an optional account number you can use to tie results back to your own vendor IDs.

Step 3: Work the mismatch list

Every combination that doesn't match needs one of three resolutions:

  1. Your data is wrong. Compare the submission against the actual signed W-9. If you mistyped something, fix your records and re-match.
  2. The vendor's W-9 is wrong or outdated. Send a new blank W-9 with a clear deadline, and explain why it matters — vendors respond faster when they understand backup withholding is the alternative. Common real-world causes: a recent marriage or divorce changed the legal name, the business converted from a sole proprietorship to an LLC or S corporation, or the contractor simply misremembered their own EIN.
  3. The vendor won't cooperate. If a payee refuses to furnish a correct TIN, you're required to impose 24% backup withholding on reportable payments. Document your solicitation attempts — they establish the reasonable cause that protects you from penalties.

Re-run the corrected combinations to confirm they now match. Keep a simple log: who mismatched, what you sent, when they responded, and the final match confirmation. That log is your reasonable-cause evidence if penalties are ever proposed.

Step 4: Make it a year-round habit

The pre-season bulk match is your safety net, but the cheapest mismatch is the one that never enters your system. Build TIN verification into vendor onboarding: no new vendor gets a first payment until a signed W-9 is on file and the name/TIN combination has passed an interactive match. It takes under a minute per vendor and eliminates nearly all January surprises.

Common Questions

Does TIN Matching tell me what the correct information is?

No — and this is by design. The IRS confirms match or no-match only; it won't disclose anyone's correct name or TIN to you. That privacy protection is exactly why you need the vendor's own corrected W-9 to resolve a mismatch.

Will matching flag fake or stolen TINs?

It flags combinations that don't match IRS records, which covers typos, outdated information, and fabricated numbers alike. A match confirms only that the name and number go together in IRS records — it doesn't verify identity beyond that.

What if a vendor's information matches but I still get a CP2100?

Check what you actually filed versus what you matched. The usual culprits: filing under a DBA name instead of the matched legal name, transposing digits between the match and the filing, or the payee's records changing after your match (for example, an SSN/ITIN change or a business entity conversion). Your match log plus the filed return will show where the two diverged.

I'm a brand-new business that has never filed a 1099. Can I use TIN Matching?

Not yet — eligibility requires having filed information returns in at least one of the two preceding tax years. Your substitute is rigorous W-9 collection at onboarding: get the signed form before the first payment, enter it exactly, and store it where you'll find it in January.

Good Vendor Records Are Just Good Bookkeeping

Notice what this entire process really is: maintaining a clean vendor master file, collecting documentation before money moves, and reconciling your records against an authoritative source before reporting. That's bookkeeping discipline applied to compliance, and it pays off far beyond 1099 season. Businesses that know exactly who they paid, under what name and tax ID, close their books faster, survive audits with less drama, and answer their CPA's January questions in minutes instead of weeks.

If your vendor records live in a shoebox of PDFs and half-remembered spreadsheet rows, TIN Matching season is the perfect excuse to fix that. Clean the file once, verify it against the IRS, and keep it clean going forward.

Keep Your Financial Records Audit-Ready All Year

Catching mismatches before you file is one part of staying on top of your business finances — having complete, transparent records is the foundation everything else rests on. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data, with every transaction version-controlled and easy to reconcile when compliance season arrives. Get started for free and see why developers and finance professionals are switching to plain-text accounting.

Share this article

Follow this topic

Source: https://beancount.io/blog/2026/09/21/irs-tin-matching-e-services-1099-name-mismatch-b-notice-guide

Published: September 21, 2026