How to Verify a Vendor’s TIN Before Making a Payment

If your team is verifying vendor TINs only at year-end, you are already behind. TIN mismatches caught at filing time trigger IRS penalties, backup withholding obligations, and B Notices, all of which take significantly more time and money to resolve than a pre-payment TIN check would have.

This guide covers the exact steps to verify a vendor’s TIN before making a payment and how to build that process into your AP workflow as a standing control. Done right, pre-payment TIN verification prevents avoidable penalties and 1099 errors.

Why Verifying a Vendor’s TIN Before Payment Is a Business-Critical Control

Checking vendor TINs at filing time means you are dealing with errors after payments are complete. The consequences show up in three areas:

IRS Penalties

IRS penalties apply when a 1099 is filed with an incorrect TIN. These penalties are tiered based on how quickly the error is corrected:

Backup Withholding

IRS backup withholding is required when a vendor’s TIN cannot be verified. You must begin 24% backup withholding and remit it to the IRS, creating vendor friction and additional filing obligations.

Vendor Fraud Prevention

Vendor fraud prevention is the third reason TIN verification belongs in your pre-payment workflow. Unverified TINs can mask shell companies or fictitious vendors. A verification step before payment is also a form of fraud control.

Step 1: Collect and Review a Completed W-9 Before the First Payment

The W-9 form is the legal foundation for every vendor TIN on record. No W-9, no payment; that should be the policy.

A valid W-9 must include all of the following:

• Legal name; not a DBA or trade name
• Taxpayer Identification Number (TIN)
• Entity type (individual, LLC, corporation, etc.)
• Signature and date

A common error at this stage is accepting a DBA or trade name in place of the vendor’s legal entity name. The IRS matches on the legal name tied to the TIN.

For foreign vendors, W-8 series forms apply instead of the W-9. If your team manages international payables, treat this as a separate workflow.

Step 2: Validate the TIN Format Before Submitting to the IRS

Validating TIN format catches obvious errors before running a match. There are three TIN types relevant to vendor payments:

Flag any of the following before proceeding:

• Fewer than 9 digits
• Letters in the number
• All zeros in any segment
• TIN type does not match the vendor’s entity type

If any of these are present, return the W-9 to the vendor for correction before running a match. Catching format errors at this stage keeps your IRS TIN matching attempts clean and your records accurate.

Step 3: Run an IRS TIN Match Before Releasing Payment

With a complete W-9 and a valid TIN format confirmed, the next step is running the match. The IRS e-Services TIN Matching Program verifies whether the name and TIN combination on your W-9 matches IRS records.

Two options are available:

• Interactive TIN Matching handles up to 25 name/TIN combinations per submission in real time. You can submit multiple groups of 25, up to the daily limit per user ID. Use this for individual vendor approvals before releasing a payment.
• Bulk TIN Matching handles up to 100,000 combinations with results returned within 24 hours. Use this for quarterly audits or pre-filing sweeps of your full vendor roster.

IRS result codes and what you must do:

• Match: Verified; safe to pay.
• No Match: Hold payment; request a corrected W-9.
• Not Issued/Invalid: Investigate before proceeding.

The program requires IRS e-Services enrollment, which can take several days to complete.

For real-time TIN verification without delay, TINCheck real-time returns results in seconds without needing IRS enrollment.

Step 4: How to Handle a TIN Mismatch Without Disrupting Your AP Process

A mismatch does not automatically indicate fraud. Name differences, recent changes, or data entry errors are common causes. Here’s what you can do in such cases:

• Hold the payment
• Request a corrected W-9 within 15 business days
• Document the discrepancy and actions taken

If corrected and verified, release payment. If unresolved, begin backup withholding on future payments and file Form 945 at year-end.

CP2100 Notice Handling

The IRS issues a CP2100 after a 1099 is filed with a mismatched TIN. You have 15 business days from the notice date to request a corrected TIN from the vendor. If unresolved within 30 business days, begin backup withholding.

The best way to avoid a CP2100 is to catch mismatches before filing. For high-volume teams, TINCheck enables real-time and bulk TIN verification without slowing AP workflows.

Step 5: Build TIN Verification Into Your AP Workflow as a Standing Control

Verifying a TIN once at onboarding is not sufficient. TINs change when vendor ownership changes, EINs are reassigned, or vendor data is updated in your system.

Re-verification should be triggered at:

• New vendor onboarding
• Annual Q4 verification sweep
• Any vendor data change

5-Step Pre-Payment TIN Verification Workflow

1. Collect a completed, signed W-9
2. Validate TIN format against the expected type
3. Run a name/TIN match through the IRS TIN Matching Program or TINCheck
4. Record the result with a timestamp
5. Release payment on a confirmed match; hold and investigate on getting any other result

5 Common TIN Verification Mistakes Businesses Make

Avoiding these vendor TIN best practices gaps is as important as running the verification itself. The most common 1099 compliance errors start here:

1. Verifying only at onboarding, not before payment. Vendor data changes after onboarding. An EIN that matched at setup may not match if ownership or entity structure has since changed.
2. Accepting a DBA name instead of the legal entity name. The IRS matches on the legal name tied to the TIN. A mismatch caused by a trade name can trigger a B Notice that a corrected W-9 policy would have prevented.
3. Skipping TIN verification mistakes for low-dollar vendors. Payments to a single vendor can accumulate past the 1099 reporting threshold during the year. Verification requirements apply regardless of individual payment size.
4. Not documenting verification records. A match result with no timestamp or audit trail provides no protection if the IRS questions your process. Document every verification with the date, result, and action taken.
5. Treating TIN verification as a finance-only task. If procurement can onboard a vendor without a verified W-9 on file, the control has a gap. AP and procurement need a shared policy on vendor data requirements before any payment is approved.

Verify Before You Pay

Apply these three steps before your next vendor payment:

• Collect a complete W-9 before payment
• Run a TIN match before payment, not after filing
• Build re-verification into your workflow

Fix mismatches before payment with a corrected W-9, not after filing when penalties apply. TIN verification before payment is what keeps your 1099s accurate and your business out of penalty exposure.

Ready to verify your vendor TINs before your next payment? Get started with TINCheck.

Frequently Asked Questions

What is a TIN mismatch?

A TIN mismatch occurs when the name and TIN on a W-9 do not match IRS records. Common causes include typos, outdated names, or using a trade name. If not corrected, it can trigger penalties and a CP2100 notice.

What to do if a TIN match fails?

Hold payment and request a corrected W-9 within 15 business days. If corrected, verify and proceed. If unresolved, begin 24% backup withholding and document all actions. File Form 945 at year-end if withholding applies.

What to do if TIN is invalid?

Return the W-9 and request a corrected form immediately. Do not release payment or file a 1099 with an invalid TIN, as this can lead to penalties and backup withholding obligations.

How to verify US tax ID?

Use the IRS e-Services TIN Matching Program to verify name and TIN combinations. Interactive matching is real-time; bulk returns results within 24 hours. Tools like TINCheck offer faster verification without IRS enrollment.

Do I need to verify TINs for low-dollar vendors?

Yes. Payments can accumulate past 1099 reporting thresholds over time. Skipping verification for low-dollar vendors creates compliance gaps and increases the risk of mismatches and penalties.