Do App Developers Need a Sales and Use Permit in Texas: What It Means for B2B Teams (2026)

TL;DR

Overview

This guide is for app developers, SaaS founders, and B2B product teams who sell software into Texas — or are building revenue operations for companies that do.

Texas is the second-largest US state by GDP and a major market for B2B software. It also has some of the most specific digital product tax rules in the country. Unlike states that treat all software identically, Texas distinguishes between SaaS (taxed at 80% of revenue), downloaded canned software (taxed at 100%), and custom software (also taxed at 100%).

According to the Texas Comptroller's taxable services guide, data processing services — which include most SaaS products — have been taxable since 1984. The 20% exemption was added to balance that classification with the encouragement of tech industry growth. Understanding which category your product falls into determines your exact tax liability.

What Is a Texas Sales and Use Permit?

A Texas sales and use permit is a license issued by the Texas Comptroller of Public Accounts that authorizes a business to collect sales tax on taxable goods and services sold in Texas. It also covers use tax — a complementary tax owed when you purchase taxable goods or services from out-of-state vendors who did not collect Texas tax.

The permit is free to obtain. There is no annual renewal fee. It does not expire, but you must actively file returns (even zero returns) once registered.

The permit is required before you start collecting tax — not as an afterthought. Collecting tax without a permit, or failing to collect and remit tax when required, both create liability.

Do App Developers Need a Sales and Use Permit in Texas?

Yes — if two conditions are both true: you sell a taxable product or service, and you have nexus in Texas.

Apps, SaaS subscriptions, downloadable software, and most digital products are taxable in Texas. Nexus — the legal connection that gives Texas authority to require you to collect tax — can be triggered by physical presence or economic volume.

Most app developers who have been selling to Texas customers for any meaningful period have already crossed the economic nexus threshold and are obligated to register, collect, and remit — even if they are headquartered in another state.

The Texas Comptroller's position is clear: digital products that deliver ongoing access to hosted software or data processing — the core model for most SaaS and subscription apps — are taxable data processing services. There is no carve-out for "pure software" or "information services" that would exempt a typical B2B app.

How Texas Taxes Apps, SaaS, and Digital Products

Texas uses a product-type classification system. Where your app falls in that system determines both whether it is taxable and how much of the sale price is subject to tax.

The 20% Exemption Rule for SaaS

SaaS products are classified as data processing services in Texas. State law grants a 20% partial exemption on data processing services — meaning only 80% of the sale price is subject to the 6.25% state rate.

In practice: a $100/month SaaS subscription generates $80 of taxable revenue. At the state rate of 6.25%, that is $5.00 in state tax per $100 billed. Local rates (up to 2%) apply on top, bringing the maximum to $6.60 per $100.

The exemption applies automatically — you do not need to file a separate exemption claim. You simply calculate tax on 80% of the data processing portion of each invoice.

Fully Downloadable Apps and Software

Apps sold as one-time downloads — where the customer receives a file they install locally — are treated as tangible personal property in Texas. The full sale price is taxable with no partial exemption.

If your product is a hybrid — a downloaded app that also uses cloud features — Texas may classify the bundled product as a data processing service, applying the 80% rule to the whole price. The Comptroller recommends consulting their office at 800-531-5441 for bundled product classifications.

Economic Nexus: The $500K Threshold

Texas established economic nexus rules on October 1, 2019, following the Supreme Court's 2018 South Dakota v. Wayfair decision. Remote sellers — including app developers and SaaS companies headquartered outside Texas — must register once they cross $500,000 in total Texas sales during the preceding 12 calendar months.

Key details on how the threshold is calculated:

• All sales count toward the threshold — taxable, non-taxable, and exempt transactions are all included. A SaaS company with $600K in Texas revenue where $100K is exempt still crosses the threshold.
• Rolling 12-month window — not calendar year. Calculate continuously, not just at year-end.
• Collection start date — once you cross $500K, collection begins on the first day of the fourth calendar month after the threshold is exceeded.
• No transaction count threshold — Texas uses only the dollar threshold, not a transaction count minimum like some other states.

