SaaS Companies and Economic Nexus: $100K Threshold Rules Across Florida, Georgia, NC, PA, and Arizona

The “Digital Delivery Exempts Me” Myth

Before South Dakota v. Wayfair (2018), sales tax nexus required physical presence — an office, warehouse, employee, or inventory in the state. SaaS companies had a legitimate argument: with no physical presence anywhere but their headquarters, they had no nexus in customer states. That argument died with Wayfair.

Post-Wayfair, every state with a sales tax adopted economic nexus standards based on revenue or transaction volume delivered into the state. The delivery method is irrelevant. Whether you ship a physical product via FedEx or deliver software through a browser, the revenue counts the same toward the state's economic nexus threshold.

This trips up SaaS founders because they conflate two separate legal questions: (1) whether they have nexus in a state, and (2) whether their product is taxable in that state. These are independent determinations. You can have nexus without owing tax (if your product is exempt), and you can sell a taxable product without having nexus (if you are below the threshold). But once you have nexus in a state that taxes SaaS, you must register and collect.

How Each State Treats SaaS Revenue Toward the Threshold

All five Tier-A states count SaaS revenue toward their economic nexus threshold. But they differ significantly in whether SaaS is actually taxable once you register, and in the specific mechanics of their threshold calculations.

Florida: SaaS Is Taxable and the Threshold Is Revenue-Only

Florida taxes SaaS under its communications services tax framework. The state uses a revenue-only threshold of $100K in the previous calendar year — there is no transaction count alternative. For SaaS companies, this means all subscription revenue from Florida customers counts toward the threshold, and once exceeded, you must register and begin collecting. Florida's tax rate on SaaS can be complex because it combines state and local communications services tax rates, which vary by jurisdiction.

Georgia: Revenue Counts but SaaS Is Not Taxed

Georgia does not impose sales tax on SaaS. However, your SaaS revenue into Georgia still counts toward the $100K or 200-transaction threshold. If you exceed the threshold, you must register — but if SaaS is your only product, you may not owe tax on any of your Georgia sales. The registration requirement still applies because the state needs to verify what you sell and confirm exemption. If you also sell any taxable products or services (consulting, physical goods, downloaded software), you would collect on those while your SaaS remains exempt.

North Carolina: SaaS Taxed as Digital Property

North Carolina broadly taxes digital goods and services, including SaaS. The state treats remotely accessed software as a taxable digital property transfer. The threshold is $100K in revenue or 200 transactions in the previous or current calendar year. SaaS companies exceeding this threshold must register and collect the state's 4.75% sales tax rate (plus applicable local taxes) on their subscriptions sold to North Carolina customers.

Pennsylvania: SaaS Taxed as Canned Software Since 2012

Pennsylvania has taxed SaaS (and all cloud-based software) as “canned computer software” since 2012 — well before Wayfair. The state's $100K threshold uses a rolling 12-month lookback, and once exceeded, SaaS subscriptions are subject to the 6% state sales tax. Pennsylvania is notable for its broad definition: any software accessed remotely, whether true SaaS, PaaS, or IaaS, falls within the taxable category. This is one of the most aggressive SaaS taxation positions in the country.

Arizona: Revenue Counts but SaaS Is Not Subject to TPT

Arizona's Transaction Privilege Tax (TPT) does not currently apply to SaaS. The state's position is that remotely accessed software is not tangible personal property and does not fall under any taxable TPT classification. However, your SaaS revenue into Arizona still counts toward the $100K economic nexus threshold. Similar to Georgia, you may need to register but would not owe TPT on SaaS sales alone. If you also sell downloaded software (not accessed remotely), that may be taxable under different TPT classifications.

Recurring ARR vs. One-Time License Fees

SaaS revenue is not monolithic. Most SaaS companies generate revenue through a mix of recurring subscriptions (monthly or annual), one-time setup or implementation fees, and occasionally perpetual license fees for on-premise deployments. Each type counts toward the threshold differently depending on timing and state rules.

Monthly Recurring Revenue (MRR)

