Sales & Use Tax FAQ for Insurance, Financial & Professional Services

Insurance, financial, and professional services firms face a narrower but surprisingly complex set of sales and use tax obligations. The services these organizations provide are generally exempt from sales tax — but the technology they purchase to run their businesses is not. Cloud-based software, SaaS platforms, ERP systems, and practice management tools all create use tax obligations that are routinely miscalculated or missed entirely, particularly for firms with employees working across multiple states. This FAQ covers the most common sales and use tax questions for firms in these industries, with a focus on SaaS taxation, multi-state employee access, use tax responsibilities, and audit exposure. For a review of your firm's specific situation, contact ACTSOLV to schedule a consultation.

Is SaaS taxable for insurance, financial, and professional services firms?

SaaS taxability varies significantly by state, and there is no universal rule. Approximately 20+ states explicitly tax SaaS, including Connecticut, Massachusetts, New York, Pennsylvania, Texas, and Washington. About 15+ states do not tax SaaS, including California, Florida, Georgia, and Maryland. Many other states fall into a gray area with unclear or evolving guidance that shifts with new legislation or administrative rulings.

For firms in these industries, the important nuance is that your organization is almost always the purchaser of SaaS rather than a provider. Your tax obligation is typically a use tax or self-assessed sales tax on software purchased from vendors who did not collect tax — rather than a collection obligation on your own services, which are generally exempt. This distinction means your compliance focus should be on what you are buying and where your employees are using it, not on what you are selling. Learn more about the often-overlooked use tax obligation on technology purchases.

What determines whether SaaS is taxable — where the provider is located or where the software is used?

Almost all states that tax SaaS use destination-based sourcing — tax is based on where the software is used or accessed, not where the provider is headquartered. For firms with employees in a single state, this is straightforward. For firms with employees across multiple states, the calculation becomes significantly more complex.

Software may be purchased and paid for centrally in one state, but if that state does not tax SaaS while employees in other states are accessing the software from states that do, the firm may be underpaying in those user-location states. Conversely, if the purchasing state taxes SaaS but the user-location states do not, the firm may be overpaying. Getting this allocation right requires knowing the taxability rule in every state where employees access the software and applying each state's rate proportionally to usage in that state. AUTOSOLV handles this allocation automatically using real-time user location data and each state's current taxability rules. See also how nexus thresholds interact with multi-state SaaS obligations.

Does remote employee access to SaaS create tax obligations in additional states?

Yes — and this is one of the most significant and underappreciated tax issues facing insurance, financial, and professional services firms today. When an employee in a state that taxes SaaS accesses cloud-based software, that usage creates a taxable event in that state, regardless of where the software was purchased or where the company's headquarters is located.

Remote and hybrid work has dramatically expanded the number of states in which firms have employees accessing SaaS tools on any given day. Many firms are unknowingly underpaying use tax across multiple states where remote employees work, while simultaneously overpaying in the central purchasing state. This exposure compounds over time and can become a material liability if surfaced during an audit. A systematic review of your remote workforce footprint against your SaaS vendor spend is the starting point for understanding the exposure. Read more about the revenue risk of use tax non-compliance for firms that have not addressed this.

How do we handle SaaS tax when employees work across multiple states?

The correct approach is a multi-point-of-use allocation. You identify the number of users accessing the software in each state, determine whether SaaS is taxable in each of those states, apply the appropriate tax rate proportionally to the usage in each taxable state, and remit accordingly — either by paying the correct tax to your vendor if they collect in all relevant states, or by self-assessing and remitting use tax directly to each state where the vendor did not collect.

In practice, most firms do not have a system in place to track user location data and apply it to SaaS invoices, which means the allocation is either not being done at all or being done inaccurately. AUTOSOLV was specifically built for this problem — it uses AI to analyze user location data, apply state-specific taxability and rate rules, and produce accurate use tax accruals for every SaaS platform in your technology stack. For a firm with 10 SaaS platforms and employees in 20 states, automating this is the only way to get it consistently right. Read 5 ways to build a business case for sales tax technology if you need to bring this issue to your CFO or controller.

What documentation does our firm need for tax-exempt SaaS purchases?

If your firm qualifies for an exemption on a SaaS purchase — which is uncommon in insurance, financial, and professional services, since most of your technology purchases are taxable — you will need to provide the vendor with a valid exemption certificate specific to the state where the software is being used. Each state has its own required form or acceptable certificate format, and the certificate must include buyer and seller information, the basis for the exemption, and a signature.

