Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
Sales tax nexus is one of those compliance topics that SaaS finance teams know they should understand but rarely get fully comfortable with. The concept is straightforward—nexus is the legal threshold at which a business becomes obligated to collect and remit sales tax in a state—but the practical details are more complex than most introductory explanations suggest. Economic nexus thresholds vary by state. Product taxability rules for SaaS vary even more. And the interaction between employee locations, revenue levels, and product categories creates a compliance picture that is genuinely difficult to manage without systematic tooling and periodic professional review.
This article is for finance leaders and controllers at SaaS companies who want to understand where their company actually owes tax, what triggers a nexus obligation, and how remote team distribution changes the calculus. It covers US state-level sales tax in depth, touches on the major international frameworks, and describes the practical steps for getting from exposure analysis to compliant collection. This is not a guide to filing mechanics or a state-by-state rate table—those are available from tax authorities directly. The goal is to give finance leaders the framework to have an informed conversation with a sales tax advisor and to decide when and how to automate.
Nexus comes in two forms, and both apply to SaaS companies.
Physical nexus has existed for decades: a business with a physical presence in a state—an office, a warehouse, or employees—is obligated to collect sales tax from customers in that state. For SaaS companies, the most common source of physical nexus is employee location. A software company where all engineers work remotely, distributed across eight states, has physical nexus in all eight of those states—regardless of where the company is incorporated or headquartered, and regardless of whether it has crossed any revenue threshold in those states.
Economic nexus emerged as a legal framework after the Supreme Court's 2018 decision in South Dakota v. Wayfair, which allowed states to impose collection obligations on sellers with no physical presence, based solely on the volume of sales into the state. As of 2026, every US state with a sales tax has enacted some form of economic nexus law. The standard threshold is $100,000 in annual in-state sales or 200 in-state transactions per calendar year—but the specifics vary meaningfully across states.
Texas and California use $500,000 revenue thresholds. Kansas has eliminated the transaction count threshold entirely. Florida applies the threshold to taxable transactions only, not gross revenue. Tennessee measures by fiscal year rather than calendar year. For a SaaS company growing at 80–100% year over year, this landscape means new nexus obligations are being triggered continuously. Getting a current-state nexus analysis is the prerequisite for all other compliance steps.
Nexus creates an obligation to collect tax—but only if the product being sold is taxable in that state. This is where SaaS gets complicated.
There is no federal definition of SaaS for sales tax purposes. Each state makes its own determination of whether SaaS falls within its taxable categories, and the definitions are inconsistent. Several states follow the Streamlined Sales Tax Project model and tax SaaS under a "specified digital products" category—this includes Michigan, Indiana, and New Jersey among others. Some states, including Tennessee and Washington, tax software delivered electronically as if it were prewritten software on a tangible medium, regardless of delivery method. New York taxes SaaS under a broad information services category that captures most cloud software.
Other states—including California, Florida, and Texas in certain interpretations—do not tax pure SaaS, though "pure SaaS" is itself a contested term in tax law. Companies selling access to functionality via browser or API may be exempt, but the line between taxable software and non-taxable SaaS is litigated regularly and changes with legislative action.
The practical implication: a SaaS company may have nexus in 15 states but taxability only in 8 of them. Running both analyses simultaneously—nexus exposure and product taxability by state—determines the actual collection obligation. Anrok and qualified sales tax advisors can assist with this combined analysis, with Anrok's Atlas research layer providing AI-backed analysis verified by tax professionals.
Remote employee locations are the most under-tracked source of physical nexus for SaaS companies. The mechanics are straightforward: an employee working from their home in Georgia creates physical nexus for the company in Georgia, regardless of where the company is headquartered or incorporated.
The practical effect for a distributed SaaS company with 30–50 remote employees is significant. A company with employees in 12 states has physical nexus in those 12 states on day one—meaning the economic nexus threshold analysis is largely irrelevant for those states. If any of those 12 states also tax SaaS under their product taxability rules, the company has an immediate collection obligation that began when the first employee was hired in that state.
Most finance teams don't have a clean process for tracking this. Payroll systems know where employees work, but that information is rarely connected to the sales tax compliance workflow. Anrok specifically addresses this gap by integrating with HR and payroll systems—including Rippling, Gusto, and Workday—to automatically incorporate employee locations into the nexus analysis. When a new employee is onboarded in a new state, the platform identifies the resulting nexus exposure and prompts the appropriate registration step.
US sales tax is complex, but it operates within a coherent legal framework. International VAT obligations add a second layer of complexity for SaaS companies with global customers.
The European Union's One Stop Shop (OSS) scheme simplified compliance for B2C digital services: a company can register in one EU member state and file a single return covering all EU B2C sales. The threshold for mandatory registration under OSS is effectively zero—EU regulations require registration from the first sale to EU consumers. The rate applied is the destination country's standard VAT rate, which ranges from 17–27% across member states.
For B2B sales within the EU, reverse charge mechanisms typically shift the VAT obligation to the customer. This simplifies compliance for SaaS companies selling primarily to business customers: the seller doesn't charge or remit VAT, and the buyer accounts for it under their local rules. However, this requires confirming business customer status and retaining valid VAT ID records for each customer, which creates an ongoing data management requirement.
The UK operates its own VAT regime post-Brexit. Australia's GST applies to digital services from the first dollar of sales to Australian consumers. Canada's GST/HST threshold is C$30,000 in annual sales to Canadian customers. Each jurisdiction has its own registration, filing, and remittance process. For SaaS companies with $1M+ in international ARR, managing these obligations manually across multiple jurisdictions is not feasible. Platforms like Anrok cover the full international compliance stack—registration, calculation, filing, and remittance—for companies with complex cross-border exposure.
The discovery that a company has uncollected nexus exposure in multiple states requires a structured response:
Quantify the exposure: Determine the dollar amount of uncollected tax in each state over the relevant lookback period—typically three to four years for most state statutes of limitations. This is the basis for prioritizing states and determining whether voluntary disclosure makes economic sense.
Evaluate voluntary disclosure options: Most states offer voluntary disclosure agreements (VDAs) that allow companies to register and pay past-due tax with penalty waivers and sometimes reduced interest. VDAs typically cap the lookback period, limiting exposure. Most finance advisors recommend VDA for any state where historical exposure exceeds a few thousand dollars.
Register and implement collection: Once historical exposure is addressed, register in each nexus state and implement the automation platform to begin collecting on current and future transactions.
Establish ongoing monitoring: Economic nexus thresholds are measured on rolling or calendar-year bases, and new threshold crossings require new registrations. An automation platform handles this monitoring continuously; a manual process requires quarterly reviews and is prone to miss trigger events during periods of rapid growth.
For a SaaS company approaching or past $1M ARR with customers in multiple states, the most practical starting point is a nexus analysis—either through a sales tax advisor or through Anrok's platform, which offers a nexus dashboard pulling current revenue by state against current thresholds. The analysis determines whether historical exposure needs to be addressed before automation goes live.
For billing entirely within Stripe, Stripe Tax is the lowest-friction way to begin collecting in nexus states once the analysis is complete. For more complex billing environments or significant international revenue, Anrok provides the broader coverage to handle the full compliance picture. TaxGPT is worth noting for the research layer: finance teams or tax advisors who need to research specific state taxability rules for SaaS products can use TaxGPT's research module to get fully cited analysis across US federal, state, and local tax law—particularly useful for the product taxability analysis where rules are inconsistent and frequently updated.
Sales tax nexus for SaaS is more complex than it appears, but the decision framework is clear: know where you have nexus from both economic thresholds and physical presence, know which states tax your product, and implement the collection and remittance process for the intersection. The cost of addressing this proactively is a fraction of the cost of remediation under audit.
The immediate next step is the nexus analysis. Pull historical revenue by state, overlay employee location data from payroll, and compare the result against current state thresholds. The resulting exposure map is the input for every subsequent compliance decision.
**Q: Do I need to collect sales tax from business customers (B2B)?**In many cases, no. B2B customers with valid sales tax exemption certificates are exempt from collection. However, you must obtain and retain the certificate to support the exemption in an audit.
**Q: Can a SaaS company owe sales tax in a state where it has no employees and no office?**Yes. Economic nexus applies based on revenue and transaction count alone. A company with no physical presence that sells $600,000 of SaaS to customers in a state that taxes SaaS and uses a $500,000 threshold has a collection obligation.
**Q: What's the typical penalty for uncollected sales tax?**Penalties vary by state but typically range from 5–25% of the unpaid tax, plus interest from the date it was due. VDA programs typically waive penalties in exchange for proactive registration and payment.
**Q: Does the economic nexus threshold reset each year?**Yes, for most states. Economic nexus thresholds are measured on a calendar-year or rolling 12-month basis. A company that falls below the threshold does not automatically lose nexus—most states require affirmative de-registration.
**Q: How does economic nexus work for marketplace sales?**In states with marketplace facilitator laws—which is most states—the marketplace is responsible for collecting and remitting tax on marketplace sales. This doesn't affect direct sales obligations.
