Sales Tax
6
Minutes Read
Published
October 6, 2025
Updated
October 6, 2025

2025 SaaS Sales Tax Nexus Rules: What Founders Need to Know Now

Stay compliant with the latest US SaaS sales tax nexus rules for 2025. Learn how economic nexus thresholds and remote seller rules impact your software subscription tax obligations.
Glencoyne Editorial Team
The Glencoyne Editorial Team is composed of former finance operators who have managed multi-million-dollar budgets at high-growth startups, including companies backed by Y Combinator. With experience reporting directly to founders and boards in both the UK and the US, we have led finance functions through fundraising rounds, licensing agreements, and periods of rapid scaling.

The Two-Part Test for US Sales Tax Compliance

Navigating software subscription tax compliance in the USA boils down to answering two fundamental questions for every single state. Before you are required to collect sales tax from customers in a specific state, your business must meet two distinct conditions. Understanding this framework is the first step toward managing your obligations effectively.

  1. Do you have nexus in that state? Nexus is the legal term for the connection your business has to a state that gives it the right to impose a tax collection duty on you.
  2. Is your SaaS product taxable in that state? Taxability is determined by state-specific laws that classify how digital products and services are treated for tax purposes.

Answering "yes" to both questions creates a tax collection obligation. If the answer to either question is "no," you do not have to collect sales tax there, even if your sales are substantial. This two-part requirement is the most important concept to grasp as you build your compliance strategy.

Understanding Nexus: When US Sales Tax Rules Apply to Your SaaS

Nexus is the starting point. It is the legal threshold of connection a business has with a state that subjects it to that state's tax laws. For modern SaaS businesses, this connection is no longer just about physical location; it is increasingly about economic activity. Nexus typically appears in two primary forms.

Physical Nexus: The Traditional Presence Test

Physical nexus is the original standard for creating a tax obligation. It is triggered by having a tangible presence within a state. This can include obvious things like an office or a warehouse. However, for remote-first SaaS companies, it can also be created unexpectedly by factors such as:

  • Having a remote employee working from their home in that state.
  • Hiring a full-time contractor who resides in the state.
  • Storing company property, even minor equipment, in a state.
  • Attending trade shows or having sales representatives visit a state, depending on the frequency and nature of their activities.

A single hire can be enough to trigger physical nexus, making it essential to track where your team members and key contractors reside as your company grows.

Economic Nexus: The Modern Standard for Remote Sellers

The most significant and complex development for remote sellers is economic nexus. This concept was established by the landmark Supreme Court case, South Dakota v. Wayfair (2018). The ruling overturned previous physical presence requirements, allowing states to mandate tax collection from out-of-state businesses if they meet certain economic thresholds. This is the primary driver of `SaaS tax obligations USA` for most companies selling across the country.

The most common economic nexus threshold is $100,000 in sales OR 200 separate transactions into a state within a 12-month period. However, these `state sales tax thresholds` are not universal, creating a patchwork of different rules. The measurement period also varies; some states use the previous calendar year, while others use a rolling 12-month lookback. This variation requires careful and continuous monitoring of your sales data.

To simplify these `remote seller rules SaaS`, it helps to group states into general categories:

  • The Majority Threshold: Most states have adopted the common $100,000 in sales or 200 transactions threshold. This should be your default rule for monitoring most jurisdictions.
  • High-Threshold States: A few large states have set higher, sales-only thresholds, which benefits businesses with high transaction volumes but lower average revenue per customer. Key examples include California ($500,000), Texas ($500,000), and New York ($500,000).
  • Simplified Transaction Counts: Critically for B2C SaaS companies, some major states have removed their transaction count threshold, simplifying compliance. For example, California and Texas now base their nexus rules on sales revenue only, ignoring the 200-transaction count.
  • No Statewide Sales Tax: Five states do not have a statewide sales tax, meaning economic nexus for sales tax purposes is not a concern. These are Alaska, Delaware, Montana, New Hampshire, and Oregon. A common point of confusion is company incorporation. While many startups incorporate in Delaware for its favorable corporate laws, this has no impact on your obligation to collect sales tax in other states where you establish economic nexus.

SaaS Taxability: Is Your Software a Taxable Product or an Exempt Service?

Crossing a nexus threshold in a state is only half the battle. Nexus alone is not enough; it only gives a state the right to tax your sales. The second critical question is whether that state's laws actually classify your product as taxable. This is where the state-by-state variation becomes acute, as each legislature has its own definition of a taxable `digital product sales tax US` item.

SaaS taxability generally falls into one of three categories, creating a complex compliance environment.

Category 1: Clearly Taxable

In these states, laws have been written or administratively interpreted to explicitly include Software-as-a-Service in the tax base. Tax authorities in these states often classify SaaS as taxable tangible personal property, a specified digital good, or an enumerated taxable service. For US companies, prominent examples of states where SaaS is clearly taxable include New York, Pennsylvania, Texas, and Washington. If you have nexus in one of these states, you almost certainly have an obligation to register and collect sales tax.

Category 2: Generally Exempt

Some states view SaaS as a non-taxable service, meaning you are not required to collect sales tax even if you have economic nexus. The logic here is that the customer is paying for a service, not for the transfer of property. The most significant example is California, where SaaS is generally considered a tax-exempt service. For businesses with major sales in California, this exemption greatly simplifies compliance, as you can cross the high $500,000 nexus threshold and still have no collection duty.

Category 3: Complicated or Conditional

