Backup Withholding Compliance for Tax Preparers: W-9, CP2100, B-Notice, and Form 945

When one of your small business clients hires independent contractors and issues 1099-NEC forms, they step into a compliance area that most preparers handle poorly: backup withholding. The rules are not complicated, but the deadlines are short, the paperwork trail matters, and the penalties for ignoring an IRS notice are real. This guide is written for tax preparers who advise the payer, the business that writes the checks and files the 1099s, not the contractor receiving payment.

This guide covers the four triggers under IRC Section 3406, the 24 percent withholding rate (with mandatory hedges for recent legislative changes), the W-9 collection workflow your clients should run before the first payment, the IRS TIN Matching program that prevents most problems before they start, how to read a CP2100 or CP2100A notice, the First and Second B-Notice workflows with their exact deadlines, Form 945 annual filing, and the failure-to-withhold penalties that apply when a client skips the process.

All figures, statutory references, and procedural details in this guide should be verified at IRS.gov and confirmed against current IRS Publication 1281 before advising clients. IRS rules and payment thresholds are subject to legislative and regulatory change. This guide is informational and does not constitute legal or tax advice.

What Backup Withholding Is and the Four Triggers Under IRC Section 3406

Backup withholding is a federal income tax withholding mechanism that applies to certain payments made to individuals and entities that would not otherwise be subject to withholding. The most common context is payments to independent contractors reported on Form 1099-NEC, but backup withholding can also apply to interest, dividends, rents, royalties, and other reportable payments. When backup withholding is required, the payer must hold back a percentage of each payment and remit it to the IRS, in the same way an employer withholds income tax from an employee's wages.

IRC Section 3406 sets out the conditions under which backup withholding is required. There are four triggers, and your client may encounter any or all of them depending on their contractor relationships and IRS notice history.

Trigger 1: Missing TIN

If a payee fails to furnish a taxpayer identification number (TIN) to the payer before payment is made, the payer is required to withhold backup withholding from any reportable payment. A TIN for an individual is their Social Security Number; for a business entity it is their Employer Identification Number. The fix is a completed Form W-9. Until the payee provides a valid TIN on a W-9, withholding is mandatory on every covered payment. This trigger is entirely preventable: collect the W-9 before the first payment, not after. The W-9 collection workflow section below covers exactly how to build that into your clients' contractor onboarding.

Trigger 2: Name and TIN Mismatch

If the IRS notifies the payer that the name and TIN combination on a filed information return does not match IRS records, backup withholding is required on future payments to that payee. This notification arrives via a CP2100 or CP2100A notice and triggers the B-notice workflow, which is covered in detail in its own sections below. The mismatch may occur because the payee provided an incorrect SSN, because the name on the W-9 does not match the name the IRS has on file for that SSN (a common issue after marriage or divorce), or because an entity used the wrong EIN. The IRS TIN Matching program (covered in Section 4) catches most of these mismatches before the 1099-NEC is filed.

Trigger 3: IRS B-Program Notification

The IRS B-program is the formal mechanism through which the IRS notifies payers of name/TIN mismatches. When the IRS sends a CP2100 or CP2100A, it is exercising its authority under IRC Section 3406(a)(1)(B) to put the payer on notice. Once that notice arrives, the payer has a specific, time-limited window to act: send the B-notice and W-9 to the affected payees, and, if the payees do not respond, begin backup withholding. The deadlines are discussed in detail in the B-notice sections of this guide.

Trigger 4: Underreporting Notification Under Section 3406(a)(1)(C)

If the IRS notifies the payer that a payee has underreported interest or dividends on past returns, and the IRS instructs the payer to begin withholding under IRC Section 3406(a)(1)(C), backup withholding is required. This trigger is less common in the contractor context and more relevant to financial institution payers. However, advisors to clients paying both contractors and passive income recipients (such as real estate investors paying interest to private lenders) should be aware it exists. When the IRS sends this type of notice, the payer must begin withholding and cannot stop until the IRS instructs otherwise. Verify the specific conditions and procedures for this trigger at IRS.gov.

The 24 Percent Backup Withholding Rate and Important Threshold Considerations

