SaaS Sales Tax USA: 2026 Guide for Founders

SaaS Sales Tax in the USA: The 2026 Guide for Founders Who Don't Want to Lose Sleep

If you sell SaaS to US customers, you deal with sales-tax rules from 45 states, DC, and sometimes your buyer's city or county, rather than the IRS.

Each state decides on its own whether your subscription is taxable, what counts as "nexus", how often you file, and what happens if you don't.

Miss the rules in one state and you can owe back-tax going back years, plus penalties that don't care that you're a 3-person team in Lisbon.

This guide is the version we wish someone handed us before our first US customer. It covers what's taxable, where you owe, how to register, how to file, and the one decision that makes 90% of this disappear: use a merchant of record that becomes the legal seller and collects and remits sales tax on the sales it makes.

The short version

US sales tax on SaaS in 2026 looks like this:

• SaaS taxability depends on the jurisdiction and product category. State and local rules determine whether your subscription is taxable.
• Physical presence or economic nexus can trigger tax duties. Sales thresholds and measurement periods vary by state. Taxability determines collection.
• No federal sales tax exists. You register state by state, file state by state, remit state by state.
• Stripe Payments leaves the tax liability with you. Stripe Tax calculates tax and helps with registration and filing. You're still the merchant of record, and you still owe.
• A merchant of record is the legal seller. It handles sales-tax collection, filing, and remittance for the transactions it sells.

What states actually tax SaaS

The taxability map is messy. Roughly:

SaaS taxable in most cases, with important qualifications: New York, Texas, Pennsylvania, Washington, Massachusetts, Ohio, Connecticut, Arizona, Iowa, Tennessee, Utah, South Dakota, West Virginia, Hawaii, New Mexico, South Carolina, Rhode Island, Maryland, Vermont, Kentucky, and Louisiana. This list concerns remotely accessed software, not just downloads; exemptions and the service you actually sell can change the answer.

• Texas: SaaS is generally taxable data processing. 20% of the charge is exempt, so tax applies to 80%, not the entire charge. See the Texas Comptroller's data-processing guidance.
• Connecticut: Remotely accessed prewritten software used in a business, trade, or occupation is treated as a computer and data-processing service taxed at 1%. Personal-use access is taxed at 6.35%. These distinctions concern the purchaser's use, not simply whether the account is labelled “business.” See Connecticut's sales-and-use-tax definitions and rates.
• Ohio and Iowa: Don't treat every subscription as taxable. Ohio's taxable automatic data processing, computer services, and electronic information services generally concern business use; Iowa exempts qualifying purchases by commercial enterprises. See Ohio's statutory definitions and Iowa's guidance on digital products and services.

Corrections to the original taxable list: Indiana and Wisconsin generally do not tax remote software access when the customer does not receive or control a copy; see Indiana's computer-software bulletin and Wisconsin's computer-software rule. Alabama generally does not tax pure SaaS access without a transfer of software, while a software sale or licence can be taxable; check the Alabama Department of Revenue's sales-and-use-tax rules. Mississippi generally excludes remote access to software hosted outside Mississippi, but software located in the state can produce a different result; check the Mississippi Department of Revenue's sales-tax guidance. These four states should not appear as unqualified “SaaS taxable” entries.

SaaS generally not taxable at the state level when you provide remote access without transferring software: California, Florida, Illinois, Georgia, North Carolina, Virginia, Colorado, Missouri, Minnesota, and New Jersey. This is not an exemption for every software-related charge: downloads, transferred copies, and separately taxable services can change the classification.

New Jersey does not draw a personal-versus-business distinction for pure remotely accessed SaaS. Where the customer receives no software, SaaS generally is not subject to sales tax. The business-use distinction instead concerns the exemption for qualifying electronically delivered prewritten software—not a blanket rule that personal-use SaaS is taxable. See the New Jersey Division of Taxation's cloud-computing guidance.

Alaska has no statewide sales tax, but local sales taxes may apply. Don't read the absence of a state tax as an exemption from local collection obligations; see the Alaska Department of Revenue's sales-tax information.

