200-Transaction Thresholds and Recurring Charges: How Subscription Boxes and SaaS Hit Economic Nexus Before $100K in Revenue
If you sell a $60/month SaaS product or a $45/month subscription box, the 200-transaction economic nexus prong is designed to catch you. In states like Illinois and Michigan, every monthly charge you process counts as a separate transaction — meaning 17 customers paying monthly in a single state generates 204 transactions in one year. That's enough to trigger nexus even though your total revenue from those customers is only $12,240. The lookback period rules compound the problem: once you cross the transaction count in a trailing 12-month window, you owe registration and collection for the following period — regardless of revenue.
Key Takeaways
- • Each monthly charge = one transaction. A customer paying $49/month generates 12 transactions per year, not one. Annual prepayments count as a single transaction.
- • 17 monthly subscribers in one state can trigger nexus. 17 customers × 12 monthly charges = 204 transactions — exceeding the 200-transaction threshold even at minimal revenue.
- • Illinois ($100K or 200 transactions) and Michigan ($100K or 200 transactions) both use the "or" connector, meaning either prong alone triggers the obligation.
- • Revenue-only states are structurally different. California, Texas, and Massachusetts have repealed the transaction-count prong. Subscription businesses in those states only face the dollar threshold.
- • Registration timing differs from collection timing. Crossing the transaction prong triggers a registration requirement, but your collection obligation start date depends on the state's specific effective-date rules.
- • Annual prepayment billing is a legitimate structural advantage — one payment per year per customer dramatically reduces your transaction count without changing your revenue.
How States Count "Transactions" for Economic Nexus
The 200-transaction threshold originates from the Supreme Court's 2018 South Dakota v. Wayfair decision, which used South Dakota's $100,000 or 200-transaction standard as the constitutional benchmark. Most states adopted some version of this dual test. But the word "transaction" is where subscription businesses get caught: it means each individual sale, not each customer relationship.
For a one-time purchase business (furniture, electronics, wholesale orders), transactions and customers roughly track together. Sell to 200 customers, and you're at roughly 200 transactions. But for subscription and SaaS businesses, the math diverges dramatically:
| Business Model | Customers in State | Transactions per Year | Exceeds 200? |
|---|---|---|---|
| One-time product sales | 200 | 200 | At the line |
| Monthly subscription ($49/mo) | 17 | 204 | Yes |
| Monthly SaaS ($60/mo) | 17 | 204 | Yes |
| Annual SaaS prepayment ($720/yr) | 17 | 17 | No |
The contrast is stark. A monthly-billing SaaS with just 17 customers in one state crosses the 200-transaction threshold. The same SaaS billing annually needs 201 customers to cross it. The revenue is identical — the transaction count is 12x different.
Illinois: $100,000 or 200 Transactions (SB 690)
Illinois adopted its economic nexus standard under SB 690, effective October 1, 2018. The test: $100,000 in gross revenue or 200 separate transactions into Illinois during the preceding 12-month period. The "or" is critical — meeting either prong independently triggers the obligation.
For subscription businesses, Illinois's marketplace facilitator rules add a layer: if you sell through a marketplace facilitator (Amazon, Shopify App Store), the facilitator's transactions on your behalf may be excluded from your personal count. But if you bill customers directly — which most SaaS businesses and subscription boxes do — every charge hits your threshold.
Worked Example: $60/Month SaaS with 20 Illinois Customers
- • Month 1: 20 customers × 1 charge = 20 transactions. Revenue: $1,200.
- • Month 5: 20 × 5 = 100 transactions. Revenue: $6,000.
- • Month 10: 20 × 10 = 200 transactions. Revenue: $12,000. You have crossed the 200-transaction threshold.
- • Month 12: 20 × 12 = 240 transactions. Revenue: $14,400. Still far below $100K.
- • Month 17: Revenue has reached $20,400. Still under $100K — but you crossed the transaction prong seven months ago. You should already be registered and collecting.
The gap is enormous. This SaaS business will not reach $100K in Illinois revenue until month 84 (seven years) — but it crosses the transaction threshold in month 10. Without the 200-transaction prong, this business would have no Illinois nexus obligation for years. With it, the obligation begins before the first anniversary.
Michigan: $100,000 or 200 Transactions
Michigan's economic nexus standard mirrors the Wayfair benchmark: $100,000 in gross revenue or 200 transactions into Michigan in the previous calendar year. Like Illinois, the "or" means either prong alone is sufficient.
Michigan's marketplace facilitator gaps are particularly relevant for subscription box sellers who also sell on Etsy or eBay — those marketplace-facilitated transactions may or may not reduce your direct transaction count depending on the facilitator's remittance agreement with Michigan.
One key difference from Illinois: Michigan uses a calendar-year lookback rather than a trailing 12-month period. This means your transaction count resets on January 1. A subscription business that crosses 200 transactions in October still has nexus for the remainder of the current year and the full following year — but the counter restarts in January of the subsequent year.
Subscriber Tier Table: When 200 Transactions Are Crossed by State Count
The table below shows how quickly monthly-billing subscription businesses cross the 200-transaction threshold at different subscriber counts in a single state. This assumes all customers are billed monthly and no customers churn.
| Subscribers in State | Month Threshold Crossed | Annual Transactions | Annual Revenue at $49/mo | Exceeds $100K? |
|---|---|---|---|---|
| 10 | Month 20 (never in first year) | 120 | $5,880 | No |
| 17 | Month 12 | 204 | $9,996 | No |
| 25 | Month 8 | 300 | $14,700 | No |
| 50 | Month 4 | 600 | $29,400 | No |
| 100 | Month 2 | 1,200 | $58,800 | No |
| 250 | Month 1 | 3,000 | $147,000 | Yes |
| 500 | Month 1 | 6,000 | $294,000 | Yes |
The pattern is clear: for any subscription business with more than 16 monthly-paying customers in a single 200-transaction state, the transaction prong triggers first. The $100K revenue threshold only becomes the binding constraint for businesses with fewer than ~170 subscribers at $49/month (170 × 12 × $49 = $99,960).
Revenue-Only States: Where the Transaction Count Doesn't Matter
Not all states use the 200-transaction prong. Several large states have repealed it or never adopted it, using revenue-only thresholds instead. For subscription businesses, these states are structurally more favorable because your transaction volume is irrelevant — only the dollar amount matters.
| State | Threshold | Transaction Prong? | Subscription Business Impact |
|---|---|---|---|
| California | $500,000 | No | Revenue-only. High bar for small subscription businesses. |
| Texas | $500,000 | No (repealed 2024) | Previously $500K or 200 transactions; now revenue-only. |
| Massachusetts | $100,000 | No (repealed 2024) | Was $500K and 100 transactions; now $100K revenue-only. |
| Illinois | $100,000 or 200 txns | Yes | Transaction prong still active. High risk for subscription models. |
| Michigan | $100,000 or 200 txns | Yes | Transaction prong still active. Calendar-year reset. |
The legislative trend is toward repeal. Over 16 states have eliminated the transaction-count prong since 2021. But Illinois and Michigan have shown no indication of following suit as of 2026, leaving subscription businesses exposed to the transaction-count mechanism in those states.
The Annual Prepayment Quirk: One Transaction or Twelve?
This is the structural question that most affects subscription businesses' nexus exposure: if a customer pays annually instead of monthly, how many transactions is that?
The answer depends on how your billing system processes the payment:
Single Annual Charge
If your billing system (Stripe, Chargebee, Recurly) processes one payment of $588 at the start of the annual term, that is one transaction. The customer contributes 1 toward your 200-transaction count for the year, not 12. This is the standard treatment: one charge = one transaction.
Monthly Billing on an Annual Plan
Some businesses offer "annual plans" that still bill monthly (often at a discounted rate). If your system processes 12 separate charges, those are 12 transactions regardless of the plan label. The state's department of revenue counts charges processed, not marketing terms.
The practical implication: a SaaS business that shifts from monthly to annual billing can reduce its per-customer transaction count by 92% (from 12 to 1) while maintaining the same revenue. For a business with 20 Illinois customers:
- Monthly billing: 20 × 12 = 240 transactions/year. Exceeds 200-transaction threshold.
- Annual billing: 20 × 1 = 20 transactions/year. Well below the threshold.
- Revenue is identical: $14,400/year in either case. Neither triggers the $100K revenue prong.
This is not a loophole — it's a structural feature of how transactions are counted. Encouraging annual prepayment is a legitimate business practice with real economic substance (improved cash flow, reduced churn). But the nexus implications are a significant secondary benefit that subscription businesses should understand.
Registration vs. Collection: Timing Differences After Crossing the Transaction Prong
Crossing the 200-transaction threshold triggers a registration requirement, but the collection obligation start date varies by state. This distinction matters because there is often a gap between when you must register and when you must begin adding tax to invoices.
| State | When to Register | When Collection Begins |
|---|---|---|
| Illinois | As soon as threshold is crossed | First day of the next calendar quarter after crossing |
| Michigan | Within 30 days of crossing | Beginning of the next calendar year (if prior-year threshold met) |
For a subscription SaaS crossing the 200-transaction threshold in Illinois in October, the sequence is: register immediately, begin collecting Illinois sales tax on January 1 (the first day of the next quarter, which is Q1 of the following year). For Michigan, if you crossed 200 transactions during 2026, you register within 30 days and your collection obligation begins January 1, 2027.
The practical risk for subscription businesses: because your billing is automated and recurring, "beginning to collect" means updating your billing system configuration by the effective date. Missing this date means every subsequent recurring charge is under-collected — and you will owe the difference out of pocket when filing.
What Subscription Businesses Should Do Now
If you run a subscription box or SaaS business billing customers monthly, here is a concrete action plan:
Action Items
- • Count your state-level customer distribution. Pull a report from Stripe, Chargebee, or your billing system showing how many active subscribers you have per state. Multiply by 12 (or the number of months remaining in the lookback period) to project annual transaction counts.
- • Identify 200-transaction states where you are close. Focus on states that still have the transaction-count prong. If you have 14+ monthly subscribers in any of these states, you are within striking distance.
- • Consider annual billing incentives. Offering a discount for annual prepayment reduces your per-customer transaction count from 12 to 1. A 10–15% annual discount is standard and provides legitimate business benefits beyond nexus management.
- • Monitor the repeal trend. States are actively eliminating the 200-transaction prong. Track which states count service and digital revenue toward their thresholds, and which are moving to revenue-only standards.
- • Automate tax collection in your billing system. Stripe Tax, Avalara, and TaxJar integrate with most subscription billing platforms. Enable them before your collection obligation date — retroactive corrections on recurring charges are operationally painful.
Frequently Asked Questions
Yes, in states that use a transaction-count prong (like Illinois and Michigan), each individual charge processed counts as one transaction toward the threshold. A customer paying $49/month generates 12 transactions per year, not one. This means a subscription business with just 17 monthly-paying Illinois customers will exceed the 200-transaction threshold in 12 months — even if total Illinois revenue is only $9,996.
Last Updated: May 8, 2026
Disclaimer: This information is provided for educational and informational purposes only and does not constitute tax, legal, or financial advice. Tax laws and regulations change frequently. While we strive to keep this information accurate and up-to-date, we make no representations or warranties of any kind about the completeness, accuracy, reliability, or suitability of this information. Please consult with a qualified tax professional or attorney for advice specific to your business situation. Always verify current requirements with the official state tax authority.