Quick overview

Nexus rules determine whether a business has a sufficient connection to a state to trigger sales-tax collection and remittance obligations. For remote Software-as-a-Service (SaaS) providers, nexus can be complicated because states differ on whether SaaS is taxable and on the triggers that create nexus. After the 2018 Supreme Court decision in South Dakota v. Wayfair, many states adopted “economic nexus” standards that can apply to purely remote sellers.

This article explains how nexus is established for SaaS businesses, provides practical steps to assess exposure, and recommends controls to reduce audit risk. It also links to related FinHelp guidance where you can dig deeper.

Why the Wayfair decision matters

Before 2018, most states required physical presence (offices, employees, property) before imposing sales tax duties on out-of-state sellers. The Wayfair decision changed that: the Court allowed states to require remote sellers to collect sales tax based on economic presence, subject to the state’s chosen thresholds. (See South Dakota v. Wayfair, 2018.)

Since then, almost every state with a sales tax has enacted economic nexus rules. Thresholds vary (common thresholds include $100,000 in sales or 200 transactions in a 12-month period, while some states set higher limits). Because thresholds and definitions vary, every SaaS provider with multi-state customers needs a state-by-state review. (Source: Tax Foundation.)

How states commonly establish nexus for SaaS providers

States use a mix of tests. The main ones to monitor are:

  • Physical presence: employees, sales reps, offices, servers, or owned/leased property in a state can create physical nexus.
  • Economic presence: reaching sales or transaction thresholds in the state. Many states use either revenue, transaction count, or both.
  • Click‑through and affiliate nexus: referrals from in-state affiliates or referral links can create nexus in some states.
  • Marketplace or marketplace facilitator rules: if you sell via a marketplace, the marketplace may be required to collect tax, shifting responsibility.
  • Digital interaction and remote employees/contractors: having remote staff or targeted digital advertising to residents may be enough in some jurisdictions.

Important: whether a state treats SaaS as a taxable “sale of software” or as a non-taxable service varies. Some states specifically tax SaaS, others exempt it, and many fall in between depending on how the service is delivered or bundled with taxable items. (See FinHelp: Sales Tax Rules for Digital Goods.)

Is your SaaS product taxable? It depends

There is no single national rule for SaaS taxability. States take different approaches:

  • Taxable in some states when the service is treated as “pre-written software” or “digital goods.”
  • Exempt in other states when the charge is for a professional or non-taxable service.

Because taxability affects whether you should collect tax (in addition to whether you have nexus), include taxability analysis in every nexus review. See FinHelp’s deeper guide: Sales Tax Compliance for SaaS Businesses.

Practical nexus triggers — realistic examples

  • A startup in Ohio sells a cloud subscription to 10,000 customers nationwide. If sales into New York exceed that state’s economic threshold, the company must register and collect NY sales tax on taxable SaaS sales.
  • Hosting servers or data centers in a state can create physical nexus in jurisdictions that consider server presence a taxable connection.
  • Placing employees, even a single sales rep or technical contractor, in a state usually creates physical nexus for both sales and payroll-related filings.

In my practice working with software companies, I’ve seen small changes — like hiring part-time remote support — trigger registration obligations in multiple states. Early detection avoids late-registration penalties.

Step-by-step checklist to assess nexus (use quarterly)

  1. Pull 12 months of sales by destination state (not billing address alone — use sourcing rules for your product).
  2. Compare revenue and transaction counts against each state’s economic nexus thresholds.
  3. Identify any physical presence (employees, contractors, servers, offices, warehouses).
  4. Review affiliate/referral relationships and marketplace sales.
  5. Determine taxability of your SaaS offering in each state (taxable vs. exempt).
  6. If nexus exists, register for a sales tax permit and begin collecting tax on new taxable sales effective the state’s required date.
  7. Keep detailed records and consult with a sales-tax specialist if thresholds are close or facts are complex.

For general registration steps and filing requirements, see FinHelp’s State Sales Tax Registration: When and How to Register.

Sourcing rules and invoicing — where is the sale taxed?

