Backup Withholding for 2026: When the 24% Rate Triggers (IRC §3406)

What is backup withholding?

Backup withholding is a federal tax mechanism under IRC §3406 that requires a payer to withhold 24% of gross payments to a vendor and remit that amount to the IRS. It triggers in three situations: the vendor refused to provide a W-9 and cumulative payments have crossed $2,000; the vendor submitted a TIN that didn't match IRS records and the 30-day B-Notice window expired without a corrected W-9; or the IRS issued a Notice 668-W directing withholding against that vendor. The rate stays flat at 24% of gross, regardless of the payment type or vendor's tax situation. The payer is liable if withholding isn't done correctly.

Key Takeaways

• The backup withholding rate is 24% of gross - applied to the full payment amount, not the net after any fees or deductions
• Three triggers under §3406 - vendor refuses W-9 past the $2,000 cumulative threshold, B-Notice TIN mismatch unresolved after 30 days, or IRS Notice 668-W levy
• The liability lands on the payer - if you skip backup withholding and the IRS audits, the unpaid withholding is your firm's problem, not the vendor's
• Form 945 is due January 31 - separate from 1099-NEC filings; quarterly EFTPS deposits required when withheld amounts exceed $2,500 in any quarter
• A corrected W-9 in writing is the only way to stop it - verbal confirmation doesn't count; you need a signed, corrected W-9 on file before releasing payments without withholding
• Most bookkeeping firms never see this in practice - a clean upstream W-9 collection workflow prevents all three triggers before they can fire

The rest of this article covers each trigger in detail, the remittance mechanics, and why backup withholding is mostly a theoretical risk for firms running the 2026 1099 filing workflow correctly.

The Three Triggers Under IRC §3406

Trigger 1: Vendor Refuses to Provide a W-9 (and Cumulative Payments Hit $2,000)

This is the most common scenario, and it's still rare for firms with a vendor-onboarding process.

Under the OBBBA-aligned §3406 proposed regulations, the backup withholding trigger now mirrors the new §6041(a) reporting threshold. Once cumulative payments to a vendor reach $2,000 in a calendar year, the W-9 requirement becomes mandatory. If the vendor hasn't provided a valid W-9 by the time that $2,000 threshold is crossed, backup withholding at 24% starts on the next payment.

A few mechanics to get right:

Counting toward $2,000 uses cumulative payments, not single transactions. Pay a freelancer $500 in February, $800 in May, and $900 in August. The August payment crosses $2,000 cumulative. If you still don't have a W-9 on file, the August payment is subject to 24% withholding on the gross amount.

Reimbursements don't count. If you pass through $400 in travel expenses as part of a $1,200 payment, only the $800 service component counts toward the threshold. Keep reimbursements documented and separated in your vendor records.

The clock starts at the first payment, not at onboarding. Collect the W-9 before the first check goes out. Chasing it after three payments is harder and creates a documentation gap.

The fix is covered in detail in the W-9 request workflow guide. Short version: make W-9 collection a hard gate before any payment is released. Payment holds are uncomfortable for a day; backup withholding errors are uncomfortable for months.

Trigger 2: TIN Mismatch After the B-Notice Window

This trigger starts with a CP2100 or CP2100A notice from the IRS, which arrives the following spring after you've filed 1099s with mismatched TINs.

The notice gives you a 30-day window to send the vendor a written "B-Notice" solicitation requesting a corrected W-9. This isn't optional. The IRS specifically requires the written solicitation, not an email or phone call.

If 30 days pass and the vendor doesn't respond with a corrected W-9, backup withholding at 24% starts on the next payment to that vendor.

What causes TIN mismatches in the first place:

• Vendor wrote their SSN where their EIN should go, or vice versa
• Single-member LLC filed under the owner's personal SSN, but the entity EIN was entered on the W-9
• Business name on the W-9 doesn't match the name the IRS has on file (common after business name changes, mergers, or marriages)
• Vendor copied an old W-9 with a TIN that's since been deactivated or reassigned

The prevention step is IRS TIN matching, which lets you submit vendor TIN/name combinations in December and get match codes back before the January filing batch goes out. Running TIN matching in December converts a spring CP2100 surprise into a routine December correction request. See the TIN matching guide for the e-Services registration and bulk upload process.

If you do receive a B-Notice and the vendor corrects their W-9 within the 30-day window, withholding doesn't start. Document the date of the notice, the date you sent the solicitation, and the date the corrected W-9 came back. That paper trail matters if the IRS questions your compliance later.

Trigger 3: IRS Notice 668-W (Federal Tax Levy)

This trigger is different in character from the first two. It doesn't come from a documentation gap on the payer's side.

A Notice 668-W is a federal levy. The IRS sends it directly to you, the payer, instructing you to withhold a portion of payments owed to a specific vendor. The levy amount and timing instructions come in the notice itself.

Compliance is mandatory and immediate. You have no discretion here. If you release a payment to a levied vendor without following the withholding instructions, the liability falls to you.

If you receive a Notice 668-W, loop in your client immediately, follow the withholding schedule in the notice exactly, and release payments only to the IRS-directed split until you receive a release notice (Notice 668-D). Most bookkeepers see zero 668-W notices in a year of client work, but when one arrives, it's not optional.

Withholding Mechanics: Gross, Not Net

