Your next state tax obligation may come from a new customer, a remote employee, or a change in how a state taxes software, not just a sales threshold. A multi-state tax nexus analysis for SaaS companies needs to look across these activities because each state may apply different rules to sales, income, and payroll taxes.
If customer, billing, payroll, and finance records sit in separate systems, it can be hard to see the full picture. A review done once can also become outdated as your company adds customers, hires across state lines, or changes its services. This guide explains how to identify the states and activities to review, which questions need state-specific verification, and how to build a repeatable process for monitoring potential obligations.
We’ll cover how customer sales and employee locations can factor into a review, why SaaS tax treatment varies by state, and how to connect tax research with business records. For businesses in San Francisco, San Mateo, San Jose, Walnut Creek, Santa Rosa, San Leandro, Menlo Park, and Sacramento, connecting State & Local Tax (SALT) questions with accounting and payroll data can make ongoing reviews more practical as the business grows.
Nexus is a connection between a business and a state that may bring tax responsibilities into consideration. The connection can arise from different kinds of business activity, and each state sets its own rules. For a SaaS company, a nexus review helps identify where activity may need a closer look. It isn’t, by itself, a decision that the company must register, collect a tax, or file a return.
The idea of nexus changed for remote sellers after the U.S. Supreme Court’s 2018 decision in South Dakota v. Wayfair, Inc., which allowed states to use sales activity, rather than physical presence alone, as a basis for sales tax nexus. That’s one reason a company’s headquarters state may not be the only jurisdiction to review. Customer sales, employee locations, offices, and other business activity can raise different questions in different states.
Illustrative example: A Bay Area SaaS company has its main office in San Francisco, customers in several states, and an employee working remotely elsewhere. Those facts may warrant a review of the relevant states. They don’t, on their own, confirm which taxes apply or what steps the company must take.
Start with a practical inventory of customer locations, sales, offices, and other business activity. Include employee and contractor locations as facts to assess, not as automatic proof of a filing obligation. Bring together records from billing, finance, HR, and payroll so the review reflects how the company actually operates.
Then check how each state treats the company’s specific SaaS product and any related offerings. States may define or tax digital services differently, so don’t carry a conclusion from one jurisdiction to another without verification.
A potential connection to a state is a starting point, not a complete action plan. Consider separate questions for income tax, franchise tax, sales tax, and payroll-related obligations. The rules and relevant business facts may differ for each, so a finding related to one tax doesn’t automatically establish what’s required for the others.
For each jurisdiction, record what activity prompted the review and what still needs confirmation. Check state-specific definitions, current rules, registration steps, collection responsibilities, and filing requirements before making decisions. A structured multi-state tax nexus analysis for SaaS companies helps your team move from broad screening to informed, documented follow-up.
A nexus analysis is a documented review of a company’s connections to states, the tax questions those connections raise, and the follow-up each question requires. For a SaaS business, make it a repeatable process rather than a one-time scan. The goal isn’t to apply one rule everywhere. It’s to identify what needs research, document what you learn, and assign the next step.
Use a consistent sequence:
Start with records your teams already maintain. Reconcile customer locations and revenue reports with billing and accounting data, and note where those sources don’t match. Map employee, contractor, office, and other operational locations for review. A customer’s billing address, for example, may not answer every question about where a sale should be sourced, so record the data used and any assumptions.
For each source, capture the reporting period and note gaps, such as an unknown work location or incomplete customer address. This makes the inventory more useful than a simple list of states: it shows how the team reached its conclusions and where more information is needed.
Review each state on its own terms. Check current state guidance for how the state classifies your SaaS and related offerings, which taxes may be relevant, and what thresholds or other rules need review. Keep conclusions distinct by jurisdiction and tax type. A result for sales tax in one state shouldn’t be treated as an answer to that state’s income or payroll questions, or as a rule for another state.
For every conclusion, save the source and the date it was reviewed. The Multistate Tax Commission’s National Nexus Program is one resource to consult as you organize a multi-state review. It doesn’t replace checking current state guidance against your specific facts. If a rule is unclear or the potential impact is material, flag it for a qualified State & Local Tax (SALT) advisor.
Keep the review connected to business operations. Finance, billing, HR, and payroll teams can help validate the underlying records, while an advisor can help assess state-specific tax questions. If your team would benefit from support connecting those records to tax research, learn more about discussing a State & Local Tax review.
A useful comparison doesn’t ask only, “Do we have customers there?” It connects each activity to a tax question, the records that can help answer it, and what still needs state-specific verification. Customer sales and revenue can point your team toward states to research, but there’s no single threshold or definition to apply across every state and tax type.
Economic activity, such as sales into a state, is one part of the review. Physical-presence facts, such as an employee, contractor, or office location, are another. Neither category alone settles every potential obligation. Use a table like this to keep the evidence and open questions visible:
| Activity | Tax type to review | State question | Evidence to gather | Verification status |
|---|---|---|---|---|
| Customer sales and revenue | Sales tax; income or franchise tax | How does the state measure relevant sales, and what activity or thresholds apply? | Customer location records, invoices, billing reports, revenue detail | Research required; confirm the period and sales measure |
| SaaS subscription or related offering | Sales tax | How does the state classify this specific product, and how are sales sourced? | Service description, contract terms, billing and customer-location data | Verify classification and sourcing for the jurisdiction |
| Employee or contractor working in the state | Payroll; income or franchise tax; potentially sales tax | What state rules may apply to this work location and activity? | Work location, role, work arrangement, payroll and contractor records | Confirm facts and review each relevant tax separately |
| Office or other business presence | Income or franchise tax; potentially sales tax | How does the state treat this type of presence? | Location records, lease or registration information, description of activity | Verify applicable state definitions and requirements |
Use customer and revenue data to prioritize research, not to assume that a particular sales level produces the same result everywhere. Reconcile billing reports with accounting records, and note missing or inconsistent location data. Review employee, contractor, office, and other operational locations as distinct facts. If a location or activity is unknown, mark it as unresolved rather than treating it as confirmed or irrelevant.
A conclusion about sales tax doesn’t answer whether income, franchise, or payroll-related requirements may apply. For sales tax, verify how the state treats the SaaS offering and sources the sale. For other tax types, check the state’s current rules against the company’s activities and records. Document the source, review date, and follow-up needed. A structured multi-state tax nexus analysis for SaaS companies keeps these separate questions organized without relying on a blanket rule or an outdated comparison.
Research becomes useful when your team can see what’s known, what’s uncertain, and who’s responsible for the next step. Keep a shared tracker for each jurisdiction under review. Include the issue, supporting evidence, accountable owner, next action, and review date. This gives finance and tax teams a record they can update as the business changes.
Separate confirmed business facts from assumptions and tax conclusions. For example, a payroll record may confirm an employee’s work location, while the tax effect of that location still needs state-specific review. Keep source documents with the tracker, and flag conclusions that need professional input instead of treating them as settled.
Use the tracker as a living worklist, not a one-time report. Reopen relevant items when customer locations, revenue patterns, staffing, products, or operations change. For broader context on how tax advice can support planning and growth, see SD Mayer’s strategic tax advice guide.
Keep the underlying records aligned. Compare billing and accounting reports with customer-location and revenue data, and establish a clear process for updating workforce locations through HR and payroll. Finance, billing, HR, payroll, and legal teams may each hold facts that affect the review. Coordinate their updates so a change recorded in one system doesn’t remain invisible to the others.
If inconsistent records make it difficult to support your conclusions, review the bookkeeping process alongside the tax work. SD Mayer’s guide to outsourced bookkeeping and financial operations offers additional context on maintaining useful business records.
A repeatable multi-state tax nexus analysis for SaaS companies depends on clear ownership as much as careful research. For information about connecting tax questions with finance, payroll, and accounting records, see how SD Mayer can support your review.
The right support depends on the number of jurisdictions you’re reviewing, the complexity of your operations, and your team’s capacity to maintain the process. Internal ownership can work well when finance and tax teams have time to gather records, research state rules, and keep findings current. Tracking software may help organize locations, activity, and review dates, but it doesn’t replace checking how a state’s rules apply to your business.
Outside State & Local Tax (SALT) advisory may be useful when state-specific questions are difficult to resolve internally or when your team needs help documenting its research. For a multi-state tax nexus analysis for SaaS companies, ask prospective advisors how they handle SaaS-related questions. Don’t assume a firm has specialized SaaS experience unless it can explain its relevant work and approach.
Before agreeing on a review, clarify what the work covers and how the results will be shared. Ask:
Clear answers help your team understand the work plan and where your own staff will need to provide information or follow up. Entity filings or registered-agent support may address separate administrative needs, so confirm that the proposed engagement specifically covers tax questions.
If billing data, accounting records, employee locations, and tax research live in separate processes, coordinating them can be challenging. An integrated approach may help your team connect the underlying records with the state tax questions being reviewed. SD Mayer offers SALT, tax, payroll, bookkeeping, and outsourced CFO and controller support. Its Client Accounting Advisory Services (CAAS) may also be relevant when you’re considering how finance operations fit into the process.
Choose support that matches your company’s needs and leaves you with clear documentation, responsibilities, and follow-up steps. To learn more about how the firm’s services could fit your process, review your multi-state tax questions with SD Mayer.
A useful nexus review turns scattered information into clear next steps. Start with reliable records, assess each state and tax type separately, and document who will resolve open questions. Then revisit the review as your customer footprint, team, or operations change. This makes multi-state tax nexus analysis for SaaS companies a repeatable part of managing growth, not just a one-time exercise.
The process is easier to maintain when tax decisions connect with the records behind them. SD Mayer lists State & Local Tax advisory among its services and brings together tax, accounting, payroll, and advisory capabilities. For businesses in San Francisco, San Mateo, San Jose, Walnut Creek, Santa Rosa, San Leandro, Menlo Park, and Sacramento, this integrated perspective can help connect state tax questions with day-to-day financial information.
To discuss your company’s multi-state tax questions and how they connect with finance and payroll records, contact SD Mayer.
Tax nexus is a connection between a business and a state that may bring state tax responsibilities into consideration. For a SaaS company, that connection could relate to customer sales, employees, offices, or other business activity. Nexus doesn’t automatically determine what the company must do next. Each state has its own rules, and potential sales, income, franchise, and payroll tax questions should be reviewed separately.
Not necessarily. A sale to an out-of-state customer is a reason to include that state in your review, but it doesn’t by itself settle whether nexus exists or what obligations follow. The answer can depend on the state’s rules, the company’s sales and other activity, and how the particular SaaS offering is treated. Check current state guidance and assess each tax type separately before deciding on next steps.
Start by mapping customer locations, sales and revenue, employee and contractor work locations, offices, and other business activity. Reconcile billing and accounting data, note missing information, and use the inventory to identify states for research. A multi-state tax nexus analysis for SaaS companies should then verify each jurisdiction’s current rules, including how it treats the specific SaaS offering and relevant tax types, rather than relying on a single nationwide assumption.
Yes, an employee’s work location can raise state tax questions and should be included in a nexus review. It isn’t an automatic conclusion that a particular tax or filing requirement applies. Document where employees work, their roles, and relevant payroll details, then review the facts under the state’s current rules. Keep employee-location updates connected to HR and payroll processes so changes reach the people responsible for tax review.
No single sales tax finding answers every other tax question. Sales tax, income tax, franchise tax, and payroll-related obligations can have different rules and depend on different business facts. Treat each one as a separate state-specific review. A potential connection identified for sales tax may be a useful prompt to assess other taxes, but it doesn’t establish that the company owes them or must take the same action.
Set a recurring review process that fits your business and update it when important facts change. New customer markets, shifts in revenue, remote hires, office changes, or new products can all prompt a fresh look. There isn’t one review schedule that fits every company. Track review dates and assign owners to open questions, then confirm current state rules before relying on an earlier conclusion.
Gather customer locations, invoices, billing reports, revenue detail, and accounting records. Add employee and contractor work locations, payroll information, office and operational records, and state registration details. Keep copies of the state guidance or other research used for conclusions, along with review dates, assumptions, and unresolved questions. For businesses in San Francisco, San Mateo, San Jose, Walnut Creek, Santa Rosa, San Leandro, Menlo Park, or Sacramento, organizing these records can support a clearer multi-state review.