Monthly subscriptions accumulate toward the threshold with each billing cycle. A customer paying $5,000/month contributes $60K annually toward the threshold in their state. Critically, each monthly charge also counts as a separate transaction for states with the 200-transaction threshold. This means a relatively small customer base on monthly billing can trigger the transaction prong much faster than expected.

Annual Contracts (ARR)

Annual contracts count as one transaction on the invoice date, with the full annual amount hitting the threshold in the period it is billed. A single $100K enterprise contract billed annually to a Florida customer would, by itself, trigger the threshold in one transaction. For states using a calendar-year lookback, the timing of the invoice matters — a December 15 annual renewal counts in the current year, not the next.

One-Time Implementation and Setup Fees

Setup fees, onboarding charges, and implementation services count toward the revenue threshold in the period they are invoiced. These are often overlooked by SaaS companies calculating their nexus exposure because they are not “subscription revenue” in the traditional sense. But states do not distinguish — gross revenue is gross revenue. A $25K implementation fee billed to a Georgia customer in Q1 counts the same as $25K in subscription charges.

When Registration Is Triggered: Either Prong

Economic nexus operates on a two-prong test in most states: $100K in gross revenue OR 200 transactions. Exceeding either prong — not both — triggers the obligation to register. For SaaS companies, understanding which prong you are likely to hit first determines how quickly you need to act.

Revenue Prong: The Enterprise SaaS Scenario

Enterprise SaaS companies with high contract values and fewer customers tend to hit the $100K revenue threshold first. Three enterprise customers at $40K ARR each in a single state puts you at $120K — over the threshold with only 3 (or 36, if monthly) transactions. The revenue prong is the primary concern for B2B SaaS selling to mid-market and enterprise accounts.

Transaction Prong: The SMB SaaS Scenario

SMB-focused SaaS products with low price points and monthly billing hit the 200-transaction threshold first. A $29/month product with 17 customers in one state generates 204 annual transactions at just $5,916 in revenue. You have nexus at under $6K in sales. This catches many SMB SaaS companies off guard — they monitor their revenue against $100K and feel safe, while the transaction count quietly exceeds 200.

Note that Florida, Pennsylvania, and Arizona have eliminated the transaction threshold and use revenue only. In these states, SMB SaaS companies have more runway. But Georgia and North Carolina retain the 200-transaction test, making it the relevant trigger for high-volume, low-price SaaS products in those states.

What Happens After You Exceed the Threshold

Once you exceed either prong during the lookback period, you typically have 30–60 days (varies by state) to register for a sales tax permit and begin collecting. The obligation is prospective from the registration deadline — you do not owe back taxes for the period before you hit the threshold. However, if you exceeded the threshold months or years ago and failed to register, you have been accumulating uncollected tax liability since the registration deadline passed.

Worked Example: $80K ARR + $30K Enterprise Deal in Florida

Consider a SaaS company with $80K in annual recurring revenue from Florida customers — a mix of 40 customers on plans ranging from $100 to $500/month. The company has been operating in Florida below the $100K threshold for two years.

In March, the company closes a $30K annual enterprise deal with a Florida-based customer. Here is what happens:

The key insight: the $30K enterprise deal did not immediately trigger nexus, but it guaranteed the company would exceed the threshold later in the year. Smart SaaS companies monitor not just their current cumulative revenue but their projected year-end total. When that projection crosses $100K, they begin the registration process early rather than scrambling when the threshold is actually exceeded.

Taxability vs. Nexus: Two Separate Questions

The most common mistake SaaS companies make is treating nexus and taxability as the same question. They are not. Here is the correct framework:

• Nexus: Do I have sufficient connection to this state to be required to register? (Answered by: Did I exceed the $100K/$200-transaction threshold?)
• Taxability: Is my specific product subject to sales tax in this state? (Answered by: Does this state tax SaaS?)

You must answer both questions independently for each state. The matrix of outcomes:

This is why SaaS companies need to track nexus across all states — including states where SaaS is exempt. Georgia does not tax your product, but once you exceed the threshold, you must register. And if you also sell any taxable service (training, consulting, physical goods), your Georgia registration means you must collect on those sales even though your core SaaS product remains exempt.