REDA One Help Center
EN
Language
English EN Español ES Português PT Italiano coming soon Français FR Deutsch coming soon العربية coming soon
reda.one ↗
Home / REDA Financials AI / Tax Management / Tax in Practice (Country Walkthroughs) / Setting Up US Sales Tax

Setting Up US Sales Tax — End to End

US sales tax works on a different principle from VAT/GST, and one idea drives the whole setup: nexus. You only charge sales tax in states where you have a registration (nexus); the rate is the buyer’s state; and whether an item is taxable depends on the item and the buyer. This article shows how to configure REDA so all three are handled automatically — with a catalogue and a couple of contrasting sales to prove it.

Getting there. This setup lives in the REDA Financials Admin app — open the App Launcher (the grid icon at the top-left of any page), pick REDA Financials Admin, and use its tax tabs (Tax Jurisdictions, Tax Types, Tax Rules, Tax Profiles, Party Tax Profiles). Most of the chain is created for you by the Tax Seeding Wizard; sales tax is then calculated automatically on the invoices you post in the day-to-day REDA Financials AI app.
Access you'll need. Setting up the tax rulebook requires the Accounting Admin v2 or Accounting Controller v2 permission set. The Accounts Payable v2, Accounts Receivable v2, and Read Only v2 sets can view the setup but not change it.
The mental model. Three questions decide US sales tax: Do I have nexus in the buyer’s state? (registration) — What’s that state’s rate? (a per-state rule) — Is this item/buyer taxable? (product profile + buyer profile, e.g. resale exemption). No nexus → no tax, by design — the opposite of a VAT country where you charge everywhere you sell.

The configuration chain

#WhatWhy it existsSource
1JurisdictionUS + each stateSeed
2Tax TypeSales Tax, Use TaxSeed
3Tax ProfileTaxable goods vs exemptSeed
4Tax RuleOne per state — the state’s rate, keyed to the destination stateSeed
5Product taxabilityThe Apply Default Tax flag marks your product taxable (see Step 5)You
6Party Tax ProfileTaxable customer / resale-exempt / consumerSeed + you assign
7GL MappingSales Tax Payable accountSeed
8Registration + defaultsYour nexus — one per state where you must collectYou

Our example catalogue

Product / serviceTypical treatmentHow it’s configured
Office furniture (tangible goods)TaxableApply Default Tax flag on
Professional consultingExempt in most statesFlag off — no rule fires, zero tax
Goods sold to a resellerExempt (resale certificate)Taxable product; the invoice lines are marked Tax Exempt
Taxability varies by state. Tangible goods are broadly taxable; services, digital products, groceries and clothing differ state by state. The shipped setup keeps this binary — a product is flagged taxable or it isn’t. If you need state-by-state taxability (taxable in one state, exempt in another), that’s built with profile-scoped rules per state — see the note in Step 3.

Step 1 — Jurisdictions

The seed creates US plus all 50 states. Sales tax is a state (and local) tax, charged at the destination — the buyer’s state — so the state jurisdictions are what the rules key to.

Step 2 — Tax Types

Tax TypeWhat it is
US-SALES-TAXCollected from the customer on a taxable sale, remitted to the state
US-USE-TAXSelf-assessed on a purchase where the seller didn’t charge sales tax

US sales tax is not recoverable like VAT — it’s a tax on final consumption, so there’s no input-credit asset; a non-resale purchase is a real cost.

Step 3 — Tax Profiles

Tax ProfileFor products that are…
US-STD-GOODSTaxable (tangible personal property, most goods)
US-EXEMPT-GOODSExempt (many services, groceries/prescriptions where exempt)
The shipped state rules don’t reference these profiles. All 50 seeded rules leave Tax Profile blank — they are catch-all rules, which fire for products flagged Apply Default Tax (Step 5). The two profiles ship as building blocks: if you later need state-specific taxability, you scope copies of the state rules to US-STD-GOODS and classify products with fiscal profiles. Until then, a product classified to a profile matches no shipped rule — taxability runs on the flag.

Step 4 — Tax Rules (one per state)

Each state ships a rule carrying that state’s combined rate, keyed to the destination jurisdiction. The rule fires when the buyer is in that state and the product is flagged taxable. A few examples:

RuleDestinationCombined rate
US-SALES-TAX-CACalifornia8.82%
US-SALES-TAX-TXTexas8.19%
US-SALES-TAX-NYNew York8.52%
…one per state, all 50. (The no-sales-tax states — Oregon, Montana, New Hampshire, Delaware, and state-level Alaska — ship as 0% rules, so a sale there computes zero rather than falling through.)

The seeded rates are state + average local. For rooftop-accurate local rates, override the rate on a state’s rule or add city/county jurisdictions — but the state rate is the right starting point.

Step 5 — Classify your catalogue

With the shipped catch-all rules, classification is one checkbox per product — Apply Default Tax:

