Sales Tax Computation

By Nupur Mittal

Co-founder at OCTA — works with accounting firms on month-end close and reconciliation automation.

Sales tax computation is the process of determining, state by state, whether a business has a legal obligation to collect sales tax, applying the correct destination-based rate to each taxable transaction, and calculating the resulting liability net of exemptions. In the US, that obligation now turns as much on economic nexus — a dollar or transaction threshold, not a physical location — as it does on where the business operates. This page walks through the full multi-state process step by step, a worked nexus-and-liability example, the red flags a careful reviewer watches for, and how firms run the computation faster with OCTA Flow while a person signs off on every filing decision.

Why sales tax computation matters, and where it goes wrong

Since the Supreme Court's 2018 ruling in South Dakota v. Wayfair, a business no longer needs a warehouse, an office, or an employee in a state to owe that state sales tax. Selling enough into a state — commonly $100,000 in sales or 200 transactions in a calendar year, though the exact threshold and whether it's an "or" or "and" test varies by state — is enough to create an obligation to register, collect, and remit. For any business selling across state lines, especially e-commerce and SaaS companies, that means nexus can appear quietly, one growing state at a time, with no single event to flag it.

The mechanical burden compounds the risk. A business with real multi-state exposure is tracking rolling sales and transaction counts against dozens of different thresholds, applying destination-based rates that combine state and local tax and change without much notice, sorting out which products and services are even taxable in which state, and validating exemption certificates that expire or don't cover what a customer claims. Missing a single nexus trigger doesn't produce one bad invoice — it produces a retroactive liability going back to the date nexus was created, often with penalties and interest layered on top, discovered years later in an audit. The goal of a rigorous sales tax computation isn't just "get this period's number right" — it's catching a newly-triggered obligation the moment it happens, before it becomes back taxes.

The sales tax computation process, step by step

A proper multi-state sales tax computation follows a consistent sequence. The steps below are the full procedure OCTA Flow executes; they also stand alone as a best-practice process any firm or in-house tax team can follow.

1. Determine nexus by state. For every state the business ships into, assess two independent tests:

• Physical nexus — does the entity have employees, inventory (including third-party fulfillment inventory), an office, or other physical presence in the state?
• Economic nexus (post-Wayfair, 2018) — most states set the threshold at $100,000 in sales or 200 transactions into the state in the prior or current calendar year. Compare total sales and transaction count into each state against that state's specific threshold, since a handful of states use different dollar figures or drop the transaction-count leg entirely.

If neither test is met, no collection obligation exists in that state — though voluntary registration is sometimes worth considering for administrative reasons. If a prior-period nexus analysis is available, compare it to the current period to flag any state that has newly crossed the line.

2. Apply destination-based sourcing. The large majority of states are destination-based: the applicable tax rate is set by the customer's ship-to location, not the seller's location. Match each transaction's ship-to address to the correct state and local rate — local rates (city, county, special district) can push the effective rate well above the state rate alone, and they vary by ZIP code or address within the same state.

3. Determine taxability. Not every product or service is taxable in every state, and getting this wrong is one of the most common sources of exposure:

• Tangible personal property — generally taxable across states, with common exceptions
• SaaS and digital services — varies significantly; some states tax it as tangible property, some exempt it, some have no clear rule
• Professional services — generally exempt in most states
• Grocery vs. prepared food — frequently taxed differently within the same state

Flag any transaction where taxability is genuinely unclear rather than defaulting it either way, and note the specific state rule that applies.

4. Apply exemption certificates. For any transaction tied to a customer claiming exempt status (resale, nonprofit, government, manufacturing, etc.), verify the certificate before excluding the sale from the taxable base:

• Confirm it hasn't expired
• Confirm it's valid for the state the transaction is sourced to
• Confirm the certificate type actually covers the product or service sold

Valid, matching certificates remove the transaction from that state's taxable base. Expired, incomplete, or mismatched certificates do not — and should be flagged as exposure rather than silently accepted.

5. Compute state-by-state tax liability. For each nexus state:

