What's the difference between issuing a test NF-e in homologation vs. production?

In homologation (tpAmb = 2), the invoice has no fiscal effect and serves to validate the XML risk-free. The logic: what SEFAZ accepts in homologation tends to be accepted in production, and what it rejects you fix before affecting real operations.

When does the NF-e with IBS/CBS become mandatory?

Per NT 2025.002, it is expected to be mandatory in homologation on 07/01/2026 and in production on 08/03/2026 (Regular Regime, CRT 3); for Simples Nacional and MEI, production is expected on 01/04/2027. That is why the comfortable test window is now.

The invoice was authorized in homologation. Is everything fine?

Not necessarily. Authorization is not proof of correct calculation, especially with relaxed validations in 2026. Open the XML and check the UB group: subgroups present, CST and cClassTrib consistent, values matching what you parameterized.

What do I need to update in Protheus to issue the test NF-e?

Apply the recent package and nfesefaz, reconcile any customizations of that source, be on a compatible release, and have the Tax Configurator with rules and cClassTrib set up. Vanquish Code checks these prerequisites in the free diagnosis.

Test NF-e for IBS/CBS in Protheus: the Dress Rehearsal Before Go-Live

Every fiscal system switchover has a moment of truth — and with the reform, it has a fixed date. Before IBS and CBS become mandatory, there's a precious window to fail for free: the homologation environment. That's where the test NF-e acts as your dress rehearsal, surfacing problems while they still cost nothing.

In this practical guide, you'll see how to issue a test NF-e with IBS/CBS from Protheus, what to really check in the XML, and which scenarios can't be left out — to reach go-live without surprises.

Why the Test NF-e Is Non-Negotiable

The homologation logic is simple and powerful: what SEFAZ accepts in homologation, it tends to accept in production. And what it rejects there, you fix before affecting real operations. Skipping this step bets your billing on a single submission.

The "let's go straight to production" risk is concrete: if Protheus doesn't generate the fields correctly, the invoice is rejected without warning. In production that means a customer waiting, shipping halted, and the team scrambling with operations frozen.

🎯 The test NF-e turns a production risk into a homologation lesson. It's the difference between finding the problem at the rehearsal or at the premiere.

The Test Window Has a Deadline

Under Technical Note 2025.002, the IBS/CBS mandatory calendar for the NF-e is set — and it defines your rehearsal time:

07/01/2026 — mandatory in the homologation environment
08/03/2026 — mandatory in production (Regular Regime issuers, CRT 3)
09/01/2026 — returns must reference the origin document
01/04/2027 — mandatory in production for Simples Nacional and MEI

In practice: the optional phase is your test field. The earlier you issue and validate, the more time you'll have to fix parameterization — instead of doing it under deadline pressure.

Preparing Protheus to Issue the Test NF-e

Updated package and nfesefaz: apply the recent version covering the IBS/CBS fields. If your nfesefaz is customized, reconcile the customizations before validating in a test base.
Compatible release and a parameterized Tax Configurator — with rules and the cClassTrib linked to products.
Certificate and environment pointed to homologation.

Step by Step: Issuing the Test NF-e in Homologation

Point to the homologation environment. Set issuance to tpAmb = 2. The invoice has no fiscal effect and carries the homologation watermark — exactly what you want here.
Select representative items. Pick products covering the different tax behaviors of your catalog, not just the simplest one.
Issue and transmit. Generate the NF-e and transmit to SEFAZ in homologation. Use Protheus's syntactic validation and NT 2025.002 as a checklist of required fields.
Read the XML — don't stop at authorization. Open the XML and check the content (next section). Authorization is not proof of correct calculation.

Issuing is half the test. The other half — what separates the professional from the hasty — is opening the XML and checking, field by field, whether the invoice says what it should.

How to Read the XML: the UB Group

IBS, CBS and Selective Tax data live in the UB group (det/imposto/IBSCBS, or gIBSCBS), which holds several subgroups. When validating the test NF-e, check:

Presence of the expected subgroups for the operation (including the regular taxation group when the cClassTrib requires it — which avoids rejection 1065).
Consistency between CST and cClassTrib — most rejections come from this combination.
Values that make sense — check that bases and rates match what you parameterized for testing. That judgment is a business one: you know your operation better than any system.

The Scenarios You Need to Test

A single invoice "that passed" doesn't mean a homologated environment. Cover the scenarios that represent your real billing:

Regular, reduced and single-phase operations;
Suspension, exemption and deferral;
Returns and interstate operations;
The most-used CFOPs, with the new taxes.

📋 For the full view of what to validate beyond issuance (CFOP, accounting integration, ECD and cash flow), pair this guide with our fiscal homologation checklist before go-live.

How Vanquish Code Runs Your Tests

Vanquish Code is a full-service IT company specialized in Protheus ERP, with DBA and Agentic AI under one roof. In the IBS/CBS test round:

We prepare the environment — package, nfesefaz, release and Configurator.
We issue per scenario in homologation, covering the behaviors of your catalog.
We validate the XML with you — UB group, CST, cClassTrib and values.
We fix parameterization and re-issue until the environment is ready for go-live.

Conclusion: Rehearse Now, Premiere Calmly

The IBS/CBS test NF-e is the dress rehearsal the reform requires before the premiere. Issuing in homologation, reading the XML's UB group and covering real scenarios is what turns the mandate into a non-event — instead of a production crisis. And the best time is while optionality still exists.

Vanquish Code runs this test round end to end. Start with a free diagnosis and reach go-live with the confidence of someone who already rehearsed.