Sales Tax Compliance Without the Chaos

Your exposure depends on where your clients sell and how much they're selling. Matt walked through a detailed analysis showing that at just $2 million in annual revenue, a company could trigger nexus obligations in 7–10 states; at $5 million, that jumps to 14–18 states; and by $25 million, you're collecting in nearly every state. The risk isn't just about physical locations—it includes economic nexus thresholds that vary by state (ranging from $100,000 to $500,000 in revenue, or 100–200 transactions). During the demo, Matt showed how Zamp tracks all your sales channels—Shopify, QuickBooks, wholesale orders, Amazon—because a single platform like Shopify only sees Shopify orders and misses your exposure across direct-to-consumer, marketplace, and resale channels.

This is one of the most common compliance failures Matt sees. When a company turns on sales tax collection in their ecommerce platform but isn't registered in those states, they're collecting money that legally belongs to the state—and they haven't remitted a penny. This creates serious liability and compounds over time with penalties and interest. Matt emphasized that auditors flag this immediately. During the demo, he showed that Zamp's team reaches out proactively when it identifies inconsistencies like this in your data, and it helps you clean up the situation rather than letting the problem grow.

Absolutely—and it's more complex than it sounds. While platforms like Amazon handle tax collection and remittance, you still have to report those orders to the state as "marketplace facilitator exempt." But here's the catch: not all marketplaces give you clean address data. eBay and Apple send gross sales amounts with little detail, while Amazon provides the complete transaction data you need to file correctly. Matt also showed that many clients are multichannel—they sell wholesale to Costco, direct-to-consumer on Shopify, and through Amazon simultaneously. Different sale types (wholesale vs. direct) count differently toward economic nexus thresholds in different states, so you need a system that tracks all channels together, not just one platform's view.

During the live demo, Matt showed how Zamp automatically pulls product SKUs from QuickBooks and lets you map tax codes in a central location—no more hunting through spreadsheets to verify whether clothing is taxable at $110 (exempt in New York City) or over. The system flags data quality issues before they become audit problems, tracks economic nexus across all your sales channels in real time, and generates state-required reports in the format each state demands (Schedule A, B, C, etc.) ready to export. Most importantly, you shift from reactive firefighting—finding missed filings and penalties months later—to proactive risk management, with the service owning the outcome from setup through filing.

This course is built on real compliance failures Matt encounters constantly. You'll learn concrete problems—why free samples can trigger use tax obligations, how transaction duplicates cause six-figure overpayments to states, what "economic nexus" actually means in the context of your client's specific revenue and sales mix—and how to identify which clients in your book are highest risk. The demo walks through an actual QuickBooks integration showing how to map exemptions, flag marketplace orders, and reconcile liability to the cent. Matt also covers the specific decision trees that tax engines use (like why a SaaS subscription in Texas is taxed on 80% of the revenue, not 100%), so you understand the logic behind the numbers your clients are seeing.