Is SaaS Taxable and Where Do You Register?

SaaS may be taxable, but there is no single nationwide answer. Each state determines how it classifies remotely accessed software and related services. A SaaS business generally needs to evaluate two questions separately: whether its product is taxable in a customer’s state and whether the business has enough connection, or nexus, to be required to register there.

Selling through an app marketplace or another platform adds a third question: whether the platform qualifies as a marketplace facilitator and collects tax on the transaction. A facilitator’s collection may reduce the seller’s responsibility for marketplace sales, but it does not automatically resolve obligations created by direct subscriptions, the seller’s physical presence, or state-specific registration rules.

When registration is required, the business generally registers with the appropriate state tax authority rather than with the federal government. The site’s sales tax application information can help businesses identify the state registration relevant to their circumstances.

When SaaS Taxability and Registration Rules Apply

A SaaS company should begin with the actual product delivered to the customer. “SaaS” is a broad commercial label, not a uniform sales-tax category. States may focus on features such as access to software, data processing, information services, digital products, or bundled professional services. The same subscription description may therefore receive different treatment from one state to another.

Taxability alone does not create a registration requirement. A seller also needs nexus with the state. That connection may arise from physical business activity, such as personnel or operations in a state, or from economic activity that reaches a state’s threshold. Economic thresholds are set individually by each state and are reviewed periodically, so sales should be tracked by destination and compared with the current rules of the relevant state revenue department.

These two tests produce several possible outcomes:

  • A subscription may be taxable, but the seller may not yet have a registration obligation in that state.
  • A seller may have nexus because of its broader business activity, even if a particular SaaS product is not taxable there.
  • A marketplace facilitator may collect tax on marketplace transactions while the SaaS provider remains responsible for its direct subscriptions.
  • A business may need to register or file because of its in-state presence even when a platform collects tax on all marketplace sales.

For that reason, a company should not build its registration list from a taxability map alone. It needs customer-location data, state-by-state sales totals, information about physical activities, and a breakdown of direct and marketplace transactions.

What Changes From State to State

The most important variable is classification. Some states tax particular forms of remotely accessed software or technology services, while others may exclude or differently classify the same offering. Contract language, invoicing, included services, and the customer’s use can matter. A subscription that combines software access, implementation, training, support, storage, or data services may require closer review than a single, clearly described product.

Texas illustrates why a broad nationwide statement is unreliable. The Texas Comptroller includes sellers of SaaS and application service providers among data-processing service providers. Under that treatment, 20% of a data-processing charge is exempt from tax. This is a Texas rule for SaaS classified as taxable data processing, not a rule that can be applied to customers in every state.

Nexus rules also vary. For Texas remote sellers, the relevant safe harbor is based on total Texas revenue, including taxable and nontaxable sales into the state. A remote seller exceeding $500,000 during the preceding 12 calendar months must obtain a permit and collect and remit tax. Collection must begin no later than the first day of the fourth month after the month in which the threshold is exceeded.

A seller required to obtain a Texas sales and use tax permit registers with the Texas Comptroller of Public Accounts. For remote sellers, registration is available through the Texas Online Tax Registration Application or by mailing Form AP-201, Texas Application. Other states use their own agencies, registration systems, account types, and requirements, so a Texas registration does not replace registration elsewhere.

How Marketplace Facilitators Affect SaaS Sellers

A SaaS provider may sell subscriptions through its own website, through a software marketplace, or through both. The platform’s role needs to be evaluated rather than assumed. A platform that processes a payment is not necessarily treated the same way as a marketplace facilitator responsible for collecting sales tax under a state’s law.

Where a qualifying facilitator is responsible for a transaction, the platform may collect and remit tax on the marketplace sale. That responsibility generally follows the covered transaction and should not be extended to subscriptions sold independently by the SaaS company. Sellers should distinguish:

  • Subscriptions sold and billed directly;
  • Transactions completed through a marketplace that has accepted collection responsibility;
  • Sales in which a platform provides payment or listing services without assuming the relevant tax obligation; and
  • Renewals, upgrades, add-ons, or services billed outside the original marketplace.

Texas again provides a useful, state-specific example. Marketplace providers engaged in business in Texas must collect, report, and remit state and local sales and use tax on marketplace sales and certify that responsibility to marketplace sellers. The rule applies to sales through the marketplace, not to a seller’s independent direct sales.

