What Is Backup Withholding? The 24% Rule Every AP Team Must Know

Backup withholding is the IRS mechanism that forces payers to withhold a flat 24% from payments to US vendors when the vendor has failed to provide a valid taxpayer identification number (TIN) or when the IRS has notified the payer that the TIN on file is incorrect. The 24% withholding is remitted directly to the IRS as a credit against the vendor's eventual tax liability.

The rule exists because the US income tax system relies heavily on 1099 reporting to match income on payer returns against income on payee returns. When a vendor's TIN is missing or wrong, that matching breaks down — the vendor can effectively receive payments without the IRS being able to track them. Backup withholding closes that gap by collecting tax at source when reporting cannot be relied on.

When Backup Withholding Is Required

The IRS specifies four circumstances that trigger backup withholding under IRC §3406. Each one applies regardless of the vendor's protests, regardless of time pressure, and regardless of existing relationship — if any trigger is present, the 24% must be withheld and remitted.

What the Payer's Liability Looks Like

If backup withholding is required and the payer fails to withhold, the payer — not the vendor — is generally liable for the 24% that should have been withheld. The IRS can collect it from the payer through assessment, plus interest, plus possible penalties. A company that paid $200,000 to a vendor whose TIN turned out to be invalid, and failed to backup-withhold, is looking at a roughly $48,000 exposure before penalties.

The mechanical basis is 26 CFR §31.3406(a)-1 — the IRS regulations that treat the payer as the withholding agent with full liability for withholding taxes it failed to collect. There is limited relief available if the vendor eventually pays their own tax, but the administrative process to obtain that relief is complex and not a good-faith defense.

When Backup Withholding Does Not Apply

Several categories of payments are exempt from backup withholding regardless of TIN status. Understanding the exemptions helps scope the problem correctly — it is a payment-type-specific rule, not a vendor-specific rule.

The TIN Matching Defense

The IRS TIN Matching Program is a free service that lets payers submit a vendor's name and TIN and receive a pass/fail result against the IRS database. A pass result creates a safe harbor — the payer has verified the TIN is correct and is not required to backup-withhold. A fail result is notice that backup withholding should be considered.

Best practice is to run TIN matching on every new US vendor before the first payment clears, and to re-verify periodically (annually is the common cadence). The matching process is automated, instant, and leaves a logged record. For an AP operation processing hundreds of vendors, TIN matching is the single most important fraud and backup-withholding defense.

The B Notice Process

If a 1099 filed by a payer contains a TIN that doesn't match the IRS database, the IRS sends the payer a 'B notice' (CP-2100 or CP-2100A). The B notice identifies the vendor whose TIN failed and starts a compliance clock. The payer must:

Remitting Backup Withholding: Form 945

When backup withholding occurs, the withheld amount must be remitted to the IRS through Form 945 (Annual Return of Withheld Federal Income Tax). Deposit timing depends on the payer's deposit schedule under IRS rules — monthly for smaller total withholders, semi-weekly for larger ones.

The payer also must report the backup withholding on the vendor's 1099 form at year end, in the 'Federal income tax withheld' box. The vendor takes that amount as a credit on their own tax return, offsetting their liability. From the vendor's perspective, backup withholding is not additional tax — it is a prepayment. From the payer's perspective, it is a compliance burden and potential liability if managed incorrectly.

Building a Backup Withholding Prevention Program

A well-run AP operation prevents backup withholding entirely by building three automated gates into vendor onboarding and payment processing:

These gates are simple to state and hard to run manually. The AP analyst under time pressure will not remember that a specific vendor needs a W-9 before their check can cut. The system can. This is another case where AP automation is a compliance control, not just an efficiency gain.

Bottom Line

Backup withholding is one of the cleanest examples of how a small administrative failure scales into a large tax exposure. A missing W-9 for a $100,000-per-year vendor is a $24,000 annual liability if the IRS determines backup withholding was required. A consistent onboarding discipline eliminates the exposure entirely. The 24% rule is not complicated; the discipline required to never trigger it is. That's where automation earns its keep.