A software company does not need an office in another state to create a tax obligation there.
A remote developer in Texas, a salesperson in New York, and a customer base spread across a dozen states can each create new registration, filing, withholding, or collection duties. For SaaS companies that expand nationally without signing a lease, this happens earlier than most founders expect and is usually discovered late.
The difficulty is that there is no single test. Income tax, franchise tax, gross receipts tax, sales tax, and payroll obligations follow different rules, and software is not taxed consistently across states. A company can be protected from one tax in a state while fully exposed to another. Multi-state tax nexus for software companies therefore means looking at where the business has people, customers, revenue, and activity, not simply where it is incorporated.
Tax nexus is the connection between a business and a state that allows the state to impose a tax or compliance obligation. Businesses have historically associated it with physical presence, which is no longer a complete way to evaluate exposure. In South Dakota v. Wayfair, the U.S. Supreme Court rejected the rule that physical presence was required before a state could impose sales tax collection obligations on a remote seller.
One point drives everything that follows: multi-state tax nexus for software companies is tax-specific, not company-specific. Establishing nexus does not mean the company owes every tax that state imposes. Each tax has to be analyzed separately.
There is no universal revenue figure that tells a software company when it becomes taxable everywhere. Four categories of triggers matter.
Potentially, yes. This is the most consequential remote employee tax nexus issue facing software companies in 2026.
Consider a San Francisco SaaS company with one office and 25 employees that hires a developer in Austin, a customer success manager in Denver, and a salesperson in New York. It still has one office, but its tax footprint has changed considerably.
California illustrates the point from the other direction. The Franchise Tax Board states that an out-of-state business can be doing business in California through employees who work from their California homes, even when its California property, payroll, and sales fall below the state’s thresholds. A California company should expect other states to reason the same way about its remote hires.
Three obligations are easy to miss:
Remote employee tax nexus is easy to create and easy to overlook. Adding an employee in a new state should prompt a tax review before payroll onboarding, not after.
It can, but SaaS tax nexus turns on two separate questions, asked in order. Crossing a threshold and selling something taxable are not the same thing. First: does the company have sales tax nexus in this state? Then: does that state tax the specific software, SaaS, or service being sold?
States do not answer the second question consistently.
State | How SaaS is generally treated for sales tax in 2026 |
California | Generally not taxable. The CDTFA describes software delivered solely electronically, with no transfer of tangible personal property, as not subject to sales tax. |
Texas | Taxable as a data processing service, with a statutory 20 percent exemption, so tax applies to 80 percent of the charge. |
New York | Taxable. Remotely accessed prewritten software is treated as taxable software rather than a nontaxable service. |
Colorado | Not taxable at the state level in 2026, but taxable in Denver and other home-rule cities. H.B. 26-1223 makes software taxable statewide from January 1, 2027. |
Treatment varies by state and changes frequently. This table is illustrative and is not a compliance determination.
Colorado captures two traps at once: a company can have no state obligation alongside a real obligation in a self-administered city, and a state’s answer today may not be its answer next filing season.
Bundling adds another layer to economic nexus for software companies. When one contract combines SaaS access, implementation, support, and custom development, many states tax the whole charge if taxable and nontaxable components are not separately stated. Invoice design is a tax decision.
Treating nexus as a single concept is one of the most common mistakes software companies make. SaaS tax nexus for sales tax purposes and income or franchise tax nexus are separate tests with separate triggers.
Issue | Income or Franchise Tax Nexus | Sales Tax Nexus |
What can trigger it? | Employees, property, business activity, and state factor presence standards | Physical presence or economic nexus thresholds |
Do remote employees matter? | Yes, potentially | Yes, potentially |
Is SaaS automatically taxable? | Not the central question | No, taxability varies by state |
Does a loss year end the obligation? | No. Minimum and franchise taxes apply regardless of profit | No. Sales tax is collected from the customer, not paid from profit |
Does one rule apply nationally? | No | No |
The loss-year row matters more than it looks. California charges an $800 minimum franchise tax to every corporation and LLC doing business in the state regardless of income, and other states impose fixed minimums or gross receipts taxes that ignore profitability. Uncollected sales tax is not a share of profit at all. It is money that should have been collected from customers and now has to be funded by the company.
Software companies should be cautious about assuming P.L. 86-272 protects them.
Public Law 86-272 limits a state’s ability to impose a net income tax when a company’s only in-state activity is soliciting orders for sales of tangible personal property. Two constraints in that rule cut against software businesses. A SaaS subscription is not tangible personal property, and the protection reaches certain net income taxes only, not sales tax, payroll obligations, gross receipts taxes, or state minimums. A company fully protected in California still owes the $800 minimum and still files.
The scope of the protection is also contested. In 2021, the Multistate Tax Commission took the position that ordinary internet activities, including placing certain cookies and providing post-sale chat support, exceed mere solicitation. States adopting that view have seen mixed results in court. New York’s regulation was upheld by the Appellate Division in May 2026, while California’s TAM 2022-01 and Publication 1050 were declared invalid in December 2023 as underground regulations — a ruling on how the guidance was issued rather than on whether the FTB’s interpretation is correct.
The practical conclusion is the same either way. P.L. 86-272 was written for catalog sellers of physical goods in 1959, and treating it as a general shield in 2026 is not a defensible position for a SaaS business.
Many companies reach this question after the exposure already exists, often when an investor or buyer asks where employees have worked and whether sales tax was collected. It is usually fixable, but timing matters.
The statute of limitations generally does not run on an unfiled return. A company that never registered may have open exposure back to the year it first created nexus, not the standard three or four years.
Voluntary disclosure agreements are the primary remedy. Most states offer one, and the Multistate Tax Commission runs a program allowing a company to approach several states anonymously at once. A VDA typically limits the lookback to three or four years and waives penalties in exchange for registration and payment, but is generally available only before the state makes contact.
The exposure appears in the financial statements first. Uncollected sales tax and unfiled income tax are loss contingencies that belong on the balance sheet under ASC 450 once probable and estimable. A reserve that surfaces for the first time during diligence reads as a control weakness. Two exposures can also outlive the entity: many states impose responsible person liability on officers for sales tax, and asset purchase agreements often carry successor liability for unpaid state taxes.
Managing multi-state tax nexus for software companies is not about registering everywhere a customer exists. It is about having a repeatable way of finding real obligations. Map five things: where employees and contractors work and what they do; where customers are and how much revenue each state produces; what is actually being sold in each contract; where property sits; and where representatives conduct business. Compare that against the income, franchise, gross receipts, sales, and payroll rules in each state with meaningful activity.
Then give the review a cadence. Beyond an annual refresh, four events should trigger an immediate look: hiring in a new state, launching a new or bundled product, crossing a revenue inflection point, and starting a financing or sale process.
Multi-state tax nexus for software companies expands well before the finance function realizes the business has entered a new jurisdiction, and the rules keep shifting as states legislate and litigate.
Through our services for software developers and consultants, ASAM LLP helps technology businesses evaluate multi-state nexus, identify income, franchise, and sales tax obligations, remediate historical exposure, and integrate state tax planning into broader tax and accounting strategy.
If your company is expanding across state lines or preparing for financing or an exit, contact info@asamllp.cpa or call +1 (415) 788-2371 to discuss your exposure.
Partner with our bilingual CPA team for expert guidance in tax, assurance, accounting, and advisory services tailored to your business needs.
San Francisco-Based CPA Firm Since 1986
Providing assurance, accounting, tax, and consulting services to local, national, and international clients with personalized attention and bilingual support.