This is the most confusing category, where the answer to taxability is "it depends." In these states, taxability is often conditional on specific factors related to your product or delivery model. The determining factor could be how the software is accessed, whether it involves the transfer of tangible personal property, if it includes mandatory professional services, or if it is customized for the user. Examples of states where SaaS taxability is complicated include Illinois and Florida. In these jurisdictions, a detailed analysis of your service offering against state regulations is often necessary.

This is a critical distinction: the tax rules for your core SaaS subscription may also be different from attached professional services or one-time setup fees. For instance, your monthly subscription fee might be taxable, while a separate charge for user training might be exempt as a non-taxable service. This adds another layer of complexity to invoicing.

A Pragmatic 3-Stage Plan for SaaS Sales Tax Compliance

Knowing the `saas sales tax nexus rules usa` is one thing; implementing a compliant process with a lean team is another. The reality for most growing startups is that you cannot afford to register in every state from day one, nor is it necessary. A pragmatic, three-stage approach aligns compliance efforts with business growth and minimizes administrative burden.

Stage 1: Monitor (From Your First Sale)

Your first step is not registration; it is monitoring. You cannot act on what you do not measure. From the moment you make your first US sale, your goal is to track sales revenue and transaction counts for every state. Your billing platform, such as Stripe or Chargebee, is your source of truth. Most of these systems can generate reports that break down sales by customer location, which is the foundation of your monitoring process.

To simplify this, you can use a tool like Stripe Tax purely for its exposure monitoring features. Without enabling collection, it provides a dashboard that shows how close you are to hitting nexus thresholds in each state. This gives you the visibility needed to plan your next steps without incurring immediate costs or administrative overhead.

Stage 2: Act (When Approaching a Threshold)

Continuous monitoring will alert you when you are getting close to a threshold, for instance, when you reach $80,000 in sales in a state with a $100,000 limit. This is your trigger to act. Your action plan at this point should be methodical:

  1. Confirm Taxability: First, verify if your SaaS is taxable in that specific state. If you are approaching the nexus threshold in California, for example, you may not need to take further action since SaaS is generally exempt there.
  2. Register for a Permit: If you are approaching a threshold in a state where your product is taxable, such as Texas or New York, you must register with that state's department of revenue to get a sales tax permit. This is a legal requirement before you can begin collecting tax from customers.

Stage 3: Automate (Immediately After Registration)

Once you are registered in a state, you are legally required to calculate, collect, and remit sales tax on all taxable sales in that jurisdiction. Manual calculation is not feasible or scalable. Tax rates can vary by city, county, and special district, and keeping up with thousands of changing rates is impossible. This is the point where you must implement an automated tax solution.

Tools like Avalara, TaxJar, and Anrok are built specifically for this purpose. They integrate directly with your billing system to perform real-time tax calculations during checkout, add the correct tax to invoices, and generate the reports needed for filing returns. Stripe Tax can also be transitioned from a monitoring tool to a full calculation and collection engine. This automation prevents costly errors, saves hundreds of hours, and ensures you remain compliant as you grow. If you sell through app stores or other platforms, investigate how marketplace facilitator rules may apply.

Your Path to Sustainable Sales Tax Compliance

Navigating US sales tax for SaaS does not have to be an overwhelming distraction from growth. By focusing on a structured process, you can manage compliance efficiently, even without a dedicated finance department. The key is to remember the two-part test: a collection obligation only exists in a state where you have both nexus AND your SaaS product is considered taxable.

Your immediate priority should be to establish a monitoring system. Use your billing platform or a dedicated tool to gain visibility into your sales totals per state. This data is the foundation of your entire compliance strategy. Do not rush to register everywhere. Instead, use your monitoring data to take a risk-based approach, acting only when you approach a specific state's threshold and have confirmed your product is taxable there.

The path to compliance is progressive: Monitor your exposure from day one, Act by registering when a threshold is near, and Automate the calculation and filing process once you are registered. This pragmatic sequence allows your compliance function to scale alongside your revenue, protecting your business without slowing it down.

Frequently Asked Questions

Q: What happens if I have remote employees in a state?
A: A remote employee typically creates physical nexus in the state where they reside. This means you may be required to register and collect sales tax there, regardless of your sales volume. The physical presence of an employee often overrides the economic nexus thresholds.

Q: Do sales to non-profits or resellers count towards economic nexus thresholds?
A: Generally, yes. Most states count gross sales revenue towards their economic nexus thresholds, which includes sales of both taxable and non-taxable items, as well as sales to tax-exempt entities like non-profits or resellers. Always check the specific state's definition of "sales" for its threshold calculation.

Q: How far back do states look when determining economic nexus?
A: Most states use a lookback period of either the previous calendar year or a rolling 12 months. If you cross a threshold in the current or previous 12-month period, you typically must register and begin collecting tax. It's crucial to know which measurement period each state uses.

Q: My company is incorporated in Delaware. Do I only worry about Delaware sales tax?
A: No. Your state of incorporation does not determine your sales tax obligations. Delaware has no state sales tax, but you are still required to collect sales tax in any other state where you establish either physical or economic nexus and your product is taxable.

This content shares general information to help you think through finance topics. It isn’t accounting or tax advice and it doesn’t take your circumstances into account. Please speak to a professional adviser before acting. While we aim to be accurate, Glencoyne isn’t responsible for decisions made based on this material.

Curious How We Support Startups Like Yours?

We bring deep, hands-on experience across a range of technology enabled industries. Contact us to discuss.