DIGITAL TAX · DIGITAL BUSINESS TAXINS-20240731-01

SaaS Sales Tax: Incorporation Is Not the Nexus Analysis

US sales-tax exposure for SaaS depends on nexus, product taxability, customer location and marketplace rules. California and New York show why the state of incorporation is not the answer.

Libertax editorial visualization for “SaaS Sales Tax: Incorporation Is Not the Nexus Analysis”
A Libertax editorial composition about SaaS Sales Tax: Incorporation Is Not the Nexus Analysis.

KEY TAKEAWAYS

KEY POINT 01Incorporation is not the sales-tax map. Economic activity and customer-market connections can create state obligations outside the formation state.
KEY POINT 02Nexus and taxability are separate questions. A seller can have sufficient nexus with a state while the particular SaaS product is non-taxable there, or vice versa.
KEY POINT 03"SaaS" is not one national tax category. California and New York illustrate why product delivery, software classification, customer location and marketplace rules must be analysed state by state.

A software company can be incorporated in Wyoming, Delaware or New Mexico and still have sales-tax questions in California, New York or another state.

That is because US sales tax does not begin with the state on the certificate of formation.

For a SaaS business, the useful sequence is:

product → customer → nexus → taxability → sourcing → marketplace role → registration and filing

California and New York provide a particularly useful contrast because similar digital access can receive materially different sales-tax treatment.

Three key takeaways

  • Incorporation is not the sales-tax map. Economic activity and customer-market connections can create state obligations outside the formation state.
  • Nexus and taxability are separate questions. A seller can have sufficient nexus with a state while the particular SaaS product is non-taxable there, or vice versa.
  • “SaaS” is not one national tax category. California and New York illustrate why product delivery, software classification, customer location and marketplace rules must be analysed state by state.

Start with four different questions

Founders often compress US sales tax into one question:

“Do I have to charge sales tax?”

That question is too early.

The analysis needs at least four stages.

1. Nexus

Does the seller have enough connection with the state for that state to impose collection or registration obligations under its current rules?

Physical presence can matter.

After South Dakota v. Wayfair, economic activity can matter as well.

State thresholds and rules are not uniform.

2. Taxability

Assuming the state has jurisdiction over the seller, is the actual product or service taxable?

This is where SaaS becomes difficult.

States classify electronically delivered software, remote access, digital goods, information services and related services differently.

3. Sourcing

Which state is treated as the place of the sale or use?

For digital products, billing address, user location, place of use or another sourcing rule can matter depending on the state and product.

4. Collection channel

Did the seller make the sale directly or through a marketplace facilitator?

Marketplace laws can change who collects and remits without necessarily eliminating all seller obligations.

These are connected questions.

They are not the same question.

California: electronic delivery can be non-taxable

California’s Department of Tax and Fee Administration distinguishes sales of tangible personal property from certain electronically transmitted products.

Its current publication on internet sales explains that electronically transmitted software, data and digital goods can be non-taxable when transferred electronically rather than on tangible media, subject to the actual facts and exceptions.

The lesson is not “SaaS is tax-free in California.”

That phrase is too broad.

A software company may sell implementation, hardware, bundled products or other items that require separate analysis.

The durable point is that electronic delivery and product classification matter.

A seller can have California nexus and still need to ask whether the specific digital supply is taxable.

New York: remote access can be taxable software

New York demonstrates the opposite danger of using one state’s conclusion nationally.

The New York Department of Taxation and Finance treats prewritten computer software as taxable tangible personal property for sales-tax purposes.

Its current software bulletin explains that this can include remote access: a customer can obtain the right to use prewritten software without receiving a physical copy, and the tax analysis can follow where the purchaser uses or directs the use of the software.

New York advisory opinions also illustrate that access to a web portal containing prewritten software can be taxable while separately stated custom programming, data entry or training may receive different treatment depending on the facts.

So the same commercial description — “subscription SaaS” — can hide different legal components.

A simple two-state scenario

Assume a foreign-owned US software company sells one cloud-based business application.

It has no office in California or New York.

Customers access the software online.

The company has significant sales into both states.

A founder might ask:

“The company is incorporated in Wyoming. Which state’s sales tax applies?”

The Wyoming formation fact does not answer it.

For California, the company must separately analyse whether it has nexus and then whether its electronically supplied product is taxable under California rules.

For New York, it must separately analyse nexus and the state’s treatment of remote access to prewritten software, then determine where customer use is sourced.

The same invoice can therefore require different state analysis even though the company, website and software are identical.

Nexus is not taxability

This distinction prevents two opposite mistakes.

Mistake one

“We crossed the state threshold, so every sale is taxable.”

Not necessarily.

Crossing a nexus threshold can create an obligation to register or analyse collection, but the product still has to be taxable under that state’s law.

Mistake two

“Our SaaS is non-taxable in this state, so nexus does not matter.”

Also unsafe.

A business can have state registration or filing questions connected with its activity even when a particular category of sales is exempt or non-taxable.

The sequence should remain disciplined:

nexus first, product treatment second, sourcing third, compliance consequence fourth.

Marketplace facilitators create another layer

Digital businesses increasingly sell through app stores, platforms and marketplaces.

Many states impose collection duties on marketplace facilitators for qualifying facilitated sales.

New York, for example, maintains specific marketplace-provider guidance.

That can reduce direct collection work for a seller.

It does not justify deleting marketplace sales from the tax map.

The seller still needs to understand:

  • which sales the facilitator is responsible for;
  • which sales remain direct;
  • whether marketplace sales count toward state thresholds;
  • what records or certificates are available; and
  • whether the seller has separate filing obligations.

Marketplace collection is a compliance allocation.

It is not a universal exemption from sales-tax analysis.

The strongest objection: a two-state article cannot solve US sales tax

Correct.

It should not pretend to.

California and New York are illustrations of the underlying mechanism, not a national matrix.

Other states can classify SaaS differently, use different thresholds, impose local taxes, define sourcing differently or apply exemptions for business use, resale or other categories.

A serious nationwide analysis requires a current state-by-state matrix.

The useful conclusion from two states is narrower:

The state of incorporation tells you almost nothing about the taxability of SaaS sold to customers across the United States.

That is the myth this article resolves.

The practical SaaS sales-tax framework

For each state where sales are material, complete one row with seven fields.

Product. What exactly receives consideration — remote software access, digital content, implementation, support, hardware, data or a bundle?

Customer. B2B, B2C, reseller, exempt organisation or another category?

Nexus. Physical, economic or other state connection under current law.

Taxability. How does that state classify the actual product?

Sourcing. Where is the customer or use treated as located?

Marketplace. Who is legally responsible for collection on facilitated sales?

Compliance. Registration, collection, filing, certificates and recordkeeping.

Then repeat the exercise state by state.

This is more work than checking the formation certificate.

It is also the correct map.

The broader international problem

The issue matters especially for non-US founders.

A person can be tax resident outside the United States, own an LLC in one state and sell digital services nationwide.

Federal entity classification is one question.

State income or franchise taxes are another.

Sales tax is another.

The owner’s country may have its own VAT or tax treatment again.

International founders therefore need to resist one of the most persistent structural shortcuts:

company jurisdiction ≠ customer-tax jurisdiction

For digital businesses, customers can create tax geography even when the company has no physical shopfront.

Sources

Disclaimer

This article provides general information only and does not constitute US state tax or legal advice. Nexus thresholds, SaaS taxability, sourcing, exemptions and marketplace rules vary by state and can change. California and New York are illustrations only; each relevant state and each product component should be checked before registration or collection decisions are made.