For SaaS sales tax, the billing address is not always the place where the software is used. Sourcing determines the jurisdiction assigned to a sale; taxability determines whether that jurisdiction taxes the product. A reliable subscription workflow answers both questions and separately checks the seller’s collection obligation. This guide focuses on US customer-location evidence and multistate business accounts.
Key takeaways
Classify the actual software and services before assigning a tax rule.
Do not substitute a server location for a customer-use rule.
Obtain customer-supported allocation evidence where the state permits it.
Version location records so renewals and credits can be explained.
Separate nexus, taxability, and sourcing
A subscription sold online does not have one universal US tax treatment. Start by describing what the customer receives: access to prewritten software, custom development, data processing, information, support, or a combination. Marketing labels such as platform or AI service do not resolve the legal classification. Read the contract and inspect how the customer actually uses the service.
Then answer three questions in order: does the seller have a collection obligation, is the specific supply taxable, and where is the transaction sourced? A correct address does not fix an incorrect product classification. Use the SaaS taxability overview for the broader classification issue and the nexus determination guide for the seller’s connection to a state.
What New York’s remote-access software rule illustrates
New York’s Computer Software bulletin treats remotely accessed prewritten software as taxable. It locates the sale where the purchaser uses or directs use of the software, rather than where the software code resides. Where employees use it inside and outside New York, the bulletin directs sellers to collect on the receipt attributable to New York users. This is a New York rule, not a nationwide allocation policy.
The practical lesson is to request information that matches the relevant legal test. A central procurement address, corporate headquarters, hosting region, and employee work location describe different facts. Keep the applicable source next to the product decision so customer-support staff can explain why the invoice may not follow the card billing address.
Collect useful evidence without building a surveillance system
For a business account, consider a customer-certified schedule of authorized users and their relevant business locations. Record who supplied it, which subscription it covers, and its effective date. Ask the tax reviewer which fields are necessary before requesting granular personal data. A useful commercial record can often be maintained without storing a history of every login.
IP-derived location may be affected by VPNs, travel, shared gateways, and remote desktop connections. Treat discrepancies as questions to resolve rather than silently replacing the customer’s declared information. Keep the original declaration and the resolution. An invoice system should distinguish a verified location from a fallback address so the fallback can be reviewed before recurring bills accumulate.
Worked example: allocating a business subscription
Assume a hypothetical $1,200 monthly subscription has 12 equally priced seats. The customer’s supported records assign four seats to New York and eight outside New York. If the applicable facts and allocation method support that split, the New York portion would be $1,200 × 4 ÷ 12 = $400. The appropriate state and local rate is then applied to that portion; the other $800 still requires analysis in its relevant jurisdictions.
This is an arithmetic illustration, not a guarantee that seat count is suitable for every contract. An enterprise agreement may price different modules, shared access, or usage differently. Document why the allocation basis reflects the purchased rights. Never treat the remaining amount as automatically exempt merely because it falls outside the first state reviewed.
Why Texas needs a separate product and use analysis
Texas’s data-processing guidance illustrates a different framework. Qualifying data-processing services generally receive a 20% exemption, with tax applying to the remaining charge. The Comptroller also addresses services used by a business in multiple states. Classification and documentation requirements must be checked before applying either treatment; “SaaS” on an invoice is not sufficient evidence.
Keep a separate rule record for each jurisdiction rather than building one nationwide percentage into the billing system. The record should explain the product category, taxable base, permitted documentation, sourcing basis, and reviewer. For a Texas implementation, start with the official data-processing publication and current Rule 3.330, then connect the result to the Texas sales tax guide.
Handle renewals, location changes, and credits consistently
Ask the customer to update its location schedule when seats are added, teams relocate, or the agreement renews. Retain the version used on each invoice. Do not overwrite prior allocations with today’s customer profile: doing so can make a credit memo impossible to reconcile to the original charge.
Before rollout, test a single-location customer, a multistate account, an incomplete declaration, a mid-term change, and a refund of a prior invoice. For every case, compare the invoice lines with the approved rule and source evidence. The checkout testing guide provides the wider testing process. Resolve inconsistent results before turning on automatic renewals.
Frequently asked questions
Does the SaaS server’s location set the customer’s tax rate?
Not under New York’s cited remote-access software rule. The purchaser’s use or direction of use is relevant there. Other states require their own analysis.
Is a business subscription automatically exempt?
No. Business status does not itself establish an exemption. Product classification and any valid exemption documentation still matter.
Can I use the same allocation percentage forever?
Treat an allocation as dated evidence. Review it when the underlying contract or customer-use facts change, and preserve historical versions.
Official sources
Reviewed against the following primary sources on Sep 18, 2026.