When sales-tax compliance breaks, it affects every part of a company. Often, no one notices until issues have piled up.
Compliance problems are usually caused by diffusion, not negligence. Finance assumes product is watching nexus. Product assumes finance owns filings. Engineering connects an integration and considers the job done. No one clearly owns exemption certificates.
The result is exposure that builds quietly until a state notice arrives, a diligence review surfaces a liability, or a filing error triggers a penalty.
Nexus Monitoring Falls Between Finance and Product
Economic-nexus thresholds are a finance problem in theory but a data problem in practice. Knowing whether sales have crossed a threshold requires active monitoring across every channel.
That task often sits unassigned between the person managing the books and the person managing the product or billing system. Founders may not hear about a new state until a notice arrives, while manual monitoring consumes time for the teams that do know the issue exists.
Filing Ownership Is Assumed, Not Assigned
Once nexus exists, someone must register and file. That requires state-portal credentials, knowledge of deadlines, and attention to jurisdiction-specific details.
In a small finance team, the work often lands on the person who figured it out once. When that person leaves, the knowledge leaves with them. A replacement can inherit a system they did not configure, and the first filing cycle after the transition may produce errors that remain undiscovered.
Integrations Are Treated as a One-Time Event
A billing-system update, new sales channel, Stripe-to-Chargebee change, or Amazon FBA expansion can break the data flow between commerce platforms and the tax stack.
Integration failures are costly because they can remain undetected for weeks or months. By the time numbers no longer reconcile, there may be a backlog of transactions to audit or refile.
Exemption Certificates Are Everyone’s Problem and Nobody’s Process
Exemption certificates expire, customer tax status changes, and a certificate valid two years ago may not cover today’s transactions. Without a process to track expiration and renewal, a company may collect tax from some exempt customers while failing to collect it from others.
Managing certificates manually across a growing customer base is difficult, so this accountability gap often appears during diligence.
Product Taxability Is an Ongoing Responsibility
Product classification is not a one-time project. States change taxability rules, bundles may need to be disaggregated, and a SaaS company that adds a physical-goods component may still be using its original categorization years later.
For companies selling across many states, maintaining accurate product-taxability mapping manually is often deprioritized until an audit makes it urgent.
The Common Thread
Each gap has the same cause: sales-tax compliance requires coordination across functions that do not naturally communicate about it, on a schedule that does not align with another business rhythm.
Kintsugi was built to handle sales-tax complexity without leaving gaps. It helps cover the handoffs where mistakes tend to be made and gives teams a clearer compliance workflow.
Book a demo with the Kintsugi team.
