TLDR

• Sales tax follows one formula. Multiply the taxable price by the combined rate. The combined rate stacks the state base on top of county and city or district add-ons.

• Rates change often. Washington State alone refreshes its rate database every quarter, so any number you hardcode goes stale (dor.wa.gov).

• Sourcing rules decide which rate applies. Most states tax at the buyer's location, twelve tax at the seller's.

• Manual calculation holds up for a single state. It collapses once you cross nexus thresholds in five or ten. This guide is written for controllers and finance ops leads, not first-time sellers.

The Sales Tax Formula

Sales Tax = Taxable Price × Sales Tax Rate. Convert the rate to a decimal before you multiply. A 7% rate becomes 0.07, an 8.25% rate becomes 0.0825.

Walk it through with a hypothetical combined rate of 7% for illustration. Actual rates vary by state and locality, so treat this number as a placeholder, not a figure to apply. Take a $1,000 taxable invoice. Multiply $1,000 by 0.07 and you get $70 in tax. Add that to the price and the customer owes $1,070.

The arithmetic never changes. What changes underneath it is the rate and whether the item is taxable at all, and those two variables carry all the risk. A real Michigan transaction runs at the state's 6% base, while a Tennessee sale can reach 9.75% once local governments add their share (itep.org). Plug the wrong rate into a correct formula and you have undercollected on every invoice.

Most how-to guides stop at the worked example, which works fine for a one-state retailer ringing up a garden hose. B2B finance teams need more. Your invoices carry exemption certificates, mixed taxable and exempt line items, and customers in states where you may not even owe tax. The formula is the floor. The rest of this guide covers what determines the rate and the taxable base, which is where manual processes actually break.

How to Find the Right Sales Tax Rate

The combined rate a buyer pays stacks in three layers. You start with the state base rate, add a county rate, then add a city or special district rate on top. A single ZIP code can sit inside overlapping districts, which is why two addresses a mile apart can carry different totals.

Michigan keeps this simple. The state charges a flat 6% with no local add-on, so a $10 item there carries $0.60 in tax for a $10.60 total (itep.org). Tennessee runs the opposite way. Its 7% state base rate climbs as high as 9.75% once local governments tack on up to 2.75% (itep.org).

That layering means you cannot assume a state has one rate. You have to resolve the rate for the exact delivery address. Washington State publishes a Tax Rate Lookup Tool that returns the combined rate by address, ZIP+4, or map, and its downloadable rate database refreshes every quarter (dor.wa.gov). Most states with local taxes run a similar lookup through their Department of Revenue.

Rates do not hold still. States raise them as exemptions and untaxed digital services shrink the share of spending that sales tax actually reaches (itep.org). Washington documents every change through quarterly notices for cities, lodging, and motor vehicles. Treat any rate you record as a snapshot. Verify it against the relevant state DOR before each filing rather than trusting a number you cached last quarter.

One more scope check before you build a rate table. General sales taxes exist in 45 states plus the District of Columbia and Puerto Rico (itep.org). The five states without one still impose other obligations, so confirm jurisdiction before you assume a sale is tax-free.

Origin-Based vs. Destination-Based Sourcing

Two sourcing methods decide which rate you charge. Destination-based sourcing applies the rate at the buyer's location. Origin-based sourcing applies the rate at the seller's location.

Most states and Washington D.C. use destination-based sourcing, so the rate follows where your customer takes delivery. A handful flip that logic for in-state sales and charge the rate at the seller's address instead. The distinction only changes what you owe when both buyer and seller sit inside the same state.

Origin rules apply to intrastate transactions, not interstate ones. The moment you ship across a state line into a state where you have nexus, destination-based sourcing takes over regardless of where your business is located. A remote seller in Texas selling into Florida charges Florida's destination rate, not Texas origin rates.

Which states use origin-based sourcing

Twelve states have historically been described as origin-based: Arizona, California, Illinois, Mississippi, Missouri, New Mexico, Ohio, Pennsylvania, Tennessee, Texas, Utah, and Virginia (Sales Tax Institute). Treat that list as a starting point, not statute. Verify each state against its Department of Revenue before you rely on it, because the enumeration shifts.