When backup withholding applies, the rate is 24 percent of each covered payment. The payer withholds that percentage from the gross payment, remits the withheld amount to the IRS, and pays the net amount to the payee. No exemptions or reductions apply once the withholding obligation is triggered; the payer must withhold on every covered payment to that payee until the condition causing the withholding is resolved (the payee provides a valid TIN, the B-notice situation is resolved, or the IRS withdraws its notification).

The payer must report all withheld backup withholding amounts on Form 945 (Annual Return of Withheld Federal Income Tax) and deposit the withheld amounts according to the applicable deposit schedule. Form 945 and deposit requirements are covered in detail in Section 8 of this guide.

See our OBBBA Practice Guide 2026 for how recently enacted legislation may affect 1099 reporting thresholds and the related withholding rules.

Prevention: Building a Proper W-9 Collection Workflow for Your Small Business Clients

The most effective backup withholding strategy is prevention. Most CP2100 notices and B-notice workflows are the downstream consequence of one failure: the payer did not collect a valid W-9 before the first payment. An independent contractor who has been paid for six months and then provides a bad TIN is a problem. An independent contractor who provides a completed W-9 on day one, before any payment clears, is not. The advisor's job is to build the W-9 collection step into the client's contractor onboarding so it happens by habit, not by exception.

Collect the W-9 before the first payment, without exception

The rule is simple: no payment should be made to an individual or entity that may be subject to 1099-NEC reporting until a completed Form W-9 is on file. In practice, this means building the W-9 request into the contractor onboarding sequence: include it in the new-vendor packet, in the contractor agreement, or in the platform invite if the client uses a payment or project management platform. The payer bears the compliance risk, not the contractor. If the contractor refuses or delays, the client must withhold backup withholding from every payment until the W-9 is received. Making this consequence explicit in the onboarding materials removes most contractor-side resistance.

What a valid W-9 must contain

A completed Form W-9 must include: (1) the payee's full legal name as it appears on their tax return or, for an entity, the legal entity name; (2) the payee's taxpayer identification number (SSN for individuals, EIN for entities); (3) the payee's address; (4) the payee's tax classification (individual, sole proprietor, LLC, corporation, partnership, or other entity type); and (5) the payee's signature and date certifying that the TIN provided is correct and that the payee is not subject to backup withholding. If any of these elements are missing or the form is undated, it is not a valid W-9 and cannot be relied upon to satisfy the payer's documentation obligation. Review your clients' W-9 files during the engagement and flag any incomplete forms for remediation.

Electronic W-9: using electronic collection platforms

Many small business clients use contractor management or payment platforms that support electronic W-9 collection. The IRS permits electronic W-9 collection and signatures, provided the electronic system meets the requirements in Treasury Regulation Section 31.3406(h)-3 and the final regulations issued thereunder. At a minimum, the system must verify the signer's identity, record the signature date, and make the completed W-9 available to the payer in a format that can be reproduced if the IRS requests it. Clients using accounting platforms such as QuickBooks, FreshBooks, or contractor payment platforms should confirm that the platform's W-9 module satisfies these requirements rather than assuming electronic acceptance is equivalent to valid W-9 collection. Verify current electronic W-9 standards at IRS.gov before recommending a specific platform workflow to clients.

What to do when a contractor provides an apparently incorrect TIN

A W-9 with a TIN that looks unusual (incorrect number of digits, formatted incorrectly, or one the client believes may be wrong) should be flagged rather than accepted at face value. The client should ask the contractor to re-submit with a corrected W-9 before processing the first payment. After the first payment, the corrective path requires either the IRS TIN Matching program (covered in the next section) or waiting for a CP2100 notice, both of which are slower and more disruptive. Establishing a front-end quality check on TIN format is inexpensive prevention.

IRS TIN Matching: The Free Tool Most Preparers Are Not Using

The IRS TIN Matching program is a free, pre-filing verification service available through IRS e-Services. It allows payers (and their authorized representatives) to verify that the name and TIN combination on a W-9 matches IRS records before filing any information return. If the name and TIN do not match, the payer can contact the payee for a corrected W-9 before the 1099-NEC is filed, which means the mismatch never becomes a CP2100 notice.

