For years, the SaaS state-tax playbook was simple: build the product, grow the customer base, and worry about sales tax only with a physical presence in a handful of states. That approach is becoming harder to defend.
As state and local tax rules continue to evolve, more states are looking closely at digital products, software subscriptions, platform fees, data services, and bundled software-plus-service offerings. For SaaS companies, the result is a more complex compliance environment — one where the tax treatment can vary significantly depending on the state, the customer, and how the product is packaged and sold.
If your company has not reviewed its state and local tax footprint recently, 2026 is a good time to take a fresh look.
01The 2026 SaaS tax landscape: what is changing?
State tax rules rarely change in a perfectly uniform way. In some cases legislatures update statutes; in others, tax departments clarify their positions through guidance, audits, administrative rulings, or enforcement activity.
For SaaS companies, that means the practical answer to "Is our product taxable?" may depend on more than whether the company sells software. States may consider:
- Whether customers download software or access it remotely
- Whether the platform performs automated functions, analytics, or data processing
- Whether human services are bundled with software access
- Whether implementation, support, consulting, or customization fees are separately stated
- Where customers use the product
- Whether the company has crossed economic nexus thresholds in a state
02Three states to watch
Three states continue to draw attention from SaaS companies and their advisors: Washington, Texas, and Tennessee.
Washington
Scrutiny around digital and bundled offerings
Washington has historically taken an assertive approach to taxing many digital products and software offerings, including certain remotely accessed software and digital automated services. The harder question is often how the state treats contracts that bundle multiple components:
- Software platform access
- Automated data analytics
- Implementation or onboarding
- Human consulting or managed services
- Premium support or enterprise add-ons
If these are sold together under a single contract price, there may be greater risk the state treats the full charge as taxable. Companies with enterprise contracts should consider whether their invoices and agreements clearly separate taxable and non-taxable elements where appropriate.
Texas
The importance of classification
Texas has long been a key state because of its approach to certain technology and data-related services — some SaaS or platform-based services may be analyzed under data processing or other service categories. The challenge is that modern products don't always fit neatly into older tax categories: AI-enabled tools, workflow automation, analytics engines, and hybrid software-service models all raise classification questions.
The takeaway is straightforward: product classification matters. A platform marketed as "software" may be viewed differently by an auditor based on what it actually does, how it is delivered, and how the contract describes the service.
Tennessee
A state to revisit as rules evolve
Like many states, Tennessee's treatment of remotely accessed software and digital offerings has developed over time, and companies selling into the state should not assume prior conclusions remain accurate indefinitely. If your business has Tennessee customers, remote employees or contractors, significant sales volume, or changing product offerings, it may be time to revisit whether registration, collection, or documentation obligations have changed.
Tennessee is an example of why SaaS taxability should be reviewed periodically — especially when scaling, expanding sales territories, or preparing for financing or acquisition.
03Why economic nexus matters for SaaS companies
Many early-stage founders still assume sales tax obligations arise only with an office, employees, or servers in a state. That is no longer a safe assumption. Under economic nexus rules, a company may be required to register, collect, and remit sales tax once it exceeds a state's revenue or transaction threshold — a dollar amount of sales, a number of transactions, or both.
For SaaS businesses these thresholds can be crossed quickly, because subscription revenue is recurring and customer growth scales across many states without any physical expansion. A company can develop obligations in states where it has no office, no employees, no property, no local bank account, and no intentional tax presence. The sales footprint alone may be enough.
04The cost of waiting
Sales tax exposure can become expensive because it is often cumulative. If a company should have been collecting tax but did not, the unpaid tax may become the company's liability — along with potential interest and penalties. And the issue is not limited to state notices or audits; it can affect strategic transactions.
Fundraising and M&A diligence
Institutional investors and acquirers often review sales tax compliance during diligence. Unaddressed exposure across multiple states may lead to:
- Purchase price adjustments
- Escrow or indemnity demands
- Delayed closing timelines
- Additional diligence requests
- Pressure to complete voluntary disclosures or remediation before closing
Even if the company ultimately resolves the issue, the process can create friction at exactly the wrong time.
Cash flow and customer experience
Retroactively addressing sales tax creates practical challenges too. Companies may need to decide whether to absorb historical exposure, recover amounts from customers, update billing systems, or change invoice presentation — each with financial and relationship implications. A proactive approach is almost always easier than a last-minute cleanup.
05A practical action plan
SaaS sales tax compliance does not need to derail growth. The goal is a scalable process that matches the company's stage, risk profile, and expansion plans.
-
Run a nexus review
Review trailing-12-month sales by state — revenue and transaction counts — and identify states where you've crossed, or are approaching, economic nexus thresholds. Include:
- Subscription revenue
- Usage-based fees
- Implementation or onboarding charges
- Support or managed service fees
- Marketplace or reseller sales, if applicable
-
Revisit product taxability
Don't assume all SaaS is treated the same. Evaluate how each state may classify your product based on what it does and how customers access it: Is it remotely accessed software? Does it perform data processing, analytics, automation, or storage? Are professional services bundled? Are implementation or consulting fees separately priced?
-
Review contracts and invoices
Enterprise contracts create complexity by combining deliverables. Clean language and invoice presentation help reduce ambiguity. Consider whether agreements clearly separate software subscription, implementation, consulting, training, support, and custom development. Clear itemization doesn't solve every issue, but it makes the analysis more supportable.
-
Automate where appropriate
Manual tracking doesn't scale. As volume grows, integrate tax automation into billing and accounting — address validation, real-time calculation, exemption certificate management, filing calendars, return preparation, and remittance. Automation isn't a substitute for analysis, but it applies your decisions consistently.
-
Plan before a financing or exit
If a round, acquisition, or major transaction may be on the horizon, address exposure early. Waiting until diligence begins limits options. A pre-transaction review identifies where registration may be required, historical exposure estimates, voluntary disclosure options, and the documentation buyers will ask for.
The bottom line
The SaaS tax environment is becoming more complex, and states are paying closer attention to digital revenue streams. The right response is not panic — it is preparation. By reviewing nexus, confirming product taxability, cleaning up contracts, and implementing scalable tools, SaaS companies can reduce risk while continuing to grow.
Ludmila suggests five questions to ask now
Where are we selling? Where have we crossed economic nexus thresholds? How are our products and services classified? Do our contracts and invoices support the intended tax treatment? Do our billing systems support multi-state compliance?
A focused review today can help protect runway, improve investor readiness, and prevent sales tax from becoming a distraction during your next stage of growth.
This article is general information, not tax or legal advice. State and local taxability of software is detailed, fact-specific, and varies by jurisdiction and product. Talk to us before relying on a particular classification, registration, or remediation approach.