If your company uses Protheus, there is a quiet change happening inside the ERP that could halt your billing: the legacy TES (Tipos de Entrada e Saída) has been retired as the calculation engine for the new taxes. Taking its place is the Tax Configurator, the FISA170 routine — and migrating to it is not a click, it is a project. Treating it as a technical detail risks invoice rejections, tax inconsistencies, and, in the worst case, penalties.
In this guide you will understand why TES is being phased out, what changes with the Tax Configurator, and — most importantly — how to carry out the TES migration without errors, with a practical step-by-step and the critical failure points that most derail projects.
Why TES Is Being Phased Out
For decades, tax calculation in Protheus revolved around TES (MATA080) and auxiliary routines like Fiscal Exceptions (MATA540) and UFxUF (FISA080). This model was designed for a simpler, more rigid tax landscape. With Brazil's Tax Reform and the arrival of the IVA Dual — IBS, CBS, and the Selective Tax (IS) — the old engine can no longer handle the required complexity.
According to TOTVS, TES does not disappear immediately: it continues to exist in Protheus, but as an integration point between modules. What it loses is its most important role: calculating taxes. That role now belongs to the Tax Configurator.
What Is the Tax Configurator (FISA170)
The Tax Configurator is a routine inside the Fiscal Books module (SIGAFIS) of Protheus, accessible from the Updates menu as the FISA170 routine. According to TOTVS, after updating the ERP it comes already embedded in the module — no separate license is required, only the correct release version and fix packages.
The key difference is flexibility. Instead of locking rules into a rigid master record, the Configurator works with the concept of a Tax ID and organizes everything into two major groups:
- Tax Rules: calculation base, rate, NCM rules, service codes, CST, and exceptions — defining how much and how each tax applies.
- Financial Rules: due dates for payables, retention generation, and financial composition — ensuring that the tax module communicates correctly with finance and accounting.
In practice, this turns Protheus into a true tax rules engine, capable of absorbing legislative changes with far less rework than the old TES.
The Migration Is Not Automatic (and That Is the Critical Point)
This is the detail that most surprises teams: migrating from TES to the Tax Configurator is not an automatic process. There is no "convert everything" button. Each tax operation must be manually reviewed and re-parameterized, reflecting CFOP, CST, NCM, and the new tax classification.
During the transition, Protheus operates in hybrid mode: when a rule exists in the Configurator it takes priority; when it does not, the system falls back to TES logic. This provides breathing room to migrate in stages — but it also hides a trap: it is easy to assume everything is working when in fact part of the operations still rely on TES, which does not correctly calculate the new taxes.
2026 has an informational character for IBS and CBS testing and validation. But this period exists for technical adaptation — not to indefinitely postpone the migration of the fiscal legacy.
Want to understand the full context of the release upgrade that enables all of this? See our guide on Protheus 12.1.2410 → 12.1.2510 upgrade.
Step by Step: How to Migrate from TES Without Errors
This is the roadmap we use to safely guide migrations, from an outdated environment to the Tax Configurator in production:
Update Protheus
Keep the environment on release 12.1.2410 or later (ideally 12.1.2510), ensuring the latest TOTVS fiscal fix packages.
Validate FISA170 access
Confirm the Tax Configurator appears in the Fiscal Books module (SIGAFIS) and that key users have a profile with fiscal permissions. If the option is missing, the update was not properly applied.
Map current tax operations
Inventory all TES in use along with their CFOP, CST, NCM combinations and exception rules before creating any new rule. Migrating without mapping is the root cause of most errors.
Register taxes and Tax Rules
Create the tax IDs and configure calculation base, rate, NCM rules, service codes, and correct CSTs.
Configure Financial Rules
Set up due dates, title generation, and retentions. A misconfigured financial link may be interpreted as a new tax and distort values and obligations.
Run a pilot and validate
Migrate one branch or operation group first, run test billing, and verify values against legislation before expanding.
Expand and monitor
Extend the configuration to all remaining operations and maintain continuous monitoring of TOTVS fiscal updates — tax rules are never static.
The Most Common Migration Errors (and How to Avoid Them)
- Migrating without mapping: skipping the inventory of current operations leads to incomplete rules and invoice rejections during billing.
- Trusting hybrid mode without checking: assuming "it's calculating" when calculations for the new taxes still come from TES.
- Misconfigured Financial Rules: incorrectly configured retentions and payables create discrepancies and impact ancillary obligations.
- Generic NCM and CST: imprecise product and service classification compromises the calculation base and applied rate.
- Skipping UAT: going directly to production without test billing is the fastest path to a penalty.
How Vanquish Code Manages Your Migration
Vanquish Code is a full-service IT company with deep expertise in Protheus ERP, DBA, and Agentic AI solutions. In fiscal migrations, our approach combines Protheus mastery with tax rigor:
- Free environment diagnostic: we assess the release, customizations, and fiscal operations map before any parameterization.
- TES → Configurator mapping: we translate current rules into structured Tax IDs, Tax Rules, and Financial Rules.
- Assisted pilot and UAT: we run test billing and value validation before go-live.
- Ongoing support and monitoring: we track TOTVS fiscal updates so your environment never falls behind.
If your company is also planning to strengthen the infrastructure behind the ERP, learn about our IT Outsourcing solutions.
Conclusion: Migrating Now Reduces Risk, Not Increases Cost
Migrating from TES to the Tax Configurator is not a choice — it is a requirement of Protheus's new fiscal architecture. The difference between companies that will navigate Brazil's Tax Reform smoothly and those that will be firefighting comes down to one word: planning. The sooner the mapping and UAT happen, the lower the risk and cost of the transition.
Vanquish Code is ready to guide this process end-to-end — from a free diagnostic to the Tax Configurator in production, with no invoice rejections and no fiscal surprises.