SAAS OPERATIONS

SaaS Sales Tax for Indie Developers: What You Need to Know in 2026

Anyway Team

· 10 min read ·

Aug 17, 2026

SaaS sales tax is an indirect tax that may apply when a customer pays to access hosted software. The result depends on the buyer's location, whether the buyer is a business or consumer, how the jurisdiction classifies the product, and who is the legal seller. An indie developer must either manage that workflow or sell through a Merchant of Record that does.

This guide explains the transaction layer. It is not personal tax or legal advice. Your own income tax and bookkeeping remain separate from the tax charged to the customer.

Why a $20 SaaS subscription can produce several tax answers

Take the same $20 monthly tool and sell it to four buyers:

A consumer in Germany
A VAT-registered company in France
A customer in Texas
A consumer in Canada

The product and price have not changed. The tax answer can still change because the customer's status, location, and local software rules are different.

That is the real SaaS sales-tax problem. The checkout needs to decide the treatment before payment, put the result on the invoice, keep the location evidence, and later report the sale to the correct authority.

What determines SaaS sales tax?

SaaS sales tax is determined by five core facts: the legal seller, the product classification, the customer's location, the customer's business or consumer status, and the seller's registration obligation. Those facts drive whether tax applies, which rate is used, who collects it, and where it is filed.

1. Who is the legal seller?

With a standard payment processor, the developer's business is normally the seller. A tax engine can calculate a rate, but the business still owns registration, collection, filing, remittance, and records.

With a Merchant of Record, the MoR is the seller for covered transactions and handles the associated indirect-tax workflow under its agreement.

2. What exactly did the customer buy?

One jurisdiction may tax access to prewritten software, another may classify it as a data-processing service, and another may not tax a remote SaaS charge when no tangible property is transferred. A downloadable license, hosted SaaS account, online course, and human consulting service should not be assumed to share one classification.

3. Where is the customer?

Digital-service rules often look to the customer's location. Evidence may include the billing address, payment-country information, IP address, or other commercially relevant information permitted by local rules.

4. Is the customer a business or consumer?

Some VAT systems treat business-to-business and business-to-consumer sales differently. A valid business tax number can change who accounts for VAT and what the invoice must show.

5. Has a registration obligation been created?

Some places use revenue thresholds, transaction activity, local presence, or platform rules. The threshold and measurement period vary. Do not copy one country's number into a global tax rule.

Is SaaS taxable in the United States?

There is no single nationwide US sales-tax answer for SaaS. States classify software and digital services under their own statutes, rules, and administrative guidance.

Texas provides a useful example. The Texas Comptroller says providers of software as a service are included within taxable data-processing services, and 20% of the charge for data-processing services is exempt under the published rule. California's audit guidance describes remote SaaS differently when the customer receives no copy of the software and the seller keeps possession and control.

The contrast shows why a simple “SaaS is taxable” flag is too crude. A seller needs current answers for:

Product taxability in the state
State and local rate sourcing
Economic or physical nexus
Exemption and resale certificates
Registration and filing frequency
Credits or adjustments after refunds

If you sell directly as the merchant, use current state revenue-department guidance and qualified advice. If an MoR sells the covered product, confirm that the provider owns the state sales-tax workflow for that transaction.

How does EU VAT apply to SaaS and digital services?

EU VAT rules distinguish the customer's status and the place of supply. The European Commission states that business-to-consumer telecommunications, broadcasting, and electronic services are generally taxed where the customer resides. Business-to-business services commonly use the customer-location rule with reverse-charge treatment when the legal requirements are met.

For a direct seller, that can require:

Identifying whether the supply is an electronic service.
Establishing the customer's location.
Determining whether the customer is a taxable business.
Validating the VAT number when relevant.
Applying the correct rate and invoice wording.
Filing through the appropriate VAT registration or One Stop Shop route.

The EU's €10,000 cross-border threshold is often repeated without its conditions. The Commission explains that it applies only in a limited scenario involving suppliers established in a single EU member state and specified cross-border B2C supplies. It is not a blanket threshold for every non-EU indie developer selling SaaS into Europe.

What about UK VAT and Canadian GST/HST?

HMRC states that digital services supplied to UK consumers are liable to UK VAT, including supplies by businesses based outside the UK when the rules apply. Its guidance also covers customer-location evidence and the treatment of third-party digital platforms.

Canada's digital-economy GST/HST rules can apply to non-resident vendors and distribution-platform operators selling taxable digital products or services to Canadian consumers. The Canada Revenue Agency notes that these rules can require registration, collection, and remittance under the applicable regime.

These examples share a practical theme: being outside the buyer's country does not automatically remove transaction-tax duties on digital sales.

The SaaS sales-tax workflow

When the developer is the seller, the complete workflow includes more than adding a tax line at checkout.

Stage: Product setup; Required decision or record: Classification of SaaS, download, service, or bundle
Stage: Customer entry; Required decision or record: Location and business/consumer status
Stage: Checkout; Required decision or record: Taxability, rate, currency, and displayed total
Stage: Invoice; Required decision or record: Seller, buyer, tax amount, IDs, and required wording
Stage: Accounting; Required decision or record: Gross sale, tax liability, fee, refund, and net revenue
Stage: Filing; Required decision or record: Return period, jurisdiction, taxable base, and tax due
Stage: Remittance; Required decision or record: Payment to the authority by the deadline
Stage: Audit trail; Required decision or record: Location evidence, exemption proof, invoices, and corrections

