The shift from “SaaS company” to “AI company” reflects real innovation in your product and market positioning. But when it comes to sales tax compliance, that rebrand doesn’t change the fundamental challenge you face: a complex patchwork of state-by-state tax rules that classify and tax your offerings based on how they’re delivered, not what you call them.
At Miles Consulting Group, we’ve spent over 23 years helping technology companies manage multi-state sales tax obligations. Increasingly, we’re working with finance leaders at AI companies who discover that their sophisticated AI-driven products face the same compliance complexities that traditional SaaS businesses encounter, and sometimes create exposures they hadn’t anticipated.
If you’re a CFO, Controller, or finance leader at an AI company, this article walks through what you need to know about sales tax compliance, where gaps commonly emerge, and how to address them before they become costly problems.
How States Actually Tax AI Companies
Most states don’t have specific tax categories for “AI products”. Instead, they apply existing frameworks developed for software, digital services, and SaaS offerings.
Whether your AI company offers machine learning APIs, AI-powered analytics platforms, or intelligent automation tools for example, states will typically evaluate your products based on:
How the product is delivered: Is it remotely accessed software, a cloud-based service or a digital platform?
What gets transferred to the customer: Does software get downloaded or installed, or does the customer access functionality through your infrastructure?
How your contracts describe the offering: What do your terms, invoices, and customer agreements actually say you’re selling?
Many states group AI-driven SaaS, APIs, and cloud-based AI solutions together with traditional software for sales tax purposes. If their rules cover remotely accessed or prewritten software, your AI product likely falls within that definition.
However, the classification isn’t universal. Some states may treat AI-as-a-service as taxable software, while others consider it a nontaxable service if no tangible product changes hands or no “software” is technically transferred to the customer.
This means AI companies must determine in each jurisdiction:
- If their specific product type qualifies as “software,” a taxable digital service, or an exempt service under that state’s law
- If economic nexus is triggered by remote sales or in-state revenues
- How sourcing rules apply when customers access services from multiple locations
The result is the same compliance challenge SaaS companies face: AI companies need to track and classify products carefully, understand where customers are located, and stay current with how states interpret emerging technology.
The Misconception About Home State Exemptions
One pattern we see repeatedly is AI companies based in states that don’t tax software or SaaS assuming their products are exempt everywhere.
This assumption is understandable but incorrect.
Sales tax generally follows destination-based sourcing for software and digital services. That means the tax treatment is determined by where your customer is located, not where your company is based.
If you’re headquartered in a state that exempts SaaS but you have customers in states that tax it, you likely have collection and filing obligations in those customer states. This is true whether you call your product “SaaS”, “AI-powered software”, “intelligent automation” or something else.
Your home state exemption doesn’t travel with your product.
When Your Contracts Don’t Match Your Business Model
Another issue that surfaces during compliance reviews is misalignment between what companies think they’re selling and what their contracts, invoices, or website actually describe.
For example, your marketing materials might emphasize AI consulting or custom solutions, while your contracts describe remotely accessed software licenses. Or your terms and conditions might reference SaaS subscription services while your sales conversations focus on AI implementation.
This matters because states look at the totality of the transaction when determining taxability. If there’s inconsistency between your invoices, contracts, customer agreements, and how you describe your services, it creates ambiguity that can work against you during an audit.
We recommend conducting a thorough review to ensure your documentation accurately reflects your business model and how revenue is generated. This clarity is essential not just for sales tax purposes, but also for financial reporting and due diligence.
The Revenue Stream You Might Be Missing
A specific exposure point we’ve identified with AI companies is revenue from marking up payment processing fees.
We’ve worked with AI businesses that generate revenue through both subscription fees and by marking up the cost of payment processing they facilitate for customers. In every case we’ve encountered, the company didn’t realize that the markup portion of their revenue could be subject to sales tax.
This isn’t unique to AI companies, but it’s a common blind spot. When you’re focused on your core AI product and subscription model, ancillary revenue streams can be overlooked during tax planning.
If your business model includes processing payments for customers and charging a markup or transaction fee, this warrants a careful taxability review. The treatment may vary by state, and the exposure can accumulate quickly if you’re operating at scale.
Why You Can’t Just Start Compliance Prospectively
When AI companies first approach us about sales tax, many want to implement compliance going forward without addressing historical periods.
The challenge is that proper compliance requires registering with states where you’ve created nexus, and those registrations ask when your obligation began. That date needs to be accurate, and it’s signed by a company officer under penalty of perjury.
If you’ve been selling into a state for two years but register today with today’s date, you’re misrepresenting your obligation timeline. This creates problems if the state later audits your history or if you’re preparing for due diligence in a transaction.
You need to address past exposure before you can move forward correctly.
This often means conducting a nexus study to identify where and when obligations were triggered, followed by remediation through Voluntary Disclosure Agreements (VDAs) where appropriate. VDAs allow you to proactively disclose past obligations in exchange for penalty relief and limited lookback periods, typically resulting in reduced or waived penalties.
Only after historical exposure is resolved can you implement ongoing compliance with confidence that your registrations and filings are accurate.
Understanding Officer Liability
One element that surprises many finance leaders is personal liability for unpaid sales tax.
In most states, company officers can be held personally responsible for uncollected or unremitted sales tax. This isn’t just a corporate obligation. If your company fails to collect and remit tax properly, state authorities can pursue individual officers for the outstanding amounts, penalties, and interest.
This creates real risk for CFOs, Controllers, and other executives who sign tax documents or have responsibility for financial compliance.
The best protection is ensuring your company has addressed its sales tax obligations completely, starting with identifying where nexus exists and resolving any historical gaps. Once you’ve established a clean baseline, ongoing compliance becomes straightforward.
But if you’re operating with unresolved exposure, that risk travels with you personally, not just with the company.
When AI Companies Should Prioritize Sales Tax Compliance
The answer varies based on your customer footprint and revenue distribution.
If your sales are concentrated in just a few states, you may have limited immediate exposure. But if your customers are spread across many jurisdictions, the complexity and risk increase significantly.
As a general guideline, we recommend AI companies take sales tax seriously when they reach:
- $100,000 in sales into any single state, or
- $3 million in total US sales annually
These thresholds aren’t legal requirements; they’re practical indicators that your exposure has grown large enough to warrant focused attention.
However, if you’ve just closed a Series A or are scaling rapidly, we’d offer different advice: start compliance now, before your growth compounds the problem.
It’s far easier to implement proper compliance from the beginning than to remediate years of historical exposure once you’ve reached significant scale. Tax due for historical periods is generally paid out of the company’s pocket, whereas if you’d started early, you could have collected it from customers.
The sooner you address this, the less disruptive and expensive it becomes.
What Finance Leaders Should Do First
If you’re uncertain about your company’s sales tax position, the first step is a nexus review.
A comprehensive nexus assessment identifies:
- Where your company has created economic or physical nexus
- When those obligations began
- What your potential historical exposure looks like
- Which states require registration and filing
This gives you a clear picture of your current situation and allows you to make informed decisions about remediation and ongoing compliance.
From there, you can:
- Address historical exposure through VDAs where appropriate
- Register properly in states where nexus applies
- Implement systems to collect tax going forward
- Ensure your product classifications and contract language align with your actual business model
At Miles Consulting Group, we help AI and technology companies conduct thorough nexus studies, resolve past exposure, and build sustainable compliance frameworks that scale with growth. Our team includes former Big Four advisors and ex-state auditors who understand both the technical requirements and the practical realities of managing multi-state obligations.
Moving Forward With Confidence
Sales tax compliance for AI companies isn’t fundamentally different from SaaS compliance, but it requires the same careful attention to state-by-state variation, product classification, and nexus management.
The companies that handle this well are the ones that:
- Understand their obligations early, before exposure becomes significant
- Address historical gaps proactively rather than waiting for an audit
- Ensure their contracts, invoices, and business documentation align
- Review all revenue streams, not just subscription fees
- Partner with specialists who understand both technology business models and state tax requirements
If you’re preparing for your next funding round, considering an acquisition, or simply want to ensure your compliance foundation is solid, we’re here to help.
We offer a complimentary nexus consultation to assess where you are today and outline the path forward. Whether you’re just beginning to think about sales tax or you’ve already started implementation and want a second opinion, we can provide clarity on what needs to happen next.
Ready to understand your sales tax position? Contact Miles Consulting Group to schedule your complimentary nexus review. Email us at info@milesconsultinggroup.com or book a consultation through our website.
