In 2026, your Brazilian e-invoice (NF-e) can be authorized even without the IBS and CBS tax breakdown — and that is precisely where the risk hides. The temporary relaxation of technical validations created a false sense of safety: the "green light" of authorization does not mean your fiscal operation is correct. That is why fiscal homologation in Protheus before go-live is no longer a formality — it separates companies that enter Brazil's tax reform compliant from those exposed to penalties.
This article gathers the go-live checklist your team must validate in Protheus before moving the new model to production — from the Tax Configurator to accounting integration. Use it so you never mistake "the system works" for "the company is compliant."
Why an "Authorized Invoice" Is Not the Same as a "Correct Invoice"
Technical Note 2025.002 (RTC) reshaped NF-e and NFC-e layouts, adding new groups, fields and validation rules for IBS, CBS and the Selective Tax. In versions 1.33 and 1.34, the tax authority postponed the rejection rule that required the IBS/CBS fields. In practice, in early 2026 invoices are not rejected for missing these taxes at authorization time.
The mistake is reading this relief as an exemption. It is purely operational: the legal obligation to break down IBS and CBS when due remains fully in force under Complementary Law 214/2025. Moreover, the waiver of collection during the transition is conditioned on fully meeting accessory obligations — which includes the correct tax breakdown. Issuing without it can be deemed non-compliance and expose the company to penalties, even when the authorizer stays silent.
What to Validate in the Tax Configurator
For IBS and CBS scenarios, the TES gives way to the Tax Configurator as the calculation engine. Before homologating, confirm the basics:
- Compatible release: the Configurator requires Protheus release 12.1.2410 or higher with the tax-reform packages applied. See our Protheus version migration guide.
- cClassTrib table imported: the tax classification codes must be loaded via FISA170. We cover it in how to import the cClassTrib table in Protheus.
- Rules by validity period, state (UF) and operation type: validate that each rule responds to the right period and scenario. See our TES-to-Tax-Configurator migration walkthrough.
- Exception scenarios: test inbound and outbound, tax substitution, deferrals, fiscal benefits and interstate operations — not just the standard sale.
Issuing Fiscal Documents in Homologation
- NF-e with IBS and CBS broken down — confirm the amounts and bases match expectations, not just that the invoice was authorized.
- XML compliant with NT 2025.002 — check that the IBS/CBS group tags are present and filled (CST, cClassTrib and values), including in returns.
- CFOP matrix — review each CFOP and map old-to-new correlations, ensuring automatic determination for interstate operations.
- Credits and deferrals — confirm credit is applied per each operation's rule.
Golden rule of homologation: do not trust the homologation environment's authorization as proof of correctness. Check the XML and the values, line by line, in the scenarios that represent your real revenue.
Accounting Integration and Accessory Obligations
- Accounting segregation: map specific accounts for IBS, CBS and IS in Protheus. If the integration does not segregate them, the ECD may be rejected.
- ECD generation with IBS/CBS data: test generation before go-live, not after.
- Protheus ↔ accounting reconciliation: ensure ERP-calculated values match the accounting system.
Cash Flow and Credit: the Test Almost No One Runs
Technical homologation handles compliance. But there is a business test often left out: the financial impact. With credit conditioned on the supplier's confirmed collection — a logic that intensifies with split payment from 2027 — supplier selection and working capital may shift. Before go-live, use the Configurator to simulate margin and pricing scenarios.
Governance: Versioning, Evidence and Rollback
- Rule versioning and change control, to trace what changed and when.
- Homologation criteria and evidence — keep XMLs and test reports as compliance proof for audits.
- Rollback plan — define how to revert if something critical fails right after go-live.
- Fiscal and IT team training — daily operation cannot depend on a single person.
The Go-Live Checklist (Actionable Summary)
- Protheus on release 12.1.2410+ with reform packages applied
- cClassTrib table imported and validated (FISA170)
- Tax Configurator rules by validity, UF and operation type
- Exception scenarios tested (tax substitution, deferral, benefits, interstate, returns)
- NF-e/NFC-e issued in homologation with IBS and CBS checked by value
- XML compliant with NT 2025.002 (CST, cClassTrib and values present)
- CFOP matrix reviewed and correlated
- Credits and deferrals applied correctly
- IBS, CBS and IS accounts segregated; ECD generated in test
- Protheus ↔ accounting reconciliation validated
- Margin and cash-flow simulation completed
- Rules versioned, evidence stored and rollback plan defined
- Fiscal and IT teams trained
How Vanquish Code Runs Your Protheus Fiscal Homologation
Vanquish Code is a full-service IT company with expertise in Protheus ERP, databases and Agentic AI. For fiscal homologation, we combine deep Protheus knowledge with project governance: free diagnosis, test cycles by validity and scenario, accounting-integration validation, and database performance for go-live, backed by our Protheus support team.
Conclusion: Homologate the Content, Not Just the Authorization
The 2026 window is the best — perhaps the last — comfortable time to fail in homologation rather than in production. Treating Protheus fiscal homologation with method, evidence and financial-impact simulation is what turns go-live into a non-event. Vanquish Code runs this end to end, from free diagnosis to switch-over.