CP2100 Notices Land in April: Three W-9 Myths That Cost Payers
IRS CP2100 and CP2100A notices arrive each April, bringing 15-business-day B-notice deadlines and 24% backup withholding exposure into busy season. Three vendor-data myths drive the risk.

Adjustments
- IRS CP2100 and CP2100A notices are generally issued in October and the following April.
- B-notices must be sent within 15 business days of the CP2100 notice or receipt date, whichever is later.
- Backup withholding runs at 24 percent and must begin no later than 30 business days after the notice date if a signed W-9 has not arrived.
- A second notice for the same name/TIN mismatch within a three-calendar-year period triggers second B-notice procedures.
- Second B-notices require Letter 147C for EINs or a qualifying Social Security card copy — another W-9 is insufficient.
The IRS generally issues CP2100 and CP2100A notices in October and again the following April, identifying missing, incorrect, or unissued taxpayer identification numbers (TINs) on information returns. That April mailing drops unfinished W-9 work squarely into busy season. A vendor's Form W-9 can be collected on time, filed correctly, and still create work months later: if nobody checks the name/TIN combination, an incorrect pairing flows into Form 1099 and eventually triggers an IRS notice.
Steve Saah's busy season action plan recommends auditing workflows for bottlenecks. Vendor data deserves a place in that review, because checking whether a W-9 was collected is different from checking whether its details are usable.
Three misconceptions make the response harder than it needs to be.
Myth 1: The IRS will sort out the mismatch
A CP2100 does not repair the client's vendor records. The payer must compare the IRS listing with its own records and determine the appropriate response.
The distinction matters: the IRS sends the CP2100 to the payer; the payer sends the B-notice (the formal backup-withholding solicitation letter) to the vendor. Not every entry calls for the same letter. Missing TINs carry separate solicitation and backup-withholding requirements, including immediate withholding where required.
For an incorrect TIN, when the name/TIN combination and account number on the IRS notice match the payer's records, the payer generally must send the appropriate B-notice to the payee. If the information differs, investigate whether a recent record update, an error in the filed return, or IRS processing explains the discrepancy. Correct or update the payer's records where necessary; there is no need to notify the IRS of that correction.
IRS Publication 1281 sets out the procedures. When required, send the appropriate first or second B-notice within 15 business days after the CP2100 or CP2100A notice date or receipt date, whichever is later. Record when the client received the notice, who owns the response, and which vendors need follow-up.
Keep a history of CP2100 and CP2100A notices. A second notification for the same account and incorrect name/TIN combination within the applicable three-calendar-year period can trigger second B-notice procedures. Publication 1281's counting rules and exceptions must be applied before deciding which notice to send.
Myth 2: Backup withholding is the vendor's problem
The vendor must supply the correct information, but the payer is responsible for withholding when the rules require it. The current backup-withholding rate is 24 percent on covered reportable payments.
A vendor's promise to investigate is not the required documentation. Under the first B-notice procedure, the payee generally must provide a properly completed and signed Form W-9 certifying the correct name/TIN combination to prevent or stop backup withholding. A second B-notice requires additional documentation; another W-9 alone is not enough.
Use Publication 1281 to diary the start and stop deadlines for the relevant notice type. Under the first B-notice procedure, if the required signed Form W-9 has not arrived, backup withholding on covered payments must begin no later than 30 business days after the CP2100 or CP2100A notice date or receipt date, whichever is later. The payer may begin earlier and must stop within 30 calendar days after receiving the required certification; withholding may stop earlier within that period. That timetable does not apply indiscriminately to missing TINs or other withholding triggers.
Amounts withheld must be deposited and reported under the applicable rules, including Form 945. Payers can be liable for tax they fail to withhold, plus applicable penalties — an exposure separate from penalties for incorrect information returns.
For the accounting firm, the practical question is who tells accounts payable to start or stop withholding. Assign that responsibility explicitly rather than assuming the person sending the vendor letter also controls payments.
Myth 3: A second B-notice is just another reminder
Where the second-notice rules apply, another W-9 is not enough. Publication 1281 requires validation appropriate to the type of TIN and says not to enclose Form W-9 with the second B-notice.
For an employer identification number, the payee generally obtains IRS Letter 147C. For a Social Security number, the required evidence is a copy of a Social Security card meeting IRS conditions: the name or number must differ from the second B-notice, or the card must be dated no earlier than six months before that notice. Other TIN types have their own documentation requirements.
A returned document should be checked, not simply marked "received." Sending the wrong request creates another exchange with the vendor while the withholding requirements remain unresolved. Keep the notice date, name/TIN combination, response, and supporting documents together; a complete history makes the correct procedure easier to establish.
What does this change for vendor onboarding?
The IRS TIN Matching program lets eligible payers and authorized agents check name/TIN combinations before filing information returns. It is not an unrestricted public lookup service.
A simple control belongs in vendor setup:
- collect the W-9 and review its entries;
- run an eligible name/TIN match;
- resolve discrepancies before filing;
- keep the result and assign an owner to exceptions.
Where practical, do this before the first payment, while the vendor is already engaged in onboarding. If the firm does not manage vendor setup, agree who does — a documented client intake procedure or a pre-filing review within the firm's engagement scope.
A workflow can be fast and still carry bad data. Giving W-9 accuracy a clear owner, alongside a defined B-notice response process, prevents an apparently completed onboarding task from becoming a busy season interruption.
via irs.gov (Original)
More from Priya Raman
Show full bio
Senior reporter covering technology and product news in CPA News is a professional daily at CPA News.
10 articles
Linked entries
- IRS OPR Tells Firms to Notify Insurers in Breach Plans
- BEC Losses Hit $3.05 Billion: Why Payment Controls Are Cybersecurity
- SEC SOX proposal could exempt 1,596 companies from 404(b) attestation
- AICPA Month in Review: Senate Passes TAS Act, AI Audit Aid, Trump Account Regs
- FASAB reopens federal environmental cleanup liability rules