• Taxable sales = Total sales into the state − exempt sales (valid certificates only) − non-taxable product/service sales
• Tax due = Taxable sales × applicable rate (state + local)
• Sum every state's tax due for total sales tax liability

6. Assess use tax on purchases. Use tax is the mirror image of sales tax: it's owed by the buyer when a vendor doesn't charge sales tax on a purchase that will be used (not resold) in the buyer's state. For each purchase where no sales tax was charged, determine whether it's a taxable use in the state, and if so compute use tax = purchase price × the state's use tax rate (typically equal to the sales tax rate).

7. Compare to the prior period. Flag any state where nexus was newly triggered, where a rate changed, or where sales volume shifted enough to be worth a second look — a state trending toward a threshold this period is a state to start tracking now, not after it's crossed.

Worked example: nexus check, state liability, and an unregistered-nexus flag

Here's a simplified Q1 2025 computation for a multi-state retailer selling into four states.

Step 1 — Nexus check

Three of the four states clear an economic or physical nexus test. Washington is the one to flag: $145,000 in sales and 210 transactions crosses Washington's $100,000/200-transaction threshold, but the entity has never registered there. That's a live compliance gap, not a future risk — sales tax should have been collected on every Washington sale since the threshold was crossed.

Step 2 — State liability calculation (California)

Repeating the same calculation for Texas ($350,000 taxable × 8.25% = $28,875) and New York ($200,000 taxable × 8.00% = $16,000) gives a combined sales tax liability of $66,625 across the three registered states for the quarter — before Washington is addressed.

Step 3 — Unregistered-nexus flag

Washington is excluded from the liability total above because the entity isn't registered there yet, which is exactly why it's flagged rather than quietly rolled into the number. The recommended path: register with Washington's Department of Revenue, then determine whether the exposure period requires a voluntary disclosure agreement to limit look-back liability and penalties versus waiting for the state to find it on audit — a materially worse outcome. This is the single highest-value flag a multi-state sales tax computation produces, because unlike a rate error, an unregistered nexus state compounds every period it goes unaddressed.

Key controls and red flags

The difference between a computation that just runs the formulas and one that actually protects the business is what you watch for. A careful reviewer flags:

• Economic nexus thresholds crossed with no registration in that state — the single most consequential flag; every period it's missed adds to the exposure
• Exemption certificates that are expired, incomplete, or don't match the product type sold — creates uncollected-tax exposure the seller, not the customer, is on the hook for
• Products or services with genuinely unclear taxability treatment — flagged rather than defaulted, with the state's specific rule noted
• High-value transactions with no tax charged and no exemption certificate on file — the most common source of an audit assessment
• Use tax exposure on purchases over roughly $500 with no sales tax charged by the vendor
• A state trending toward its nexus threshold but not yet over it — worth tracking proactively, not waiting to react
• Rate changes since the prior period that weren't reflected in the computation

Catching these consistently, across every nexus state and every period, is what turns sales tax from a filing chore into an actual compliance control.

What a completed sales tax computation produces

A finished computation isn't just a total due — it's a documented workpaper a tax manager can review and a state auditor can follow line by line. A complete sales tax computation package includes:

How OCTA Flow automates sales tax computation

OCTA Flow does the mechanical nexus tracking, rate matching, and liability computation for you, and leaves the registration and filing decisions with your team. The workflow mirrors the process above:

1. Pick the Sales Tax Computation Skill. Flow already knows the full procedure: nexus testing, destination-based sourcing, taxability review, exemption certificate validation, state-by-state liability, and use tax assessment.
2. Connect your data. Point Flow at the connected accounting or e-commerce system, or upload the period's files — sales transaction detail, ship-to address data, state rate tables, exemption certificates, and the purchase ledger for use tax.
3. Run. Flow tests every state against its economic and physical nexus thresholds, sources each transaction to the correct destination rate, applies valid exemption certificates, and builds the state-by-state liability schedule.
4. Review findings by severity. Instead of a raw liability number, Flow surfaces the exceptions that actually need a decision — ranked by severity, each with a plain-English explanation and a recommended action: file the return, escalate an unregistered nexus state to a SALT specialist, request a missing exemption certificate, or route the computation to a tax partner for sign-off. Your team works the exceptions, not every transaction.
5. Sign off. Once the computation is reviewed and any registration or filing decisions are made, Flow assembles the workpaper with the full audit trail intact.