A calculation API can help with the checkout row. It does not, by itself, complete the other rows.

How a Merchant of Record handles SaaS sales tax

A Merchant of Record is the legal seller for the covered customer sale. The MoR uses the product and buyer information to determine the applicable indirect tax, collects it at checkout, issues the invoice, files the return, and remits the tax.

The developer supplies the software and receives net revenue. This moves the transaction-tax operation into the MoR's sale rather than leaving the founder to register wherever customers appear.

The division of work looks like this:

Responsibility: Legal seller for covered transaction; Merchant of Record: Yes; Indie developer: Supplies the product
Responsibility: Customer payment; Merchant of Record: Collects it; Indie developer: Connects product access
Responsibility: Sales tax, VAT, or GST; Merchant of Record: Calculates, collects, files, and remits; Indie developer: Provides correct product information
Responsibility: Customer invoice; Merchant of Record: Issues or manages it; Indie developer: Keeps payout and product records
Responsibility: Product delivery; Merchant of Record: Confirms order status; Indie developer: Delivers access or service
Responsibility: Personal or business income tax; Merchant of Record: No; Indie developer: Records and reports local income

The last row is important. An MoR can handle customer transaction tax without replacing the founder's accountant or local income-tax return.

How Anyway handles tax on SaaS sales

Anyway states that it is the Merchant of Record for every covered Business transaction. Its published workflow includes:

Calculating applicable sales tax, VAT, and GST
Collecting the tax from the buyer
Filing the transaction tax
Issuing a compliant invoice
Recording the merchant's net revenue after tax and fees

Anyway also connects the tax record to a product, checkout, order, and Finance entry. Its official documentation says an eligible Card/USD sale records the buyer's gross amount, the applicable Anyway fee, the net amount owed to the merchant, and the related order ID.

The published price is 3.9% + $0.50 per transaction, with the MoR service, global tax and compliance, billing, and subscriptions included. There is no published monthly or setup fee on the current Business page.

For an indie developer, that means the tax operation begins with a verified product and one hosted payment link. Start with Anyway when the product is ready for review.

What information should you collect at checkout?

Even when an MoR handles the tax, accurate buyer information helps produce the correct transaction record. The checkout may need:

Billing country and address
Customer name and email
Business name when relevant
VAT or tax number when relevant
Product and price
Currency
Evidence used by the seller to determine customer location

Your own app should also retain a stable, non-sensitive purchase reference. Anyway payment links can preserve merchant_reference, user_id, and other string parameters in merchantMetadata so the paid order can be matched to the right account.

Do not put identity documents, passwords, or confidential tax data into checkout query parameters. Keep sensitive information inside the approved checkout fields or your secured systems.

A launch checklist for indie developers

Before accepting the first global SaaS payment:

Write a precise product description and identify whether it is SaaS, a download, a service, or a bundle.
Decide who will be the legal seller: your business or a Merchant of Record.
Confirm who owns tax registration, rate calculation, invoices, filing, remittance, refunds, and audit records.
Test a consumer and business checkout where both are supported.
Check the invoice for seller identity, customer details, currency, and tax.
Test a refund and confirm the tax and balance adjustments.
Keep payout records for local bookkeeping and income reporting.

If you have no company yet, read how to sell SaaS globally without setting up a company. For the seller model itself, use the complete Merchant of Record guide.

Frequently asked questions

Is SaaS subject to sales tax?

Sometimes. Taxability depends on the jurisdiction, product classification, customer location, and customer status. US states can reach different answers, while VAT and GST systems often apply specific digital-service rules.

Do I charge tax based on my country or the customer's country?

Many digital-service rules use the customer's location, especially for business-to-consumer sales, but the exact rule depends on the jurisdiction and transaction. Confirm the place-of-supply or sourcing rule that applies to the legal seller.

Does Stripe Tax file and remit SaaS sales tax for me?

A tax-calculation product and a Merchant of Record are different models. Stripe's own documentation explains that a business using Stripe Tax must file and remit collected tax in the locations where it is registered unless it uses a separate filing service or MoR arrangement.

Does a Merchant of Record handle VAT and GST?

An MoR generally handles applicable indirect tax for covered customer transactions under its agreement. Anyway specifically states that it calculates, collects, and files sales tax, VAT, and GST as the Merchant of Record.

Does an MoR remove my income-tax obligations?

No. Customer transaction tax and the developer's income tax are separate. Keep records of gross sales, fees, refunds, and payouts, then follow the income-reporting rules that apply where you live.

What happens to tax when a customer receives a refund?

The seller's records need to connect the refund to the original transaction and apply the correction under the relevant jurisdiction's rules. An MoR manages that payment and indirect-tax adjustment for covered sales.

Put the tax responsibility in the transaction design

Sales tax should not be a cleanup task after the first hundred customers. Decide who the seller is before checkout goes live, then make sure product classification, buyer evidence, invoices, refunds, filings, and payouts all point to the same operating model.

Anyway places those duties inside its Merchant of Record sale. The developer keeps building and delivering the SaaS; Anyway handles the covered checkout, transaction tax, invoice, order record, and payout path. Create an Anyway merchant account when you are ready to sell globally.