States use sourcing rules to decide which jurisdiction gets the tax. Common approaches include:

  • Origin sourcing: tax based on seller’s location (rare for remote SaaS).
  • Destination sourcing: tax based on the customer’s location (common in many states).

For SaaS billed to customers in multiple states, implement billing logic that captures the customer’s jurisdiction (shipping address, primary use location, or IP/address combination) and stores supporting documentation.

See FinHelp’s State Sales Tax Sourcing Rules for more details on how states decide which jurisdiction taxes a sale.

Marketplace facilitator and reseller rules

If you sell through marketplaces (App Stores, SaaS marketplaces, resellers), check whether the marketplace is the collection agent under state law. Marketplace-facilitator laws make platforms responsible for tax collection in many states — this can simplify compliance for sellers but read the law carefully for exemptions and reporting requirements.

Recordkeeping and audit preparedness

Maintain records that substantiate nexus decisions and tax collected: sales by state, customer addresses, contracts, invoices, server locations, employee locations, and marketing targeting. States expect multi-year retention (commonly 3–7 years). If audited, you’ll want contemporaneous documentation for when and why you registered (or didn’t).

Penalties, interest and voluntary disclosures

If a state determines you had nexus and you failed to collect tax, you may owe back tax, interest, and penalties. Many states offer voluntary disclosure programs that limit look-back periods and waive penalties if you proactively register and pay. Consider a voluntary disclosure if you identify missed nexus obligations; consult a tax attorney or CPA before applying.

Automation and tools

Tax engines and billing platforms can automate nexus monitoring, taxability determinations, and tax collection. Popular capabilities to evaluate:

  • Real-time tax rate calculation by jurisdiction.
  • Nexus monitoring dashboards that compare transactions to state thresholds.
  • Audit-ready reporting and exemption certificate management.

In my experience, integrating a tax engine early — especially as you scale — reduces manual work and lowers audit exposure. See FinHelp’s articles on Sales Tax Compliance Automation: Tools for Small E-commerce Businesses.

Best practices summary

  • Run a state-by-state nexus review at least quarterly.
  • Treat SaaS taxability as a separate question from nexus; answer both before you decide not to collect.
  • Track customer location using defensible sourcing logic and store supporting evidence.
  • Use voluntary disclosure programs when appropriate to limit exposure.
  • Educate sales, finance, and engineering teams so hires, server placements, or marketing campaigns trigger a nexus review.

Common mistakes to avoid

  • Assuming no physical office means no nexus: economic nexus and other tests can apply.
  • Ignoring marketplace facilitator rules: marketplaces often collect tax on your behalf, but reporting and registration obligations can still exist.
  • Failing to document sourcing and customer location: weak documentation increases audit risk.

Frequently asked questions (brief)

Q: Do I owe sales tax if my customer is in a state that taxes SaaS?
A: Only if you have nexus with that state and the state’s law treats your SaaS offering as taxable. Both conditions must be met.

Q: How far back can a state assess unpaid tax?
A: Statutes of limitations differ; many states can assess 3–4 years, but look-back periods can be extended for fraud or if you didn’t file. A voluntary disclosure agreement can limit the typical look-back.

Q: What if I sell both taxable and non-taxable items on the same invoice?
A: You must separate taxable and non-taxable charges and collect tax only on the taxable portion. Bundling rules vary by state and may require allocation.

Further reading and internal resources

Authoritative sources

  • Tax Foundation — Nexus and economic nexus resources and state-by-state guides: https://taxfoundation.org/ (consult for current state thresholds)
  • U.S. Supreme Court, South Dakota v. Wayfair, Inc., 2018 — the decision enabling economic nexus rules.
  • State Departments of Revenue — for definitive rules on taxability, thresholds, and registration. Check the revenue website for each state where you do business.

Professional note and disclaimer

In my practice advising SaaS businesses, I regularly encounter state-specific nuances that materially change a company’s obligations. This article provides general education, not legal or tax advice. For an actionable nexus analysis tailored to your facts, consult a sales tax professional or state tax attorney.

(Last reviewed: 2025)