If your company issues invoices through Protheus ERP, there is a date you need on your radar right now: June 30, 2026 — the planned support expiration for release 12.1.2410. And that is only the tip of a much larger shift: Brazil's Tax Reform, which entered its transition phase in January 2026 and is fundamentally redesigning how Protheus calculates taxes.
The good news: 2026 is, by law, an informational year — meaning there is still time to adapt safely and methodically. The bad news: most companies are discovering too late that compliance is not a simple "click to update." This guide explains what changes, which deadlines cannot be ignored, and the practical checklist to keep your Protheus running without disruption.
What Changes in Protheus with the Tax Reform
Brazil's Tax Reform replaces five taxes with a Dual VAT model. In practice: PIS and Cofins (and IPI for most operations) are replaced by CBS — the Contribution on Goods and Services, a federal-level tax. Meanwhile, ICMS (state) and ISS (municipal) are replaced by IBS — the Tax on Goods and Services.
Since January 1, 2026, most companies must already highlight IBS and CBS on electronic tax documents (NF-e and NFC-e — Brazil's electronic invoice standards). The critical point is that this highlight is not optional: new mandatory fields appeared in the fiscal document layout, and an outdated ERP simply cannot generate them correctly.
In other words: 2026 is the year to get your house in order at low financial risk. Companies that reach 2027 with misaligned systems will be paying taxes on a misconfigured base — and that error will cost real money.
Why TES Is No Longer Sufficient
For years, tax calculation in Protheus revolved around the TES (Tipo de Entrada e Saída — Entry and Exit Type). The problem is that TES logic was designed for the old fiscal model — and the Reform introduces new principles, such as full non-cumulativity and destination-based taxation, that TES cannot represent on its own.
This is why TOTVS introduced the Tax Configurator (routine FISA170, also known as CFGTRIB) as the new fiscal calculation engine in Protheus. It centralizes rules, enables validity control, and gives the tax department greater autonomy to configure each calculation component individually.
Migration from TES to the Tax Configurator is not automatic. Each operation must be manually reviewed and configured — and that is precisely where the project's complexity lies.
For mid-size and large companies with many branches, high invoice volumes, and fiscal exceptions, this means treating the configuration register as a compliance asset, not a data-entry task. Errors in CFOP, CST, NCM, and tax rates are the primary causes of NF-e rejection.
The Protheus Deadlines Your Company Cannot Miss
The transition calendar combines fiscal deadlines (from legislation) with technical deadlines (from Protheus release cycles). The most important milestones are:
- June 30, 2026: planned support expiration for release 12.1.2410. After this date, the version will no longer receive critical fixes, making migration to 12.1.2510 a priority.
- October 2026: consolidation of the Tax Configurator as the main calculation engine, with the arrival of release 12.1.2610.
- January 2027: effective CBS collection begins, replacing PIS and Cofins.
- 2029 to 2033: gradual IBS transition, with full ICMS and ISS phase-out planned by 2033.
If your company does not yet know which release it is running, that is the first diagnostic to perform. Contact Vanquish Code — the initial assessment is free.
cClassTrib and the New Fiscal Classification Triad
One of the most concrete day-to-day changes is the cClassTrib (Tax Classification Code). With the Reform, correct document classification now requires a triad: the correlation between the NCM code (Brazil's product classification), the IBS/CBS CST, and the cClassTrib.
In Protheus, this management is centralized in the Tax Configurator. Importing the official table requires attention to technical details:
- The environment must be on version 12.1.2410 or higher, with an updated data dictionary (running UPDDISTR) so the new IBS/CBS tables are available.
- Protheus imports the file in .CSV format with exact column headers — any discrepancy blocks the import.
- Incorrect classification causes NF-e transmission rejections and distorts the calculation of new taxes.
It is meticulous work, with little margin for error. TOTVS has been continuously publishing Technical Notes (such as the NT 2025.002 series) with ongoing adjustments to NF-e and NFC-e layouts.
Checklist: What to Do Now in Your Protheus
Here is a practical sequence of what your company should address in 2026, while financial risk is low:
- Assess your current version: identify the release in use and how far it is from 12.1.2410 / 12.1.2510.
- Plan the upgrade: include customization review (ADVPL/TL++), regression testing, and planned rollback — without breaking existing integrations.
- Update the data dictionary: confirm UPDDISTR has run and IBS/CBS tables are available.
- Map your current TES entries: understand what each one does before migrating logic to the Tax Configurator.
- Configure the Tax Configurator and cClassTrib: set up the NCM × CST × cClassTrib correlation reflecting the reality of each operation.
- Validate infrastructure and database: invoice volume, performance, and environment stability are all part of the equation.
- Train fiscal, accounting, and IT teams: the new logic only generates safety when teams can operate and validate results independently.
- Test thoroughly: use 2026 as the validation environment the law provides, before effective collection begins in 2027.
How Vanquish Code Handles Your Protheus Compliance
Adapting to the Tax Reform involves two fronts that typically end up in separate hands: the technical (version upgrade, database, customizations) and the fiscal (Tax Configurator, cClassTrib, parametrization). When split across vendors, the client becomes the integration point — and bears the risk.
Vanquish Code is a full-service IT company that brings together, in the same team, expertise in Protheus ERP, specialized DBA services, and Agentic AI solutions. Our approach to tax reform compliance:
- Free environment assessment: we evaluate your version, customizations, data quality, and database health before any proposal.
- Safe upgrade plan: migration to the appropriate release with regression testing and planned rollback, without disrupting operations.
- Tax Configurator setup: TES migration, cClassTrib import and per-operation validation.
- DBA and performance: database tuning to handle the fiscal volume without becoming a bottleneck.
- Team training: fiscal, accounting, and IT enablement to operate the new model with confidence.
Conclusion: 2026 Is the Year to Get It Right — With Time to Spare
The Brazil Tax Reform in Protheus ERP is not a change you can solve the night before the deadline. Between the 12.1.2410 release expiration, the TES-to-Tax-Configurator migration, and the cClassTrib configuration, the work is simultaneously technical and fiscal — and it requires planning.
The calendar, however, favors those who act now: 2026 is an informational year with low financial risk, ideal for full validation before effective collection in 2027. Vanquish Code is ready to lead this process end-to-end — from the free diagnostic to complete fiscal validation.