IRS Form 1099-K Threshold Changes: What AP Teams and Payment Platforms Need to Know

The One Big Beautiful Bill Act repealed the $600 1099-K threshold and restored $20,000 and 200 transactions, retroactive to tax year 2022. If you run a payment platform or pay vendors through one, here is what still applies and how it affects W-9 collection.

Updated October 28, 2026.

What Changed, and Why It Matters

For years, the Form 1099-K threshold for third-party settlement organizations sat at more than $20,000 in gross payments and more than 200 transactions in a calendar year. The vast majority of small sellers and freelancers never hit that bar.

The American Rescue Plan Act of 2021 lowered that threshold to $600 with no minimum transaction count, and the IRS delayed enforcement three times, announcing transitional thresholds of $5,000 for 2024 and $2,500 for 2025. Then the One Big Beautiful Bill Act (Public Law 119-21, signed July 4, 2025) repealed the $600 rule before it ever took full effect and restored the original threshold retroactively to tax year 2022. The threshold is now $20,000 and 200 transactions for every year:

Tax Year Threshold
2022 and earlier $20,000 and 200 transactions
2023 $20,000 and 200 transactions (the IRS had delayed the $600 rule)
2024 $20,000 and 200 transactions (the IRS transitional $5,000 figure no longer applies)
2025 onward $20,000 and 200 transactions (restored by the 2025 law)

What about the $600, $5,000, and $2,500 figures? They no longer apply to any year. The IRS transitional thresholds were administrative relief for a rule Congress has since repealed. Payment card transactions, however, are still reported with no threshold at all.

Key takeaways

  • The 1099-K threshold is more than $20,000 and more than 200 transactions for every year, including 2022 to 2025.
  • Payment card transactions are reportable with no threshold, and several states set lower 1099-K thresholds of their own.
  • The threshold decides who gets a form, not who needs a TIN: every payee needs a validated TIN before the first payment or 24% backup withholding applies.
  • Payments you make by check, ACH or wire are still yours to report on 1099-NEC or 1099-MISC at $600 for 2025 payments and $2,000 for payments made in 2026 and later.

Who Is Affected

The rule applies broadly to third-party settlement organizations (TPSOs): any platform that facilitates payments between buyers and sellers. That includes:

  • Payment apps: PayPal, Venmo, Cash App (business accounts)
  • Gig platforms: Uber, DoorDash, Etsy, eBay, Airbnb
  • Freelance marketplaces: Upwork, Fiverr, Toptal
  • Any business paying vendors or contractors through digital channels

Bank-to-bank transfer networks that only move money between accounts do not settle payments for goods and services and do not issue 1099-Ks, so a contractor paid that way is still reported by you, not by the network.

If your platform processes payments or your AP team pays vendors electronically, this rule touches your workflow. The table below shows who files what for the common ways a vendor gets paid:

How the vendor is paid Who files Form Threshold
Credit or debit card The card processor 1099-K None
Third-party network (PayPal, marketplace payouts) The platform (TPSO) 1099-K More than $20,000 and more than 200 transactions
Check, ACH or wire for services You, the payer 1099-NEC $600 for 2025 payments; $2,000 for payments made in 2026 and later
Check, ACH or wire for rent, prizes or other income You, the payer 1099-MISC $600 for 2025 payments; $2,000 for payments made in 2026 and later
Gross proceeds paid to an attorney You, the payer 1099-MISC box 10 $600

A payment made by card or through a third-party network is reported by the processor on 1099-K, so you do not also report it on 1099-NEC or 1099-MISC. Everything you pay by check, ACH or wire stays on your own returns.


The Compliance Problem Hiding Inside the Threshold

The restored threshold means fewer 1099-Ks get filed. It does not mean fewer payees need a valid TIN. Every payee needs a valid TIN on file before you pay them, or you're required to apply 24% backup withholding, whether or not they ever reach the reporting threshold.

That leaves three live problems for AP teams and payment platforms:

1. TIN gaps don't shrink with the threshold You can't know in March which sellers will cross $20,000 and 200 transactions by December, so valid tax information has to be on file for all of them at onboarding. Payment card transactions are reportable with no threshold at all, and several states set their own, lower 1099-K thresholds, so the population you must report on is larger than the federal TPSO rule alone suggests.

2. Mismatch risk increases More payees means more opportunities for TIN/name mismatches. The IRS won't tell you the correct TIN when they flag a mismatch: they just tell you it's wrong. If you can't resolve it, you're on the hook for backup withholding on every future payment to that vendor.

3. B-Notice and 972CG exposure grows Mismatches caught after filing trigger CP2100 notices and eventual B-Notice obligations. At scale, unresolved mismatches can accumulate into IRS Notice 972CG, a penalty notice that can reach $340 per incorrect return for returns due in 2026, up to $4,098,500 per year for large filers ($1,366,000 for filers with gross receipts of $5 million or less). The full tier table by year is on the IRS 1099 penalties page.

The notices lag the filing. A CP2100 arrives 12 to 18 months after you file, and a 972CG that lands in fall 2026 covers tax year 2024 returns that were due in 2025. A mismatch you leave in the file today is a notice in 2027 or 2028.

What Good Compliance Looks Like Before Year-End

The goal is to have a validated TIN on file for every payee before you file, not after the IRS flags a problem.

Step 1: Collect W-9s at onboarding Every new vendor or contractor should complete a W-9 before their first payment. Build this into your onboarding workflow, not your year-end scramble.

Step 2: Validate TINs against IRS records A W-9 on file is not the same as a validated TIN. Run every TIN through IRS TIN Matching, the only IRS-run check of a name and TIN pair before you file, to confirm the combination is correct.

Step 3: Resolve mismatches before filing When IRS matching returns a mismatch, don't wait for a B-Notice to act. Cross-reference your records, reach out to the vendor for a corrected W-9, and re-validate. If a CP2100 does arrive, send the First B-Notice within 15 business days of the notice date or receipt (whichever is later), give the payee 30 business days, and begin backup withholding on payments after that.

Step 4: Document everything Reasonable cause is your best defense against 972CG penalties. Documented outreach (timestamped emails, W-9 requests, validation logs) shows the IRS you acted in good faith.


How TIN Comply Helps

TIN Comply is built specifically for the compliance workflow that 1099-K reporting demands:

  • IRS TIN Matching: validate TIN/name combinations against IRS records in bulk or via API
  • W-9 Collection: automated vendor outreach, digital W-9 collection, and instant TIN validation in one workflow
  • EIN Discovery: when a vendor gives you a bad TIN, cross-reference millions of business records for ranked candidates and the legal name on record for the EIN
  • Audit Trails: every validation, outreach attempt, and correction logged with timestamps and user attribution for IRS documentation

Start a free trial or request a risk assessment to see where your current vendor file stands.


Bottom Line

The restored 1099-K threshold shrinks the filing population, not the compliance work. Payment platforms and AP teams that wait until Q4 to collect W-9s and validate TINs will face the same year-end scramble, with state filings, card transactions, and backup withholding still in scope for payees below the federal threshold. The time to build a clean, validated vendor file is before the payments go out, not after the IRS notices arrive.


This article is for informational purposes only and does not constitute legal or tax advice. Consult a qualified tax professional for guidance specific to your organization.