Background and why this matters

States set their own sales-tax rules, and over the past decade many have expanded or clarified their laws to include digital goods and services. That means two businesses offering the same SaaS product can have different tax obligations depending on where their customers live. In my 15 years working with software companies, I’ve seen the most costly issues come from missed registrations and incorrect taxability decisions that trigger audits and back taxes.

How compliance works (practical steps)

  • Determine nexus: States can require you to register if you have physical presence (employees, servers, offices) or economic connections (sales thresholds or number of transactions). Many states use economic thresholds (commonly $100,000 in sales or 200 transactions), but the exact trigger varies — check state rules before assuming you’re exempt (see Tax Foundation for state-by-state summaries).
  • Classify the product: States differ on whether SaaS, digital downloads, streaming, and subscriptions are taxable. Classification often depends on statutory definitions and administrative guidance from the state department of revenue.
  • Register for permits: Once nexus exists, register for a sales-tax permit with the state revenue department and set up filing frequencies (monthly, quarterly, or annual). See state-specific steps in our guide to State Sales Tax Permits.
  • Collect based on sourcing rules: States use destination-based sourcing (tax rate based on customer location) or origin-based sourcing (seller location). For most remote SaaS sales, destination sourcing applies.
  • File and remit: Submit returns and pay collected tax on the schedule required. Keep records of exemption certificates, refunds, and customer addresses.
  • Monitor changes: States frequently update guidance and laws that affect taxability and thresholds.

Key compliance concepts

  • Economic nexus: A sales or transaction threshold that creates an obligation to collect sales tax in a state.
  • Taxability determination: Whether the state treats a service or digital product as taxable.
  • Marketplace facilitator rules: Platforms may be required to collect and remit tax for sellers listed on the platform.
  • Sourcing rules: Determines which jurisdiction’s rate applies to a sale.

Examples and common traps

  • Example: A SaaS company with 15,000 customers nationwide may not have physical presence in most states but can create nexus if sales into a state exceed its economic threshold. If that state taxes SaaS, the company must register and collect tax there.
  • Common trap: Treating all SaaS as non-taxable because there is no tangible product. Many states explicitly tax delivered software or subscription access.
  • Audit risk: States may audit prior years; failure to register or collect can lead to back taxes plus interest and penalties.

Who is affected

Any business selling SaaS, digital subscriptions, hosted software, streaming access, or downloadable digital goods to customers in the U.S. should evaluate state filing obligations. This includes startups, enterprise SaaS vendors, digital marketplaces, and membership platforms.

Practical checklist (implement now)

  1. Map customers by state and calculate gross receipts and transaction counts for the last 12 months.
  2. Review taxability guidance for each state where you exceed economic nexus thresholds.
  3. Register for sales tax permits where required (see our State Sales Tax Permits: Registration and Compliance Steps).
  4. Implement a tax engine or service (e.g., Avalara, TaxJar) that supports SaaS tax rules and nexus tracking.
  5. Capture and store exemption certificates for exempt customers.
  6. Reconcile collections monthly and file timely returns.
  7. Maintain documented policies and a versioned taxability matrix for product offerings.

Professional tips

  • Use automation: Tax engines reduce manual errors and help with multi-state rate and nexus tracking.
  • Start early: Register proactively when you approach thresholds—voluntary disclosure agreements exist in many states that limit penalties for coming forward.
  • Keep product documentation: Document feature sets and delivery methods; these details often determine taxability.
  • Consult a specialist: In my practice, a short engagement with a sales-tax specialist often saves more than the cost of ignoring a complex state rule.

Common mistakes to avoid

  • Assuming SaaS is always exempt.
  • Relying solely on customer self-certification without collecting valid exemption certificates.
  • Ignoring marketplace facilitator rules that may shift collection responsibility.
  • Not tracking changes in sourcing rules or new economic nexus legislation.

Further reading and internal resources

Authoritative sources

  • Tax Foundation — state sales tax and digital goods overviews (https://taxfoundation.org)
  • State departments of revenue — check the revenue site for each state where you sell for authoritative rules (example: New York Department of Taxation and Finance).

FAQs

  • Are SaaS providers always required to collect sales tax?
    No — taxability varies by state. Determine nexus and then check whether that state taxes the specific service.

  • What are the typical economic nexus triggers?
    Many states use thresholds such as $100,000 in annual sales or 200 transactions, but exact rules differ by state. Always verify each state’s statute or guidance.

  • What if I discover I didn’t collect tax in prior periods?
    Consider voluntary disclosure programs in the states where exposure exists; these can limit penalties. Engage a tax professional to compute exposure and negotiate terms.

Disclaimer

This article is educational and not legal or tax advice. For tailored guidance, consult a state sales-tax specialist or licensed tax advisor.