This is the single most underused backup withholding prevention tool available to preparers advising 1099-NEC filers. The program is free. The IRS built it specifically to reduce information return errors. A client with 50 contractors who runs TIN Matching before filing their 1099s can identify mismatches proactively, correct them before the February filing deadline, and avoid the entire CP2100 and B-notice workflow. Recommending TIN Matching as a standard step in the pre-1099 process is one of the most concrete, time-saving pieces of advice you can give a client who files more than a handful of 1099-NEC forms each year.

How to access TIN Matching through IRS e-Services

TIN Matching is available through the IRS e-Services portal at IRS.gov. Access requires an IRS e-Services account. For tax preparers, the same e-Services account used to access Transcript Delivery System (TDS), IVES, and e-file tools also provides access to TIN Matching. Payers (the client business) can also register directly for e-Services and use TIN Matching themselves; however, many small business clients will prefer to delegate this to their preparer as part of the pre-1099 preparation process.

TIN Matching supports two methods: interactive matching (enter a single name/TIN combination and receive an immediate response) and bulk matching (submit a file of up to 100,000 name/TIN combinations and receive results within 24 hours). For clients with large contractor rosters, the bulk option is the practical choice. Each combination returns one of four results: the name and TIN match IRS records; the name and TIN do not match; the TIN is not currently issued; or the TIN was issued but the account is inactive or the entity type does not match. Any result other than a match should prompt an outreach to the contractor for a corrected W-9 before the 1099 is filed.

Why TIN Matching should run before every 1099-NEC batch

A CP2100 notice typically arrives in the fall following the filing season in which the mismatched 1099s were submitted. By the time it arrives, several payments may have already been made without backup withholding, creating a potential failure-to-withhold exposure. Running TIN Matching in January, before the 1099s are filed, collapses that entire exposure window. The mismatch is identified before the filing, corrected before the deadline, and no CP2100 ever arrives. The client avoids the B-notice workflow entirely, and the preparer avoids having to manage a time-sensitive compliance process for a client who did not know the obligation existed.

Verify current TIN Matching availability, access procedures, and any usage limitations at IRS.gov before advising clients. The IRS may update program access requirements or batch file specifications.

Understanding the CP2100 and CP2100A: What These Notices Mean and What Triggers Them

If TIN Matching was not run and mismatched or missing TINs were filed on 1099-NEC forms (or other reportable information returns), the IRS will issue a CP2100 or CP2100A notice to the payer. These notices are the IRS's formal notification that the filed information returns contained one or more name/TIN combinations that do not match IRS records. Receiving one of these notices starts a compliance clock: the payer has a specific, short window to act.

What triggers a CP2100 or CP2100A

The IRS generates CP2100 and CP2100A notices through a matching process run against filed information returns. The notice is triggered when a 1099-NEC (or other covered information return) contains a payee TIN that does not match the name/TIN combination in IRS records, or that is missing entirely. The mismatch may reflect an incorrect SSN, an EIN used where an SSN was expected (or vice versa), a name formatted differently than IRS records show (married name versus maiden name, a legal entity name versus a trade name), or a TIN that has never been issued.

CP2100 versus CP2100A: volume threshold

The IRS uses two versions of this notice based on the number of error returns included:

• CP2100: Issued to payers who filed 50 or more information returns containing missing or incorrect TINs. Because the volume is higher, the IRS sends CP2100 notices by certified mail to put the payer on formal notice of the larger filing error profile.
• CP2100A: Issued to payers who filed fewer than 50 information returns with missing or incorrect TINs. The notice format is similar, but the delivery method may differ. Both notices trigger the same B-notice obligations; the distinction is administrative, not substantive.

What the notice tells you and how to read it

