Vendor Data Hygiene: Why Stale TIN Records Create IRS Problems
Most B-Notices come from stale data, not bad vendors. A legal name changes after a merger or a sole proprietor switches to an EIN, and the W-9 you hold no longer matches IRS records; here is how to catch those changes before filing season.
Updated October 28, 2026.
How Vendor Data Goes Stale
Vendor master files grow over time and degrade quietly. The problems rarely announce themselves. They surface months or years later when the IRS matches your 1099 filings against their records and finds discrepancies.
The most common ways vendor TIN data goes bad:
Legal name changes A vendor gets acquired, rebrands, or restructures. Their EIN stays the same but their legal name changes. The W-9 you have on file still shows the old name, and the IRS matching system will flag it as a mismatch.
Entity type changes A sole proprietor incorporates. They now have an EIN where they previously provided an SSN. If they don't proactively send you an updated W-9 and you don't ask, you're filing 1099s against an ID that no longer matches their IRS record.
Name formatting inconsistencies IRS TIN Matching compares the TIN with a four-character name control. For a business it is the first four significant characters of the legal name (a leading "The" is dropped); for an individual it comes from the surname, and a hyphenated surname keeps its hyphen (Garcia-Lopez gives GARC). A DBA in the legal name field ("Lakeside Pizza" for an entity whose legal name is "Harborview Hospitality Inc") or an individual entered surname-first can fail matching even when the TIN itself is correct.
Vendor turnover and re-onboarding A vendor you haven't paid in three years gets reactivated. Nobody pulls a fresh W-9. The old record goes back into circulation with data that may be years out of date.
Manual entry errors A digit transposed during data entry. A name with a special character that got stripped out when it was imported into your ERP. Small errors that compound over time as the same incorrect record gets replicated across systems.
Key takeaways
- Vendor records go stale through name changes, entity changes, reactivations and entry errors, none of which announce themselves.
- The IRS matches your 1099 against its current records, so a W-9 that was right when collected can still fail.
- Run the full vendor master through IRS TIN Matching in Q3, when there is still a quarter to collect corrected W-9s.
- Each incorrect return due in 2026 can cost $340 under IRC 6721, and the CP2100 for it arrives 12 to 18 months after filing.
Why Year-End Discovery Is the Worst Time
Most AP teams find out about stale TIN data in one of two ways: they run a pre-filing TIN match in November and get a flood of mismatches, or they receive a CP2100 notice from the IRS after filing season.
Both scenarios put you in a reactive position. At pre-filing you're scrambling to reach vendors and collect corrected W-9s before the filing deadline. After a CP2100 you're managing First and Second B-Notice workflows, backup withholding obligations, and potential 972CG penalties, all while trying to run normal AP operations.
The penalty exposure is real. IRS Notice 972CG can reach $340 per incorrect return for returns due in 2026, with an annual cap of $4,098,500 for large filers ($1,366,000 for filers with gross receipts of $5 million or less); the full penalty table covers other years. You have 45 days from the notice date to respond. And the IRS's standard for penalty abatement, reasonable cause under Treas. Reg. 301.6724-1, requires documented evidence that you followed the annual solicitation rules and acted responsibly. Discovering a problem in November and fixing it in December is not the same as having a process that catches it in March.
What Good Vendor Data Hygiene Looks Like
The goal is to find stale data before the IRS does. That means building validation into your workflow at multiple points throughout the year, not just at onboarding and year-end.
At onboarding Collect a W-9 before the first payment. Validate the TIN/name combination against IRS records before the vendor enters your system. Reject records that don't pass validation at the source. Don't let bad data in.
When vendor information changes Any time a vendor updates their address, legal name, or banking information, treat it as a trigger for a W-9 review. Name changes in particular should always prompt a fresh TIN validation.
Before 1099 filing season Run your full vendor list through IRS TIN matching in Q3, not November. That gives you a full quarter to chase down corrected W-9s, re-validate, and clean up records before the filing deadline pressure hits.
After receiving a CP2100 When the IRS sends a CP2100, you have a specific list of mismatched TINs to work through. For each one: cross-reference your records to determine if it's a data entry error or a genuinely bad TIN, send the First B-Notice within 15 business days of the notice date or receipt (whichever is later), give the payee 30 business days to return a W-9, begin 24% backup withholding on payments after that if nothing arrives, and document every step. The documentation is your reasonable cause defense.
The year, as a calendar:
| When | What to run | Why |
|---|---|---|
| Every new vendor | W-9 before the first payment; IRS TIN Matching on the name and TIN pair; sanctions screen | Keeps bad data out of the master |
| On any vendor change | Fresh W-9 and re-match when the legal name, entity type or ownership changes | A name change with the same EIN fails matching |
| Q3 (July to September) | Bulk TIN match of every vendor paid this year | A full quarter to resolve mismatches before filing |
| January | Final match of anyone added or changed since Q3 | 1099-NEC is due February 1, 2027 for tax year 2026 |
| On a CP2100 (12 to 18 months after filing) | First B-Notice within 15 business days; backup withholding after 30 business days | Pub. 1281 timeline |
| Monthly | Sanctions re-screen of the active vendor base, weekly for higher-risk vendors | Lists change on any business day |
The Vendor Master Cleanup Problem
For most organizations, the harder challenge isn't keeping new data clean. It's dealing with years of accumulated stale records in an existing vendor master.
A typical vendor master cleanup involves:
- Deduplication: identifying and merging duplicate vendor records
- TIN validation: running the full vendor list through IRS TIN matching to surface all mismatches
- EIN cross-reference: for mismatches where the vendor is unresponsive, checking an independent EIN database for the legal name on record for the EIN
- W-9 outreach: systematic outreach to vendors with missing or invalid W-9s
- Sanctions screening: screening the cleaned list against OFAC and the other 330+ sanctions and watchlists that apply
This is a significant project for most AP teams to run internally. TIN Comply's vendor master cleanup managed service handles the full process, from initial validation through outreach, re-validation, and delivery of a clean, audit-ready vendor file.
How TIN Comply Helps
- IRS TIN Matching: validate TIN/name combinations individually, in bulk, or via API at any point in the year
- Bulk File Processing: upload your full vendor master as .csv or .xlsx and get results across TIN matching, EIN lookup, and sanctions screening in one pass
- EIN Lookup: when a vendor is unresponsive and you need to find their correct TIN, cross-reference millions of business records for ranked candidates and the legal name on record for the EIN
- W-9 Collection: automated vendor outreach, digital W-9 collection, and instant TIN validation in one workflow
- Vendor Master Cleanup: fully managed service for organizations that need to clean up years of accumulated stale data
Start a free trial or learn about our vendor master cleanup service.
Bottom Line
Vendor data hygiene is not a year-end project. It's a continuous process. The AP teams that avoid B-Notices and 972CG penalties are the ones that catch stale TIN data in March, not November. Building validation into onboarding, change management, and mid-year review cycles costs far less time than managing the IRS notices that stale data generates.
This article is for informational purposes only and does not constitute legal or tax advice. Consult a qualified professional for guidance specific to your organization.