The result: nexus monitoring and rate application — the part that's tedious and easy to let slip — run every period without fail, and your people spend their time on the states and judgment calls that actually carry risk.

Control and trust: Flow proposes, you approve

This matters more in tax than almost anywhere else in accounting: OCTA Flow never files a return or registers the business in a state on its own. Every recommendation — file, register, escalate, request a document — is a proposal that a person reviews and confirms before any action is taken. Flow does the computation and shows its reasoning; a person makes the call.

That control model runs through the whole process:

• Findings, not silent filings. Flow raises what it found and what it recommends — a newly-triggered nexus state, an expired certificate, an unclear taxability call — and your team decides how to act on it.
• Severity and escalation built in. An unregistered-nexus state is flagged as critical and routed to a state and local tax (SALT) specialist rather than buried in a summary total.
• A complete audit trail. Every nexus determination, rate applied, exemption accepted, and approval is logged, so the computation is fully traceable if a state ever asks how a number was reached.

You get the speed of automated nexus tracking and rate calculation with the accountability of a person deciding where and when to register and file — exactly what multi-state tax exposure requires.

What the computation draws on

To run a sales tax computation, Flow uses the same sources a tax preparer already works from:

• Sales transaction detail — every sale for the period with ship-to state, amount, and product type (required)
• Ship-to address data — the destination address per transaction, for destination-based sourcing (required)
• State rate tables — the state and average local rate for each state the business sells into (required)
• Exemption certificates — customer, state, and certificate type for exempt customers (optional)
• Purchase ledger — purchases where no sales tax was charged, for use tax assessment (optional)
• Prior-period nexus analysis — the last period's nexus determination and registered states, to flag what's newly triggered (optional)

Flow works from whatever your client has connected — it matches each input by its purpose, so it doesn't matter what the files are named or which system they came from.

Related skills and terms

Frequently Asked Questions

What is economic nexus for sales tax? Economic nexus is a sales tax collection obligation triggered by sales volume into a state rather than physical presence — established by the Supreme Court's 2018 South Dakota v. Wayfair decision. Most states set the threshold at $100,000 in sales or 200 transactions in a calendar year, though the exact figures and whether it's an "or" test vary by state.

How do I know if I have sales tax nexus in a state? Check two tests for every state you sell into: physical nexus (employees, inventory, or an office in the state) and economic nexus (sales or transaction volume crossing that state's specific threshold). If either test is met, you generally have an obligation to register, collect, and remit in that state.

What is destination-based sourcing? It's the rule, used by most states, that the applicable sales tax rate is determined by the customer's ship-to location rather than the seller's location. That means the same sale can carry a different rate depending on exactly where it's shipped, since local rates layer on top of the state rate.

How do exemption certificates work in a sales tax computation? A valid, unexpired certificate that matches both the state and the product type lets a seller exclude that sale from its taxable base. An expired, incomplete, or mismatched certificate does not — the sale stays taxable, and an uncollected certificate is exposure the seller is liable for, not the customer.

What is use tax and how is it different from sales tax? Sales tax is collected by the seller from the buyer at the point of sale. Use tax is the mirror obligation owed by the buyer when a vendor didn't charge sales tax on a purchase that will be used — not resold — in the buyer's state. Both ultimately fund the same state tax base; use tax exists so untaxed purchases don't escape it.

Can multi-state sales tax computation be automated? Nexus testing, rate application, taxability matching, and exception-flagging can be automated and reviewed, while registration and filing decisions stay with your team. That's the model OCTA Flow uses.

Does OCTA Flow file my sales tax returns or register my business in a state? No. Flow proposes every filing and registration action — a person on your team or your SALT specialist reviews and decides before anything is filed or registered. Nothing happens automatically.

See how firms track nexus and compute multi-state liability with human sign-off → start a 30-day OCTA Flow trial.