The CP2100 and CP2100A notice will identify: the payer (your client), the tax year for which the information returns were filed, and a list of the specific payees whose name/TIN combinations generated a mismatch or were missing. For each listed payee, the notice shows the name and TIN as they appeared on the filed information return and indicates whether the problem is a missing TIN, an incorrect TIN, or a name/TIN combination that does not match IRS records. This list is the working document for the B-notice workflow: every payee on the list requires a First B-Notice, and the 15-business-day deadline starts from the date the payer receives the CP2100 or CP2100A. Verify current notice format and reading guidance in IRS Publication 1281.

First B-Notice Workflow: The 15-Business-Day Deadline That Cannot Slip

The First B-Notice is the payer's formal written notification to the payee that their name and TIN combination on file does not match IRS records. The notice must follow a specific format prescribed by the IRS. The payer cannot substitute their own letter or paraphrase the IRS language; the notice must use the exact language and format specified in IRS Publication 1281. Sending a non-compliant notice does not satisfy the obligation and does not start the payee's response clock. Confirm the current required First B-Notice language and format in IRS Publication 1281 before drafting anything.

What to include in the First B-Notice mailing

Each First B-Notice mailing to an affected payee must include: (1) the IRS-prescribed First B-Notice text, completed with the payer's name, address, and contact information and the payee's identifying information; and (2) a blank Form W-9 for the payee to complete and return. Per current IRS Publication 1281 guidance, the envelope containing the First B-Notice must bear the required legend on the outside indicating this is an important tax document requiring immediate attention. Verify the required envelope language in the current version of IRS Publication 1281.

What happens if the payee ignores the First B-Notice

If the payee does not return a completed W-9 within 30 days of the expiration of the 15-business-day mailing period, the payer must begin backup withholding on all subsequent payments to that payee. Once withholding starts, it continues until one of two things happens: the payee provides a valid TIN on a completed W-9, or the IRS instructs the payer to stop withholding. There is no discretion here. If the payee is unresponsive, the client withholds. Period. Clients who resist this because they do not want to complicate their contractor relationship should understand that the alternative is a failure-to-withhold penalty assessed against them personally as the payer.

What happens when the payee returns a W-9 after a First B-Notice

If the payee returns a completed W-9 within the response window, the payer may stop withholding (if it has already begun) and is not required to verify the new TIN again before the next 1099-NEC filing cycle. However, the payer should update their records with the corrected name/TIN combination. If the same payee appears on a subsequent CP2100 with the new TIN, the Second B-Notice rules apply. Running TIN Matching on the corrected W-9 before the next 1099 filing is a practical safeguard that costs nothing and confirms the new TIN is valid before it becomes next year's problem.

Second B-Notice Workflow: Higher Documentation Standard, Same Urgency

A Second B-Notice is required when the same payee appears on a second CP2100 or CP2100A notice within a three-year period. The three-year window is measured from the date of the first CP2100 or CP2100A that listed that payee, not from the date the First B-Notice was sent. Advisors managing clients with recurring contractor relationships should track this three-year window by payee, because the documentation requirements for a Second B-Notice are substantially different from the First, and a client who sends a First B-Notice when a Second B-Notice is required has not satisfied the obligation.

The key difference: a new W-9 is not enough

When a First B-Notice is sent, the payee can satisfy the obligation by returning a completed Form W-9 certifying their name and TIN. A Second B-Notice requires more. The payee must provide either:

• A copy of their Social Security card (for payees who are individuals using a Social Security Number), confirming the exact name and SSN combination the IRS has on file.
• An IRS Letter 147C (for payees using an Employer Identification Number), which is an IRS-issued letter confirming the entity's name and EIN as they appear in IRS records. A Letter 147C can be obtained by calling the IRS Business and Specialty Tax Line. Payees requesting a 147C should be prepared to provide their EIN and answer IRS authentication questions.

A payee who responds to a Second B-Notice with only a new W-9 has not satisfied the requirement. The payer must communicate this to the payee and request the correct documentation. Until the Social Security card or Letter 147C is received, backup withholding must continue. Clients who have reached a Second B-Notice situation with a payee should understand that the IRS is treating this as a confirmed, repeated mismatch: the documentation bar is higher because one prior attempt to resolve it did not succeed.

Sending the Second B-Notice: same timing, stricter content

