Most SaaS companies discover their sales tax exposure the hard way. A routine audit, a state notice, a new CFO who asks whether the company has been collecting in states where it crossed nexus thresholds two years ago. The numbers are often uncomfortable. Back taxes, interest, and penalties can accumulate quietly while a company is focused on growth, and the patchwork of state rules makes it genuinely difficult to know where you stand without a systematic approach.
The underlying problem is not a lack of effort. It is a lack of framework. SaaS sales tax looks simple at first glance and reveals its complexity only when you go to apply it. Does your product count as taxable software or a nontaxable service? Which state's rules apply when your customer has users in six states? Does selling into a state where you have no office actually trigger an obligation?
These questions do not have universal answers. What they have is a set of core concepts that determine the answer in any specific situation. Master these eight and you will be equipped to read a state's sales tax guidance, evaluate your exposure, and make defensible compliance decisions.
Nexus is the legal connection between your business and a state that requires you to collect and remit that state's sales tax. Before 2018, nexus meant physical presence: offices, employees, data centers. Remote sellers with no physical footprint could sell into any state without triggering a tax obligation.
The Supreme Court's decision in South Dakota v. Wayfair changed that. The Court held that economic activity alone, specifically exceeding a threshold of revenue or transaction volume within a state, is enough to establish nexus. Every state with a sales tax now uses economic nexus as its primary framework for remote sellers.
The most common threshold is $100,000 in annual sales to customers in a state. The 200-transaction test that many states added alongside the revenue threshold is being phased out: Illinois removed it effective January 1, 2026, following similar moves by Alaska and Utah. Physical nexus still exists and still matters. If you have employees, contractors, or infrastructure in a state, that alone creates an obligation regardless of revenue.
For SaaS companies, nexus analysis is a recurring exercise, not a one-time check. Every new market entered, every sales hire made in a new city, and every year of growth can change the picture.
Having nexus in a state does not automatically mean you owe tax there. You only have a collection obligation if the product you sell is taxable under that state's law. And for SaaS, taxability is genuinely unsettled across the country.
As of 2026, roughly half of U.S. states tax SaaS in some form. The other half either exempt it explicitly or have not addressed it clearly, which creates its own kind of risk. States that have issued guidance treat SaaS in different ways. Some classify it as taxable tangible personal property under legacy software rules. Some treat it as a taxable digital service. Some exempt it because services generally are not taxable in that state. A few apply different rules depending on whether the customer is a business or a consumer.
New York taxes SaaS as prewritten software under its broad interpretation of tangible personal property. California generally does not tax SaaS because it is not transferred on a physical medium. Texas taxes SaaS because it classifies remote access to software as a taxable data processing service. Louisiana expanded its digital tax rules in 2025 to include SaaS and IT services.
Maryland now applies a 6% rate to SaaS sold for individual use and a 3% rate to the same product sold for use in an enterprise computer system, effective July 2025. That distinction between B2C and B2B treatment, different rates for the same product depending on who is buying it, is becoming more common and requires precise invoicing and classification at the transaction level.
Once you know a state taxes SaaS, the next question is which state's rate to apply to a given transaction. Sourcing rules answer this. For SaaS, two frameworks are in use.
Destination-based sourcing taxes the transaction where the customer uses the software. This is the majority approach and the one the Streamlined Sales and Use Tax Agreement recommends for digital products. Under destination sourcing, a sale to a company headquartered in Ohio is taxed at Ohio's rate, regardless of where your servers are.
Origin-based sourcing taxes the transaction where the seller is located. This approach is less common for digital products but still applies in some states for some categories.
The practical complexity for SaaS is that your customer may have users distributed across multiple states. A single enterprise contract covering 500 users in eight states may require you to apportion the subscription revenue across those states and apply each state's rate to the appropriate portion. This is not a theoretical edge case. It is the reality for any SaaS company with enterprise customers, and it is one of the primary reasons manual tax calculation breaks down at scale.
Many B2B SaaS transactions that would otherwise be taxable qualify for exemption. The most common scenario: a business purchasing your software to resell it, bundle it into their own product, or use it in a qualifying manufacturing or research process may be entitled to purchase tax-free. But the exemption is not automatic. You, the seller, are responsible for collecting and retaining valid exemption documentation.
An exemption certificate is a form issued by the buyer that certifies their purchase qualifies for a specific exemption under state law. The most widely used is the Streamlined Sales Tax exemption certificate, accepted in member states. Individual states also have their own certificate formats.
If you accept a valid certificate in good faith, you are relieved of the obligation to collect tax on that transaction. If you cannot produce the certificate during an audit, the liability typically reverts to you. Exemption certificates expire, and the rules on how long they remain valid vary by state. A certificate management process is not optional for SaaS companies with significant B2B revenue.
Common exemption categories relevant to SaaS include resale, manufacturing, nonprofit, government, and educational institution exemptions. Not every category applies in every state, and the definitions of qualifying use vary.
Once you have nexus and taxable sales in a state, you are required to register, collect, and remit. Remittance happens on a schedule: monthly, quarterly, or annually, depending on your sales volume in that state. States assign filing frequency based on how much tax you are expected to collect. Higher volume means more frequent filing.
Filing frequency can change as your business grows. A company that files quarterly in a state one year may be required to file monthly the following year once its revenue there crosses a threshold. If the state notifies you of a frequency change and you miss it, late filing penalties apply.
Each state has its own filing deadlines, forms, and remittance methods. Some states participate in the Streamlined Sales Tax program, which simplifies registration and filing across member states through a single registration system. But many states, including several with significant SaaS markets, are not SST members and require separate registrations and filings.
Most SaaS companies do not sell just software. They sell implementation services, onboarding, training, support, professional services, and API access alongside the core product. How these components are packaged and priced has direct tax consequences.
If a taxable SaaS product and a nontaxable service are sold together for a single price, many states will tax the entire bundle. This is called the bundling or mixed transaction problem. The taxable component can pull the nontaxable component into taxability.
States handle this differently. Some require the seller to separately state nontaxable components on the invoice and maintain documentation that the stated price reflects fair market value. Others apply an all-or-nothing rule. A few use a predominant purpose test: if the primary purpose of the bundle is the taxable product, the whole bundle is taxable.
For SaaS companies running usage-based pricing models, the analysis becomes more complex because the effective mix of taxable and nontaxable usage may change month over month. Getting bundling right requires both product and finance teams to understand how different pricing structures interact with the tax rules in each state where you have customers.
Use tax is the counterpart to sales tax. When a seller does not collect sales tax on a taxable transaction, the buyer is generally responsible for self-assessing and remitting use tax to their state. For SaaS companies operating in states where they have nexus, this is not directly your problem. But it becomes relevant in two ways.
First, if you are buying software or digital services from a vendor that does not collect tax in your state, your company may owe use tax on those purchases. Finance teams at SaaS companies often overlook this because they are focused on collecting tax from customers, not on their own procurement. A use tax audit can surface years of uncollected liability on vendor payments.
Second, when you sell into a state where you do not yet have nexus, your customers there technically owe use tax on your product. Many do not pay it. As your revenue in that state grows and you cross the economic nexus threshold, your obligation to collect shifts from zero to full. Understanding this transition point matters for planning your registration timeline.
State-level analysis is necessary but not sufficient. Many states allow counties, cities, and special districts to impose their own sales and use taxes on top of the state rate. For SaaS, local jurisdictions can create obligations that exist independently of state treatment and that follow different rules entirely.
Chicago is the most-cited example. Illinois does not impose a state sales tax on SaaS. But the City of Chicago imposes a Personal Property Lease Transaction Tax on cloud-based services and SaaS accessed by customers in the city. That rate increased to 15% as of January 1, 2026. A SaaS company with Chicago-based customers can owe Chicago city tax even while owing nothing at the Illinois state level.
Home rule cities in states like Colorado, Alabama, and Alaska have authority to administer their own sales taxes independent of the state system. Compliance in these jurisdictions often requires separate registrations, separate filings, and specific rate lookups at the address level rather than the state level.
Local jurisdiction complexity is one of the strongest arguments for automated tax calculation in SaaS. Manually maintaining accurate local rate data across thousands of taxing authorities is not a viable strategy for a growing company.
These eight concepts do not operate in isolation. They layer on top of each other. Nexus determines whether you have an obligation at all. Product taxability determines whether that obligation applies to your specific product. Sourcing rules determine which jurisdiction's rates apply. Exemptions reduce the taxable base. Bundling affects how your product structure interacts with the taxable base. Filing frequency governs the operational rhythm of remittance. Use tax fills the gaps where sales tax collection has not yet been triggered. And local jurisdictions add a layer of granularity that state-level analysis alone cannot capture.
Every SaaS sales tax question, however specific, traces back to one or more of these eight concepts. A new state expanding its digital tax rules matters because it changes the product taxability answer. A new enterprise customer in a different state matters because it may affect your sourcing obligations. A contract restructuring matters because of bundling rules.
The companies that manage sales tax well are not the ones with the most tax lawyers. They are the ones that have built their compliance infrastructure around a clear understanding of the underlying framework and invested in the automation needed to apply that framework at scale.
Is your SaaS sales tax strategy built for 2026? Every month you wait, your nexus footprint grows and your audit exposure with it. CereTax helps SaaS finance teams get compliant faster with automated tax calculation, real-time rate updates, and expert guidance built for the way software is actually sold.
👉🏻  Book a Strategy Call with CereTax to simplify SaaS sales tax compliance across subscriptions, refunds, exemptions, and multi-jurisdiction billing.
