SAAS OPERATIONS
US Sales Tax for SaaS: Nexus, Taxability, and the MoR Route
Anyway Team
· 9 min read ·
US sales tax for SaaS has no single national answer. A seller must check whether it has nexus in a state, whether that state taxes the exact software or service, where the customer uses it, and whether an exemption applies. A Merchant of Record can take this transaction-tax work for covered sales.
Anyway acts as Merchant of Record for covered transactions, calculates, collects, and files applicable sales tax, and pays the SaaS vendor net proceeds.
US sales tax for SaaS starts with four questions
Work through these in order:
Nexus: Does the seller have enough connection to the state for a collection duty?
Taxability: Does the state tax this type of SaaS, software access, data processing, or digital product?
Sourcing: Which location controls the state and local result?
Exemption: Does a valid customer or use exemption change the charge?
A threshold alone does not show whether a sale is taxable. A product classification alone does not show whether the seller has a duty to collect. Both facts are required, plus the correct sourcing and exemption evidence.
Economic nexus after Wayfair
In South Dakota v. Wayfair (2018), the US Supreme Court overruled the earlier physical-presence-only rule. South Dakota's law applied to sellers with more than $100,000 in annual in-state sales or at least 200 in-state transactions, and the Court found the nexus sufficient for the large sellers in that case.
The decision did not create one threshold for all states. Each state sets its own statute, measurement period, included revenue, registration timing, and rules for marketplace sales. Some states have changed or removed transaction-count tests since 2018.
Physical presence still matters. Employees, offices, contractors, inventory, or other activity can create nexus even when online revenue is below an economic threshold. Review both physical and economic connections.
“SaaS is taxable” is not a national rule
States classify online software differently. The same product can receive different treatment because one state sees a nontaxable electronically delivered product, another sees taxable data processing, and another treats remote access as a licence to use prewritten software.
Three official state examples show why a one-line answer fails.
California: electronically transmitted software is generally not taxable
The California Department of Tax and Fee Administration says sales of electronic data products, including software and mobile applications, are generally not taxable when transmitted to the customer over the internet. Its guidance notes that adding a printed copy or physical backup medium can make the full sale taxable.
This is a delivery rule, not a universal exemption for every technology service. Bundles, tangible items, implementation work, and other facts can change the result.
Texas: SaaS can be taxable data processing
The Texas Comptroller lists SaaS sellers and application service providers as data-processing providers. Texas states that data processing is taxable and that 20% of the charge is exempt, which generally leaves 80% of a qualifying data-processing charge subject to tax.
Texas also has a remote-seller safe harbor. Its current FAQ says a remote seller is not required to obtain a permit and collect use tax when total Texas revenue is below $500,000 in the previous 12 calendar months. The calculation includes taxable and nontaxable Texas revenue and certain marketplace sales.
The taxability rule and the nexus safe harbor solve different questions. A taxable SaaS product does not create a collection duty until the seller has the required connection, and a seller over the threshold still needs to classify each sale.
New York: remote access can be prewritten software
A 2024 New York advisory opinion concluded that charges for a web portal were taxable sales of prewritten software. It treated customer access and control as a licence to use that software. The opinion said separately stated, reasonable charges for certain custom programming, data entry, and training were not taxable under the stated facts.
The opinion sourced the software charge to the locations of the customer's employees who used or directed the use of the portal. If users were inside and outside New York, the receipts were allocated accordingly.
New York advisory opinions are limited to the requesting taxpayer and the facts presented. This example is useful for issue spotting, not as a ruling on every SaaS product.
A state comparison snapshot
State example: California; Official treatment highlighted here: Electronically transmitted software and digital products are generally not taxable; Extra fact to retain: Whether any tangible medium is supplied
State example: Texas; Official treatment highlighted here: SaaS providers can fall within taxable data processing; 20% of the charge is exempt; Extra fact to retain: Texas revenue for the preceding 12 months
State example: New York; Official treatment highlighted here: Remote access can be a taxable licence to use prewritten software; Extra fact to retain: Locations of the customer's users
These examples are not a fifty-state matrix. They show why product description, delivery, buyer location, and nexus data must stay connected to every order.
How a direct SaaS seller manages sales tax
A company selling directly through a payment processor usually needs a tax operating system:
define the product's tax category in every relevant state;
monitor physical and economic nexus;
register before collection when required;
capture evidence of the customer's taxable location;
calculate the state and local rate;
collect and display tax at checkout;
validate exemption certificates;
file returns and remit on each assigned schedule;
retain transaction and exemption records;
update rules when the product or law changes.
A processor can move the money without becoming the seller. A tax calculation tool can compute a rate without filing every return unless that service is part of the contract. The does Stripe handle sales tax? guide separates processing, calculation, filing, and seller liability.
A four-question map for organizing US SaaS sales-tax decisions and transaction evidence.
The Merchant of Record route
A Merchant of Record changes who makes the covered retail sale. The MoR is the legal seller to the customer and takes the payment, transaction-tax, invoice, refund, and dispute responsibilities stated in its agreement.
Anyway states that it is the Merchant of Record for every covered Anyway Business transaction. It calculates, collects, and files applicable sales tax where buyers are located, issues compliant buyer invoices, and sends net payouts to the SaaS vendor's bank account.
This gives a small SaaS team a direct way to sell across US states without building its own fifty-state transaction-tax operation for covered sales. The application can keep its own brand, accounts, workspaces, features, and service delivery.
What the SaaS vendor should still record
The MoR handles the covered end-customer transaction, but the SaaS vendor still needs a reliable commercial record. Retain:
internal customer and workspace ID;
product, plan, period, and entitlement;
buyer location evidence captured through the approved checkout flow;
MoR order, invoice, and subscription references;
fee, refund, dispute, and net payout detail;
the contract and tax-responsibility statement from the MoR.
This record supports accounting, customer support, audits, and provider changes. It also distinguishes MoR-covered orders from any direct channel the vendor operates.
Exempt customers and B2B sales
Some US buyers may claim a resale, government, nonprofit, or other exemption. The applicable form and validation rule depend on the state and the exemption type. A generic tax ID is not always an exemption certificate.
Do not remove tax because a buyer types “business” into a field. Use the provider's approved exemption process, retain the required document, and apply the exemption only to the covered products and dates.
B2B status does not automatically make US SaaS tax-free. This differs from some cross-border VAT reverse-charge flows. Keep the Merchant of Record for B2B SaaS rules separate from US state exemption rules.
Pricing and tax display
Decide whether the advertised price is tax-exclusive or tax-inclusive for the intended market, then make the checkout and terms consistent. US buyers often expect sales tax to be added based on location. The order summary should identify the product amount, tax, total charged, and legal seller.
Anyway's complete MoR service has a public price of 3.9% + $0.50 for each transaction and no listed monthly or setup fee. At a $100 transaction amount used for fee modeling, the formula produces $4.40.
Use the actual contract to confirm the fee base, currency treatment, refunds, and other operational details before publishing a margin forecast.
US sales tax for SaaS checklist
Write a precise description of what the customer can access and do.
Identify every direct and MoR sales channel.
Confirm which party is the legal seller in each channel.
Review physical-presence facts across employees, offices, contractors, and inventory.
Monitor state economic-nexus thresholds for direct sales.
Classify the product by state rather than using one national answer.
Capture customer-location and exemption evidence.
Keep direct tax registrations and filings separate from MoR-covered sales.
Reconcile tax, fees, refunds, and payout at order level.
Recheck state rules when the product bundle or sales model changes.
Frequently asked questions
Is SaaS subject to US sales tax?
It depends on the state and the product facts. California generally does not tax electronically transmitted software, Texas includes SaaS providers in taxable data processing, and New York can treat remote software access as taxable prewritten software.
What is economic nexus for SaaS?
Economic nexus is a state collection connection based on in-state economic activity, often measured by revenue over a stated period. Thresholds and included sales vary by state.
Did Wayfair create a $100,000 national threshold?
No. The case reviewed South Dakota's law, but each state sets its own current nexus rules. Do not copy South Dakota's threshold into a national policy.
Does B2B SaaS avoid US sales tax?
Not automatically. A business buyer may still owe tax unless the product is nontaxable or the buyer supplies a valid state-specific exemption.
How does Anyway handle US SaaS sales tax?
Anyway acts as Merchant of Record for covered transactions and states that it calculates, collects, and files applicable sales tax, then issues the buyer document and pays the vendor net proceeds.
Does an MoR remove my income-tax obligations?
No. Transaction tax on the customer sale and the SaaS vendor's business income are different. Record the MoR payout under the rules where your business operates.
Put the tax duty with the covered sale
Create a SaaS product with Anyway and test a US order from checkout through tax display, invoice, entitlement, and bank payout before launch.
Official sources checked
Information checked on August 26, 2026. State tax rules change and product facts matter; this article is general information, not tax advice.