Two states have already moved. New Mexico transitioned from origin to destination sourcing on July 1, 2021 (tax.newmexico.gov), and Colorado followed on October 1, 2022 (tax.colorado.gov). Vendor lists disagree on New Mexico for exactly this reason, which is why a primary-source check matters before you publish a rate or program a calculation.

California deserves its own footnote. State, county, and city taxes follow origin rules at the seller's location, but district taxes follow destination rules at the buyer's location (cdtfa.ca.gov). A Los Angeles seller shipping to a San Francisco customer charges LA rates on the state, county, and city portions and SF rates on the district portion. Ohio adds a similar wrinkle, applying origin sourcing to tangible goods and destination sourcing to services (tax.ohio.gov).

What Is and Isn't Taxable

Sales tax starts with tangible personal property. Goods you can see, touch, or carry out of a store form the default taxable base in every state that levies sales tax. Services and intangible goods have historically sat outside that base, though states keep expanding their definitions to pull digital products and subscriptions back in (Sales Tax Institute).

Two everyday categories prove the base is never universal. Many states exempt groceries or tax them at a reduced rate, and several exempt clothing under a price threshold. Verify both against the specific state Department of Revenue before you collect, because the rules differ by state and change often.

SaaS and digital goods

SaaS is where taxability gets genuinely hard for a finance team. It is not tangible personal property, so states have improvised. Some treat it as a taxable digital service, some treat it as an exempt service, and a few classify it as tangible personal property outright (Sales Tax Institute). As of 2025, SaaS is taxable in some form across 25 US jurisdictions (Sales Tax Institute).

Three frameworks describe how a given state handles it. Fully taxable states treat SaaS like a good or an enumerated taxable service. Non-taxable states treat it as an exempt intangible. Conditional states make the answer depend on the use case, the delivery method, or who is buying.

The conditional category is the one that catches controllers off guard. Iowa exempts business-use SaaS but taxes personal-use SaaS. Ohio does the exact reverse, taxing business use and exempting personal use (Sales Tax Institute). Two neighboring states reach opposite conclusions on the same product, which is why a single internal rule for your whole product line will eventually be wrong somewhere.

Treat every example here as illustrative, not as a determination for your business. Avoid blanket state-by-state SaaS claims, because the classification often turns on contract language, bundling, and customer type rather than the product name. Custom software adds another layer, since several states exempt software built for a single buyer while taxing the prewritten version delivered the same way.

The cost of getting this wrong shows up later as uncollected tax you still owe. The safe path is to confirm each jurisdiction's current treatment against its primary tax authority and document the basis for every taxability decision you make.

Applying Sales Tax to Mixed Orders

Tax applies to the taxable items in a cart, not the cart total. You calculate the taxable base by summing only the items that are subject to tax, then multiply that subtotal by the rate. Exempt items stay out of the calculation entirely.

Picture a checkout with two products. One is a taxable item priced at $40. The other is an exempt item priced at $30, exempt because the destination state carves it out of its tax base. You apply the rate only to the $40. At a hypothetical combined rate of 7%, the tax is $2.80, and the order total comes to $72.80. The $30 exempt item never enters the taxable base.

This line-item logic holds whether the cart has two products or two hundred. Your system has to know the taxability status of each SKU at the destination, then split the cart accordingly before applying the rate. A single wrong classification quietly understates or overstates the tax on every order that includes that SKU.

Bundling creates a real risk you should watch for. When you combine a taxable item and an exempt item into one bundled price on the invoice, many states treat the entire amount as taxable because the components are no longer separately stated. Keep taxable and exempt items as distinct line items with their own prices. Separately stating each component preserves the exemption and keeps the taxable base accurate, which is exactly the kind of detail an auditor checks first.

Why Manual Sales Tax Calculation Breaks Down at Scale

A spreadsheet works fine when you sell in one state with a stable rate. It collapses the moment your company crosses economic nexus thresholds in a dozen states and starts owing destination-based tax everywhere your customers sit. Four failure modes show up in that order, and each one compounds the last.