The Second B-Notice mailing follows the same 15-business-day deadline from receipt of the CP2100 and must use the IRS-prescribed Second B-Notice language and format from IRS Publication 1281. The Second B-Notice text differs from the First because it specifies the higher documentation requirement (Social Security card or Letter 147C) and explains why a W-9 alone is not sufficient. Confirm the current required Second B-Notice language and format in the current version of IRS Publication 1281 before mailing. The consequences of a deficient Second B-Notice are the same as a deficient First B-Notice: the obligation has not been met and the payer's penalty exposure runs.

Form 945: Reporting and Depositing Backup Withholding on Non-Payroll Payments

Backup withholding on non-payroll payments (contractor payments, 1099-NEC reported amounts, and similar payments) is not reported on Form 941 (the quarterly payroll tax return). It is reported separately on Form 945, Annual Return of Withheld Federal Income Tax. Form 945 is an annual return covering the full calendar year, not a quarterly return. Every payer who withholds backup withholding during the year must file Form 945 for that year, regardless of the total amount withheld.

Annual filing deadline

Form 945 for a given calendar year is due by January 31 of the following year. For example, backup withholding withheld during calendar year 2025 is reported on Form 945 due January 31, 2026. If all withheld taxes were deposited on time throughout the year, the IRS allows an extended deadline of February 10. Verify the current deadline and any applicable extensions at IRS.gov and in the current Form 945 instructions, as due dates may shift for weekends and holidays or may be adjusted by IRS guidance.

Deposit requirements: check the current instructions

Form 945 filers use a deposit schedule (annual or monthly) based on a lookback period, similar in structure to the payroll deposit rules for Form 941 but applied to the non-payroll withholding context. Payers who withheld below the threshold for the lookback period may be able to remit with the return rather than making separate deposits. Payers above that threshold must deposit on the monthly schedule.

The lookback period for Form 945 is the second calendar year preceding the current filing year. For a client determining their 2025 deposit schedule, the lookback period is calendar year 2023. The current deposit thresholds, the specific deposit deadlines for monthly depositors, and the rules for new payers (who have no lookback history) are all set out in the current Form 945 instructions. Direct clients to those instructions and verify annually, because the thresholds may change. See also the payroll tax guide for the parallel deposit framework under Form 941, which shares structural similarities with the Form 945 deposit rules.

What Form 945 reports

Form 945 reports the total backup withholding withheld during the year from non-payroll payments. This includes backup withholding on contractor payments (1099-NEC), interest (1099-INT), dividends (1099-DIV), rents and royalties (1099-MISC), and any other covered payment from which backup withholding was required. It does not include withholding on wages (reported on Form 941) or withholding on pension distributions (reported on Form 945 but under different IRC provisions). A client who withheld on contractor payments and also made other reportable payments subject to backup withholding will include both on the same Form 945. Verify the complete list of covered payment types in the current Form 945 instructions.

Client Advisory Workflow: How to Manage the CP2100 Response Timeline as the Preparer

When a client brings you a CP2100 or CP2100A, your job is to manage a process, not just give advice. The client does not know what the notice means, does not know what 15 business days looks like on a calendar, and does not know that a new W-9 alone will not satisfy a Second B-Notice. Your role is to run the workflow. Here is how to structure it from the moment the notice arrives.

Documents to collect from the client before starting

Before you can run the B-notice workflow, gather the following from the client: (1) the CP2100 or CP2100A notice itself, including the envelope to document the received date; (2) the original W-9s on file for every payee listed on the notice; (3) the 1099-NEC forms filed for those payees, to confirm the name and TIN combination that appeared on the filed return; (4) records of any prior CP2100 notices that listed the same payees, to determine whether a First or Second B-Notice applies; and (5) a payment ledger or accounts payable record for the current year showing amounts paid to each affected payee, so you can determine whether backup withholding is already required and at what amount. If the client cannot locate a prior CP2100 notice, check with the IRS transcript for the payer account; the IRS record of notices issued will show whether a prior CP2100 was sent for that payer.

Penalties for Failing to Backup Withhold or Respond to B-Notices

