IRS Form 1099-K Threshold Changes: What AP Teams and Payment Platforms Need to Know
New rules around Form 1099-K are shaking up the way payment platforms and businesses handle reporting obligations in the United States. If you're a merchant on platforms like PayPal, Venmo, or any third-party payment processor, you may now be subject to lower reporting thresholds — potentially creating new tax compliance challenges.
What Changed — and Why It Matters
For years, the Form 1099-K threshold sat at $20,000 in transactions and more than 200 payments in a calendar year. The vast majority of small sellers and freelancers never hit that bar.
That's changing. The IRS is moving to a $600 threshold with no minimum transaction count — meaning a single sale of $600 or more can trigger a reporting requirement. The transition has been phased:
| Tax Year | Threshold |
|---|---|
| Prior to 2023 | $20,000 + 200 transactions |
| 2023 (transitional relief) | $20,000 (IRS delayed enforcement) |
| 2024 (transitional relief) | $5,000 |
| 2025 and beyond | $600 (expected full enforcement) |
Why the delays? The IRS has acknowledged implementation complexity — particularly for payment platforms that need to collect and validate TINs at scale. Delays don't mean the rule goes away. They mean you have time to prepare.
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, Zelle (business accounts)
- Gig platforms: Uber, DoorDash, Etsy, eBay, Airbnb
- Freelance marketplaces: Upwork, Fiverr, Toptal
- Any business paying vendors or contractors through digital channels
If your platform processes payments or your AP team pays vendors electronically, this rule touches your workflow.
The Compliance Problem Hiding Inside the Threshold Change
The lower threshold doesn't just mean more 1099-Ks get filed. It means more payees need a valid TIN on file before you pay them — or you're required to apply 24% backup withholding.
That creates three immediate problems for AP teams and payment platforms:
1. TIN gaps surface at scale At the $20,000 threshold, only your highest-volume payees triggered a 1099-K. At $600, the population explodes — including occasional vendors, one-time contractors, and casual sellers who never provided a W-9.
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 $310 per incorrect return, up to $3.78 million per year.
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 to confirm the name/TIN combination is correct before you file.
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.
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 threshold changes demand:
- 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 to find the correct one
- Audit Trails — every validation, outreach attempt, and correction logged with timestamps for IRS documentation
Start a free trial or request a risk assessment to see where your current vendor file stands.
Bottom Line
The 1099-K threshold change is not a future problem. Payment platforms and AP teams that wait until Q4 to collect W-9s and validate TINs will face the same year-end scramble — just with a much larger payee population. 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.