FREE TOOL
Free Nexus Calculator: see where you likely owe sales tax across all 50 states.
Try it free
Sales tax is the obligation that catches finance leaders off guard. Not because the concept is difficult to grasp, but because the operational reality of managing it correctly across multiple states, multiple products, and a growing business turns out to be significantly more complex than most CFOs realize until something goes wrong.
Most finance leaders pick up their first real understanding of sales tax compliance in one of three ways: they receive a notice from a state they didn't know they were supposed to be filing in, they inherit a compliance setup from a previous finance team and have no idea whether to trust it, or they go through a transaction and a diligence team surfaces exposure nobody knew existed. A fundraise, an acquisition, a sale process: these are the moments when years of quiet misconfiguration suddenly become very expensive.
This article is the orientation that should come earlier. You'll learn what sales tax compliance actually requires at a strategic level, which decisions belong on your desk and which can safely live elsewhere, and how to recognize when your current setup isn't working before a state notice forces the conversation. If you've ever felt like you should understand this function better than you do, you're in the right place.
Sales tax is a transaction-level obligation. Every time a customer buys something from you, some states require you to collect tax from that customer and remit it to the state. The obligation exists in the states where you have nexus, which is the legal connection between your business and a state that creates a tax responsibility. Nexus can come from physical presence (offices, employees, inventory, trade show attendance) or from economic activity alone (crossing a state's revenue or transaction threshold).
The economic nexus standard became universal after the Supreme Court's 2018 South Dakota v. Wayfair decision. Before Wayfair, a business generally needed physical presence in a state to trigger sales tax obligations. After Wayfair, states can require you to collect and remit sales tax based purely on your sales volume into that state, typically once you cross $100,000 in revenue or 200 transactions. This means a company with no employees, no offices, and no inventory in a state can still owe that state sales tax if enough customers live there.
What makes this genuinely complex for a CFO is the combination of four things that don't exist anywhere else in the tax code. First, it varies by state in ways that are hard to systematize. Second, it's entirely self-assessed and self-reported, meaning no one tells you when you've crossed a threshold. Third, it's calculated on gross revenue rather than profit, so losses don't reduce exposure. Fourth, the penalty structure for non-compliance includes both uncollected tax and interest and penalties that accrue from the date the obligation started, not the date anyone discovered it.
The practical implication is this: unlike income tax, where the IRS sends you a return and you respond, sales tax requires your organization to proactively determine where you have obligations, register, configure your systems correctly, file returns on time, and keep everything current as the business changes. Nothing about that process is automatic. Someone has to own it.
Before you can appropriately resource or delegate the sales tax function, you need to personally understand three foundational questions. These aren't operational details. They're the strategic orientation that determines whether your compliance posture is sound or whether you're carrying exposure you don't know about.
This is the single most important question in sales tax compliance, and most CFOs at growing companies can't answer it with confidence. The honest answer requires a current nexus analysis. Not a list of states where you have offices, but a systematic mapping of physical presence and economic nexus thresholds against your actual sales data by state.
The nexus footprint changes constantly. Every new remote hire, every trade show, every state where revenue crosses $100K, every Amazon fulfillment center that stores your inventory: each creates a new nexus obligation. If your last nexus analysis was done at implementation of your tax software or at a prior fundraise, it's out of date.
Use The Sales Tax People's nexus calculator to get a preliminary read. A meaningful analysis requires transaction-level data and a professional review, but the calculator tells you quickly whether you have obvious gaps.
Nexus and registration answer the question of where you have obligations. Configuration answers the question of whether you're calculating correctly in those states. A business can be registered everywhere it should be and still be systematically over-collecting or under-collecting because its product taxability rules, exemption certificate logic, or address sourcing are wrong.
This is the Avalara misconfiguration problem. The software is running, returns are filing, everything looks fine, and the calculations have been wrong since go-live. For a CFO, the right question isn't "do we have automation software" but "has anyone with sales tax expertise ever audited whether the configuration produces correct results." Most companies have not done this. Our article on Avalara misconfiguration explains how this happens and what to look for.
Filing returns is the most visible part of sales tax compliance. It's also the smallest part. The function also includes monitoring nexus thresholds, updating registrations as the business changes, managing exemption certificate validity, reconciling marketplace sales against direct-channel filings, keeping product taxability current as product lines evolve, and responding to state notices.
Many companies have someone "handling sales tax" who is in practice only filing returns and handling none of the rest. That's the most common gap we encounter. The person or provider doing the work may be excellent at what they do, but if their scope is limited to return preparation, the strategic layer of the function is unowned.
Sales tax compliance has a clear division between strategic decisions that require judgment and executive accountability, and operational tasks that are genuinely delegable to a team member or an outside provider. Conflating the two is how both under-delegation (the CFO spending time on return filings) and over-delegation (nobody noticing that the nexus footprint has expanded) happen simultaneously.
| The CFO Should Own | Can Be Delegated to Finance Team or Outside Provider |
| Understanding the company's current nexus footprint | Day-to-day return filing and remittance |
| Approving the approach to historical exposure (VDA vs. register going forward vs. accept risk) | Exemption certificate collection and renewal tracking |
| Resourcing decision: software + internal team vs. fully managed service | Nexus threshold monitoring and alerts |
| Ensuring diligence-readiness before any fundraise, M&A, or exit process | Taxability code mapping and configuration maintenance |
| Escalation path when the company receives a state notice or audit | Responding to routine state correspondence |
| Strategic decisions when taxability is genuinely ambiguous | Filing frequency updates as filing schedule requirements change |
| Understanding what's covered by automation and what isn't | Marketplace reconciliation and double-remittance checks |
The decisions in the left column are the ones that surface unexpectedly in board meetings, diligence reviews, and audit defense situations. A CFO who hasn't thought through these doesn't have a compliance problem yet. They have a compliance gap that will become a problem at the worst possible moment.
If you're looking at the left column and realizing you haven't made explicit decisions about some of these items, that's normal. Most CFOs haven't. The point isn't to create anxiety. It's to clarify what actually requires your judgment versus what can safely run without your involvement.
Sales tax compliance can be resourced in three ways, and the right answer changes as the company grows.
A tax automation platform (Avalara, Vertex, TaxJar, and others) handles calculation and filing. Your internal finance team owns configuration, monitoring, exemption certificates, and everything else.
This works at smaller companies with simple product catalogs, few states, and a finance team member with bandwidth and some tax knowledge. It breaks down when the business grows faster than the team's capacity to keep the configuration current.
For a full evaluation of what to look for in a tax automation platform, the companion guide covers this in detail.
The automation platform handles mechanics. A sales tax specialist, either an internal hire with state and local tax expertise or an outside advisory firm, owns the strategic layer: nexus analysis, taxability research, configuration audits, and escalation on complex questions.
This is the right model for mid-market companies with complex product mixes, multi-state footprints, or significant change velocity (new products, new markets, acquisitions). It separates the operational burden from the judgment layer.
An outside provider handles the entire function end-to-end: registration, configuration, filing, certificate management, nexus monitoring, and audit response. The CFO's involvement is periodic review and escalation for genuinely strategic decisions.
This is appropriate when the internal finance team doesn't have sales tax expertise, when the compliance footprint is large and complex, or when the cost of an internal specialist is hard to justify relative to transaction volume.
Software alone is never sufficient. The automation platform does what it's configured to do. If nobody with sales tax expertise is periodically reviewing whether the configuration is still correct, whether the nexus footprint is current, and whether the exemption certificate files would survive an audit, the software is generating a false sense of compliance.
The question isn't which model is best. It's which model matches your current complexity, your team's capabilities, and your risk tolerance. And it's worth revisiting that question every 12 to 18 months as the business changes.
For companies that need help thinking through registration strategy or addressing historical exposure, our VDA and registrations page explains the options.
None of these warning signs are proof of a problem individually, but any of them is worth investigating. More than two or three and a configuration review is warranted.
Your effective sales tax rate as a percentage of revenue has been flat for years. A growing, changing business in a correctly configured system produces some rate variation as the product mix and geographic footprint shift. A completely flat rate usually means the configuration isn't tracking reality.
You've never had a sales tax professional review your setup. The accountant who files your returns and handles your income tax is not the same as someone with state and local tax expertise. Generalist accountants file returns. They don't audit taxability configurations, conduct nexus analyses, or advise on VDA strategy.
You're registered in the same states you were registered in three years ago, despite meaningful business changes. New hires in new states, trade show attendance, revenue growth into new markets: each of these can create nexus obligations without triggering any visible alert in your current setup.
You have marketplace sales and you're also filing your own returns in those states. Double remittance is extremely common and almost never caught without a deliberate reconciliation. If Amazon is collecting and remitting as a marketplace facilitator and you're also including those sales in your own returns, you're paying the same tax twice.
You've launched new products or changed your pricing model since the last time anyone reviewed your taxability configuration. New product lines, new subscription tiers, new bundling: each can change taxability in ways the software won't flag on its own.
You received a state notice and nobody is sure what triggered it or how to respond. A state notice is a signal that the state's data shows a discrepancy between what they expect and what you're doing. The right response is not to file whatever the notice asks for without understanding why.
You couldn't answer the three questions in section two with confidence. That's the clearest signal of all.
Sales tax compliance ends up on the CFO's agenda in one of two ways: proactively, because the CFO treated it as a financial risk worthy of the same attention as any other material liability, or reactively, because something surfaced it at the worst possible moment.
The moments where reactive discovery is most expensive: a fundraise where investor diligence surfaces unregistered states; an acquisition where the buyer's tax team quantifies exposure that drops the valuation; a sale process where the quality of earnings team finds years of incorrect taxability mapping; a state audit that opens during a period of maximum operational distraction.
Sales tax exposure is unusual among financial risks in that it compounds silently. There's no income statement line that flags it. Returns file. Software calculates. Everything looks fine. The exposure builds at the rate of your revenue in unregistered states, plus penalties and interest, across however many years the gap has been open. A business that discovers a five-year nexus gap is looking at a very different number than a business that caught it at twelve months.
The CFO who treats sales tax as an accounting function to be delegated and forgotten is the one who discovers it at the worst time. The CFO who treats it as a financial risk with a known profile, manageable with the right resourcing and the right periodic review, rarely has an unpleasant surprise.
Most of the CFOs we work with didn't have a crisis. They had a quiet realization that they didn't actually know whether their compliance setup was working. Maybe it was a question from a board member they couldn't answer with confidence. Maybe it was a new state notice sitting in someone's inbox. Maybe it was just the nagging sense that a function this consequential shouldn't feel this opaque.
The gap between "I think we're fine" and "I know we're fine" is exactly where exposure lives. And that gap closes with one conversation.
A What's Next consultation with our team takes about an hour. It's not a sales pitch. It's an honest assessment of where you stand: your current nexus footprint, whether your configuration looks sound, and what, if anything, needs to change. We'll answer the three questions from section two with specificity. You'll leave knowing whether your compliance posture is solid or whether there's work to do.
Some CFOs walk away with confirmation that their setup is working. Others discover gaps they didn't know existed and get a clear path to address them. Either way, you'll have the orientation you need to own this function the way you own every other material financial risk.
Just talking should always be free. Schedule your What's Next call and find out where you actually stand.
At a strategic level, a CFO needs to understand four things about sales tax. First, it is a transaction-level obligation — every time a customer buys something, certain states require the business to collect tax from that customer and remit it to the state, and the obligation exists wherever the business has nexus. Second, nexus is no longer just about physical presence — since the Supreme Court's 2018 Wayfair decision, states can require sales tax collection based purely on sales volume, meaning a company with no offices or employees in a state can still owe that state sales tax. Third, the compliance burden scales with the business — every new state entered, product launched, employee hired, and acquisition closed potentially creates new filing obligations. And fourth, the consequences of getting it wrong fall on the business — software doesn't guarantee compliance, and the CFO is typically the executive accountable when something surfaces in an audit or a transaction process.
Before the Supreme Court's 2018 South Dakota v. Wayfair decision, a business generally needed a physical presence in a state — an office, employees, inventory — to trigger sales tax obligations there. After Wayfair, every state with a sales tax can require businesses to collect and remit sales tax based purely on their economic activity in that state. The most common threshold is $100,000 in annual revenue or 200 transactions into a state, though several states have since eliminated the transaction count and rely solely on the revenue threshold. The practical consequence for CFOs is that any business selling across state lines — including those with no physical presence whatsoever in a state — may have sales tax obligations in dozens of states based entirely on where their customers are. A business that has been growing nationally since 2018 without regularly reviewing its nexus footprint almost certainly has unaddressed filing obligations in multiple states.
Not every sales tax decision requires CFO involvement — but several do. Nexus strategy belongs at the CFO level: deciding which states to register in proactively, how to respond when economic nexus thresholds are approaching, and what to do when a business decision like hiring a remote employee or opening a warehouse creates new state obligations. Vendor and platform selection belongs at the CFO level: choosing between a software tool and a managed service, understanding what the chosen platform covers and what it does not, and knowing who is accountable when an error occurs. Audit and dispute responses belong at the CFO level: an audit notice from a state is not a routine compliance task — it is a risk management event that requires executive awareness and often legal counsel. And material exposure decisions belong at the CFO level: whether to pursue a Voluntary Disclosure Agreement, how to handle historical gaps identified during a compliance review, and how to disclose known liabilities in a transaction process.
Six warning signs consistently appear before a company's sales tax problems surface in a notice or audit. First, the nexus footprint has never been formally reviewed — the business has been growing into new states, hiring remote employees, and adding products without anyone confirming that the filing obligations are keeping pace. Second, automation software was implemented and never revisited — Avalara or Vertex was set up at go-live and the configuration has not been touched despite changes in the business, product mix, or state laws. Third, the effective tax rate is suspiciously flat — it has barely changed despite geographic expansion or product mix changes, which signals that the system is not applying state-specific rules correctly. Fourth, exemption certificates were never systematically managed — B2B customers marked as exempt in the system but no valid certificates on file. Fifth, the company has received state notices that were resolved without a broader compliance review. And sixth, the only people who have ever reviewed the compliance setup are the people who built it.
Yes. Because sales tax is classified as a trust fund tax — money collected from customers on behalf of the state and held in trust until remittance — many states can pierce the corporate structure and hold responsible individuals personally liable for unpaid sales tax. Personal liability typically extends to owners, officers, and individuals who had control over the business's finances and the authority to direct tax remittance. In practice, this means a CFO who had financial oversight during a period of non-compliance can face personal assessments for the unpaid amounts, even if the company subsequently restructures, goes bankrupt, or changes ownership. This is one of the most important reasons why sales tax is not simply a compliance checkbox — it is a personal risk management issue for the finance leader, not just a corporate one. Addressing known compliance gaps proactively is always less costly and less personally risky than waiting for a state to surface them.
Effective delegation of sales tax compliance requires three things: clarity about what is being delegated, a mechanism for the CFO to stay informed without being in the weeds, and an independent check on whether the delegated function is actually working. The execution tasks — filing, registration maintenance, exemption certificate collection, rate updates, and return reconciliation — can be fully delegated to an internal team member, an outsourced compliance provider, or a managed service. The CFO should receive a periodic compliance summary that covers the company's current nexus footprint, any new state obligations triggered during the period, any notices or audit activity, and the status of any open remediation items. And at least annually, an independent party — not the team or vendor doing the day-to-day work — should confirm that the nexus footprint is complete, the taxability configuration is accurate, and the exemption certificate library is defensible. Delegation without independent oversight is how misconfiguration runs for years without detection.
The first step is to resist the temptation to assume the existing setup is correct because it has been running without obvious problems. Silence is not a compliance signal — it just means no state has surfaced a problem yet. The right approach in the first 90 days is to commission an independent nexus review that maps where the business actually has obligations against where it is currently registered and filing. Review the taxability configuration in whatever automation software the company uses and confirm that the product and service classifications are accurate for the current product catalog. Pull a sample of exempt transactions and verify that valid exemption certificates are on file. Check the filing history for gaps, late filings, or states that appear to have been registered but are no longer active. And identify any business changes that occurred in the prior two to three years — new hires, new products, new states, acquisitions — that may have created compliance obligations nobody addressed. This exercise takes days, not months, and it gives the incoming CFO a defensible baseline position rather than inherited uncertainty.
We care about your data – privacy policy
