TenkaTenka
Sign in

Tenka Help Center › Platform › Price per outcome

Price per outcome

Turns the Outcome Certificate (D5) into a commercial offer of "% of what was recovered/saved". The golden rule: the offer is priced ACTUARIALLY — the expected cost of delivering the outcome comes from FREQUENCY × SEVERITY of the tenant's portfolio, never a guess (selling an outcome without pricing …

🕒 Updated on Sep 13, 2026📖 ~4 min read

What you find on this screen

A portrait of the screen, read from the screen itself — it changes when the screen changes.

Available actions

EditSave

The list shows

TenantCountryCurrencyLocaleTime zoneDocumentTaxActions

Form fields

País
Moeda
Locale
Formato Documento
Dhcadastro

Start here

Um núcleo, muitos países
Each tenant has a country, and the country decides the rest: currency, date and number format (locale), document type and — most importantly — whether Brazilian tax features are turned on. The platform core is agnostic; Brazil is a plug-in, not a premise.
Which question this screen answers
Super admin screen to localize each account (tenant): country, currency and locale. The country is what decouples Brazilian tax features — when the account is from another country (Mexico in v1), the NF-e, SPED, eSocial, Reinf and similar screens become inaccessible, and the platform runs on the agnostic core. Accounts without their own localization behave as Brazil (LOCALIZACAO.PAIS_PADRAO parameter).

How to

The "inherited" label
An account without its own localization follows the platform's LOCALIZACAO.PAIS_PADRAO parameter and appears with the "inherited" label. It only gets its own localization when someone edits it — which is right for most: less explicit configuration, less to forget.
Edit
The dialog asks for country, currency and locale. When the country is changed, currency and locale adjust to that country's default — review before saving if the customer uses an unusual combination.

Rules

O país liga e desliga o fiscal brasileiro
Brazil tenant = NF-e, SPED, eSocial, Reinf and Brazilian tax regime turned on, as always. Tenant from another country (Mexico in v1) = those screens are decoupled and no longer open for the account. It is not a profile permission: it is the product design per country.
Trocar o país de uma conta em uso é decisão grande
The change takes effect on the account's next navigation: tax screens disappear (or appear), and currency/locale start formatting everything. Check the currency in ISO 4217 (BRL, MXN...) and the locale — decimal places and date format come from there, and a wrong locale opens the wrong spreadsheet in Excel without giving any error.
The account’s time zone rules its "today"
Since 1.77.0 the system clock is the account's, not the server's: the transaction period, the "today" of lists, the day's due date and the time routines are triggered all use the time zone chosen here. An account without its own time zone inherits the country's (catalog of supported countries); with no cataloged country, the platform default in Parameters applies (LOCALIZACAO.FUSO_PADRAO).
Converter a base para data com fuso é GMUD, não deploy
Storing the time zone alongside each date (timestamptz) is a type change in hundreds of tables and therefore does not happen on its own in a deploy. The converter is already installed in the database and idle; it is triggered by BMCode, within an agreed window. Meanwhile the platform works normally with the account's time zone applied in the calculation.
Moeda funcional: obrigatória, e é ela que aparece nos números
The functional currency is the currency in which the account operates — and since 1.77.0 it is mandatory. It determines the symbol and decimal places of every value displayed, exported or printed: the yen and the Chilean peso have no cents, and the system respects that. Accounts that did not yet have a currency received their country's; changing it here takes effect immediately.

Frequently asked questions

Que pergunta esta tela responde
Which country is each account from — and are Brazilian tax features on or decoupled? The super admin screen sets, per tenant, the country, currency and locale. The country is what turns off Brazilian tax features: in an account from another country (Mexico in v1), the NF-e, SPED, eSocial and Reinf screens become inaccessible and the platform runs on the agnostic core. An account without its own localization behaves as Brazil through the LOCALIZACAO.PAIS_PADRAO parameter — that is what the "inherited" label in the list indicates.
Troquei o fuso e nada mudou na tela. Por quê?
The time zone is cached per company so the database is not queried on every date calculation. Saving here already clears that cache; if the screen still shows the old value, reload the page. Dates ALREADY STORED do not move: they continue to represent the instant they were stored.
Trocar a moeda funcional converte os valores já lançados?
No. The numbers remain exactly as they are — what changes is how they are presented and in which currency the system says they are. Conversion between currencies is something else and goes through the exchange rate (exchange service), which blocks when there is no rate for the day instead of assuming 1.
Was this article helpful?

In the same module: Platform1

Tenka Academy

Step-by-step learning paths for your industry, inside the platform.

Explore the Academy