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 / Classifying Parties & Products / Tax Profiles

Tax Profiles

A Tax Profile classifies a product or service by how it is taxed — standard-rated, reduced-rate, zero-rated, exempt. It answers the “what” in a transaction, the partner to the “who” that Party Tax Profiles answer.

Think of it as the tax-relevant category of a thing you sell. A loaf of bread, a children’s book, and an export are all zero-rated in the UK — very different products, one tax treatment. The Tax Profile is what groups them so a single rule can cover them all.

Getting there. Open the App Launcher (the grid icon at the top-left of any page) → REDA Financials Admin → the Tax Profiles tab. In practice the Tax Seeding Wizard creates a country's standard profiles; open the tab to review or maintain one.
Access you'll need. Setting up and maintaining tax profiles 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 them but not change them.
One small object, a big job. A Tax Profile is barely more than a code and a category. But it’s the hinge that connects your products to your tax rules: a product points at a Tax Profile (via its fiscal profile), and a rule targets a Tax Profile — so the right rate finds the right product without anyone matching them by hand.

The fields — with UK & Brazil values

FieldTypeRequiredWhat it’s for🇬🇧 UK Standard🇧🇷 Brazil Standard
CodeText · External IDYesMatch/seed keyGB-STD-20BR-STD-GOODS
CategoryPicklistYesThe treatment kind (see below)Standard GoodsStandard Goods
DescriptionText AreaNoWhat this profile coversStandard-rated supplies at 20%Standard goods
NotesLong TextNoExamples, edge cases……
Is ActiveCheckboxNoOff → excluded from matchingYesYes

The Category picklist captures the standard treatments: Standard / Reduced Rate / Zero-Rated / Exempt Goods, Capital Goods, Standard / Reduced Rate / Exempt Services, and Digital Services.

How it connects products to rules

The Tax Profile sits in the middle of a short chain:

Product  →  Product Fiscal Profile  →  Tax Profile  ←  Tax Rule

A product is linked to a Tax Profile through its Product Fiscal Profile (which also carries country codes like the UK’s — none, India’s HSN, Brazil’s NCM). A Tax Rule names a Tax Profile as one of its matching conditions. When the two line up — the product’s profile equals the rule’s profile — that rule fires for that line.

In practice, on an invoice line. When you add a line, the engine resolves the line’s Tax Profile — from an explicit override on the line if set, otherwise from the product’s fiscal profile. It then fires every rule scoped to that profile. Sell a zero-rated book and the zero-rate rule (0%) matches; sell standard goods and the 20% rule matches. Same engine, different profile.

The full resolution ladder

For every line, the engine works down four steps and stops at the first that answers:

Line override. A Tax Profile set directly on the invoice line wins outright — the product isn’t even consulted. Use it for the exceptional line, not as a habit.
Product’s fiscal profile. The product’s active Product Fiscal Profile for the entity’s country supplies its Tax Profile (a country-less fiscal profile acts as the global fallback).
The default-tax flag. No profile found, but the product’s Apply Default Tax flag is on → only the catch-all rules (those with a blank Tax Profile) fire.
Zero tax. No profile and no flag → the line gets no tax at all. Deliberately strict: an unclassified product never picks up a rate by accident.

That last step is worth remembering when troubleshooting: a line with no tax and no error usually means an unclassified product with Apply Default Tax switched off.

Rules with no profile — the catch-all

A Tax Rule can leave its Tax Profile blank. That makes it a catch-all — it isn’t tied to any product treatment. Catch-all rules are how the simplest setups avoid classifying every product: pair a single “standard VAT” catch-all rule with the Apply Default Tax flag on a product, and you get correct tax with no Tax Profile to maintain. This is the usual UK pattern, and it’s covered in Product Fiscal Profiles.

Catch-all rules don’t mix with profile-scoped rules. By design, a catch-all rule fires only for products that have no fiscal profile (and rely on the default-tax flag). It does not stack on top of a product that’s already classified by a Tax Profile. This prevents an unrelated catch-all from accidentally double-taxing a properly classified product.

Real data: UK and Brazil tax profiles

🇬🇧 UKCategory🇧🇷 BrazilCategory
GB-STD-20 StandardStandard GoodsBR-STD-GOODS StandardStandard Goods
GB-RED-5 ReducedReduced Rate GoodsBR-IPI-GOODS ManufacturedCapital Goods
GB-ZERO Zero-RatedZero-Rated GoodsBR-REDUCED-GOODS ReducedReduced Rate Goods
GB-EXEMPT ExemptExempt GoodsBR-SERVICES Services (ISS)Standard Services

The UK’s four mirror its four VAT treatments one-for-one. Brazil’s separate goods from services (services attract ISS, not ICMS) and call out manufactured goods (which attract IPI) — the profile is how a product gets steered onto the right set of taxes.

Guardrails & setup

  • Code is uppercase, no spaces — it’s the key seeding matches on. The two enforcing messages, verbatim: “Tax Profile Code cannot contain spaces. Use hyphens as separators (e.g., CA-STD-GOODS, BR-STD-GOODS, US-TAXABLE).” and “Tax Profile Code must be in UPPER CASE (e.g., CA-STD-GOODS, BR-STD-GOODS). Please correct the value entered.”
  • Category is required — every profile must declare its treatment kind.
  • Deactivate rather than delete. An inactive profile drops out of matching while past documents keep their context — the same discipline as everywhere else in the rulebook.
  • Seeded per country. The Tax Seeding Wizard creates the country’s standard profiles; you link products to them via fiscal profiles, or use the default-tax flag for simple cases.
  • Keep the set small. Profiles are treatments, not product categories — a country rarely needs more than a handful. If two profiles always match the same rules, they should be one profile.

Where to go next

  1. Party Tax Profiles — the party-side classification.
  2. Product Fiscal Profiles — how products carry a tax profile.
  3. Tax Rules — rules that match on tax profile.
  4. How Tax Calculates on a Document — profiles used during calculation.

Frequently asked questions

Tax Profile = the product (what’s being sold). Party Tax Profile = the business (who’s trading). A rule can use both — e.g. “standard goods (tax profile) sold to an end consumer (party profile).”

No. For multi-rate or multi-country setups, yes — classify each product via a fiscal profile. For simple single-rate setups (typical UK), skip it: set the product’s Apply Default Tax flag and use a catch-all rule. See Product Fiscal Profiles.

Through its Product Fiscal Profile — a junction record that ties a product to a Tax Profile, scoped by country and carrying classification codes (UK: none; India: HSN; Brazil: NCM). A line can also override the profile directly.

Was this article helpful?