Sales Tax Compliance

You're registered for sales tax in 11 states. Each state has its own filing frequency (some monthly, some quarterly, some annual), its own forms, and its own rules for what counts as taxable in your product category. Your finance team tracks all of it in a spreadsheet. Three filings were late last year, and one state sent a notice. Sales tax compliance is the end-to-end process of meeting a business's obligations to collect, remit, and report sales tax in every jurisdiction where it has nexus. It covers four operational requirements: registration (getting a sales tax permit in each state where nexus exists), collection (charging customers the correct rate on taxable transactions), remittance (paying collected tax to the state authority by the due date), and filing (submitting the return that documents taxable sales, exempt sales, tax collected, and tax owed). These are four separate obligations, each with its own failure mode. A business can collect sales tax correctly but file late and pay penalties. It can register in a state but fail to collect on product categories that are taxable there. It can file on time but remit the wrong amount because its exemption certificates weren't managed properly. The spreadsheet approach works until the number of jurisdictions, filing frequencies, and product categories outgrows what manual tracking can handle, which usually happens before the third late filing.

How it works

Registration is the first operational step, and every later obligation follows from it. Once registered in a state, the business must collect tax on all taxable sales to customers there, including retroactively applying the correct rate to customer categories that may have been handled incorrectly before registration. Registration also comes with an assigned filing frequency: states usually assign monthly filing to higher-volume taxpayers and quarterly or annual filing to lower-volume ones. The frequency can change as revenue grows, and states give varying notice when they change it. Collection requires the correct rate (state rate plus local rates) for each transaction, applied to the correct taxable base, since some items may be exempt. It also means separating taxable from exempt sales and keeping documentation for exempt transactions, mainly exemption certificates from qualifying buyers. Remittance means paying the collected tax to the state by the due date. Many states require electronic payment above certain thresholds, and some require prepayments or accelerated remittance from high-volume taxpayers. Filing means submitting the return, which reconciles gross taxable sales, deductions for exempt sales, tax collected by jurisdiction, and credits. In states with complex local rate structures, such as Louisiana, Colorado, and Alabama, the return may need line-by-line local jurisdiction breakdowns, which you can only produce if transaction data was captured at the right level of geographic detail.

Where it gets complicated

When a buyer claims a sales tax exemption, whether as a reseller, a nonprofit, a government entity, or under a product-specific exemption, the seller has to collect and keep a valid exemption certificate that documents the basis for it. Without a valid certificate on file, the seller carries the tax liability for that transaction if it is challenged in audit. Certificates are state-specific: a Texas Resale Certificate is not valid in California, and a blanket certificate valid in one state may expire in another. Expiration rules also vary by state; some certificates are good for one year, some for three years, some until revoked. For companies selling to many business customers, certificate management means collecting certificates before the first exempt sale, tracking expiration dates, chasing renewals, and matching certificates to customer accounts in the billing system. That is a significant administrative load. Keeping certificates in a shared drive or spreadsheet is a common failure point: they can't be searched easily, expiration dates go untracked, and an audit finding that 40% of exempt sales lack valid certificates is a material liability. The SST Governing Board's standardized exemption certificate helps for transactions in SST member states, but non-member states use their own forms.

How platforms handle it

Sales tax compliance platforms offer two main models for return filing. In the DIY model, the platform aggregates transaction data by state and period, calculates the return figures, and produces either a pre-populated return file or a data export that you use to file manually or through the state's e-filing portal. You are responsible for submitting the return and paying by the due date. In the managed filing model, the platform handles filing end to end: it prepares the return, submits it to the state on your behalf (under a power of attorney), and initiates payment from your designated bank account. You review a filing calendar and a pre-filing summary but never touch the state portal. Managed filing removes most of the operational work of multi-state compliance but makes you dependent on the platform's accuracy and timeliness. The due diligence question is what happens when a managed filing is late or wrong: who pays the penalty, and what liability does the platform accept for its own errors? Most platforms disclaim liability for errors in taxpayer-provided data, so the quality of the transaction data flowing from your billing system into the platform stays your responsibility.

Questions to evaluate your sales tax compliance operations

• Do you have a complete, current filing calendar for every registered state, with filing frequency, due dates, and remittance method for each?
• Are exemption certificates collected before the first exempt sale to each customer, and are expiration dates tracked with renewal reminders?
• Does your transaction data system capture everything each state's return requires, including local jurisdiction breakdowns for states with complex local rate structures?
• Is there a reconciliation between tax collected per the billing system and tax remitted per the returns for each state at each filing period?
• Do you have a process for identifying and handling changes to your filing frequency when a state upgrades you to a higher-frequency schedule?
• If you use managed filing services, have you reviewed the platform's error and late filing policy to understand who bears liability for platform-caused failures?

Where sales tax compliance programs break down in practice

The most consistent setup failure is registering for sales tax without a plan for ongoing compliance. Registration is the easy part; the operational burden comes from the 24 to 36 monthly, quarterly, and annual filings per state that follow indefinitely. Companies that register under the pressure of a nexus notice, without putting tax automation or a compliance management system in place at the same time, end up filing by hand in a growing number of states with rising error and lateness risk. The second common failure is not tracking exemption certificates systematically. Without a dedicated certificate process, or a platform that handles certificates automatically, exempt sales pile up without documentation and the liability grows with every audit period. An audit finding covering three years of exempt sales without certificates can mean a seven-figure adjustment for companies with significant business-to-business sales. The third failure is not reconciling tax collected to tax remitted. Rounding differences, timing cutoffs, and data mapping errors can make the two drift apart over time. Without a periodic reconciliation, the differences build up unnoticed until an audit forces the reconciliation after the fact.

Comparing tax engines

Tax engines separate on jurisdiction depth and on whether registration, filing and certificate storage are included or sold separately. Once sales tax compliance is settled as a requirement, read the Tax Software category guide for how the market splits, then weigh the Avalara profile against the Vertex profile on that requirement rather than on the feature list. Our Avalara pricing breakdown records what the vendor publishes and what is quote-based. The Avalara against Vertex comparison sets two of them side by side on the same criteria. Before you book demos, put your own numbers through the tax compliance ROI calculator so the business case is written down before a vendor writes it for you.

Frequently asked questions

Related terms

Indirect Tax, Sales Tax Nexus, and Tax Automation come up in the same workflow as sales tax compliance, and the rest of the tax engines cluster is indexed in the finance operations glossary.