ProductApply Default TaxResult
Office furnitureOnThe buyer’s state rule fires (where you have nexus)
Professional consultingOffNo rule fires — zero tax, every state

No fiscal profiles are needed for this pattern — and note the strictness cuts both ways: a product with the flag off and no fiscal profile simply gets no tax, which is exactly what you want for exempt services.

Step 6 — Party Tax Profiles

Party ProfileUse for
US-TAXABLE-B2BA normal taxable business customer
US-EXEMPT-RESELLERA buyer who gave you a resale / exemption certificate — the profile records the certificate basis
US-CONSUMERAn end consumer (taxable)

Two things about the reseller case. The profile is the record: it carries the exemption and its basis (“Resale certificate — buyer holds valid reseller permit”), so the justification lives on the account. The switch that stops the tax is on the invoice: mark the resale lines’ Tax Base as Tax Exempt, and the engine skips them entirely — no rules, no tax. (The shipped state rules don’t filter by buyer profile; rules can be scoped to a buyer’s Party Tax Profile if you want that automated per customer.)

Step 7 — GL mapping

One mapping covers the common case — sales tax you owe the state:

SidePosts toAccount kind
Sales2371-SALES-TAX-US — Sales Tax PayableLiability (you remit to the state)

Step 8 — Register where you have nexus

This is the step that defines US behaviour. Create an Entity Tax Registration for each state where you have nexus — physical presence, or economic nexus (typically > $100k or 200 transactions a year in that state).

Register per nexus state. One registration per state where you must collect (e.g. California, Texas). In states where you have no nexus, you create no registration — and REDA charges no tax there.
Set the entity & customer jurisdictions. The customer’s ship-to state is the destination the rule keys on.
Set default GLs on the entity (AR, revenue).

The payoff — nexus, rate & taxability, automatically

You have nexus in California and Texas, not in Florida. Sell $1,000 of office furniture (taxable). The configured data decides:

SaleSales taxWhy
To a customer in California$88.20 (8.82%)Nexus in CA + taxable product
To a customer in Texas$81.90 (8.19%)Nexus in TX + taxable product
To a customer in Florida$0.00No nexus in FL — you can’t collect
To a reseller in California$0.00Lines marked Tax Exempt (resale certificate on file)
Consulting (any state)$0.00Product not flagged taxable — no rule fires

The California sale’s journal:

AccountDebitCredit
Accounts Receivable$1,088.20
Revenue$1,000.00
Sales Tax Payable — 2371-SALES-TAX-US$88.20
Your state returns fall out of the accounts. Sales tax collected accumulates in 2371-SALES-TAX-US by jurisdiction; each state’s remittance traces to its Source Line Tax rows. Register a new state the day you cross its economic-nexus threshold and REDA starts collecting there — not before.

Use tax — the purchase side

When you buy taxable goods and the seller didn’t charge sales tax (an out-of-state vendor with no nexus in your state), you owe use tax — the same rate, self-assessed. Configure it like a purchase-side tax so REDA accrues the liability rather than letting the cost slip through untaxed.

If sales tax is wrong, check the chain

  1. Nexus. No registration in the buyer’s state → no tax (by design). Crossed a threshold? Add the registration.
  2. Destination set. The customer’s (ship-to) state drives the rate — it must be set.
  3. Product taxability. Is Apply Default Tax ticked on the product? Off (with no fiscal profile) means zero tax by design. And a product classified to a fiscal profile matches no shipped rule — the seeded state rules are catch-alls.
  4. Exempt lines. A line whose Tax Base is Tax Exempt is intentionally untaxed — the resale pattern; check the buyer’s certificate is on file.

Where to go next

  1. Entity Tax Registration — nexus recorded as registrations.
  2. UK VAT — VAT contrasted with sales tax.
  3. Tax Jurisdictions — US states as taxing jurisdictions.
  4. Tax Rules — how state rate rules match.
  5. Tax Seeding Wizard — load US state packs quickly.

Frequently asked questions

Because you have no nexus (registration) in that state. In the US you only collect where you’re registered — that’s the law (post-Wayfair, economic nexus is typically $100k or 200 transactions a year per state). Register the state and REDA starts collecting.

Assign their Account the US-EXEMPT-RESELLER party profile with the certificate recorded as its exemption basis — that’s your audit record — and mark the resale lines Tax Exempt on their invoices, which is what actually stops the tax. To automate it per customer, scope your state rules to the taxable buyer profiles so exempt-profile buyers fall outside them.

The seed uses state + average local rates. For rooftop accuracy, override the rate on the state’s rule, or add county/city jurisdictions and rules. Many businesses run on the state-level rate plus periodic updates.

It depends on the state — most professional services are exempt, but some states tax specific services and digital products. With the shipped setup, flag a service’s Apply Default Tax on if it’s taxable where you sell, off if not. If the same service is taxable in one state and exempt in another, build profile-scoped copies of those states’ rules against US-STD-GOODS and classify the service with a fiscal profile.

Was this article helpful?