The withholding rate is 24% of the gross payment amount. This is a source of errors when bookkeepers or clients try to back-calculate.

Example: Vendor invoice is $3,000. Backup withholding applies.

• Correct: Withhold $720 (24% of $3,000). Vendor receives $2,280.
• Incorrect: Net out a $200 platform fee first, then withhold 24% of $2,800. This underfunds the withholding by $48 per payment and creates a liability.

Don't deduct fees, processing charges, or reimbursements from the gross before calculating withholding. The IRS takes 24% of what was agreed to in the invoice, not what arrived after your bank took a cut.

Remittance: Form 945 and EFTPS Deposits

Backup withholding goes to the IRS through Form 945 (Annual Return of Withheld Federal Income Tax), not through payroll forms or the 1099-NEC process.

Form 945 due date: January 31 of the year following the withholding. For 2026 withholding, that's January 31, 2027. This is the same due date as 1099-NEC recipient copies, but it's a separate filing. Don't confuse them.

EFTPS deposit schedule: If withheld amounts exceed $2,500 in any calendar quarter, you must deposit through EFTPS on a quarterly basis rather than waiting for the January 31 annual return. The EFTPS deposit due dates align with standard federal tax deposit rules.

• Q1 (Jan-Mar): Deposit by April 30
• Q2 (Apr-Jun): Deposit by July 31
• Q3 (Jul-Sep): Deposit by October 31
• Q4 (Oct-Dec): Deposit with or before the Form 945 due date (January 31)

For most small bookkeeping practices, the withholding amounts in any given quarter won't cross $2,500 because backup withholding events are rare. But track the running total by quarter so you don't miss a deposit threshold mid-year.

Stopping Backup Withholding

Once backup withholding starts, the only way to stop it is a corrected W-9 from the vendor, submitted in writing. Verbal confirmation and emails promising "I'll send it" don't meet the standard.

Steps: Send the vendor a written request and keep it on file. Withhold on all payments until the corrected form arrives. When it does, verify the TIN through the IRS TIN matching program or cross-check against the CP2100 data. Stop withholding on the next payment after you have the verified, corrected W-9 in hand.

Backup Withholding vs. the 1099 Filing Process

Backup withholding is a separate obligation from the 1099-NEC and 1099-MISC filing deadlines. They interact, but they don't merge.

When a vendor is subject to backup withholding, you still issue a 1099 at year-end. The form reflects the total gross payment; Box 4 (Federal income tax withheld) shows the amount remitted to the IRS. The vendor credits Box 4 against their tax liability on their return.

For 1099 corrections: if you discover the withholding was triggered by a database entry error on your side and the vendor's TIN was correct, the Box 4 amount stays because that money went to the IRS. The correction adjusts the payment totals, not the withholding line.

The gross-payment withholding logic applies regardless of whether you're filing 1099-NEC or 1099-MISC.

The Real-World Frequency: Close to Zero for Organized Firms

Backup withholding almost never fires for firms running a disciplined vendor-onboarding process. The triggers exist because some subset of payers release payments without collecting W-9s and then scramble when the IRS sends notices.

Collect the W-9 before the first payment. Run TIN matching in December. File accurate 1099s in January. Backup withholding never enters the picture.

The one scenario that stays live even for organized firms is the Notice 668-W levy, which arrives because of the vendor's own tax situation, not yours. Know the response process and move quickly when it shows up.

How Growthy Handles This

Growthy categorizes automatically against your vendor records. When a vendor payment hits a ledger entry, the system flags it against the 1099-eligible vendor list. Built by a CPA firm partner who still reconciles books for real clients, Growthy hits 85% accuracy on first import and 90%+ on returning books after 30 days.

The W-9 status gate, vendor TIN tracking, and Box 4 withholding amounts are part of the workflow, not a separate checklist to manage manually. See the full feature set for how vendor compliance integrates with the categorization layer.

If you want to run the 2026 1099 filing season without backup withholding surprises, start with Growthy.

Frequently Asked Questions

Who is liable if backup withholding isn't done: the payer or the vendor? The payer. Under IRC §3406, the obligation to withhold and remit belongs to the party making the payment. If you release a payment without withholding when backup withholding applies, the IRS can assess the unpaid withholding against you, plus interest and penalties.

Does backup withholding apply to payments made through Stripe or PayPal? No. Payments through third-party settlement organizations above the 1099-K threshold are reported by the processor, not by you. Your §3406 backup withholding obligation applies to direct payments you make to vendors, not to payments routed through a processor that issues its own 1099-K.

Can I use withheld amounts to offset what I owe to the vendor? No. The withheld amount goes to the IRS. The vendor's invoice remains fully owed; you split the payment between the vendor and the IRS.

What if a vendor provides a W-9 but the TIN still doesn't match IRS records? Start the B-Notice process. Send the vendor a written solicitation within 15 business days of receiving the CP2100. The vendor has 30 days to provide a corrected W-9. If they don't, backup withholding starts on the next payment. Running IRS TIN matching in December catches these mismatches before the CP2100 arrives.

Is backup withholding connected to the glossary of 1099 terms? Yes. The bookkeeping glossary covers B-Notice, CP2100, TIN, and related compliance terms that come up in backup withholding scenarios.

Tax figures verified against IRS Notice 2025-62, IRS 1099-K FAQs, §3406 proposed regulations, and IRS Pub 1099 General Instructions on 2026-05-14.