Is SaaS taxable in Texas? A developer's guide to the state's 80/20 rule

If you are building checkout systems or billing architecture that must calculate SaaS sales tax, this guide covers Texas's SaaS taxability classifications, local tax stacking caps, enterprise multistate apportionment, and how the Ziptax Sales Tax API returns verified rates without requiring you to manually build an internal tax engine.

Texas SaaS sales tax at a glance

Product Taxability Rules

State Registration & Collection Triggers

Which types of software does Texas tax?

Texas does not draw the tax line solely on the delivery mechanism. Instead, it classifies software based on statutory definitions of tangible personal property versus enumerated services.

Remotely hosted cloud software is classified as an enumerated data processing service, granting it a statutory 20% deduction that does not apply to other software formats.

How do you charge the correct sales tax rate for SaaS in Texas?

To calculate sales tax on Texas SaaS, you must apply the combined state and local tax rate to 80% of the gross sales price, not to the total invoice amount.

For example, billing a Texas business $1,000 for a monthly SaaS subscription looks like this:

1. Multiply the $1,000 charge by 80% to get the taxable base: $800.
2. Apply the combined rate for the customer’s address to that $800, not to the full $1,000.
3. The remaining $200, the exempt 20%, owes no tax at all.

Either way, engineering teams have two options for resolving the actual combined rate at a given address: call a real-time sales tax API, or manually build and maintain an internal rate engine.

Option 1: Use the Ziptax Sales Tax API

The Ziptax Sales Tax API evaluates physical street-level rooftop addresses and returns accurate tax rates accounting for overlapping municipal boundaries, transit authorities, and the statutory 2.0% local cap.

To calculate a live rate against a Texas address, call the v60 endpoint:

Bash

curl -G https://api.zip-tax.com/request/v60 \
    -H "X-API-KEY: <apiKey>" \
    -d key=your-api-key \
    --data-urlencode "address=301 Congress Ave, Austin, TX, 78701"

To verify complete payload structures, explore the REST API documentation.

When integrating the API response into your billing stack:

• Apply the 80% Proration Logic: The API returns the authoritative combined tax rate for the coordinate or street address. For SaaS transactions, multiply that rate by 80% of the line-item subtotal.
• Store Regulatory Metadata: Record the returned jurisdiction identifiers, transit district codes, and transaction timestamps to defend audits and substantiate local use tax distribution.
• Dynamic Catalog Tagging: To systematically differentiate between 80% taxable SaaS, 100% taxable downloads, and exempt custom services, review Taxability Information Codes (TICs) or search for the correct product code to ensure appropriate catalog assignment.
• Exemption Tracking: Maintain active records when B2B accounts provide multi-state allocation forms or resale certificates. You can programmatically manage exemption certificates through Ziptax compliance tools.
• Filing and Remittance: When economic volume requires automated remittance, you can set up merchant management to route reporting data to TaxCloud for automated state filing.

Option 2: Build and maintain an internal engine

If you choose to build internal billing rules for Texas, your setup needs to accommodate four statutory hurdles:

1. Enforce the 2% Local Statutory Cap: Texas local jurisdictions (cities, counties, special purpose districts, and transit authorities) frequently have aggregate enacted rates exceeding 2.0%. Texas law enforces a hard 2.0% maximum local use tax rate under Texas Tax Code Chapters 321 and 323. Your logic cannot simply sum all overlapping local district rates. In areas where posted rates exceed 2.0%, local use tax is allocated strictly by priority order: City tax takes priority first, County tax second, Special Purpose District (SPD) tax third, and Transit Authority (MTA/CTD) tax last.
2. Single Local Use Tax Rate Election (1.75%): Under Texas Tax Code § 151.0595 and 34 TAC § 3.334(i), remote sellers without a physical place of business in Texas can elect to collect a flat 1.75% Single Local Use Tax rate instead of calculating destination-specific municipal and special district rates. This results in a uniform 8.00% combined rate statewide (6.25% state + 1.75% local). However, this election must be formally filed with the Comptroller, cannot be used by businesses with physical nexus in Texas, and cannot be used by marketplace providers.
3. Proration Order of Operations: Internal tax calculation must separate taxability classification from rate calculation. Flagging SaaS as "taxable" in an enterprise billing tool will overcollect by 20% on every order unless the base proration engine executes before the rate multiplier.
4. Origin vs. Destination Sourcing Rules: Under 34 TAC § 3.334, Texas sellers with a physical place of business in the state where orders are received collect local sales tax based on the seller's location (origin). Remote sellers lacking physical presence collect local use tax based on the customer's delivery or receipt location (destination), unless the seller has elected the flat 1.75% single local use tax rate.

