NFS-e IBS/CBS: how to check and test the group

A Nota Fiscal de Serviços eletrônica (NFS-e), Brazil's electronic service invoice, can be received without the group for Imposto sobre Bens e Serviços (IBS) and Contribuição sobre Bens e Serviços (CBS) and still not prove tax compliance. Ato Conjunto RFB/CGIBS nº 7, de 11/11/2026 set 01/03/2027 for part of the ISS (Imposto sobre Serviços) cases on software under Simples Nacional.
Nota Técnica 009 (NT 009), the document specifying technical layout changes, had releases 1 to 3 projected for official production on 01/12/2026 in guidance issued on 29/10/2026 by the Comitê Gestor da NFS-e (CGNFS-e). A release is the version in which each set of changes is made available.1 For an NFS-e with IBS/CBS, the tax team confirms the classification and requirements, while the integration maps the data before transmission. According to the same guidance, the document "will not suffer technical rejection for this specific reason" if the group is not reported in the Ambiente de Dados Nacional (ADN), the national data environment. That does not prove compliance or waive a legal obligation. The 01/12/2026 date is technical, not a universal legal deadline.
For ISVs (Independent Software Vendors, software companies that sell their products to other businesses), the distinction affects buyer records and the contract between systems. In guidance published on 29 October 2026, CGNFS-e described technical receipt of the group and its completion requirements.1 The ADN configuration and the result of each submission need to be checked. The safer course is to decide which information to gather for each operation, rather than treat technical guidance as a tax answer.
Key facts / Decision matrix: In its guidance of 29/10/2026, CGNFS-e said that if the IBS/CBS group was not reported, the NFS-e "will not suffer technical rejection for this specific reason" in the Ambiente de Dados Nacional (ADN), including for taxpayers already subject to the obligation. Other rejections are possible, and the guidance does not waive the applicable obligation.1 According to CGNFS-e on 29/10/2026, when reporting the IBS/CBS group in the NFS-e, even voluntarily, the taxpayer must complete the codes and classifications required by the technical structure of each field and provide complete buyer or recipient data when the type of operation requires it.1 In its NFS-e news item of 29/10/2026, CGNFS-e projected releases 1 to 3 of Nota Técnica 009 (NT 009), the document specifying technical changes, in official production on 01/12/2026. It said it would publish the formal schedule; the subsequent status was not confirmed.1 In the news item of 29/10/2026, release 1 of NT 009 was in restricted production, a test environment without tax effect.1 The legal obligation to issue the NFS-e and the availability of the layout, the document's technical field structure, are separate matters. Ato nº 4 and Ato nº 7 establish deadlines according to the operation and the issuer's regime.25
What changed in NFS-e IBS/CBS validation?
In its guidance of 29/10/2026, the Comitê Gestor da NFS-e (CGNFS-e) said that an NFS-e without the IBS/CBS group "will not suffer technical rejection for this specific reason" in the Ambiente de Dados Nacional (ADN), including for taxpayers already subject to the obligation. Receipt does not prove compliance with the applicable legal obligation.1
The ADN is the national environment through which NFS-e documents circulate, and it is where the system checks whether the IBS/CBS group was reported and whether the required codes are filled in. In its guidance of 29 October 2026, the committee included taxpayers already subject to Ato Conjunto RFB/CGIBS nº 4, without guaranteeing the result of each submission.1 Ato Conjunto RFB/CGIBS nº 4, de 30 de julho de 2026, art. 1º, III, d, as amended by Ato nº 7, de 11 de novembro de 2026, provides for issuance for taxable events from 01/10/2026 for ISS services on the list in LC nº 116/2003 outside subparagraphs a, b and c.6 For taxpayers opting for Simples Nacional, art. 1º, § 1º, as amended by Ato nº 7, sets 01/01/2027 for that case.5 Classification depends on the operation.
The same company can have sales subject to the obligation and sales outside its scope in the same month. The product record needs to identify the type of operation before the fields are defined.
Reporting the group requires data work. When an obligation applies, the tax team or an independent adviser should confirm the classification and requirements before issuance; the technical guidance does not resolve that analysis. When completion is not yet mandatory, the team can consider completing the group voluntarily. In both cases, the taxpayer must report all corresponding codes and classifications required by the technical structure of each field and provide complete buyer or recipient data when the type of operation requires it.1 If information is missing, an internal control can identify its source and return the sale to the team responsible for correction.
This distinction belongs in the integration design. A product decision to show or hide fields does not replace the tax decision for the operation. System validation must reflect the technical requirements valid for the deployed version. The two decisions need to be coordinated before submission.
Which codes and buyer data belong in the group?
According to CGNFS-e on 29/10/2026, when the IBS/CBS group is reported in the NFS-e, all corresponding codes and classifications required by the technical structure of each field must be completed, and complete buyer or recipient data must be provided when the type of operation requires it.1 Testing the applicable requirements guarantees neither acceptance nor tax compliance.4
The condition changes by operation. A software sale that reports the IBS/CBS group in the NFS-e needs the codes and classifications of the technical structure in each field, and the requirement for complete buyer data depends on the type of operation described in the guidance of 29/10/2026. Outside that scope, the same data obligation is not inherited automatically. Whoever maintains the records needs to receive the classification from tax treatment before assembling the document, because the integration does not decide classification. The official updates and deployments page brings together documentation and environment changes and should be read alongside the layout of the version actually deployed. The recommendation is to assign internal responsibility for the accuracy of the records and their preservation until the document is assembled, because the technical source does not assign that responsibility to a specific role. Recording that decision avoids rework when the layout changes.
The official updates and deployments page helps locate documentation and environment changes.4 It should be read alongside the layout for the version actually in use. A change announced for testing should not be presented as a rule already deployed in official production. Likewise, the existence of a field in the layout does not establish, without the applicable condition, that it is required for every operation.
Buyer records deserve the same precision. When an operation requires complete recipient information, the integration needs to receive it in time for issuance and retain it until the NFS-e is assembled. This requirement does not make every buyer detail mandatory for every sale. Product and tax teams should agree on a collection rule by type of operation, with an explanation for the sales team and the people maintaining the records.
For sales with an international component, those responsible also need to distinguish the nature of the operation and the data actually required, without automatically transferring rules from one domestic flow to another. The analysis of foreign-trade NFS-e and IBS/CBS for ISVs provides context for that distinction. The applicable layout remains the reference for determining how to complete the fields.
The practical result is a data contract: for each operation, record the source of the information, the condition that makes it necessary, the person responsible for classification and the point at which the integration holds an incomplete submission for review. That hold is a company control, not a claim that the ADN will reject every partially completed group.
What is the impact on checkout, records and integration?
For an NFS-e with IBS/CBS, checkout and records need to supply the integration with the data required for the operation before transmission. According to CGNFS-e guidance of 29/10/2026, classifications are required when the group is reported, and complete buyer data depends on the type of operation.1 Product, engineering and finance should decide together when to interrupt the flow for review.
The impact on the NFS-e with IBS/CBS appears at three points. At checkout, the product team defines which information to request before completing the sale and which can be added later. Collection varies by type of operation. In the records, finance confirms who validates buyer data and how outdated information is corrected, while engineering defines how the data reaches the issuer and how a transmission failure is identified. At transmission, the ADN response indicates what was technically accepted, and the CGNFS-e guidance of 29/10/2026 does not promise automatic rejection for every partial completion of the IBS/CBS group. The table separates the behavior described by CGNFS-e from the decisions that remain with the team; it does not replace layout testing or tax analysis of the operation. Without that division, a technical response can circulate among teams without anyone knowing which data to correct at its source.
| Situation | Technical guidance of 29/10/2026 | Dependence on operation data | Team decision | Legal check |
|---|---|---|---|---|
| IBS/CBS group absent from the NFS-e | On 29/10/2026, CGNFS-e said the NFS-e "will not suffer technical rejection for this specific reason" in the ADN | The tax team checks whether an obligation applies to the operation | Confirm classification and requirements with the tax team or an independent adviser before issuance | Technical receipt does not prove tax compliance |
| IBS/CBS group reported in the NFS-e, subject to checks | In its guidance of 29/10/2026, CGNFS-e requires codes and classifications specified by the technical structure of each field | Complete buyer or recipient data when the type of operation requires it | Under internal policy, transmit and examine the response | Confirm the treatment of the operation |
| IBS/CBS group reported in the NFS-e with missing requirements | The requirements described by CGNFS-e on 29/10/2026 need to be checked; there is a risk of inconsistency | Identify the missing field and condition | Under internal policy, hold for correction and test the response | Review the obligation and classification |
In the third row, holding the submission is an internal control: the team identifies the missing information and returns it to the person responsible for the records or classification. The notice does not provide a single error code for every case.
In third-party distribution, the party responsible for the sale should not assume its own platform will issue the NFS-e. The article on representation and the Cadastro Nacional da Pessoa Jurídica (CNPJ) in the NFS-e helps frame that question before the data contract is defined. The actual arrangement and tax responsibilities must be checked for each operation.
How does the legal deadline differ from NT 009 production?
Ato nº 7, de 11/11/2026 provides for NFS-e issuance for taxable events from 01/03/2027 for ISS services under subitems 1.03, 1.05 and 1.09, including under Simples Nacional.5 On 29/10/2026, CGNFS-e projected 01/12/2026 for releases 1 to 3 of Nota Técnica 009 (NT 009) in official production. These are separate milestones.1
The difference between the legal NFS-e issuance deadline and the technical calendar lies in the instrument. The legal deadline comes from Ato Conjunto RFB/CGIBS nº 4, de 30/07/2026, as amended by Ato nº 7, de 11/11/2026: 01/10/2026 for issuers outside Simples Nacional, for ISS services in LC nº 116/2003 not included in subparagraphs a, b and c of item III; 01/01/2027 for subparagraphs d to h among taxpayers opting for Simples Nacional; and 01/03/2027 under § 1º, II for the other cases in the main provision, also restricted to taxpayers opting for Simples Nacional, as well as for subitems 1.03, 1.05 and 1.09 under III, b. Production of NT 009 runs on a separate calendar, with releases projected for 01/12/2026. A technical milestone for the IBS/CBS group does not change the legal milestone, and a document accepted in the test environment does not prove that an obligation was met. The team should therefore check the date applicable to the operation and, separately, the layout version available in the environment where it issues invoices.
For taxpayers opting for Simples Nacional, Ato nº 7 establishes 01/01/2027 for the cases under subparagraphs d to h of item III of the main provision of art. 1º of Ato nº 4 as amended, and 01/03/2027 for the other cases in that main provision. These milestones do not postpone other issuance obligations.5 According to CGNFS-e guidance of 29/10/2026 for microempresas (ME) and empresas de pequeno porte (EPP) opting for Simples Nacional, NFS-e for reporting periods from 01/11/2026 must be issued through the Emissor Nacional, via its web interface or application programming interface (API). For earlier reporting periods, the guidance describes separate treatment for retroactive issuance in municipalities with their own issuer.7 The tax team needs to confirm the sale's applicable case and the issuer's regime, without applying one date to all software.
The constitutional tax transition and the issuance schedule follow different milestones; the application of LC nº 214/2025 should be checked against updated official text. The current full texts of LC nº 214/2025 and LC nº 116/2003 were not accessed in this review; references to those laws in Ato nº 4 and Ato nº 7 do not replace that check. According to the Câmara dos Deputados comparative table for Emenda Constitucional (EC) nº 132/2023, from February 2024, the constitutional transition gradually replaces ISS with IBS between 2029 and 2032, with ISS extinguished in 2033. That table is not the current consolidated constitutional text, and the tax calendar is separate from the deadlines for issuing tax documents.8
That is the difference between a regulatory calendar and a deployment calendar. A company may need to check its obligation on one date and, separately, adapt its integration to a layout the authority expects to make available on another. Having the new layout in testing does not by itself bring forward or postpone the legal obligation.
According to the notice of 29/10/2026, the layout in official production followed NT 004, plus the tpRetPisConfins domain from NT 007, and already included the structure for IBS/CBS information. On the same date, release 1 of NT 009 was in restricted production, a test environment without tax effect.1 The test notice describes that release.3 In its guidance of 29/10/2026, CGNFS-e projected releases 1 to 3 in official production on 01/12/2026 and said it would publish the formal schedule; its subsequent status was not confirmed in this review. Individual availability dates for releases 2 and 3 were not confirmed in this review.1 A technical forecast is neither a legal obligation nor a completed deployment. Before changing the production integration, the team should follow the notices and confirm the version actually available.
For an analysis of issuance cases, see IBS and CBS on the NFS-e: deadlines for some software services. The decision here is different: which data must be complete when the operation reports the group, regardless of its specific legal deadline.
How can teams prepare the integration and reduce rework?
To prepare the NFS-e IBS/CBS integration, the team can map operations and test requirements before the production date projected by CGNFS-e on 29/10/2026: 01/12/2026 for releases 1 to 3 of NT 009.1 The legal deadline must be checked separately for each case and regime.
The CGNFS-e notice of 29/10/2026 places releases 1 to 3 of Nota Técnica 009, which changes the NFS-e layout and covers the IBS/CBS group, in production by 01/12/2026 and states that release 1 is already available in the restricted-production environment, which serves testing and not valid issuance. The same guidance calls for checking the layout of each environment, because a change published for testing does not count as a production requirement. To turn that plan into an executable task, record for each operation the layout version, the environment used, the synthetic input data, the observed response and the person responsible for the correction. The test set needs to cover three cases of the IBS/CBS group: absent, reported with the applicable data, and missing required information. None of those cases allows the team to presume the server's response: ADN behavior is known only from the actual transmission response, and technical acceptance does not confirm tax classification.
- Inventory operations and responsibilities. Product and finance record the types of sale, the issuer involved and the person responsible for confirming classification. The same platform can participate in different arrangements; each arrangement needs a documented decision.
- Map fields, conditions and sources. Engineering relates fields in the current layout to data available at checkout, in records and in integrated systems. The tax team confirms applicable classifications and when complete buyer information is required. Missing fields go back to the person responsible for their source.
- Separate testing from official production. The team consults documentation for the restricted-production environment and identifies the layout version used in each environment. According to the notice of 29/10, release 1 was in restricted production without tax effect; the team should check the version available now and test both the presence and absence of data without assuming that the result already applies to official production.134
- Review the integration contract. Sender and receiver need to agree on format, record updates and treatment of incomplete fields. The internal control should identify why the flow stopped and who must correct the data, without exposing real buyer information in examples or unnecessary logs.
- Follow the release and responses. Before the change, confirm the notices and available version. Afterwards, examine transmission responses, separate data failures from other failures and send classification questions for tax review. A later documentation change may require another round of tests.
This plan does not determine any company's regime. For users of the Emissor Nacional, the analysis of what ISVs under Simples Nacional should validate adds an operational perspective; the team still needs to check the current conditions of its own case. The review should preserve the link between the tested layout version and the decision recorded by finance.
One design decision is worth making early: where will the operation stop if required data is missing? If the system finds the absence only when assembling the NFS-e, the sale has already passed through stages that will have to return to the records. If the condition is known earlier, product can request the information at the appropriate point and reserve manual review for what remains undefined. This is an organizational measure, not a guarantee of a tax outcome.
Frequently asked questions
CGNFS-e guidance of 29/10/2026 does not make receipt of an NFS-e without the IBS/CBS group proof of tax compliance. If the group is reported, the required codes and classifications must be checked; complete buyer data depends on the type of operation. The legal deadline varies by case and regime, separately from the technical forecast.15
Three confusions cost rework. The first is treating receipt of an NFS-e without the IBS/CBS group as proof of compliance: the guidance of 29/10/2026 rules out rejection for that specific reason, without waiving the obligation or covering other rejection reasons. The second is assuming that reporting part of the group is harmless: when the group is reported, the codes and classifications set out in the technical structure must be completed, and buyer data depends on the type of operation. The third is confusing an internal hold with an ADN rejection, when the hold is the team's own decision. Two separate calendars add to this: the legal milestone of Ato Conjunto RFB/CGIBS nº 4/2026, as amended by Ato nº 7/2026, and the technical forecast of the Nota Técnica 009 releases on 01/12/2026. One does not replace the other.
Can reporting only part of the IBS/CBS group cause an inconsistency?
Yes. On 29/10/2026, CGNFS-e advised that when reporting the IBS/CBS group in the NFS-e, taxpayers should complete the codes and classifications required by each field's technical structure and provide complete buyer or recipient data when the operation requires it. Partial completion can cause inconsistency, without implying automatic rejection in every case.1
Does technical acceptance without the group eliminate a tax obligation?
No. On 29/10/2026, CGNFS-e said an NFS-e without the IBS/CBS group "will not suffer technical rejection for this specific reason" in the Ambiente de Dados Nacional (ADN). The current configuration and result need to be checked. Receipt does not prove tax compliance; the tax team or an independent adviser should confirm the applicable obligation.1
Is buyer data required for every operation?
Not for every operation: under the guidance of 29/10/2026, complete buyer or recipient data must be provided when the type of operation requires it. The specific fields depend on the current technical documentation and the type of sale being analyzed.14
Is the projected NT 009 production date the legal issuance deadline?
No. On 29/10/2026, CGNFS-e projected releases 1 to 3 of NT 009 in official production on 01/12/2026, without establishing that deployment had occurred.1 For the NFS-e, Ato nº 7 provides for issuance for taxable events from 01/03/2027 for ISS services under subitems 1.03, 1.05 and 1.09, including under Simples Nacional.25
What should the team test before changing the integration?
The team should test the NFS-e IBS/CBS group fields, the conditions for buyer data and the handling of missing information in the correct environment. On 29/10/2026, CGNFS-e said release 1 of NT 009 was in restricted production without tax effect. Testing guarantees neither acceptance nor compliance.13
References and further reading
Deadlines vary by case. The CGNFS-e news item of 29 October 2026 records the technical forecast of 01/12/2026 for releases 1 to 3 of NT 009.1 Ato nº 4 and Ato nº 7 allow readers to check the cases and regimes for NFS-e issuance without treating the technical forecast as a universal legal deadline.65
The references cover three families of documents. CGNFS-e news items record the guidance of 29/10/2026 on completing the IBS/CBS group, the technical forecast of 01/12/2026 for releases 1 to 3 of NT 009, release 1 in testing and the Simples Nacional guidance for reporting periods from 01/11/2026. Ato Conjunto RFB/CGIBS nº 4/2026 and Ato Conjunto RFB/CGIBS nº 7/2026 set out the cases and the regime for each milestone: 01/10/2026 for the services in art. 1º, III, d, outside subparagraphs a, b and c and outside Simples Nacional; 01/01/2027 for subparagraphs d to h among taxpayers opting for Simples Nacional; 01/03/2027 under § 1º, II for the other cases in the main provision among taxpayers opting for Simples Nacional, and under III, b for subitems 1.03, 1.05 and 1.09. The comparative table for EC nº 132/2023 describes the transition between 2029 and 2032 and the extinction of ISS in 2033. Check updated documentation before changing the production integration.
1. CGNFS-e: guidance of 29/10/2026
2. CGNFS-e: schedule under Ato nº 7
3. CGNFS-e: release 1 in testing
4. CGNFS-e: updates and deployments
5. Ato Conjunto RFB/CGIBS nº 7/2026
6. Ato Conjunto RFB/CGIBS nº 4/2026
7. CGNFS-e: guidance for Simples Nacional
8. Constitutional comparative table for EC nº 132/2023, Câmara dos Deputados, February 2024
What is the supplier's next step?
For an NFS-e with IBS/CBS, the supplier needs to record who is responsible for issuance, records and tax decisions in each operation. Under CGNFS-e guidance of 29/10/2026, complete buyer data depends on the type of operation.1 Defining the distribution model before integration identifies who must provide or correct each piece of information.
The verification sequence has four steps. First, confirm the NFS-e issuance case under Ato nº 4 as amended by Ato nº 7, identifying the applicable subparagraph and the issuer's regime. Second, identify whether the issuer opts for Simples Nacional, because art. 1º, § 1º sets 01/01/2027 for subparagraphs d to h of item III and 01/03/2027 for the other cases in the main provision. Third, check the deployed layout version and the ADN response for the IBS/CBS group, separating technical acceptance from tax compliance. Fourth, record who corrects each rejected item of data, with a deadline and owner. In parallel, the data contract needs to name who is responsible for issuance, records and classification in each operation, including when the sale goes through a distributor. This record allows the team to respond to an ADN rejection without reopening the entire commercial negotiation.
Nexforce Marketplace offers software distribution and local contracting, with local-currency billing and a tax invoice for the buyer. The supplier can discuss the distribution model with the Nexforce sales team. The supplier's tax team or an independent tax adviser should analyze the operation's classification and obligations. Nexforce Marketplace should not be assumed to validate the IBS/CBS group automatically.

Sell software in Latin Americawith no setup and saving 50%
Distribute your SaaS through the Nexforce platform scaling sales channels in a simple way
Run SimulationRelated articles

Merchant of Record: a continuity plan for ISVs
A roadmap to define billing per cycle and check renewals, payments and tax documents when the responsible party changes.
Read more
IBS and CBS on NFS-e: deadlines for some software services
Joint Act RFB/CGIBS No. 7/2026 changes NFS-e issuance deadlines linked to IBS and CBS for specific cases. This analysis examines platform and software services and separates classification, schedules, and operational steps.
Read more
China recurring billing: how to reconcile with NFS-e
A step-by-step method to review authorization, renewal failures, cancellation and reconciliation of subscriptions billed locally in China, with the Brazilian tax questions that depend on the contract.
Read more