No state sales tax at all: Alaska, Delaware, Montana, New Hampshire, Oregon. (Alaska has local sales tax in some boroughs and cities, so don't relax fully.)

Treat any single-source list (this one included) as a starting point. Statutes change, departments of revenue publish letter rulings that flip a position, and bundling matters. New Jersey is taxable if your SaaS is for personal use, not taxable if it's for business use. Texas taxes SaaS at 80% of the sale price because they treat 20% as a non-taxable data-processing service. Connecticut taxes business SaaS at a reduced 1% rate. The detail is where founders get cooked.

The state answer isn't always the last word. These local and district rules change what you collect:

Calling your product SaaS or AI doesn't settle which rule applies. States look at what the buyer actually gets, so answer these about your own product:

• Remote access: Do customers only use the software on your servers, or do they install something?
• Downloads: Do you deliver a desktop app, plugin, or file the buyer keeps?
• Data processing or reports: Is the main output processed data or a report? Texas, for one, taxes that as a data processing service.
• Communications: Does the product send messages, calls, or texts on the buyer's behalf? Some states classify that separately from software.
• Separate charges: Do you bill implementation, training, or support on their own lines, or bundle them into the subscription?

Economic nexus, the thing that triggers everything

Before South Dakota v. Wayfair (2018), you only owed sales tax in a state where you had physical presence. Wayfair ended that limit.

Now most states add economic nexus: cross a sales threshold in their state, and registration and collection duties can follow. Physical presence still counts. An employee or office in a state can create nexus with no sales threshold at all.

Crossing a threshold in a state that doesn't tax SaaS doesn't make your subscription taxable there.

Each state sets its own threshold: the dollar amount, which sales count toward it, and whether a transaction test applies at all.

A common pattern is $100k in sales into the state, sometimes with a transaction count beside it, measured over a period the state picks.

Rules that differ from the pattern:

• Alabama: $250k, measured on the previous calendar year under its remote-seller rules.
• Tennessee: $100k. (No transaction count.)
• New York: more than $500k and more than 100 sales, measured over the preceding four sales tax quarters under its nexus rules. You need to pass both tests.
• California and Texas: $500k, with no transaction count. Texas measures the previous 12 calendar months under its remote-seller rules.
• Kansas: $100k in the current or preceding calendar year under its remote-seller rules.

Where a state still uses a transaction test, that's the SaaS trap. Monthly billing creates 12 invoices a year per customer, and a state can count each one as a transaction.

Illinois uses a sales-based threshold under its 2026 nexus rules.

Deadlines after you cross a threshold differ by state.

In Kansas, you collect on the next transaction after you cross and register within 30 days (rules linked above).

In Texas, collection starts on the first day of the second month after the month you cross $500k (rules linked above).

Miss the start date and you accrue tax and penalties from the day you should have started collecting.

Copy this worksheet into a spreadsheet and add each state you sell into. The Texas row illustrates a remote SaaS seller with no physical presence whose Texas revenue exceeds $500,000 in July 2026. The dates are hypothetical. Fill the two “Your state” rows with your own records and add more as needed.

Give the sheet to one person, usually whoever owns billing. They update it monthly from sales data, and again whenever someone starts working from a new state.

How registering and filing actually works

Per state, you:

1. Apply for a sales tax permit on the state's department of revenue site. Free in most states, $20 to $100 in a few. The permit starts your filing duties, so apply once you need to collect.

2. Get a permit number and a filing frequency (monthly, quarterly, or annual based on volume).

3. Set up your billing system to collect the right rate at checkout. The rate depends on the state's sourcing rule and the customer's location, so capture a full address instead of a ZIP code alone.

   Watch B2B accounts billed from a headquarters in one state while their users log in from others. Some states let you split that sale across the states where the software is used.

   If you split a sale, keep the records behind it: user or seat counts by state, and the customer's written statement of where the software is used.

4. Remit collected tax on the schedule the state assigned you. Late filing brings a penalty plus interest, at rates each state sets. Many states, Texas included, expect a return for a $0 period while your permit is active.

5. Renew the permit if your state requires it. Some permits run until you close them, others expire on a fixed cycle.

Each return has to tie back to your own records. Keep these for every state you file in:

• Reconciliation. Match billed sales and tax collected against refunds, credits, exemptions, and the totals for each jurisdiction before you file.
• Supporting records. Keep permit details, every filed return, payment confirmations, and the reasoning behind each taxability call.
• A deadline owner. Name one person who owns each state's due dates, $0 periods included.

Build that ledger from invoices, never from processor payouts. A payout already has fees and refunds taken out, so it won't match the tax you owe.

Do this for every state where you have nexus and your software is taxable. By the time you hit $5M ARR with US distribution, you're probably filing in 30+ states. A typical mid-size SaaS spends 40 to 80 hours a month on compliance, plus $1k to $5k a month on tools (Avalara, TaxJar, Anrok) and accountants.

The merchant of record shortcut

A merchant of record (MoR) is the legal seller of your product. The customer's receipt has the MoR's name on it.

For every sale it makes, the MoR calculates the sales tax, collects it, files the returns, and remits the money in the states it covers.

Three things stay with you: income tax on your business profit, tax on any sales you make outside the MoR, and sales tax you owed before you switched.

You still build the product, ship it, and answer the support tickets. The MoR is the seller only at checkout.

What that gets you:

• One legal entity holds the state permits, not you. For sales the MoR makes, you don't register in the states it covers.
• The MoR's nexus, not yours. For transactions it sells, the MoR evaluates its own nexus and collection obligations in the jurisdictions it covers. You don't need to assume it has crossed every state's threshold—or that transaction volume alone establishes its obligations.
• Filing is their job. The MoR files the returns in the states it covers, and you never see the forms.
• Audit risk transfers for those sales. If a state audits sales the MoR made, it audits the MoR.
• One global revenue line in your books, not 46 reconciliations. The MoR's settlement report replaces per-state collection and remittance records.

The tradeoff: the MoR takes a bigger cut of each sale. Creem charges 3.9% + 40¢ per successful transaction, including processing, tax handling, invoicing, compliance, and dispute handling, with no monthly or setup fee.

Stripe alone is 2.9% + 30¢ for domestic cards, with extra fees for international cards and currency conversion. The sales tax itself is a separate line your buyer pays at checkout, on top of the price.

Say your indie SaaS does $500k a year through checkout at a $50 average order: 10,000 successful payments, all USD domestic cards, no refunds. Using the rates above, Creem's fees come to $23,500 against $17,500 for Stripe's domestic card processing.

That's a $6,000 gap before payout charges and any extra services.

Plan on $40k to $80k a year for a tax tool, an accountant, internal hours on returns, and the constant low-grade panic of "did I miss a state?" Compared with that budget, the MoR is usually the right trade for indie and international teams.

For a US-based founder selling B2B at high ACVs, doing it yourself with Anrok or TaxJar can pencil. Depends on your team's appetite for paperwork.

Creem handles US sales tax, EU VAT, and UK VAT as the legal seller for SaaS and AI teams selling globally. Enter your monthly sales in the Creem fee calculator to compare fees with your current setup.

What Stripe actually does (and doesn't)

Stripe gets named in every sales tax conversation, so worth being precise:

• Stripe Tax Basic calculates tax and supports collection at checkout, using your product classifications and tax registrations. Stripe's separate “Register for me” service handles registration; it does not itself prepare returns or remit tax.
• Stripe Tax Complete adds registration and filing services. Registration alone does not prepare returns or remit tax.
• Automated US filing is available through Stripe or filing partners for supported registrations and eligible accounts.
• Supported filing services also handle remittance. You authorize the tax payments through the Stripe or partner filing arrangement.
• With Stripe Payments plus Stripe Tax, you remain the legal seller. Your name is on the receipt. Your EIN is on the permit. Automated filing leaves your sales-tax liability with you.

Stripe Managed Payments is a separate merchant-of-record product for eligible SaaS and digital goods. Stripe is the legal seller on those sales.

For a deeper comparison: is Stripe a merchant of record?

The specific things that bite indie SaaS founders

A short list of pitfalls we see weekly in support tickets:

1. Trailing 12 months vs calendar year. Alabama uses the prior calendar year. Arkansas uses the current or preceding calendar year.

   Texas's measurement period is the previous 12 calendar months. Track each state's measurement period so a calendar-year report does not miss a crossing.

2. Transaction counts need their own rules. Count the transactions included in a state's nexus test. Recurring invoices and unique customers are not interchangeable.

   Apply a transaction test only where one exists, and count $0 trials only where that test includes them.

3. Marketplace facilitator laws. If you sell through the Apple App Store or Google Play, their tax handling covers app-store transactions in the jurisdictions where they collect and remit the tax.

   Your own direct sales still need separate compliance.

4. B2B exemption certificates. B2B status alone creates no exemption. A resale certificate must cover the purchaser's qualifying use.

   Collect, validate, and store the certificate so you can support the exemption in an audit.

5. Bundling. If your SaaS subscription includes a hardware peripheral or a professional service, the bundle rules in each state determine what's taxable. How you charge for the components matters too.

   Classify the bundle before billing. Getting it wrong can leave you owing tax you never collected.

6. Backfile risk. When you finally register in a state you've been selling into for two years, you need to establish when nexus began and which earlier sales were taxable. You can owe back-tax, interest, and penalties on those sales.

   Reconstruct that history before registering, then review the state's disclosure or remediation procedures to see how to resolve the exposure.

FAQ

Stop reading. Pick a path.

Two valid paths:

1. Do it yourself. Pick TaxJar, Anrok, or Avalara. Register in each state where you have physical or economic nexus and your software is taxable, then file on the schedule that state assigns.

For a small team, plan on 4 to 10 hours a month of founder or finance time. Realistic if you're US-based, B2B-heavy, and your team likes spreadsheets.

1. Offload to a merchant of record. Creem calculates, collects, files, and remits sales tax on the covered transactions it sells.

A new product can go live on our hosted checkout in one afternoon, and existing subscriptions move over through a custom migration with the Creem team.

Start selling with Creem. Only pay when you earn.

If you're shipping AI tools, monetizing in public, or building a small SaaS without a finance hire, path 2 was built for you. Read the docs.

Do I need to collect sales tax on my SaaS if I'm based outside the US?

Yes, if you have physical or economic nexus in a US state and your SaaS is taxable there. Your home country doesn't shield you.

When a merchant of record sells the transaction, the MoR is the legal seller, so collecting tax on that sale is its job.

At what revenue should I worry about US sales tax?

From your first US sale. Track sales and transaction counts by state, plus any physical presence such as an employee working there.

For most SaaS founders, state thresholds become pressing between $30k and $80k MRR depending on customer mix. Don't wait until you cross thresholds to think about it. Pick a path (DIY with TaxJar/Anrok, or MoR) before any state requires you to collect.

What's the penalty for not collecting sales tax I owed?

You still owe the uncollected tax, usually out of pocket since the customer is long gone, plus penalties and interest.

In Texas, paying 1 to 30 days late costs 5%, after 30 days it's 10%, a late report costs $50 even when no tax is due, and interest starts on day 61.

Other states set their own penalties and interest. Some can also hold officers personally liable or lien your business bank account under their own laws.

Can I just not sell to US customers?

You can geo-block, yes. About 12% of the indie SaaS teams we onboard chose to skip US distribution for sales-tax reasons.

It's a legitimate strategy, but you'd be giving up roughly 60 to 70% of the SaaS market. Blocking new sales doesn't clear tax you already owed. For most teams the math doesn't work, though for a few it absolutely does.

Is a merchant of record the same as a payment processor?

No. A payment processor (Stripe Payments, Adyen, Braintree) moves money. A merchant of record (Creem, Paddle, LemonSqueezy, FastSpring) is the legal seller and uses a payment processor under the hood.

The difference is whose name is on the receipt and whose problem the tax is. Stripe also sells Managed Payments, a separate MoR product, so the label follows the product you use.

Where can I read the official state-level rules?

Start at the SST Governing Board for the 24 states in the Streamlined Sales Tax compact, then go state by state from each department of revenue site.

The SST taxability matrix is the closest thing to a canonical reference for SaaS treatment.

SST's shared registration is a separate tool: one application covers the member states you choose.

Each state still sets its own taxability and returns, and every registration starts filing duties, so register only where you need to collect.