Rate-change lag is the first crack. States like Washington update their downloadable rate database quarterly, and no spreadsheet pings you when a city or district rate moves. You find out during reconciliation, after you have already undercollected or overcollected for a quarter.

Multi-state nexus turns one rule set into fifty. After the 2018 Wayfair decision, you owe tax based on where your buyer receives the product, not where you operate. A controller managing this by hand has to track distinct thresholds, sourcing rules, and filing calendars for every state where sales volume crosses the line. The work scales linearly with your customer map while your finance team does not.

Product misclassification is the failure that costs the most and shows up the latest. A New York Tax Appeals Tribunal ruling found a company had treated its vendor management software as a non-taxable service when the state classified it as taxable prewritten software, leaving years of uncollected tax on the books (tax.ny.gov). You can apply the formula correctly on every invoice and still be wrong because you put the product in the wrong bucket.

Audit exposure ties the first three together. When an auditor reviews three years of transactions across multiple states, every stale rate, missed nexus trigger, and misclassified line item becomes an assessment with interest. Manual systems leave no clean trail showing which rate applied on which date and why, so you end up defending decisions you cannot reconstruct.

None of these are edge cases for a company in the $10M to $250M range. They are the predictable result of outgrowing a system built for one state while your customer map has expanded to twenty, with no engine underneath tracking which rules changed last quarter.

Sales Tax Compliance at Scale with Taxwire

Once your company crosses economic nexus thresholds in a handful of states, the manual approach you started with stops scaling. You are tracking quarterly rate changes across jurisdictions, classifying products against rules that vary by state, and reconciling all of it before each filing deadline. Taxwire handles that work so your finance team stops chasing rate tables.

Taxwire builds and maintains its own tax engine and does not license third-party rate data. That distinction matters when a county add-on changes mid-quarter or a state revises how it treats digital goods. You get rate and taxability logic maintained directly by the people who own the engine, not resold data that arrives with a lag.

Implementation moves in two stages. Live calculation may go live in days, so your checkout or invoicing starts applying correct rates quickly. Full compliance setup — including state registration, historical data cleanup, exemption certificate work, and filing readiness — takes one to two weeks.

For a controller evaluating automation, the question is whether the tool removes the recurring tasks that eat your team's time and create audit exposure. Taxwire calculates tax at the line-item level, applies the right sourcing rule per transaction, and keeps product taxability current as states revise their rules. You review and approve. You stop hand-checking rates against DOR pages.

If you are managing multi-state sales tax manually and feeling the strain, see how Taxwire works and what a setup looks like for your transaction volume.

Frequently Asked Questions

What is the sales tax formula?

Sales tax equals the taxable price multiplied by the combined sales tax rate. Convert the rate to a decimal first, so a 7% rate becomes 0.07, then multiply it against the taxable portion of the order. The taxable base excludes any exempt items, so confirm product taxability before you run the calculation.

Does sales tax apply to shipping?

Shipping taxability depends on the state and how the charge appears on the invoice. Colorado's Department of Revenue states that delivery and freight charges are generally not subject to sales tax as long as they are separable from the purchase and separately stated on the invoice (tax.colorado.gov). Bundle shipping into one combined price with taxable goods, and the entire amount may become taxable.

What is the difference between sales tax and use tax?

Sales tax is collected by the retailer at the point of sale, while use tax is owed by the buyer when no retailer collected the tax. California's CDTFA explains that a purchaser may owe use tax on items bought from out-of-state or online retailers who do not collect California tax (cdtfa.ca.gov). The two operate as companions designed to tax the same consumption either way.

Are labor and services subject to sales tax?

Labor and services are generally not taxable, though many states tax specific enumerated services. Colorado's Department of Revenue confirms that separately stated labor charges are not taxable, but charges bundled with tangible property into one price make the full transaction taxable (tax.colorado.gov). Rules vary by state, so check each jurisdiction's enumerated service list.

What is the difference between origin-based and destination-based sales tax?

Origin-based sourcing applies the seller's location rate, while destination-based sourcing applies the buyer's location rate. Origin rules only cover intrastate sales where seller and buyer sit in the same state. Sell across state lines, and destination-based sourcing applies regardless of your home state.