What does NF-e rejection 1065 mean?

It is the validation "The IBS and CBS Tax Classification provided requires the regular taxation group to be informed". The cClassTrib has ind_gTribRegular = 1, meaning it requires the gIBSCBS/gTribRegular group in the XML — and it was not generated. Without that group, SEFAZ rejects the invoice.

Why did my NF-e hit rejection 1065 if the cClassTrib looks correct?

Because the cClassTrib may be correct, but the rule that generates the regular taxation is missing in Protheus. Without a calculation rule for regular IBS/CBS linked to the item, the gTribRegular group is never populated — and the invoice is rejected even with the right code.

What is the difference between rejection 1065 and 1037?

They are opposites. Rejection 1065 occurs when the cClassTrib requires the regular taxation group but it is absent. Rejection 1037, in one of its variations, occurs when the classification does not allow that group, but it was included anyway. The root is always the consistency between CST, cClassTrib, and the XML groups.

How can I prevent rejection 1065 before go-live?

By correctly linking cClassTrib to products, configuring regular taxation in the Tax Configurator, and issuing test NF-e invoices to verify the gTribRegular group in the XML before production. Vanquish Code conducts this homologation scenario by scenario.

NF-e Rejection 1065 in Protheus: How to Fix the Regular Taxation Error

You submitted the invoice to SEFAZ and received this message: "Rejection 1065 — The IBS and CBS Tax Classification provided requires the regular taxation group to be informed". The invoice was not authorized, billing has stalled, and the clock is ticking. The good news: the cause of rejection 1065 in Protheus is specific and has a direct fix.

In this guide, we explain what rejection 1065 actually means, why it happens in Protheus, and the step-by-step to unblock issuance — plus how to tell it apart from related rejections.

What Is Rejection 1065

The full message reads: "The IBS and CBS Tax Classification provided requires the regular taxation group to be informed [nItem: X]". In plain terms: the cClassTrib used for that item has the indicator ind_gTribRegular = 1, meaning it requires the XML to include the Regular Taxation group (gIBSCBS/gTribRegular). Since that group was not generated, SEFAZ rejects the invoice.

🔎 In short: the classification code you provided "promises" regular taxation, but the XML was generated without that data. Rejection 1065 is SEFAZ enforcing that consistency.

Why This Happens in Protheus

In practice, the cClassTrib may even be correct — the problem is that the rule that generates the regular taxation is missing. The most common scenarios:

Regular taxation not configured: the IBS/CBS regular calculation (with taxes like IBSREG and CBSREG) was not set up in the Tax Configurator for that code.
Generic automatic load: environments that relied solely on the automatic tax load often miss certain scenarios — and the gTribRegular group ends up absent.
Profile or rule unlinked: the item falls into a profile that does not point to the regular taxation rule. This is the direct consequence of a poorly configured cClassTrib link.

Step-by-Step to Resolve Rejection 1065 in Protheus

Confirm the cause in the XML. Verify that the rejected item uses a cClassTrib with ind_gTribRegular = 1 and that the gTribRegular group was indeed not generated.
Configure the IBS/CBS Regular calculation. In the Tax Configurator, set up the Regular Taxation rule for that code — including the regular IBS and CBS taxes (IBSREG, CBSREG) — following TOTVS documentation for the regular calculation.
Link the item profile to the rule. Ensure the product/participant/operation profile for the item points to the rule that generates the Regular Taxation group. See how to organize this in linking cClassTrib to products.
Reissue and validate the XML. Reprocess the invoice and confirm the presence of the gIBSCBS/gTribRegular group with the correct base and values — don't rely on authorization alone.

Fixing rejection 1065 is not just "clearing the error screen". It means ensuring that the fiscal rule behind the cClassTrib exists and generates the group that the legislation requires.

Don't Confuse 1065 with Related Rejections

Several Tax Reform rejections share the same root: the CST + cClassTrib combination being inconsistent with the generated XML. Knowing the differences speeds up diagnosis:

Rejection	What it means
1065	The cClassTrib requires the Regular Taxation group, but it is absent.
1037	In one variation: the classification does not allow the Regular Taxation group, but it was included anyway (the opposite of 1065).
1021	IBS/CBS group informed when it should not be (e.g., CST 410 — immunity/non-incidence).
1024	cClassTrib incompatible with the informed CST.
1115	IBS/CBS group not informed when it is mandatory.

Notice the pattern: nearly all of them point to consistency between CST, cClassTrib, and the XML groups. Resolving rejection 1065 methodically also helps prevent the others.

How to Prevent Rejection 1065 Before Go-Live

Link cClassTrib correctly and segment profiles by tax behavior.
Configure regular taxation for all codes that require it.
Issue test NF-e invoices per scenario and check the XML groups before production — exactly what we recommend in the fiscal homologation checklist.

How Vanquish Code Unblocks Rejection 1065 in Your Protheus

An invoice rejection is an emergency — and emergencies are exactly what Vanquish Code's on-demand support handles. Our approach:

Fast diagnosis of the root cause in the XML and Tax Configurator setup.
Regular Taxation configuration and correct profile and rule linking.
Reissuance and per-scenario validation, verifying the gTribRegular group in the XML.
Hourly or package pricing with SLA — no need to hire a full-time in-house specialist.

Conclusion: Consistency Is Everything

Rejection 1065 is SEFAZ demanding that the XML deliver what the cClassTrib promises. The fix involves configuring regular taxation in the Tax Configurator, linking the rules to the item, and validating the gTribRegular group before reissuing. Resolve it methodically and you'll prevent several related rejections at the same time.

If your invoice is stuck right now, Vanquish Code unblocks it on demand. Start with a free diagnostic of your environment.