How do you know whether your SaaS subscription is taxable in a state where you have nexus?

Nexus and taxability are separate tests

Crossing a threshold or having presence tells you a state can require you to register. It says nothing about whether your product is taxable there. Software delivered as a subscription is one of the least consistent categories in state tax law: some states treat it as taxable prewritten software, some as a taxable data processing or information service, some exempt it as a nontaxable service, and some tax it only when the buyer is a business, or only when the buyer is an individual. Related: What should a small software company do when a remote employee moves to a new state?

The inconsistency exists because the taxing categories were written long before subscription software existed, and each state has squeezed it into whatever definition was closest. That produces strange results. A state may tax the same product differently depending on whether the customer downloads any component, whether a person provides support as part of the plan, or whether the subscription includes storage or a communication feature. Your product's real feature set decides the answer, not the label on your pricing page.

Keep reading: Economic Nexus: A State by State Reality, How to Know When You Are Approaching Nexus, Registering in a New State, Step by Step. See how ShopTaxie helps you sales tax nexus tracking and filing reminders.

How to research a single state honestly

Start with the department of revenue's own material: published rulings, bulletins, and the FAQ pages on software, digital products, and services. Then read how the state defines tangible personal property, prewritten software, and data processing, because those definitions are what an auditor will apply. Match your product's actual features to those definitions rather than to how your marketing describes it.

Where the guidance is ambiguous, look for letter rulings on products similar to yours, and consider requesting one for your own product if the tax at stake is large enough to justify the wait. Document what you found, when you found it, and where. If your product changes materially, for example by adding a downloadable desktop component or an on-premise option, redo the analysis for any state whose answer turned on those details.

Sourcing and customer type complicate it

Even in a state that taxes your product, the answer depends on where the sale is sourced. For subscriptions, most states source to where the customer uses the service, usually the billing or primary business address, but customers with users in several states may require an allocation across those states. Getting customer addresses right in your billing system is where taxability actually starts; an address you never validated becomes a sourcing error you never noticed. Related: What should a small business do when a state sends a nexus questionnaire out of the blue?

Customer type matters too. Business customers may hold exemption certificates for resale or a specific use, nonprofits and governments often qualify for exemptions, and resellers may be buying for resale. Collect certificates at signup or renewal, store them where you can retrieve them by customer, and mark the customer exempt in billing. Without a valid certificate on file, the state expects tax, and an auditor will not accept a customer's verbal assurance in place of paper. Related: Multi State Selling Without the Panic

Building a taxability matrix you can maintain

Keep a simple matrix: state, product line, taxable or exempt, source of the conclusion, and date checked. Give bundled offerings their own rows, because a bundle of taxable and exempt items can become fully taxable in some states if the price is not separately stated. Review the matrix annually, and whenever you launch a new product line or change how an existing one is delivered.

Tie the matrix to your nexus tracker so that on the day you cross a threshold in a state, you already know whether to switch tax on there. That pairing is what turns a scramble into a checklist. It is also the piece most small SaaS teams skip, because nexus tracking feels urgent and taxability research feels academic. An auditor sees it the other way around. Related: Economic Nexus: A State by State Reality