A client who ignores a CP2100, fails to send B-notices on time, or fails to begin backup withholding when required faces penalties from two directions: failure-to-withhold penalties under IRC Section 3406, and information return penalties for the original TIN mismatch filings. Understanding both gives advisors the framing needed to communicate the actual cost of non-compliance to clients who may not understand why the B-notice workflow matters.

Failure-to-withhold penalties under IRC Section 3406

When a payer is required to withhold backup withholding and fails to do so, the payer is liable for the full amount of the withholding that should have been deducted from the payment, plus interest. This is not a penalty in the traditional sense: the payer owes the IRS the tax that should have been withheld from the payee's payments, regardless of whether the payee ultimately pays the tax themselves. The payer cannot offset this liability by showing that the payee reported and paid the income on their own tax return. If the payer failed to withhold when required, the payer's liability stands.

In addition to the withheld tax liability itself, the IRS may also assess a failure-to-deposit penalty under IRC Section 6656 if the payer withheld backup withholding but did not deposit it on the required schedule. The failure-to-deposit penalty rates range based on how late the deposit is. Verify current Section 6656 rates and any applicable safe harbor provisions at IRS.gov before advising clients on deposit penalty exposure.

Information return penalties for TIN mismatches under IRC Sections 6721 and 6722

The original failure that led to the CP2100, filing a 1099-NEC with a missing or incorrect TIN, is itself a separate penalty event under the information return penalty rules. IRC Section 6721 imposes penalties on payers who file information returns with incorrect or missing TINs. IRC Section 6722 imposes penalties on payers who furnish payee statements (the copy of the 1099 sent to the contractor) with incorrect or missing TINs.

The penalty amounts under Sections 6721 and 6722 are adjusted periodically for inflation and depend on how quickly the error is corrected: lower penalties apply if the payer corrects the error within a short period after the filing deadline, higher penalties apply for corrections made later, and the maximum penalty applies when no correction is made. Annual penalty caps also apply per filer. Verify current penalty amounts, correction window deadlines, and annual caps at IRS.gov before advising clients, as the IRS adjusts these figures by revenue procedure periodically.

A key exception: the reasonable cause defense is available under both Sections 6721 and 6722. If the payer solicited the TIN in good faith through the W-9 process, made reasonable attempts to obtain correct information, and the mismatch was the result of incorrect information provided by the payee, the payer may qualify for relief. This is one of the reasons the W-9 collection workflow and documentation matter: a client who followed the proper W-9 solicitation steps and ran TIN Matching can demonstrate good faith; a client who never collected a W-9 cannot. Document the solicitation effort, including the date the W-9 was first requested, the date it was received, and any corrective solicitations made after a mismatch was identified.

Related Guides

• IRC 6041: Form 1099 Reporting Obligation and OBBBA $2,000 Threshold: IRC 6041 is the statute that requires payors to file the 1099 forms at the center of every backup withholding workflow; understanding the IRC 6041 payor classification rules and the OBBBA $2,000 threshold is required before the backup withholding compliance checklist in this guide can be applied correctly; practitioners who use this backup withholding guide should also read the IRC 6041 guide for the underlying filing obligation framework.
• IRC 6050W: Form 1099-K Payment Card and Third-Party Network Reporting: backup withholding applies to third-party network transactions under IRC 6050W when the payee fails to furnish a TIN or when the IRS notifies the PSE of a name/TIN mismatch; Form 945 deposits apply to the amounts withheld from 1099-K-covered payments on the same schedule as other backup withholding; practitioners advising clients who receive TIN-mismatch CP2100 notices for 1099-K transactions should use this backup withholding guide alongside the IRC 6050W guide.
• IRC 6721-6724 information return penalties: a payor who ignores CP2100 B Notices and fails to file or furnish correct 1099 forms faces IRC 6721 failure-to-file and IRC 6722 failure-to-furnish penalties in addition to backup withholding liability; the IRC 6723 other-requirement penalty and the IRC 6724 reasonable cause waiver and intentional disregard rules govern the same TIN-solicitation failures that drive backup withholding exposure, so practitioners handling B Notice cases should read the information return penalty guide alongside this one.

Frequently Asked Questions