Five things to watch out for if you take this route:

1. ZIP-based shortcuts, including ones that overcharge. Texas's 2% local cap means a flat add-up of every jurisdiction's posted rate can land above what's actually owed. In Waxahachie, for example, the city's own use tax can't be collected at its full posted rate without pushing the total over the 2% cap, so the actual combined rate collected comes in below a naive sum of the jurisdictions involved. Resolve rates from the full street-level address, not a ZIP-level guess in either direction.
2. Applying the 80/20 discount to the wrong product line, or forgetting it entirely. The exemption is specific to data processing services (SaaS). Downloaded software, software on physical media, and digital goods such as e-books, audio, and video are all taxed on 100% of the price. A billing system that applies one taxability rule across every "software" SKU will get either SaaS or the other categories wrong.
3. Mixing up where "place of business" actually sits. Texas's statutory definition of a place of business for sourcing purposes is about where sales personnel receive orders, not where your infrastructure lives. A SaaS company can run every server in another state and still have local sales tax sourced to a Texas sales office, and conversely, hosting infrastructure in Texas does not by itself create a place of business for sourcing.
4. Treating the single local use tax rate as automatically available. Remote sellers with no Texas place of business can elect a flat 1.75% single local use tax rate instead of calculating the exact combined local rate for every destination address; the rate is published in the Texas Register by January 1 each year. Businesses with a Texas presence, and marketplace providers, cannot use it, and it has to be formally elected (and can be revoked) rather than applied by default.
5. Assuming registration is immediate once you cross the threshold. Texas gives you until the first day of the fourth month after the month you exceed the $500,000 safe harbor to get registered and start collecting. Treating every day past the crossing date as already past due, or conversely assuming you have no deadline at all, both produce the wrong operational trigger.

When does a SaaS business have to collect sales tax in Texas?

Tax collection obligations are triggered by establishing physical or economic nexus. To review baseline standards across states, view collection requirements and nexus guidelines.

For Texas specifically, follow these operational rules to determine when your obligations start.

Rule 1: Monitor registration thresholds

A remote software vendor must register with the Texas Comptroller when either condition occurs:

• Physical Presence: Maintaining an office, resident employee, physical hardware, or owned/leased real property in Texas.
• Economic Threshold: Total gross revenue from Texas sales exceeds $500,000 over the preceding 12 calendar months. Remote vendors must check economic nexus thresholds continuously.

Because Texas evaluates economic nexus on gross revenue, exempt sales, marketplace sales, and the 20% exempt portion of SaaS all count toward the $500,000 threshold. Texas does not enforce a transaction count threshold.

Rule 2: Comply with the statutory grace period

Under 34 TAC § 3.286(b)(2), Texas does not require immediate same-day registration upon crossing the $500,000 threshold. A remote seller has until the first day of the fourth month following the month in which the threshold was exceeded to obtain a sales tax permit and begin collecting tax. For example, if your trailing 12-month Texas revenue surpasses $500,000 on June 15, you must register and begin collecting tax by October 1.

Where Ziptax helps

Building an internal sales tax engine requires continuous statutory maintenance, local boundary geocoding, and rules-based base proration. Ziptax provides a direct API infrastructure layer designed to handle state-specific nuance seamlessly:

• Rooftop Boundary Resolution: Pinpoints exact municipal, transit, and special purpose district lines using physical address coordinates, eliminating the miscalculations of ZIP-code rate matching.
• Built for Checkout Speed: Sub-millisecond response times engineered for direct checkout pipelines, SaaS subscription renewals, and custom ERP integrations.
• Transparent Architecture: Simple developer integration with zero enterprise lock-in.
• The TaxCloud Runway: When your transaction volume scales or your users demand automated filing and remittance services, you can pair Ziptax with TaxCloud for the rest of compliance. You get a lightweight API to deploy today and a filing and remittance backend ready when you need it.

