Sales Tax Compliance Risks Grow Across Channels and Systems

Sales tax errors often start with gaps in data and coordination, then spread across products, locations and sales channels. The recurring trouble spots are nexus monitoring, product taxability, exemption records and sourcing. For businesses selling through several systems, the challenge is keeping those decisions consistent from the first quote through the invoice, return or credit.

Errors cut across company sizes

Greg Chapman, who leads Avalara’s AvaTax business, says common failures include missing changes in economic nexus or marketplace facilitator arrangements, misclassifying products and bundles, allowing exemption certificates to lapse, and using inaccurate address information. Each can affect whether tax is collected, how much is charged, or whether the business can support its treatment later.

The underlying risks show up in businesses of different sizes, though the operational causes can vary. Smaller teams may have limited capacity to monitor changes and maintain controls. Larger organizations may have more systems and business units, which can make it harder to keep tax logic aligned. In either case, decentralized decisions and inconsistent records weaken accuracy and make timely reconciliation more difficult.

These issues are connected. A product classification feeds the tax decision; the customer’s exemption status may change that result; and the transaction’s location can determine which sourcing rules apply. If the records used by different teams or systems don’t match, a correct decision in one part of the workflow can still become an incorrect invoice or return.

More channels mean more handoffs

Selling through a marketplace, a company website, physical points of sale, wholesale accounts and subscriptions adds coordination work. A marketplace may collect tax for a seller on transactions conducted through that channel, while the business still needs to account for its own direct sales and other transaction types. The treatment can also depend on the arrangement and the details captured for each sale.

Promotions, partial shipments, returns and credits complicate the record further. A refund or credit needs to retain enough of the original transaction’s information to support the tax treatment. Fulfillment from different locations can also change sourcing and applicable rates. When systems don’t pass those details along consistently, teams may struggle to explain why a quoted amount differs from the final invoice or how a later adjustment was calculated.

Chapman’s proposed remedy is operational consistency: use one governing tax approach across channels, maintain an authoritative source for tax content, standardize the data exchanged between systems, and reuse a central tax engine. Transaction records should connect quotes, invoices and returns so teams can trace how a decision was made and reconcile the lifecycle of an order.

Place the calculation where it can be checked

Tax determination has to fit the sales workflow. Calculating at the quote or cart stage helps set the customer’s expectation; the final calculation belongs at invoicing in the system of record. A central determination service can support both steps when it receives normalized information, including product classification, billing and shipping addresses, nexus status, exemptions, marketplace indicators and transaction timing.

Platforms such as QuickBooks, Shopify, NetSuite and Salesforce may each play a role in the order-to-cash process. Maintaining separate rate tables and tax rules inside each can lead to differences over time, followed by reconciliation gaps. A shared service connected through platform integrations gives teams a consistent place to apply tax logic while retaining the transaction details needed to review results.

The practical test is whether a tax decision can be followed from the initial quote to the final invoice and any later return or credit. If each system holds only part of the story, staff may have to reconstruct the record by hand. Shared data standards and clear system connections reduce that burden and make discrepancies easier to identify.

AI can assist, but controls still matter

AI tools are being used for product classification, certificate capture and validation, address cleanup, monitoring changes in tax rules, anomaly detection, notice triage and forecasting nexus risk. These tasks can involve large volumes of records and repeated manual review, so automation may reduce processing effort and help teams apply decisions more consistently.

But AI output needs reviewable evidence behind it. Practitioners should look for explanations and audit trails, human oversight for tax determinations, measurable accuracy standards, version tracking for models and tax content, and safeguards for private data. Hallucinations, biased training data and model drift can all affect results. The system’s outputs therefore need to remain grounded in authoritative tax content and an accountable process.

For finance and tax teams, the central question is whether their systems preserve consistent, traceable decisions as the business adds channels, products and fulfillment paths. Automation can help with the workload, but reliable results still depend on accurate inputs, clear ownership and records that connect each stage of a transaction.