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 / Party Tax Profiles

Party Tax Profiles

A Party Tax Profile classifies a business for tax purposes — is this a VAT-registered company, an end consumer, a tax-exempt body, a Brazilian Lucro Real firm? It answers the “who” in a transaction, for both sides: the seller (you) and the buyer (your customer or vendor).

Keep it separate in your mind from a Tax Profile, which classifies the product (the “what”). They’re two independent dimensions on a tax rule — because who is trading and what they’re trading are genuinely different questions. A standard product sold to an exempt charity is taxed differently from the same product sold to an ordinary business.

Getting there. Open the App Launcher (the grid icon at the top-left of any page) → REDA Financials Admin → the Party Tax Profiles tab. In practice the Tax Seeding Wizard creates a country's standard profiles; open the tab to review or maintain one, then assign it on each customer/vendor Account and on your Entity.
Access you'll need. Setting up and maintaining party 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.
Why the party changes the tax. A VAT-registered business can reclaim input tax; an end consumer can’t. An exempt government body pays none. And in Brazil the seller’s regime changes the rates outright — a Lucro Real firm and a Lucro Presumido firm selling the same goods pay different PIS and COFINS. The party profile is how the engine knows.

Where it’s assigned — the two parties

A party profile isn’t set on the invoice — it lives on the business records, and the engine reads both ends:

RecordTax fields you setRole in the engine
Entity (your company)Party Tax Profile, Tax JurisdictionThe seller profile & origin
Account (customer / vendor)Party Tax Profile, Tax JurisdictionThe buyer profile & destination

So you assign a profile once per customer and once per entity. From then on, every invoice between them carries those classifications automatically — no per-invoice choice, no chance to forget.

The fields — with UK & Brazil values

Every field, with a UK profile (VAT-registered business) beside a Brazil profile (Lucro Real ICMS contributor):

FieldTypeRequiredWhat it’s for🇬🇧 UK Registered🇧🇷 Brazil Lucro Real
CodeText · External IDYesMatch/seed key (COUNTRY-TYPE-REGIME)GB-VAT-REGBR-LR-CONTRIB
Taxpayer TypePicklistYesRegistered Business · Unregistered · End Consumer · Government · Non-Profit · Foreign EntityRegistered BusinessRegistered Business
Tax RegimePicklistNoStandard · SME · Lucro Real · Lucro Presumido · Simples Nacional · Composition · Flat Rate · OtherStandardLucro Real
Is Tax ExemptCheckboxNoFully exempt from taxNoNo
Is State Tax ContributorCheckboxNoRegistered collector of state tax (Brazil ICMS)NoYes
Exemption BasisTextIf exemptCertificate / legal basis for exemption——
Description / NotesTextNoWhen to assign this profile……
Is ActiveCheckboxNoOff → can’t be assigned to new recordsYesYes

How the engine uses the profiles

A Tax Rule can target a party profile on either side, and most rules leave them blank (= “any party”). When set, the engine matches:

Rule dimensionMatched againstUse
Party Tax Profile (Buyer)The customer/vendor Account’s profile“Only for end consumers,” “only for exempt bodies”
Party Tax Profile (Seller)Your Entity’s profile“Only when we sell as X”
Seller RegimeThe Entity profile’s Tax Regime valueThe Brazil PIS/COFINS rate split
Buyer Contributor ScopeThe Account profile’s Is State Tax Contributor checkboxBrazil DIFAL/FCP fire only for non-contributor (consumer) buyers
In practice: the Brazil regime split. Brazil ships two PIS rules — one for Lucro Real (1.65%, non-cumulative, recoverable) and one for Lucro Presumido (0.65%, cumulative, not recoverable). Each rule carries a Seller Regime condition. When your entity’s party profile is BR-LR-CONTRIB (Lucro Real), only the 1.65% rule matches; switch the entity to a Lucro Presumido profile and the 0.65% rule takes over instead. Same product, same customer — the seller’s profile changes the tax. (This pairs with the two PIS Tax Types and their recoverability flags.)

Real data: UK and Brazil profiles

🇬🇧 United Kingdom — 3 profiles

CodeNameTaxpayer TypeRegime
GB-VAT-REGVAT Registered BusinessRegistered BusinessStandard
GB-VAT-FRSFlat Rate SchemeRegistered BusinessFlat Rate Scheme
GB-VAT-UNREGUnregistered / Below ThresholdEnd ConsumerStandard

🇧🇷 Brazil — 5 profiles

CodeNameRegimeICMS Contributor?
BR-LR-CONTRIBLucro Real (ICMS Contributor)Lucro RealYes
BR-LP-CONTRIBLucro Presumido (ICMS Contributor)Lucro PresumidoYes
BR-SN-CONTRIBSimples NacionalSimples NacionalYes
BR-EXEMPTTax Exempt EntityOtherNo
BR-CONSUMEREnd Consumer (Non-Contributor)OtherNo — this is what makes DIFAL/FCP fire

The contrast is the point: the UK distinguishes parties mostly by registration status (registered, flat-rate, unregistered), while Brazil distinguishes them by tax regime, because the regime drives the rates.

Guardrails & setup

  • Code is uppercase, no spaces — external ID, two validation rules enforce it.
  • Exemption Basis is required when a profile is exempt — you must record the certificate or legal basis, so the exemption is defensible in an audit.
  • Assign on the Account and the Entity. Set each customer/vendor’s Party Tax Profile and Tax Jurisdiction; set your entity’s once. The engine does the rest.
  • Seeded per country. The Tax Seeding Wizard creates the country’s standard profiles; you assign them to your accounts.

Where to go next

  1. Tax Profiles — the product-side classification counterpart.
  2. Product Fiscal Profiles — how products link into the tax system.
  3. Tax Rules — how rules match on party classification.
  4. How Tax Calculates on a Document — party profiles in a live calculation.
  5. Sales Invoice Tax — party profiles shaping invoice tax.

Frequently asked questions

A Party Tax Profile classifies the business (registered, exempt, Lucro Real…). A Tax Profile classifies the product (standard-rated, zero-rated, exempt). They’re separate dimensions, and a rule can use both at once — e.g. “standard goods sold to an end consumer.”

On the customer’s Account — the Party Tax Profile and Tax Jurisdiction fields. Your own company’s profile goes on the Entity. The engine reads the entity (seller) and the account (buyer) on every invoice.

Through the regime. In Brazil, rules carry a Seller Regime condition; your entity’s profile sets the regime (Lucro Real, Lucro Presumido, Simples), so only the rules for that regime fire. It’s why a Lucro Real firm and a Lucro Presumido firm pay different PIS/COFINS on identical sales.

It marks a party as a registered collector of state-level tax — in Brazil, an ICMS contributor. It distinguishes businesses that participate in the ICMS chain from end consumers and non-contributors, which affects how interstate tax (and DIFAL) is treated.

Was this article helpful?