The 1099 Vendor Cleanup Checklist: Catch Duplicates Before January Wrecks Your Weekend

TL;DR: The most expensive 1099 mistakes — duplicate filings, CP-2100 notices, backup withholding fights — almost always trace back to vendor master data that wasn't cleaned up before filing. This is a controller's checklist for the cleanup window between May and October, when there's no filing pressure but the same vendors will show up again in January. Run it once, save your team the January meltdown.

If you're reading this in May, June, or July, you're in the cleanup sweet spot. Filing season is over, the IRS has stopped sending notices for last year, and you have months before the next round of W-9 collection starts. This is when smart finance teams clean their vendor data — quietly, methodically, with no deadline pressure.

If you wait until December, you'll be doing this work at the same time as month-end close, year-end audit prep, and W-9 chasing. That's how mistakes get made and weekends get cancelled.

This is the checklist to use right now.

Why 1099 cleanup is really vendor data cleanup

The headline of "1099 cleanup" is a little misleading. The IRS doesn't care about your forms — it cares about whether the name and TIN on each form match its records. When they don't match, you get a CP-2100 notice, and the burden shifts to you to fix it or start backup withholding at 24%.

The reason names and TINs don't match is almost always one of five things:

1. Outdated W-9. The vendor restructured, changed legal name, married — and never sent you a new W-9.
2. TIN/name mismatch. Sole proprietor used a DBA name instead of their legal name.
3. Transposition error. Someone typed the EIN wrong when entering the vendor.
4. Duplicate vendor records. Same vendor exists twice with slightly different names, leading to two 1099s where one should exist.
5. Missing TIN. A vendor relationship that predates your formal onboarding process.

The penalty math (so you can justify the project)

• Late or incorrect 1099: $60-$330 per form, depending on how late
• Intentional disregard: $660 per form, no cap
• Backup withholding failure: You owe the 24% the IRS would have collected
• Time cost: Responding to a CP-2100 takes 30-60 minutes per affected vendor when you scramble in January

If you have 200 1099-eligible vendors and 5% have data issues, that's 10 forms with potential penalties. At $330 each, that's $3,300 in fines, plus 5-10 hours of remediation.

The 1099 vendor cleanup checklist

Phase 1: Export and audit (Week 1)

☐ 1. Export your full vendor list from your ERP

Include: legal name, DBA, EIN/SSN, entity type, address, email, total YTD payments, payment method (check/ACH vs card), and 1099 reportability flag.

☐ 2. Identify your 1099-reportable population

Filter to vendors who received $600+ in services payments via check, ACH, or Zelle. Remove vendors paid only by credit card or third-party payment networks. Remove employees, exempt corporations, and one-time refunds.

☐ 3. Cross-reference with last year's filed 1099s

Did you file a 1099 last year for a vendor that's not on this year's reportable list? Either they didn't get paid this year (fine) or they got paid but weren't flagged (problem — investigate).

☐ 4. Check for missing W-9s

Any vendor on your reportable list without a W-9 on file is a problem. Make a list. Email auto-reminders go out every 5 business days starting now, not December.

Phase 2: Find the duplicates (Week 2)

☐ 5. Run exact-match deduplication

Sort by EIN/SSN. Any rows with the same TIN are almost certainly the same vendor — even if the names look different. Merge them.

☐ 6. Run fuzzy duplicate detection on vendor names

The duplicates that cost you money look like:

VLOOKUP can't link these. Excel's Remove Duplicates won't catch them. You need fuzzy matching.

Three options:

• Manual scrub: 15-20 hours on a 1,000-vendor list, high error rate
• Python with rapidfuzz/fuzzywuzzy: 1-2 days if you have technical skills
• Fuzzy matching tool: DedupFuzzy handles 1,000 vendors in 15 minutes

For a deeper look at why exact-match logic fails, see our guide on removing duplicate company names from a CSV.

☐ 7. Merge duplicates in your ERP

For each duplicate group: keep the record with the most recent activity, move payment history to the surviving record, mark the others as inactive with a note pointing to the survivor.

Phase 3: Validate TINs (Week 3)

☐ 8. Enroll in IRS Bulk TIN Matching

This is free through IRS e-Services. If your company doesn't have access yet, get it set up now — approval can take 2-3 weeks.

☐ 9. Run bulk TIN match on every reportable vendor

Upload your full reportable list. The IRS returns match/mismatch results within 48 hours.

☐ 10. Resolve every mismatch before filing season

• Re-request the W-9 with a clear explanation that backup withholding will start otherwise
• Verify the legal name on the W-9 matches IRS records (sole proprietors must use legal name, not DBA)
• Update your vendor record once you have the corrected information
• Re-run TIN matching to confirm the fix

Phase 4: Standardize and lock down (Week 4)

☐ 11. Standardize legal names to match W-9 exactly

The name in your vendor master should match the name on the W-9 character-for-character.

☐ 12. Apply your naming convention to all active vendors

If you don't have a documented naming convention, write one now. One page is enough.

☐ 13. Set up onboarding controls for new vendors

• W-9 required before any payment is issued
• TIN matched at onboarding (interactive IRS lookup)
• Duplicate detection at the vendor creation screen
• Segregation of duties between vendor creation and invoice approval

☐ 14. Schedule the next cleanup

Calendar reminder for Q2 next year.

What goes wrong if you skip this

Scenario 1: The duplicate filing. Vendor "Smith Consulting LLC" got a 1099-NEC for $14,000. The same vendor, recorded as "Smith Consulting, L.L.C." in a different region's books, got another 1099-NEC for $9,000. The IRS now thinks the vendor was paid $23,000.

Scenario 2: The CP-2100 cascade. You filed 180 1099s in January. In April, the IRS sends a CP-2100 notice listing 22 mismatches. Each one requires a B-notice to the vendor giving them 30 days to provide a corrected TIN, or you start 24% backup withholding.

Scenario 3: The audit finding. Internal audit reviews the AP process and identifies 47 inactive duplicate vendors. The finding requires written remediation, retesting in six months, and a management response in the audit committee report.

The realistic time investment

Common questions

When exactly should I do this in 2026? Ideal window: May through September.

Do I need to clean vendors that aren't 1099-reportable? For 1099 purposes, no. But if you're already cleaning, do it all.

What if our ERP has built-in duplicate detection? Use it as a first pass. Most catch only high-confidence duplicates (90%+ similarity) and miss the 70-89% range that often contains real duplicates.

Should we do TIN matching ourselves or use a third-party service? The IRS bulk TIN matching is free and works well. For a one-time annual cleanup, it's fine.

What about credit card payments and 1099s? Payments via credit card or third-party payment processors are reported by the processor on a 1099-K, not by you. Don't double-report.

Where DedupFuzzy fits in this checklist

DedupFuzzy handles checklist item #6 — the fuzzy duplicate detection that's the largest manual time sink. Built specifically for:

• Legal entity suffix variations (Inc., LLC, Corp., L.L.C.)
• Punctuation and ampersand variations (& vs and)
• Word order changes (John A. Smith vs Smith, John A.)
• Confidence scores so you know which pairs need review

Free tier covers 500 rows. Paid plan at $49/month handles unlimited volume.

Try it on your reportable vendor list: dedupfuzzy.com.

Related guides

• How to Clean Up Your Vendor Master File
• How to Remove Duplicate Company Names From a CSV File
• Fuzzy Matching Explained