Treat the notice as an operational event
An owner opens an IRS envelope listing several vendors whose reported names and taxpayer identification numbers did not match. The accounting team asks every vendor for another Form W-9 and files the envelope away. That response may miss the required procedure, particularly when a vendor has appeared on an earlier notice. The business needs to determine what was filed, what its records show, and which action applies to each account.
The IRS backup withholding B program uses CP2100 and CP2100A notices to identify missing or incorrect taxpayer identification information. Publication 1281 explains the applicable notice and withholding procedures. A vendor's assurance that the number is right is useful information to investigate, but it does not by itself close the payer's obligations. Assign the notice to someone with authority to coordinate tax reporting and future payments.
Reconcile the exact reported combination
Retrieve the information return actually submitted, including the tax year, payer identifier, recipient name, recipient TIN, account number, and transmission acknowledgment. Compare the IRS listing with that return and the vendor master record. A trade name, an owner's legal name, and the name of a disregarded entity can appear in different places. Do not change the vendor's legal identity based solely on what appears at the top of an invoice.
Classify each discrepancy. The company may have transmitted the wrong number, updated its records after the original filing, or reported information that agrees with its current records but still failed the IRS match. Those situations do not all call for the same response. Record the conclusion and supporting evidence rather than applying a blanket instruction to the entire vendor list. Preserve the original submission before editing the accounting system.
Use a vendor-level example
Assume three vendors appear on a notice. Vendor A's filed number contains a transposed digit that does not match the signed form already held by the business. Vendor B's filed information agrees with the vendor record, and the company has no earlier notice for that account. Vendor C's information also agrees, but the archive contains a previous applicable notice. A mass request for three replacement forms conceals the different procedural histories.
The controller creates three rows, links the evidence, and asks the preparer to identify the action required for each row under the current instructions. The first and subsequent B-notice procedures differ; a second notice can require validation beyond simply obtaining a new W-9. This example illustrates why history matters. It does not determine the applicable deadlines, withholding start date, or cure for any real vendor account.
Coordinate the response with payment processing
The action register should show the notice received date, applicable procedural deadlines, notice version sent, delivery evidence, vendor response, reviewer, and any required withholding instructions. Confirm that accounts payable can implement withholding on affected payments. A tax preparer can identify the requirement while the payment platform continues sending the full invoice amount unless someone changes the approved workflow and tests a payment preview.
Backup withholding is currently 24% when applicable. The business must coordinate remittance and reporting, including Form 945 and the relevant payee return. Do not calculate a withholding amount on an ordinary invoice until the responsible reviewer has established that the payment is subject to the rule. Maintain a distinct liability account so withheld money is not treated as extra operating cash or an unearned reduction of vendor expense.
Close the file only when the procedure is complete
Completion means more than receiving an email from the vendor. Document the accepted evidence, the date any withholding instruction begins or ends, and the advisor's reason for that treatment. Reconcile actual payments and remittances to the decision. Keep correspondence and identifying information in a restricted folder, with a nonsensitive status field available to purchasing staff who need to know whether the account is ready for payment.
The owner should also ask why the mismatch reached filing season. Review vendor onboarding, name-and-number entry controls, and eligibility for the IRS TIN Matching service. That service does not establish worker classification or validate an expense deduction. It addresses one specific information-reporting risk. A sound closeout both resolves the notice under the appropriate procedure and changes the process that allowed incorrect data to recur.
Sources & further reading
Consult the original guidance and its effective dates. These references support the educational discussion; their application depends on the specific facts.