Certificates should be stored digitally and reviewed periodically, as most states require renewals every one to three years. Practically speaking, most firms in these industries are more focused on managing use tax on taxable purchases than on claiming exemptions. Genuine SaaS exemption opportunities are limited in this space. If you do have certificates on file, CertSOLV provides a centralized system to store, track, and manage their renewal so they remain valid and audit-ready. Read more about how to handle expired or invalid exemption certificates.

Are implementation, customization, or training fees taxable when purchasing SaaS?

This depends on how the charges are structured and which state is involved. When implementation, customization, or training fees are bundled into the SaaS subscription as a single price, the entire amount is generally taxable in states that tax SaaS. When these fees are separately stated on the invoice as their own line items with distinct pricing, they are often treated as professional services — which are generally not taxable — though this varies by state.

From a buyer's perspective, it is worth asking vendors to itemize these charges clearly on invoices. Doing so can meaningfully reduce the taxable portion of what you owe. From a compliance standpoint, your use tax calculations should reflect only the taxable portion of each invoice, which requires reviewing invoice structure rather than applying use tax to the total payment. Vendors who bundle everything into one line item create ambiguity that tends to resolve against the taxpayer in an audit. For more on how software product and pricing structures affect tax liability, read tax software product enhancements that could put you in the hole.

Are cloud-based accounting, ERP, and practice management systems subject to sales tax?

In states that tax SaaS, yes. Cloud-based accounting platforms, ERP systems, CRM tools, and practice management software are all generally subject to sales tax or use tax in those states because they are accessed via the cloud and fit the definition of taxable SaaS. If your vendor charges you sales tax on these subscriptions in a state that taxes SaaS, that charge is likely correct. If your vendor does not charge sales tax — because they have no nexus in your state or are not registered there — you may owe use tax on those payments.

Enterprise software contracts represent significant spend, and the use tax exposure on multi-year ERP or practice management platform contracts can be material if it has not been addressed. Regularly reviewing your technology vendor invoices for correct tax treatment is a sound compliance practice. AUTOSOLV automates this review by evaluating every vendor invoice against current state taxability rules and generating the correct use tax accrual, so nothing is missed. Learn more about the revenue risk of use tax non-compliance for firms carrying unaddressed vendor invoice exposure.

Are we responsible for use tax if our SaaS vendor does not charge sales tax?

Yes. Use tax is the purchaser's obligation. When a vendor fails to collect sales tax on a taxable SaaS transaction — whether because the vendor has no nexus in your state, is not registered there, or simply made a billing error — the responsibility for remitting that tax falls on you as the buyer. This is not a widely understood obligation, but it is consistently enforced during audits.

Many insurance, financial, and professional services firms have significant use tax exposure on SaaS and other technology purchases precisely because their vendors are often headquartered in other states and are not registered to collect tax in every state where the firm's employees work. A use tax review of your technology vendor spend is often where the most significant uncollected liability is found for firms in these industries. AUTOSOLV automates the accrual process so every vendor invoice is evaluated and the correct use tax is assessed and booked automatically, eliminating the manual review burden. Read more on why use tax is so often overlooked.

What if we bill clients for software access as part of our consulting or advisory services?

When software access is included as part of a broader consulting or advisory engagement, taxability depends on how the charges are structured on the client invoice and on the rules in the state where the services are delivered. Some states tax the software component even when bundled with exempt professional services. Others exempt the entire arrangement if the primary purpose of the engagement is a non-taxable service. Still others require an allocation between the taxable and non-taxable components.

If the software access is separately stated as its own line item, it is more likely to be treated as taxable SaaS in states that tax it. If it is embedded in a single professional services fee with no breakdown, the analysis shifts to what the client is primarily paying for. Because professional services are the core offering for most firms in this space, billing practices that clearly document the nature and value of each component are important both for client transparency and for tax defensibility. Read more about balancing client service with tax compliance when structuring these engagements.

How do insurance and financial services firms typically discover their SaaS use tax exposure?

Most firms discover their SaaS use tax exposure one of three ways: during a state sales and use tax audit, when a tax professional conducts a voluntary compliance review, or when an analysis of technology vendor spend and employee location data surfaces the gap. Audits are the most disruptive path because they come with back tax assessments, penalties, and interest on top of the original liability.

A voluntary compliance review — including a Voluntary Disclosure Agreement in states where unaddressed exposure exists — allows firms to come forward proactively, often with reduced lookback periods and penalty abatements. For firms that have grown significantly, added remote employees in new states, or expanded their technology stack in recent years, a systematic use tax review is a worthwhile investment before an audit makes it necessary. Contact ACTSOLV to discuss what a use tax exposure review looks like for your firm, and read the case study on how ACTSOLV streamlined compliance for a technology-forward professional services company.