Get Texas SaaS tax rates from an API

Address-level rates for every Texas jurisdiction, plus the rest of the US, Canada, and select other markets. Free starter plan, then scalable usage-based pricing.

Frequently asked questions

Do you have to register in Texas if only 80% of your SaaS revenue is taxable?

Yes, if your gross Texas receipts exceed $500,000. Under 34 TAC § 3.286, economic nexus is determined by total gross revenue sourced to Texas, which includes taxable sales, nontaxable sales, the exempt 20% portion of SaaS, and sales for resale.

Why is SaaS only 80% taxable in Texas?

Texas Tax Code § 151.0035 classifies SaaS as an enumerated data processing service. Texas Tax Code § 151.351 statutorily exempts 20% of the value of data processing and information services from sales and use tax. The Comptroller automatically applies this 20% deduction to all cloud-hosted software subscriptions.

Does Texas tax downloaded software differently than SaaS?

Yes. Downloaded prewritten software is classified as tangible personal property under Texas Tax Code § 151.009 and 34 TAC § 3.308. It is taxed on 100% of the sales price and does not receive the 20% data processing exemption.

How does Texas tax custom software developed for a single client?

Custom software programs and customized application development are 100% taxable as tangible personal property under Texas Tax Code § 151.009 and 34 TAC § 3.308(b)(1). Texas does not provide a general exemption for custom programming when the client receives an operational computer program.

Can remote sellers use the flat 1.75% local tax rate?

Yes. Under Texas Tax Code § 151.0595, remote sellers without a physical place of business in Texas may elect to collect the Single Local Use Tax rate (currently 1.75%) instead of tracking individual city and district rates across the state. This rate must be officially elected with the Comptroller and cannot be used by vendors with physical nexus in Texas.

Sources

1. Texas Tax Code § 151.0035 (Data Processing Services Defined): https://statutes.capitol.texas.gov/Docs/TX/htm/TX.151.htm#151.0035
2. Texas Tax Code § 151.351 (Information Services and Data Processing Services 20% Exemption): https://statutes.capitol.texas.gov/Docs/TX/htm/TX.151.htm#151.351
3. Texas Tax Code § 151.009 (Tangible Personal Property Defined): https://statutes.capitol.texas.gov/Docs/TX/htm/TX.151.htm#151.009
4. Texas Tax Code § 151.0595 (Single Local Use Tax Rate): https://statutes.capitol.texas.gov/Docs/TX/htm/TX.151.htm#151.0595
5. 34 Texas Administrative Code § 3.330 (Data Processing Services & Multistate Apportionment): https://texreg.sos.state.tx.us/public/readtac$ext.TacPage?sl=R&app=9&p_dir=&p_rloc=&p_tloc=&p_ploc=&pg=1&p_tac=&ti=34&pt=1&ch=3&rl=330
6. 34 Texas Administrative Code § 3.308 (Computers—Hardware, Computer Programs, Services, and Sales): https://texreg.sos.state.tx.us/public/readtac$ext.TacPage?sl=R&app=9&p_dir=&p_rloc=&p_tloc=&p_ploc=&pg=1&p_tac=&ti=34&pt=1&ch=3&rl=308
7. 34 Texas Administrative Code § 3.286 (Seller's and Purchaser's Responsibilities, Nexus, and Registration): https://texreg.sos.state.tx.us/public/readtac$ext.TacPage?sl=R&app=9&p_dir=&p_rloc=&p_tloc=&p_ploc=&pg=1&p_tac=&ti=34&pt=1&ch=3&rl=286
8. 34 Texas Administrative Code § 3.334 (Local Sales and Use Taxes Sourcing & Priority Rules): https://texreg.sos.state.tx.us/public/readtac$ext.TacPage?sl=R&app=9&p_dir=&p_rloc=&p_tloc=&p_ploc=&pg=1&p_tac=&ti=34&pt=1&ch=3&rl=334
9. Texas Comptroller of Public Accounts, Publication 94-105 (Local Sales and Use Tax Collection Priority): https://comptroller.texas.gov/taxes/publications/94-105.php
10. Texas Comptroller of Public Accounts, Remote Sellers Guidelines: https://comptroller.texas.gov/taxes/sales/remote-sellers.php