Seller location can change the result. A Texas-based seller must hold a Texas tax permit and file sales and use tax returns even if every sale occurs through a marketplace provider that collects the tax. By contrast, a remote seller selling only through a marketplace provider that has certified it will collect Texas tax is not required to hold a Texas permit. That remote seller must retain its marketplace sales records for at least four years, and the exception does not extend to direct sales outside the marketplace.

These distinctions are why a facilitator’s tax collection should not be treated as a universal exemption from registration. For a broader explanation of platform roles, see what a marketplace facilitator law does. The practical issues can also differ by platform, as discussed in the guide to whether Walmart Marketplace collects sales tax.

Common SaaS Sales-Tax Mistakes

Assuming every cloud subscription is treated alike

Product labels are not enough. A seller should document what customers can access, what services are included, how charges appear on invoices, and whether optional components are separately stated. Using one nationwide tax setting without reviewing state classification can lead to collection where tax is not due or failure to collect where it is.

Confusing an EIN with a sales-tax permit

An EIN is a federal business tax identifier administered by the IRS. The registration document is Form SS-4, Application for Employer Identification Number; it is not a state sales-tax permit. Businesses can obtain an EIN free from the IRS, and applicants whose principal place of business is in the United States may apply online. A legal entity such as an LLC, partnership, or corporation should be formed with its state before applying for the EIN.

A SaaS company may need both an EIN and one or more state sales-tax registrations, but the documents serve different purposes. Obtaining one does not establish the other.

Counting only taxable subscriptions toward nexus

A state’s economic-nexus calculation may not match the set of transactions on which tax is ultimately collected. The Texas remote-seller calculation, for example, includes both taxable and nontaxable Texas sales. Sellers should therefore retain complete state sales totals rather than tracking only invoices currently coded as taxable.

Ignoring sales outside the marketplace

A facilitator’s collection responsibility generally concerns covered marketplace transactions. Direct website subscriptions, enterprise contracts, renewals billed by the seller, consulting work, and other off-platform revenue may require a separate analysis. A mixed-channel business should avoid relying on a marketplace report as its complete nexus record.

What a SaaS Business Should Do Next

Start by creating a product and channel inventory. Describe each subscription tier, add-on, implementation service, support package, and other separately billed item. Then identify whether each transaction is direct or processed through a marketplace, and retain the platform’s documentation concerning its tax-collection role.

Next, organize revenue by customer destination and review the company’s physical activities. Compare those records with the current nexus and SaaS classification rules in each material state. Do not assume that the customer’s billing address, user location, contracting entity, or place of use will always produce the same sourcing result; the appropriate information depends on the state’s rules and the facts of the transaction.

Where both taxability and nexus point to an obligation, determine which state account is required and register before beginning seller collection. Where a marketplace facilitator collects, confirm exactly which transactions it covers and whether the seller still has a registration, filing, or record-retention obligation. Keep direct sales separate from facilitated sales in accounting records so returns can be prepared consistently.

Finally, revisit the analysis when the business adds a subscription feature, changes its contracts, enters a new marketplace, hires or assigns personnel in another state, or materially expands sales in a jurisdiction. SaaS tax treatment and registration exposure depend on current products, current channels, and current state rules—not simply on how the business was classified when it launched.

Frequently Asked Questions

Is SaaS taxable in every state?

No. SaaS does not have one nationwide sales-tax treatment. States classify remotely accessed software and related services under their own laws, so taxability depends on the customer’s state, the product’s features, and how related services are sold and invoiced.

Where does a SaaS company register for sales tax?

A SaaS company generally registers with the tax authority in each state where it has a registration obligation. That analysis considers the state’s treatment of the product, the seller’s physical or economic nexus, and whether a marketplace facilitator is responsible for particular transactions.

Does a marketplace collecting sales tax mean a SaaS seller never has to register?

No. Marketplace collection generally applies only to covered marketplace transactions. Direct subscriptions and other off-platform sales require separate review, and an in-state seller may still have permit and filing obligations. In Texas, for example, a Texas-based marketplace seller must hold a permit and file returns even when the marketplace collects all tax.

Does an EIN work as a SaaS sales-tax permit?

No. An EIN is a federal business tax identifier issued by the IRS through Form SS-4. A state sales-tax permit is a separate registration issued or administered at the state level.

How does Texas tax SaaS?

The Texas Comptroller includes SaaS sellers and application service providers among data-processing service providers. For SaaS classified as taxable data processing, 20% of the data-processing charge is exempt. This treatment is specific to Texas and should not be used as a nationwide rule.

Official Resources

Need a state sales tax number? We prepare and file your sales tax application for any state – it only takes a few minutes to submit.

Start your application »

Scroll to Top