1099-K Threshold for 2026: Reverted to $20,000 + 200 Transactions (What Bookkeepers Track)

A lot of bookkeepers spent two years planning for a $600 1099-K threshold that never arrived. First it was delayed. Then it was phased. Then Congress stepped in with the One Big Beautiful Budget Act (OBBBA) and officially buried it.

The 1099-K threshold is back to $20,000 gross and 200 transactions, retroactive to 2022. That means Stripe, PayPal, Venmo Business, Square, and Shopify Payments only send your client a 1099-K when both gates are crossed in the same calendar year. If a vendor receives $4,800 through Stripe Connect, they won't get a 1099-K at all. And the payer's 1099-NEC responsibility doesn't disappear just because a processor is involved.

That gap is where year-end reconciliation breaks down. This guide walks through exactly what the reversion means, where state rules differ, and how to catch the coverage gaps before they create IRS headaches.

What is the 1099-K threshold for 2026?

The 1099-K threshold for 2026 is $20,000 in gross payments AND 200 transactions from a single payment processor. Both conditions must be met for the processor to issue a 1099-K. This threshold was restored by the One Big Beautiful Budget Act (OBBBA), which retroactively eliminated the phased reduction to $600 that the American Rescue Plan Act had scheduled. Processors including Stripe, PayPal, Venmo Business, Square, and Shopify Payments follow the federal $20,000 / 200-transaction rule unless the payee's state mandates a lower threshold.

Key Takeaways

• The $600 threshold is dead - OBBBA permanently reverted the 1099-K threshold to $20,000 gross AND 200 transactions, retroactive to 2022, ending the ARPA phase-down
• Both gates must be crossed - A payee receiving $25,000 via Stripe in 149 transactions gets no 1099-K; a payee at 210 transactions totaling $19,000 also gets none
• Payer 1099-NEC responsibility does not go away - If you pay a contractor $4,800 via Stripe Connect and they won't receive a Stripe 1099-K, you still owe a 1099-NEC if total payments reach $2,000 (the new 2026 NEC threshold)
• Nine states have lower thresholds - CA, MA, VT, IL, MD, VA, AR, NJ, and NY require processors to issue 1099-Ks below the $20,000 federal floor; know your client's state
• 1099-K reports gross amounts - Processor fees and refunds are not netted out; reconciling the 1099-K against books requires backing those out manually
• The reconciliation gap is real - Contractors paid only via processor often assume the processor handles their tax reporting; payers assume the processor handles the contractor's; the IRS can receive nothing

What OBBBA Actually Changed

Before OBBBA, the American Rescue Plan Act of 2021 had scheduled the 1099-K threshold to drop from $20,000 to $600 starting in tax year 2022. The IRS delayed implementation twice through Notice 2023-10 and Notice 2024-85 while Congress debated. OBBBA resolved the debate by repealing the ARPA change entirely.

The result: the $20,000 gross / 200-transaction dual threshold is now permanent law, not a temporary delay. There's no pending phase-down to plan around. The threshold applies retroactively to tax years 2022 through 2025, which also clarifies any amended-return questions for prior years.

For a deeper look at how 1099-K fits within the broader 1099 landscape, see the 1099 filing guide for bookkeepers. Unfamiliar with how 1099-K compares to other information return types? The 1099 glossary covers key terms including gross proceeds, third-party settlement organizations, and backup withholding in plain language.

One nuance that often confuses clients: "gross payments" on a 1099-K means what the processor received on the payee's behalf, before deducting anything. Stripe counts a $500 sale as $500, even if it immediately deducted a $14.75 processing fee. That definition of "gross" determines whether a payee crosses the $20,000 threshold. It does not mean that $20,000 is taxable income, which is a distinction worth flagging to clients early.

How the Dual Gate Works in Practice

Both conditions must be met simultaneously within the same tax year from the same processor. This creates several non-obvious scenarios bookkeepers see regularly.

Scenario 1: High volume, low dollars. A wedding photographer gets paid through Venmo Business for 230 small deposits totaling $18,400. She exceeds 200 transactions but comes in under $20,000. No 1099-K from Venmo.

Scenario 2: High dollars, low volume. A web developer receives $45,000 through Stripe across 8 invoices. Way over $20,000, but only 8 transactions. No 1099-K from Stripe.

Scenario 3: The gap scenario. A contractor is paid $4,800 via Stripe Connect across 12 transactions. Neither gate is crossed. Stripe issues nothing. If total payments to this contractor during the year reached $2,000 or more (under the new 2026 NEC threshold), the payer owes a 1099-NEC, not Stripe. Many clients don't realize this distinction until the IRS does.

Scenario 4: Split processor payments. A contractor receives $12,000 through PayPal and $10,000 through Square. Neither processor hits $20,000, so neither issues a 1099-K. But the payer may still owe a 1099-NEC depending on the nature of the work and total compensation.

This is why understanding the dual gate matters for 1099-NEC vs 1099-MISC decisions as well. When a processor is involved, the form-type question and the threshold question intersect.

State Thresholds That Override Federal

Nine states have enacted their own 1099-K reporting thresholds below the federal $20,000 / 200-transaction floor. Processors are required to follow the more restrictive of the two rules when the payee has a state address in one of these states.

For clients in these states, expect processor-issued 1099-Ks to arrive for vendors well below the federal threshold. This matters for reconciliation: a client in California may receive a 1099-K for a $750 payment they hadn't flagged as a potential reporting event.

A few practical notes on state rules:

Address on file drives the determination. Processors use the payee's address as reported in their account settings. If a California-based contractor lists a Texas address, they may not receive a state-mandated 1099-K. That's the contractor's responsibility to maintain, but bookkeepers should know the rule is address-driven, not residency-driven.

State 1099-K does not override federal 1099-NEC. A California contractor who receives a Stripe 1099-K for $750 is not thereby exempt from the payer's 1099-NEC obligation. The two forms track different things from different angles. The 1099-K reports what the processor processed. The 1099-NEC reports what the payer paid. Both can apply to the same payment.

Multi-state clients need a state-by-state vendor review. A bookkeeping client with contractors in CA, MA, and TX faces three different rules. Texas vendors follow the federal floor. California and Massachusetts vendors may generate 1099-Ks for amounts as low as $600. The reconciliation workload scales with vendor location diversity, not just payment volume.

Reconciling 1099-Ks Against the Books

The biggest reconciliation issue with 1099-Ks isn't the threshold. It's that the form reports gross amounts.

A client who ran $85,000 through their Stripe account may get a 1099-K for $85,000. But the books show $78,200 in revenue after $5,300 in processing fees and $1,500 in refunds. That $6,800 difference isn't income that disappeared. It needs to be documented so the return doesn't show an $85,000 1099-K with only $78,200 reported on the income side.

The reconciliation steps look like this:

1. Pull the 1099-K from the processor (usually available in the tax documents section of the dashboard by late January)
2. Export the full year transaction report with fees and refunds itemized
3. Reconcile gross amount to books: Revenue + refunds received back + gross fees = 1099-K gross
4. Document the reconciliation in the client's records before preparing the return

This is also where payment reconciliation workflows become relevant beyond just the bookkeeping layer. Clients who pay vendors through payment processors need to track not just what they received, but what they paid out through those same rails.

The 1099-NEC Gap Nobody Talks About

Here's the scenario that creates the most confusion.

A bookkeeper's client pays a marketing contractor $4,800 over the course of the year through Stripe. The client assumes Stripe will handle the 1099-K. The contractor assumes the same. Stripe issues nothing because neither gate was crossed.

Under 2026 rules, the $2,000 1099-NEC threshold (updated from the old $600 threshold via OBBBA and §6041(a)) applies here. The payer owes a 1099-NEC to the contractor if total nonemployee compensation reached $2,000 or more. The payer also needs a W-9 on file. Without it, 24% backup withholding may apply going forward.

If your client doesn't have W-9s for vendor payments, that's the first gap to close. The IRS's TIN matching system exists specifically to verify before the first payment, not after the first penalty. See how to request a W-9 from a vendor for a workflow that keeps contractor payments compliant before 1099 season arrives.

The backup withholding rules also connect here. A missing or incorrect TIN on file triggers a B-Notice from the IRS, which activates mandatory 24% backup withholding on future payments. Identifying that gap in Q3 costs 20 minutes. Identifying it in February costs a lot more.

What Growthy Tracks Automatically

Processor payments hit the books differently than direct contractor payments. A single Stripe payout may net 30 transactions, multiple clients, and a batch of refunds. Sorting out which amounts belong to which vendor for 1099-NEC purposes is a manual slog in most bookkeeping tools.

Growthy categorizes automatically based on how each transaction is coded and flags payment processor payouts for reconciliation. The system starts at 85% first-import accuracy on real client data, reaching 90%+ on returning accounts as it learns each client's payment patterns. Built by a CPA firm partner who still reconciles books for real clients, it's designed around the gaps that actually trip up year-end close, not idealized transaction flows.

When a Stripe payout lands, Growthy identifies it as a processor deposit, not revenue, and holds it for fee and refund netting before marking the transactions reviewed. That distinction keeps the 1099-K reconciliation clean from day one instead of requiring a year-end cleanup pass across hundreds of transactions. It also flags contractors paid through processors who haven't crossed the 1099-K threshold, so you can decide whether a 1099-NEC is warranted before the January deadline.

For the full feature set, see Growthy's AI bookkeeping features.

1099-K Threshold: Frequently Asked Questions

Does the OBBBA reversion affect 2022 through 2025 returns?

Yes. OBBBA made the $20,000 / 200-transaction threshold retroactive to 2022. This resolves any open questions about whether processors should have issued 1099-Ks under the ARPA phase-down amounts for those years. They were not required to.

If a client gets a 1099-K for more than they reported as income, what happens?

The IRS cross-references 1099-K amounts against reported income. A mismatch triggers a CP2000 notice. The fix is documentation: show the processor fee and refund reconciliation that explains the difference. This is why the reconciliation step matters before filing, not after.

Can a single vendor trigger a 1099-K from two different processors?

Yes. The threshold applies per processor, not per payee across all processors. If a freelancer gets $12,000 through PayPal and $14,000 through Venmo Business, neither processor crosses $20,000, so neither issues a 1099-K, regardless of total income.

What if the client paid a vendor through both a processor and a direct check?

The processor portion and the direct payment are tracked separately. The processor handles its own 1099-K determination. The payer is responsible for the 1099-NEC on the full year's nonemployee compensation if it reaches $2,000, regardless of payment method mix.

Do 1099 filing deadlines differ for 1099-K versus 1099-NEC?

Yes. 1099-K (processor-issued) is due to the recipient by January 31 and to the IRS by February 28 (paper) or March 31 (electronic). 1099-NEC is due to both the recipient and the IRS by January 31, with no electronic extension. Payer-issued 1099-NECs carry the tighter deadline.

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.

Track 1099-K thresholds and processor payments automatically — try Growthy free.