For most B2B SaaS companies with meaningful Texas customer bases, $500K in annual Texas revenue is a realistic threshold to hit. A team of 10 Texas enterprise customers at $50K ARR each crosses it. Plan your compliance calendar around your Texas revenue trajectory, not just your current state.

Physical Nexus Triggers

Physical nexus exists the moment your business has a physical connection to Texas — and it triggers registration immediately, with no revenue threshold to clear.

Common physical nexus triggers for app developers:

• An employee or contractor working in Texas — even part-time or remote workers who live in Texas create nexus for their employer
• An office, co-working space, or business address in Texas
• Servers or data center infrastructure hosted in Texas (though cloud infrastructure on shared AWS or Azure typically does not create nexus)
• Attending a trade show or conference in Texas and making sales there
• Storing inventory in a Texas warehouse (relevant for hardware-attached apps)

A single Texas-based engineer on your payroll creates physical nexus. If you are scaling your team and hiring in Texas, coordinate your tax registration with your first Texas hire — not six months later.

How to Register for a Texas Sales and Use Permit

Registration is free and done online through the Texas Comptroller's eSystems portal. Here is the process step by step:

Step 1 — Gather Your Information

You will need: your federal EIN (or SSN for sole proprietors), your NAICS code (most SaaS companies use 511210 — Software Publishers), your business legal name and address, a description of what you sell, and the date you first made a taxable Texas sale.

Step 2 — Complete the Online Application

Go to comptroller.texas.gov/taxes/permit and complete the Texas Online Tax Registration Application. For multi-location businesses, you can register all locations in a single application. The form takes 15–30 minutes for most businesses.

Step 3 — Receive Your Permit

Permits are typically issued within 2–4 business days. Your permit number is your Texas Taxpayer ID. Post the permit at your Texas business location if you have one — this is legally required for physical locations.

Step 4 — Configure Tax Collection in Your Billing System

Before issuing your first post-registration invoice, configure your billing platform (Stripe, Chargebee, Recurly, etc.) to collect tax on Texas transactions. For SaaS, set the taxable amount to 80% of the subscription price. Document this configuration so you can demonstrate compliance methodology during any future audit.

Filing Frequencies and Remittance Deadlines

Texas assigns a filing frequency based on your sales tax liability. Most app developers and SaaS companies start with quarterly or annual filing, then move to monthly as revenue grows.

You must file a return even in periods with zero Texas tax collected. Zero returns confirm to the Comptroller that your account is active and compliant — skipping them triggers notices.

Late payment penalties: 5% if paid within 30 days of the due date, 10% if paid after 30 days. Interest accrues on top of penalties at the annual rate set by the Comptroller. For fast-growing SaaS companies, one missed quarterly filing can mean a five-figure penalty if tax liability was high.

B2B Exemptions and Resale Certificates

A common misconception: B2B software sales are automatically tax-exempt. They are not. Texas taxes B2B and B2C software sales identically.

There are two legitimate paths to a tax-exempt B2B transaction:

1. Resale Certificate

If your B2B customer is reselling your product or service as part of their own taxable product — for example, a software agency that builds apps for clients using your API — they can provide a valid Texas resale certificate. You collect no tax on that transaction.

Keep the certificate on file. If you are audited and cannot produce it, you owe the tax plus penalties — even though the customer was legitimately exempt.

2. Statutory Exemption Certificate

Texas grants tax exemptions to qualifying organizations: nonprofits, churches, educational institutions, and government entities. These customers provide an exemption certificate (Texas Form 01-339 or equivalent). Collect and retain the certificate for each exempt transaction.

Standard commercial B2B customers — corporations, partnerships, LLCs buying software for their own operations — do not qualify for either exemption. Tax applies in full.

Common Pitfalls for App Developers

These are the mistakes that generate the largest back-tax exposures for digital product companies selling into Texas.

1. Treating All Digital Products as Non-Taxable

Many app developers assume software is not a "physical product" and therefore not taxable. Texas has taxed digital goods and data processing services since 1984. The assumption that software escapes sales tax in Texas is wrong and expensive.

