The exact sales tax rate for
any US address.

The fastest way to find out is to run a nexus study. We connect to your revenue systems (Stripe, Shopify, NetSuite, QuickBooks, ChargeBee, or a CSV) and consolidate transactions by ship-to state. We then run nexus against both economic thresholds (typically $100K in sales OR 200 transactions in most states, with California and New York at $500K) and physical-presence triggers (employees, inventory, 3PLs, offices). You see the state-by-state picture plus an alerting threshold, so new states approaching nexus surface before the next invoice tips you over.

A single remote employee in a state creates physical nexus in almost every state, regardless of role or hours. Inventory stored in a state, including stock held at a third-party fulfilment centre, also creates physical nexus, and is one of the most common quiet triggers for ecommerce sellers. Contractors are state-specific: some states treat them as creating nexus, others don't. We surface the answer per state during onboarding.

Yes, in most states. Economic nexus is typically set at $100K in sales OR 200 transactions over a 12-month window, so a single invoice large enough to cross $100K can create nexus on its own. We've seen six-figure sponsorship and enterprise invoices do exactly that. The fix is to check nexus before issuing large invoices into a new state, not after, which is what real-time nexus alerts on our platform are built for.

No. Foreign qualification is a corporate-registration concept, not a tax-nexus concept, and the two get conflated routinely, including by some AI research tools. Physical nexus comes from real activity (offices, employees, inventory), not from being foreign-qualified to do business in a state. A mail-forwarding-only address doesn't create nexus either. We audit your existing foreign qualifications against actual nexus and unwind the ones you don't need.

No. SaaS taxability varies significantly by state, and within a state by customer type and how the software is delivered. New York treats most SaaS as tangible personal property (taxable). Several other states fully exempt B2B SaaS. A handful sit somewhere in between depending on bundling, delivery mode, or customer use. We maintain a state-by-state SaaS matrix and assign the correct product tax code to each transaction so the treatment is right everywhere automatically.

Yes, and it's surprisingly common. A product tax code meant for physical goods applied to custom B2B software or services can cause you to collect and remit tax that wasn't actually owed, accumulating false liabilities over years. We audit your current product catalog, re-map mis-coded items, and identify what's recoverable from prior periods through state refund or credit claims where the lookback window allows.