IRS B Notice Explained: Triggers and How to Avoid One

Quick answer: An IRS B notice (officially the CP2100 or CP2100A) tells your business that a payee’s name and Taxpayer Identification Number (TIN) on a Form 1099 do not match IRS records. It triggers backup withholding and possible penalties. You avoid B notices by verifying TINs before you file.

Every year, the IRS sends out millions of notices to businesses with mismatched data on their Form 1099 filings. If your business pays contractors, freelancers, or vendors, there is a good chance one will land in your mailbox eventually. The notice itself is not a penalty. It is a warning, and how you respond determines whether it stays that way.

This guide breaks down what a B notice is, what causes one, and the exact steps to take when you receive it. You will also learn how to stop B notices from showing up in the first place, which is where most of the time and cost savings live. Let’s start with the basics.

What is an IRS B notice?

An IRS B notice is a backup withholding notice the IRS sends when a payee’s name and TIN combination on an information return does not match its database. The “B” stands for backup withholding, the action you may be required to take as a result.

The notice comes in two forms: the CP2100 and the CP2100A. The IRS issues a CP2100 when you file 50 or more information returns with errors. It issues a CP2100A when you file fewer than 50. The content and your required response are identical. The only difference is the volume of errors involved.

The IRS typically sends these notices twice a year, in October and the following April. Each one arrives with a list of the payee name and TIN combinations that failed to match. Your job is to compare that list against your records and act fast.

What triggers a B notice?

A B notice comes down to one core problem: the name and TIN you reported do not match what the IRS has on file. Several common errors cause this mismatch, and most of them happen during data entry or vendor onboarding.

Here are the usual culprits:

Incorrect TINs provided by the payee on their Form W-9

Transcription errors when your team enters the TIN into your system

Transposed numbers in a Social Security number or EIN

Name changes a payee never reported to the Social Security Administration

Nicknames or trade names used instead of the legal name on file

Most of these slip through because verification happens after filing, not before. A single typo or an outdated W-9 is enough to put a payee on the IRS list. Catch these errors early and the notice never gets generated.

What happens if you ignore a B notice?

Ignoring a B notice carries real costs. The consequences stack up the longer the mismatch stays unresolved, and they hit your bottom line directly.

Here is what your business risks:

Backup withholding. You may be required to withhold 24% of future payments to the affected payee and send it to the IRS.

Penalties. The IRS can charge per incorrect return. For returns due in 2025, penalties run $60 per return if corrected within 30 days, rising to $340 per return after August 1, and $680 per return for intentional disregard.

Follow-up notices. Continued non-compliance leads to a 972CG notice, the “Notice of Proposed Civil Penalty,” which formalizes the fines you owe.

Audit risk. Uncorrected TIN mismatches can invite broader IRS scrutiny of your filings.

The math adds up quickly. Filing a batch of 1099s with TIN errors can turn a clerical mistake into thousands of dollars in fines. The good news is that prompt action keeps a B notice from ever becoming a penalty notice.

How do you respond to a B notice?

When a CP2100 or CP2100A arrives, treat the date on the notice as your starting line. You have 15 business days from that date to send a B notice to each affected payee. Follow these steps in order.

Step 1: Compare the list against your records

Pull the list of mismatched name and TIN combinations and check it against your internal vendor files. Sometimes the error is on your end, a transposed digit or a stale W-9. Sometimes the record agrees with your files, which points to an IRS processing issue or a recent update. Correct your own records where needed, but do not call or write the IRS to report the correction.

Step 2: Send the B notice to affected payees

For each payee whose record does not agree, send the appropriate B notice. A first B notice includes a blank Form W-9 and asks the payee to verify their name and TIN. A second B notice, issued when the same payee appears twice within three years, requires the payee to provide official validation instead, a Social Security card for individuals or IRS Letter 147C for entities.

Step 3: Start backup withholding if there is no response

If the payee does not respond within 30 calendar days, begin backup withholding at 24% on their future payments. Keep withholding until you receive a properly completed Form W-9 (or the required validation for a second notice). Once you do, stop backup withholding within 30 calendar days.

Step 4: Document everything

Keep records of every B notice you send and every action you take for at least four years. This documentation is your defense. If the IRS later proposes a penalty, a clear paper trail can help you abate it.

How do you prevent B notices in the first place?

Responding to a B notice costs time, attention, and often money. Preventing one costs far less. The fix is simple: verify name and TIN combinations before you file, not after.

A few practices keep B notices off your desk:

Verify TINs before filing. Run name and TIN combinations through TIN matching ahead of each filing season to catch mismatches while you can still fix them. Checking twice a year, once in spring and once in fall, clears errors before 1099 season.

Collect a complete W-9 upfront. Request a legible, fully completed Form W-9 from every vendor before you make the first payment, with the correct entity type selected.

Standardize your onboarding. Build a repeatable validation step into vendor onboarding, including double-entry verification for TINs and a check of legal name against payment name.

Automate the verification. Tools like TINCheck validate name and TIN combinations in real time, flag problems before filing, and maintain an audit trail of your efforts.

Each of these turns a reactive scramble into a routine check. Your team stops chasing corrections after the fact and starts filing clean data from the start.

Stop B notices before they start

A B notice is a warning, not a verdict. Respond on time, follow the steps, and document your work, and it stays a minor administrative task. Ignore it, and it grows into backup withholding, penalties, and audit exposure.

The smarter play is prevention. Clean TIN data going in means clean filings going out, which means fewer notices, fewer penalties, and far less rework for your team. Verifying TINs before you file is the single most effective way to keep your 1099 process compliant.

Ready to stop B notices before they start? Get started with TINCheck today and validate your TINs in real time.

Frequently asked questions

What is the difference between a CP2100 and a CP2100A notice?

The difference is volume. The IRS issues a CP2100 when you file 50 or more information returns with errors, and a CP2100A when you file fewer than 50. The information and required response are the same for both.

How long do I have to respond to a B notice?

You have 15 business days from the date on the CP2100 or CP2100A to send B notices to your affected payees. The clock starts on the notice date, not the date you receive it, so act quickly.

When do I have to start backup withholding?

You must begin backup withholding at 24% if a payee does not respond to your B notice within 30 calendar days. Continue withholding until you receive a valid Form W-9 (first notice) or official TIN validation such as Letter 147C (second notice), then stop within 30 calendar days.

What is the difference between a first and second B notice?

A first B notice asks the payee to confirm their name and TIN with a new Form W-9. A second B notice, triggered when the same payee is flagged twice within three years, requires official validation instead, a Social Security card for individuals or IRS Letter 147C for entities.

Can I be penalized for a B notice?

Yes. If you fail to respond, fail to collect valid TINs, or fail to start backup withholding when required, the IRS can issue a 972CG penalty notice. Penalties run per incorrect return and increase the longer they go uncorrected. Responding on time and keeping documentation is your best protection.

What is the best way to avoid B notices?

Verify name and TIN combinations before you file. Running TIN matching ahead of filing season catches mismatches while they are still easy to fix. Automated tools like TINCheck validate data in real time and flag errors before they reach the IRS.