2. Ignoring Economic Nexus Until Audited

A fast-growing SaaS with 50 Texas customers paying $20K/year each has $1M in Texas revenue — double the nexus threshold — and likely has never registered. The Comptroller can audit up to 4 years of records. At 8.25% on 80% of $1M, that is $66,000 in back tax before penalties and interest.

3. Miscalculating the Taxable Amount for SaaS Bundles

If your product bundles SaaS access with professional services, implementation fees, or hardware, you must separate the data processing component and apply the 80% rule only to that portion. Applying 80% to a bundled invoice that includes fully taxable components underpays the tax.

4. Losing Exemption Certificates

Accepting a verbal or undocumented claim of exempt status from a customer — even a real nonprofit — means you are liable for the tax if audited without a certificate on file. Require certificates before zeroing out tax on any transaction. Build this into your sales process, not your finance process.

5. Forgetting to File Zero Returns

If you have a period with no Texas revenue — because a customer cancelled or you paused sales — you still must file a return showing zero liability. Missing returns trigger the Comptroller to estimate your liability and issue a deficiency notice, which creates administrative work and potential penalties to clear.

What This Means for B2B GTM Teams

Texas is a priority market for most B2B software companies. Its technology corridor — Austin, Dallas, Houston, San Antonio — concentrates enterprise buyers in finance, energy, healthcare, and logistics. If your go-to-market strategy targets B2B enterprise accounts, Texas is likely in your top-3 US markets by revenue opportunity.

That means sales tax compliance is not a back-office concern — it is a revenue operations requirement. Deals stall when procurement teams ask for tax certificates you cannot provide. Enterprise buyers in Texas routinely require vendors to confirm permit status as part of vendor onboarding.

Build Compliance Into Your GTM Stack Early

The most efficient approach: register before you close your first Texas enterprise deal, not after procurement asks. Sales tax permit registration takes 30 minutes and 2–4 days. Retroactive compliance after an audit takes months and a tax attorney.

For B2B teams using a CRM, tagging Texas accounts and flagging their tax status in the contact record is a simple operations step that prevents compliance gaps as you scale. Pair this with your SaaS enrichment stack to ensure billing addresses are accurate — tax jurisdiction depends on where the customer is, not where you are.

Use Automated Tax Tools for Scale

At 50+ Texas customers, manually tracking tax calculations across invoices creates risk. Tools like Avalara, TaxJar, and Stripe Tax handle state-by-state calculation, the 80% SaaS rule, and return filing automation. This is a non-negotiable investment once you cross $500K in Texas ARR.

For teams operating at scale across multiple states, understanding sales tax exposure by state belongs in your GTM engineering infrastructure alongside CRM hygiene, enrichment, and outbound sequencing.

Teams using SyncGTM for waterfall enrichment can ensure every Texas account has an accurate billing address, state, and company profile — the foundation for correct tax jurisdiction assignment. Clean account data prevents billing Texas customers at the wrong local rate, which is one of the most common audit triggers.

See our full breakdown of what waterfall enrichment is and how it works to understand how enriched account data supports both outbound targeting and revenue operations compliance.

Conclusion

Do app developers need a sales and use permit in Texas? Yes — and most SaaS companies selling into Texas have crossed the threshold already.

Economic nexus at $500K covers most meaningful B2B software businesses. Physical nexus covers anyone with a Texas employee. Texas taxes 80% of SaaS revenue at up to 8.25%. B2B sales are not exempt unless the customer provides a valid certificate.

Register before your first Texas enterprise deal closes — not after procurement asks. The process takes 30 minutes and 2–4 days. Ignoring it creates back-tax exposure that compounds every quarter.

For B2B GTM teams, clean account data — accurate billing addresses, verified state codes — is the operational foundation for correct tax jurisdiction. Pair that with automated tax calculation and a filing cadence, and compliance becomes a solved problem rather than an audit risk.

Ready to build clean account data into your revenue stack? Try SyncGTM free. Waterfall enrichment across 50+ providers returns verified firmographic and contact data for every account in your ICP — the foundation for both outbound targeting and accurate billing.