Quick answer: The OBBBA, signed July 4, 2025, permanently restored the TPSO Form 1099-K threshold to more than $20,000 and more than 200 transactions. But a higher threshold does not simplify compliance. Backup withholding, payment card rules, per-platform aggregation, and state thresholds all operate independently of that federal threshold.
The headline change of 2025, the OBBBA restoring the federal TPSO threshold, created a dangerous assumption: that a higher threshold means a lighter compliance load. It doesn’t. A platform that recalibrates its threshold logic and stops there will file fewer forms while quietly building new gaps in its program. This guide walks through each layer of 1099-K enterprise compliance, what changed, what didn’t, and what your team needs to lock down before filing season.
What Form 1099-K Reports and Who Must File
Form 1099-K reports payments for goods and services processed through payment settlement entities. Two filer categories exist, and the difference shapes every downstream decision.
Third-Party Settlement Organizations (TPSOs) settle third-party network transactions — payment apps, online marketplaces, and platforms like PayPal, Venmo for Business, Stripe, Square, and eBay. The OBBBA threshold applies here.
Merchant Acquiring Entities (MAEs) are banks or organizations contractually obligated to settle payment card transactions. The TPSO threshold rules do not apply to MAEs. If your team treats MAE volume and TPSO volume under the same threshold logic, every downstream calculation inherits the error.
The OBBBA Threshold Change
The OBBBA permanently restored the pre-ARPA TPSO threshold. Per IRS Fact Sheet FS-2025-08, TPSOs are not required to file unless gross payments to a payee exceed $20,000 and transactions exceed 200.
- Pre-ARPA: $20,000 and 200 transactions
- ARPA (2021): reduced to $600, no transaction minimum
- IRS delays: $5,000 (2024) and $2,500 (2025)
- OBBBA (July 2025): restored $20,000 and 200 transactions, retroactive to tax years beginning after December 31, 2021
Platforms that issued 1099-Ks under the lower transitional thresholds do not need to amend them. Platforms that did not file under ARPA rules will not face penalties. The OBBBA reduces form volume, it does not reduce the compliance infrastructure your platform needs.
The Zero-Threshold Trap for Payment Cards
The most consequential distinction has nothing to do with the OBBBA: no threshold applies to payment card transactions. MAEs must issue Form 1099-K for every dollar of card volume, no minimum amount, no transaction count. Applying the TPSO threshold to card volume is a compliance failure that scales with your transaction count.
| Transaction Type | Filer Category | Federal Threshold |
| Payment card | Merchant Acquiring Entity | None — all amounts reportable |
| Third-party network | TPSO | Over $20,000 and more than 200 transactions |
Per-Platform Aggregation and Backup Withholding
The threshold applies per platform, not across every platform a payee uses. A payee receiving $15,000 on Platform A and $10,000 on Platform B crosses neither threshold and receives no 1099-K, even though combined volume exceeds $20,000.
Backup withholding overrides the threshold entirely. If a TPSO applied backup withholding under IRC Section 3406(a) for any payee, it must file a Form 945 and a Form 1099-K regardless of transaction volume. Backup withholding at 24% is required when:
- A payee fails to provide a valid TIN
- A payee provides an incorrect TIN
- The IRS notifies the platform of a name/TIN mismatch through the B-Notice process
The restored threshold reduces form volume, but it does nothing to reduce the scope of TIN validation. A platform that files fewer 1099-Ks still has to validate every account.
Payee Identity Management at Scale
Payee identity management is a continuous function, built into your settlement engine.
- W-9 at onboarding: Require Form W-9 from all US persons before activating accounts. No W-9, no settlement.
- W-8 for foreign merchants: Non-US merchants require Form W-8BEN or W-8BEN-E. A 30% withholding rate may apply unless a treaty exception is in place.
- Bulk TIN matching: Run the full payee roster through IRS TIN Matching before Q4. 1099Pro’s bulk TIN matching workflow supports this at enterprise scale.
- Annual re-verification: Payees who update their name, EIN, or address must re-submit a W-9 before settlement resumes.
- Backup withholding enforcement: Payees who fail to provide a valid TIN after B-Notice solicitation require 24% withholding, enforced in real time.
Filing Boxes, Deadlines, and State Rules
Box 1a reports gross, before fees, before refunds. Netting understates what the IRS expects to cross-check against payee returns. Box 4 reports 24% backup withholding and requires Form 945 at year-end.
Several states maintain thresholds below the federal standard and do not conform to federal changes (per FS-2025-08):
- Massachusetts, Maryland, Virginia, Vermont, Washington DC: $600
- New Jersey: $1,000
- Illinois: $1,000 with four or more transactions
A payee with $8,000 in annual payments sits below the federal threshold but above several state thresholds. CF/SF participation does not resolve compliance in non-conforming states, and states like Florida and Tennessee require separate direct filings.
| Obligation | 2027 Deadline (TY2026) |
| Recipient copy furnished | February 1, 2027 |
| Paper filing with IRS | March 1, 2027 |
| eFile with IRS | March 31, 2027 |
The eFile mandate applies to organizations filing 10 or more total information returns, a threshold enterprise platforms cross immediately. For corrections: Type 1 errors (amount, code, data) require a corrected form with the “CORRECTED” box checked; Type 2 errors (name or TIN) require a two-step void-and-refile process.
Voluntary Filing and Program Readiness
The OBBBA threshold is a minimum, not a ceiling. A TPSO may file voluntarily to reduce the risk of payees underreporting income in states that still tax it. One hard rule: if backup withholding was applied to any payee below the threshold, that payee requires a 1099-K regardless of policy.
Use Q4 to get ahead of filing season:
- Audit your active payee TIN file and run bulk TIN matching
- Confirm backup withholding workflows are operational
- Identify payees approaching state-level thresholds
- Verify per-platform aggregation logic
- Document your voluntary filing policy
- Confirm state-specific filings for non-CF/SF states
A lower form volume does not mean a simpler program. The infrastructure required to operate correctly; TIN validation, state segmentation, backup withholding enforcement, and correction management, remains fully active.
Start a free trial with 1099Pro to see how bulk TIN matching, high-volume IRIS transmission, state filing management, and audit-ready correction workflows support enterprise 1099-K compliance end to end.
Frequently Asked Questions
What is the difference between a TPSO and a merchant acquiring entity?
A TPSO settles third-party network transactions and reports when a payee exceeds $20,000 and 200 transactions per platform. An MAE settles payment card transactions with no threshold — all card volume is reportable at any amount.
Do the thresholds apply across all platforms a payee uses?
No. The thresholds apply per platform. A payee receiving $15,000 on one platform and $10,000 on another has not crossed the threshold on either.
Does backup withholding override the threshold?
Yes. If backup withholding was applied under IRC Section 3406(a), the TPSO must file a Form 1099-K regardless of volume, plus a Form 945 for the amount withheld.
How should platforms handle payees in states with lower thresholds?
State requirements operate independently of the federal threshold. Conduct a jurisdiction-by-jurisdiction review annually. CF/SF participation does not resolve compliance in non-conforming states.
Can a TPSO file voluntarily below the federal threshold?
Yes. The threshold is a minimum, not a ceiling. Document the decision and apply it consistently. If backup withholding was applied, a form is required regardless of policy.