SaaS taxability varies dramatically by state, and economic nexus means your obligations likely extend far beyond your home state. Here's how multi-state compliance actually works for software companies.
What You'll Learn
- Why SaaS taxability varies dramatically by state — and why "it depends" is the only honest answer
- How economic nexus creates tax obligations in states where you have no employees or offices
- Which states currently tax SaaS and which don't
- How usage-based pricing and multi-jurisdiction access complicate tax calculations
- How exemption certificate management works specifically for SaaS buyers
- How automation handles the compliance complexity that manual processes cannot
The core challenge: A SaaS company with customers in 40 states may have tax obligations in each, even if it maintains only one office. Each nexus state has distinct taxability rules, exemption certificate requirements, and registration obligations.
Why SaaS is different
Physical products usually have clear taxability. SaaS doesn't — for three reasons.
- States wrote sales tax laws before cloud software existed
- Rules were updated incrementally, creating a patchwork of inconsistent definitions
- Whether your product is "prewritten software," a "digital good," or a "service" can vary by state — and the classification drives taxability
Related resources
Why SaaS Taxability Varies by State
States established sales tax laws before SaaS existed, focusing on physical goods that could be touched, shipped, and assigned a delivery address. Internet-delivered software doesn't fit these frameworks, so states have updated their laws incrementally — resulting in a patchwork of rules that vary significantly across jurisdictions.
The three distinctions states draw most frequently:
Prewritten vs. custom software
Most states that tax software apply sales tax to prewritten or "canned" software — standardized products sold to multiple customers. Custom software, developed for a specific customer's requirements, is often exempt. Many SaaS products fall between these categories, combining a standard platform with significant customization. The classification on this spectrum can determine taxability in states such as Texas and Washington.
Software delivered vs. software accessed
Some states distinguish between software that is downloaded and installed — taxable as tangible personal property — and software accessed remotely via a browser, which may not be taxable as tangible property. New York does not make this distinction and taxes remote access to software as broadly as downloaded software. Other states maintain the distinction, so the same product may be taxable in one state and exempt in another based solely on delivery method.
The "digital goods" classification
Approximately half of U.S. states with sales taxes have enacted digital goods laws that address electronically delivered products, including software, streaming services, and online subscriptions. The scope of these laws varies: some tax digital goods broadly, others apply only to specific categories, and some exempt B2B digital transactions. SaaS companies with enterprise customers must determine whether their product qualifies as a "digital good" in each state and understand the tax implications of that classification.
Economic Nexus for SaaS Companies
Before South Dakota v. Wayfair (2018), SaaS companies without physical offices or employees in a state generally had no sales tax obligation there. After Wayfair, states may require sales tax collection from businesses that exceed an economic threshold — typically $100,000 in annual sales or 200 transactions — regardless of physical presence.
For SaaS companies, this means a business based in California with customers nationwide may have economic nexus in 30 or more states. Each nexus state may require registration, separate tax returns, and compliance with unique taxability and exemption rules.
The registration timeline problem: Economic nexus obligations begin on the day a threshold is crossed, not when registration occurs. A SaaS company that exceeds New York's $500,000 threshold in March but registers in October owes seven months of uncollected tax before filing its first return. Proactive threshold monitoring is essential to avoid retroactive exposure.
P.L. 86-272 does not protect SaaS
Federal Public Law 86-272 limits states from imposing income tax on companies whose only in-state activity is soliciting orders for tangible personal property. This protection does not apply to sales tax, and it does not apply to services or digital products.
For SaaS companies, P.L. 86-272 provides no protection against sales tax obligations in states where economic nexus has been established.
Internet activity and income tax nexus
Some states now consider certain internet activities — customer support through an online portal, cookies placed on customer devices — to be non-solicitation activities that can create income tax nexus, even for companies that otherwise qualify for P.L. 86-272 protection.
SaaS companies with significant digital customer interaction should monitor this area as state guidance continues to evolve.
State-by-State SaaS Taxability Reference
The table below summarizes the current taxability status for major states. Always verify requirements with each state's department of revenue — taxability rules for SaaS and digital products continue to change.
| State | SaaS Taxable? | Notes |
|---|---|---|
| New York | Yes | Taxes remote access to software as broadly as downloaded software; no delivery-method distinction |
| Texas | Yes | Taxes prewritten software; custom software may be exempt; classification of SaaS matters |
| Washington | Yes | Prewritten vs. custom distinction applies; B2B digital goods broadly taxable |
| Pennsylvania | Yes | Cloud-based software taxable as a digital product; applies to SaaS broadly |
| Tennessee | Yes | SaaS taxable as a computer software service |
| Connecticut | Yes | Digital goods and software-as-a-service are subject to sales tax |
| Illinois | Conditional | Taxable if the SaaS provider has a proprietary interest in the software; non-taxable if purely a service |
| California | Conditional | Generally not taxable as a service; may be taxable if there is a transfer of software |
| Massachusetts | Conditional | Taxable when vendor has a proprietary interest; otherwise treated as a non-taxable service |
| Florida | No | SaaS subscriptions generally not subject to Florida sales tax |
| Virginia | No | Access to remotely hosted software not taxable |
| Missouri | No | Not taxable as a service; no tangible personal property transfer |
| New Jersey | No | Exempt under New Jersey's digital goods rules when no tangible software is transferred |
This table reflects general rules as of the article's publication date. State rules for SaaS taxability change frequently. Verify directly with each state's department of revenue before making compliance decisions.
Usage-Based Pricing and Multi-Jurisdiction Access
Standard per-seat or flat-subscription SaaS pricing is already complex. Usage-based pricing — where customers pay based on API calls, transactions processed, data stored, or seats used — introduces further compliance challenges that most tax systems are not designed to address.
Where is the software "used"? Many states source SaaS revenue based on where the customer's employees access the platform. For enterprise customers with employees in multiple states, a single contract may generate taxable sales in several jurisdictions. The seller may owe different amounts to different states from the same subscription, calculated by the proportion of usage in each state.
Apportionment by usage location
This sourcing approach creates data requirements that most billing systems do not natively support. Tracking user locations and calculating the taxable portion of each invoice by state requires either custom billing logic or a tax engine capable of real-time calculations.
A static tax calculation applied at contract start will be inaccurate for most of the billing period as team composition changes.
Variable billing and rate changes
In states with usage-based sourcing, the taxable amount for a customer can change monthly as usage patterns shift, employees relocate, or accounts add and remove users in different locations.
Accurate compliance requires dynamic tax calculation at each billing event — not a fixed rate set at contract start that becomes stale within the first quarter.
Exemption Certificates for SaaS Buyers
Not all SaaS buyers owe sales tax, even in states where SaaS is taxable. Government entities, nonprofits, and businesses purchasing software for resale or direct use in manufacturing or production may qualify for tax exemption. A valid exemption certificate must be on file with the seller.
The certificate complexity for SaaS sellers: The exemption type must often match both the buyer and the specific use case. A manufacturing company purchasing a SaaS platform for production scheduling may have a valid manufacturing exemption, while the same company buying a general productivity subscription may not. The certificate must cover the actual purchase — not just the buyer's general status.
Certificate requirements scale with nexus
Because SaaS companies often have economic nexus in 20 to 40 states, certificate management can scale rapidly. Each new nexus state requires certificates from exempt customers, validated against that state's specific requirements, tracked for expiration per the state's renewal cycle, and retrievable for audit documentation.
For SaaS companies, CertSOLV manages the entire certificate lifecycle across all nexus states — collection, validation, tracking, renewal, and audit export.
Common SaaS buyer exemption types
- Government entities — government purchase certificate specific to the state
- Nonprofits — nonprofit exemption certificate; rules vary significantly by state
- Manufacturers — manufacturing exemption for software used directly in production
- Resellers — resale certificate if the software is incorporated into a taxable product for resale
In all cases, the certificate must describe the purchase in sufficient detail to support the claimed exemption. A generic resale certificate is usually insufficient for SaaS.
How Automation Handles the Complexity
The combination of variable taxability rules, economic nexus obligations in multiple states, usage-based billing, and exemption certificate management makes manual compliance impractical for SaaS companies beyond the early stage. Automation is essential for managing these functions at scale.
Real-time tax calculation at invoice level
Your billing system applies current state taxability rules at the invoice level, in real time. When a customer in California is invoiced for a SaaS subscription, the system determines whether that specific product is taxable in California, applies the correct rate for the customer's location, and accounts for any valid exemption certificate on file — automatically for every invoice, every billing cycle, across every nexus state.
Nexus threshold monitoring
Automated nexus monitoring continuously tracks your sales by state and alerts your team when you are approaching a threshold, before an obligation is created. For growing SaaS companies, this is the most reliable way to stay ahead of registration requirements and avoid the retroactive liability that comes from discovering nexus late.
Exemption certificate automation
When a new customer claims tax-exempt status, an automated system sends a certificate request, guides the customer to the correct state form, validates the certificate against current requirements, and links it to the customer record. Renewal reminders are sent automatically before expiration. If a certificate lapses, the system suspends exempt status until a valid certificate is provided.
Audit-ready documentation
State auditors reviewing a SaaS company's exempt sales expect certificates that match the specific products sold, validated against each state's requirements, with a documented trail of receipt and verification. Automated systems generate this documentation as part of normal operations. Manual processes rarely produce documentation that meets this standard.
The scale problem for SaaS compliance
A SaaS company with 500 customers across 35 nexus states has a compliance surface area that no manual process can reliably cover. Variable taxability rules, monthly billing events, multi-state user apportionment, and 35 separate certificate renewal cycles running simultaneously require systems, not spreadsheets.
Get multi-state SaaS compliance under control
ACTSOLV's AUTOSOLV and CertSOLV work together to handle nexus monitoring, tax calculation, exemption certificate management, and audit documentation across all your nexus states. Schedule a consultation to review your current sales footprint and compliance gaps.
Related Resources
- How Sales Tax Software Monitors Economic Nexus Thresholds and Flags Risks Automatically
- Economic Nexus Created a Certificate Management Crisis
- How to Validate Exemption Certificates: A Step-by-Step Verification Guide
- Exemption Certificate Management: The Complete 2026 Guide
- ACTSOLV SaaS & Digital Products Industry Page
- CertSOLV: Sales Tax Exemption Certificate Management Software
Frequently Asked Questions About SaaS Sales Tax
Is SaaS always taxable?
No. SaaS taxability varies significantly by state. Some states tax SaaS broadly, some only under specific conditions, and some do not tax it at all. For example, Florida does not apply sales tax to SaaS subscriptions, while New York taxes remote access to software as broadly as downloaded software. The answer depends on the state, the product, and sometimes the buyer's specific use case.
Does my SaaS company need to collect sales tax if we have no offices outside our home state?
Potentially, yes. Economic nexus rules established by South Dakota v. Wayfair (2018) allow states to require tax collection from out-of-state sellers who exceed a sales or transaction threshold, typically $100,000 in annual sales. A SaaS company with customers nationwide may have registration obligations in 30 or more states, regardless of office location.
How do I determine where my SaaS product is "used" for tax purposes?
Most states source SaaS revenue based on where the customer's users access the software. For enterprise customers with employees in multiple states, a single subscription may be apportioned across several states based on usage proportion. Determining this requires tracking user location data by account and applying it to each billing event, which often requires integration with an external tax engine.
What type of exemption certificate do SaaS buyers need to provide?
It depends on the buyer's exemption basis and the state. A government buyer needs a government purchase certificate, a nonprofit needs a nonprofit exemption certificate, and a manufacturer buying software for production may need a manufacturing exemption certificate specific to that state. In all cases, the certificate must describe the purchase in sufficient detail to support the claimed exemption — a generic resale certificate is usually insufficient for SaaS.
How does usage-based pricing affect sales tax?
Usage-based pricing complicates sales tax because the taxable amount can change each billing cycle as usage patterns shift. In states that source SaaS revenue based on user location, a customer's tax calculation may also change monthly as team composition changes. Accurate compliance requires dynamic tax calculation at each billing event rather than a fixed rate at contract start.
How does Illinois's 2026 threshold change affect SaaS companies?
Illinois eliminated its 200-transaction threshold effective January 1, 2026, making sales volume the sole measure of economic nexus. SaaS companies with many small Illinois customer accounts that previously fell under the transaction threshold without exceeding $100,000 in sales may now avoid nexus. Companies should review their Illinois sales data against the new sales-only threshold.
