In 2018, a SaaS founder selling $2 million a year to customers in 40 states could plausibly ignore sales tax outside their home jurisdiction. By 2026, that same founder is staring down registration deadlines in at least 25 states, a patchwork of "true object" tests that contradict each other across state lines, and audit exposure that compounds at roughly 30 percent of unpaid tax per year. The South Dakota v. Wayfair decision did not create this complexity—it weaponized state laws that were already incoherent and pointed them at software companies.
Here is what makes the problem unique to digital goods. A widget seller can read a state's tax code, find "tangible personal property," and know the rule. A SaaS vendor reading the same code finds "data processing services," "information services," "digital products," "computer services," "specified digital goods," and sometimes nothing at all—often in the same state's revenue rulings, depending on the year. Two states with nearly identical statutory language routinely reach opposite conclusions on the same product. A single feature toggle—say, adding human-reviewed reports to an automated dashboard—can flip the tax treatment of an entire subscription line.
If you sell software, streaming media, or digital goods to U.S. customers, this guide explains what changed in 2026, how to think about the true object test that determines taxability in roughly half the states, and how to set up a compliance posture that scales with your revenue rather than collapsing under it.
The Three Categories States Use to Classify SaaS (And Why It Matters)
States that tax SaaS arrive there by three distinct legal routes, and the route matters because it determines which features of your product trigger tax, which exemptions apply, and which exemption certificates you can accept.
Route 1: SaaS treated as tangible personal property. This is the broadest tax treatment. States like Hawaii, New Mexico, South Dakota, and Washington classify access to remotely hosted software as the sale of a digital product analogous to a physical good. Once a transaction is treated as tangible personal property, the default presumption is taxability, and the burden falls on the seller to prove an exemption applies. Resale certificates from B2B buyers generally work, but the documentation requirements are strict.
Route 2: SaaS treated as a taxable service. Texas is the textbook example. Texas does not tax SaaS as software—it taxes 80 percent of the SaaS charge as a "data processing service" under a rule that predates cloud computing by decades. The 20 percent exemption recognizes that some portion of any data processing transaction is the customer's own labor in using the service. Tennessee, Ohio, Connecticut, and the District of Columbia use variations of the same approach: classify SaaS as one of several enumerated taxable services (data processing, information services, computer services) rather than as a product.
Route 3: SaaS treated as nontaxable intangible service. California, Florida, Illinois, Nevada, North Carolina, Oklahoma, and Virginia are the major holdouts. These states treat SaaS the way they treat legal advice or accounting—a nontaxable professional or intangible service. Note that "nontaxable" means today. Several of these states have legislative proposals to extend sales tax to digital services, and the trend across recent legislative sessions is one-directional: more states tax SaaS than fewer.
A founder who knows which route applies in each customer state can plan accordingly. A founder who treats "is SaaS taxed?" as a binary yes-or-no question will misregister, misclassify exempt B2B customers, and end up either over-collecting (and inviting class action refund claims) or under-collecting (and inviting audit assessments).
The True Object Test: Where Bundles, AI, and Hybrid Products Live or Die
The true object test is the single most important concept for any SaaS company that sells anything more complicated than pure software access. It is the rule states apply when a transaction includes both taxable and nontaxable elements and the customer pays one bundled price.
The test asks: what is the customer's primary objective in entering the transaction? If the dominant purpose is access to taxable software, the entire bundle is taxable—including incidental services, training, and support. If the dominant purpose is a nontaxable service (like consulting, custom analysis, or human-delivered work), the entire bundle escapes tax even when it includes taxable software components.
In practice, two states applying the true object test to the same product can reach opposite conclusions. Tennessee, for example, treats SaaS as taxable when the true object is access to software, but exempt when the true object is a human-delivered service that happens to be enabled by software. Texas applies a similar analysis under its data processing rule. California, when it does tax software at all, looks at whether the customer's primary intent is to license intellectual property versus consume a service.
This matters for three categories of modern products:
- AI-augmented services. A product that uses AI to generate marketing copy may be classified as software access (taxable in Texas, Washington, Hawaii) or as a content-creation service (treated more leniently in many states). The classification often turns on whether the human reviews the AI output and whether the customer receives a deliverable they could not get without the human.
- Embedded software with consulting. Implementation packages, white-glove onboarding, and managed services bundled with a SaaS subscription create true-object ambiguity. Pricing the components separately on the invoice usually helps; some states unbundle automatically when individual prices are stated, while others require it.
- Streaming and digital media with editorial curation. A flat-fee streaming service is typically a taxable digital product. A subscription that includes editorial recommendations, custom playlists, or expert commentary may shift the true object toward a service.
The single most important compliance step a multi-product SaaS company can take is to write down its true-object analysis for each SKU, document the customer-facing description that supports that analysis, and revisit it whenever the product changes.
Economic Nexus After Wayfair: The Threshold Math in 2026
Before South Dakota v. Wayfair in 2018, a state could only require an out-of-state seller to collect sales tax if the seller had physical presence—employees, inventory, or property—in the state. Wayfair overturned that rule. States can now impose collection obligations based purely on economic activity, with no physical footprint required.
Almost every state followed South Dakota's template: $100,000 in annual sales or 200 transactions to in-state customers triggers nexus. By 2026, the 200-transaction prong is dying. Illinois eliminated it effective January 1, 2026, joining Colorado, Iowa, Maine, North Dakota, Washington, and Wisconsin in moving to revenue-only thresholds. States quietly admitted what tax practitioners knew from day one: tracking 200 $5 invoices created administrative burden disproportionate to the revenue it captured.
For SaaS companies specifically, the practical implications of post-Wayfair economic nexus are:
- Volume from one large customer can trigger nexus on its own. A single $120,000 enterprise contract in a state can establish nexus even if you have no other customers there.
- Free trials, freemium tiers, and discounts complicate the threshold. Some states measure gross receipts (before discounts); others measure net. Some include free tiers as zero-dollar "transactions" toward the 200-transaction count; others do not.
- Nexus persists. Once established, economic nexus typically continues for the remainder of the year you cross the threshold plus the entire following calendar year, even if your sales fall below the threshold. Backing off nexus is harder than triggering it.
- Marketplace facilitator laws can shift the obligation. If you sell through the AWS Marketplace, Microsoft Azure Marketplace, Shopify App Store, or similar platforms, the marketplace may be required to collect tax on your behalf in many states. Your reseller agreement should specify who has the obligation.
The hardest part of nexus compliance is not collecting tax once you know you owe it. The hardest part is monitoring 45 thresholds continuously, in 45 different denominators (gross versus net, 12-month rolling versus calendar year, previous year versus current year), and knowing when you crossed the line.
What Changed for 2026
Three changes worth knowing about for the current year:
Illinois ends its 200-transaction threshold (January 1, 2026). Remote sellers now establish Illinois nexus only after exceeding $100,000 in gross receipts. Small-volume sellers who were tripped into Illinois nexus by transaction count alone can deregister—but should do so deliberately, often after a clean closeout filing.
Maine adds digital audio and audiovisual services to its taxable base. Streaming music and video subscriptions to Maine customers became taxable in 2026, joining the broader list of digital products Maine already taxes. SaaS vendors who sell media-adjacent products should re-examine Maine taxability.
District of Columbia raises its digital goods rate. Effective October 1, 2026, the D.C. tax rate on digital goods and services rises from 6.0 percent to 7.0 percent. Vendors who collect D.C. tax need to update their tax engines on the effective date; a one-month lag at the higher rate is the most common audit finding in jurisdictions with rate changes.
Washington continues to expand "retail services." Washington has been adding digital service categories to its sales tax base for several years. The 2026 expansions cover additional cloud-hosted services that were previously gray-area. If you sell to Washington customers and rely on a 2022 or 2023 taxability memo, refresh the analysis.
How a Real SaaS Company Should Approach Compliance
The textbook answer to "how do I comply with sales tax in 45 states" is to register everywhere, install a tax engine, and collect on every taxable transaction. The textbook answer is usually wrong for a Series A or Series B SaaS company. Here is a more realistic phased approach.
Phase 1: Build the Map (Revenue Under $1M)
Before you register anywhere, build a spreadsheet that lists every state you sell into, your trailing-12-month revenue by state, the state's economic nexus threshold, the state's SaaS taxability treatment, and the state's effective rate. If you have not crossed any thresholds and you are not closing on a Series B (which will trigger diligence questions), you may have no obligations at all yet. Many SaaS companies under $1M in revenue have no sales tax exposure because they have not crossed economic nexus in any state.
Accurate bookkeeping from day one is what makes this map possible. You cannot compute trailing-12 revenue by customer ship-to state if your accounting system does not retain ship-to addresses on each invoice. Bake the data capture in early—retrofitting two years of historical invoices to recover state-level revenue is a multi-week project.
Phase 2: Register Where You Owe ($1M–$10M)
Once you cross nexus in a state, you have a legal obligation to register and collect prospectively. You do not have to register the day you cross—most states give you 30 to 60 days—but stalling beyond that begins accumulating unregistered liability. The mechanical steps:
- Determine the registration effective date based on when you crossed the threshold and the state's rules for the first taxable transaction.
- Register through the state's online portal (or the Streamlined Sales Tax central registration if the state participates, which covers about half of all states with one registration).
- Configure your tax engine or billing system to begin collecting on the effective date.
- File the first return on the assigned schedule (monthly, quarterly, or annually depending on volume).
Pay attention to two registration traps. First, registration is often retroactive to your nexus date, not the day you fill out the form—meaning the state expects tax for the gap period. Second, registering creates an ongoing filing obligation; you must file zero returns in months with no taxable sales, or face penalties for non-filing even when no tax is due.
Phase 3: Clean Up Historical Exposure (Voluntary Disclosure)
If you discover that you owed tax in a state for prior years and never registered or collected, registering directly is the worst move. A direct registration tells the state to look back, assess the full historical liability, and apply penalties that average about 30 percent of unpaid tax plus compounded interest.
The right tool is a Voluntary Disclosure Agreement (VDA). A VDA is a contract between you and the state, typically negotiated through a third-party representative who keeps your identity anonymous until the deal is signed. In exchange for voluntarily coming forward, states usually offer:
- A limited look-back period (commonly three or four years instead of the open-ended exposure)
- 100 percent penalty waiver
- Often a reduction or waiver of interest
The catch: you only qualify if the state has not already contacted you. A nexus questionnaire, an audit letter, or even an information request can disqualify you. The window for VDAs closes the moment the state knocks. Companies preparing for a financing round, an acquisition, or an IPO routinely run VDA campaigns across multiple states in the months before diligence begins, because acquirers will discount the purchase price by the full undisclosed liability—or insist on indemnity escrows.
VDAs cost real money. Typical professional fees run several thousand dollars per state, and the agreements take several months to negotiate. But the alternative—paying back tax, full penalties (typically 25 to 50 percent of the tax bill), and compounded interest, across an open look-back period—is almost always worse.
Phase 4: Automate ($10M+)
At growth-stage revenue, manual compliance breaks. The combination of 30+ active registrations, monthly filings in many of them, address-level rate determination, exemption certificate management, and product taxability updates exceeds what a finance team can sustain manually. The standard solution is a sales tax engine (Avalara, Anrok, Stripe Tax, TaxJar, Vertex) integrated with your billing system. The engine handles real-time rate lookup, taxability rules, and filing.
Even at this stage, automation is not a substitute for judgment. Tax engines apply defaults that may be wrong for your specific product configuration. Someone on the finance team has to own the taxability classification for each SKU, review the engine's results periodically, and update the configuration when products change.
Common Mistakes That Trigger Audits
Five mistakes account for the bulk of sales tax audit findings against SaaS companies:
- Treating B2B as automatically exempt. Many states do not have a blanket SaaS exemption for business buyers. Some allow resale exemptions only for true resale, not for use in the buyer's own operations. Collect and validate resale or exemption certificates before treating a customer as exempt.
- Ignoring sourcing rules. SaaS sales are usually sourced to the customer's billing address or primary use location, but rules vary. Sourcing to the wrong jurisdiction can mean collecting at the wrong rate—and over-collected tax is your liability to refund, not the state's.
- Failing to file zero returns. Once registered, a state expects a return every period whether you had taxable sales or not. Missed zero returns generate penalty notices that often exceed any actual tax due.
- Mishandling rate changes. When a state changes its rate mid-year (as D.C. is doing in 2026), the prior rate applies through the effective date and the new rate after. Tax engines handle this if configured; manual compliance often misses the cutover by a billing cycle.
- Not documenting the true-object analysis. If a state auditor questions whether your bundled service is taxable, the written record of how you classified it—and what customer-facing materials support that classification—is your defense. Without it, the auditor's analysis wins by default.
Keep Your Financial Records Audit-Ready From Day One
Sales tax compliance compounds the importance of clean, transparent financial records. Every nexus determination, true-object analysis, and VDA filing relies on accurate state-by-state revenue data, exemption certificates indexed to invoices, and a clear audit trail from booked revenue to tax collected to tax remitted. Beancount.io provides plain-text accounting that gives you complete transparency and version control over your financial data—no black boxes when an auditor asks how you arrived at a number, and no vendor lock-in when your accountant wants to review the raw ledger. Get started for free and see why developers and finance teams choose plain-text accounting for the kind of compliance work where every entry has to be defensible.