A new point of attention in NFS-e: authorization is no longer synonymous with compliance
After months of widespread flexibility, the mandatory schedule for IBS and CBS in the Electronic Service Invoice (NFS-e) has begun to take more concrete shape for those providing services under the standard regime. The Executive Secretariat of the National Standard NFS-e Management Committee reinforced, based on Joint Act RFB/CGIBS No. 4/2026, a point that often goes unnoticed by tax teams: (cite index="48-10">there is an important difference between the invoice being authorized by the system and the invoice being in compliance with legislation.
What changes on October 1, 2026
(cite index="37-1">The requirement begins on October 1, 2026 for most services subject to the Tax on Services (ISS) and moves forward for specific categories in December. In practice, this means that, starting from that date, most services classified under Complementary Law No. 116/2003 will require the display of IBS and CBS on the national standard NFS-e.
What remains for December 1, 2026
A second batch of operations has a longer deadline. According to the schedule consolidated from the Joint Act, (cite index="38-6">December 1, 2026: Digital platforms (own supplies and intermediations); technology and support services under sub-items 1.03, 1.05, and 1.09; urban/auxiliary transportation services under sub-item 16.01; supplies of intangible goods (outside ICMS/ISS); condominium fees; and leases of movable property or leases/assignments of real estate. As for Simples Nacional taxpayers who choose to display the taxes, (cite index="51-3">the indicated mandatory date is January 1, 2027.
Authorized, but non-compliant: the detail that changes the game
The most relevant point for those working in tax, accounting, and IT is this: until the end of the year, the national system will not block issuance due to missing IBS and CBS fields. But this does not eliminate the obligation. (cite index="46-4">After the applicable mandatory date for each operation, the absence of this information may characterize non-compliance of the tax document, even if the invoice is technically authorized. In other words, the invoice goes through, the system accepts it, but the document remains irregular under the legislation, subject to the rules and possible sanctions of Joint Act RFB/CGIBS No. 4/2026 itself.
It's worth reinforcing that this suspension of rejection should not be confused with exemption. As has been signaled since August, (cite index="50-3,50-4">the flexibility should be understood as a measure to prevent operational blockages during the systems' adaptation period, and not as an exemption from the obligation. For companies and accounting firms, the possibility of issuing the NFS-e without blocking should not be used as a reason to postpone adaptation.
Technical basis: CGNFS-e Technical Notes No. 008 and 009
From the perspective of issuing systems, the technical reference remains the same since the ratification made in August: (cite index="46-9,46-10">Joint Technical Act RFB/CGIBS No. 1/2026 formally ratified CGNFS-e Technical Notes No. 008 and No. 009. The documents establish the specifications and conceptual model necessary for the bookkeeping and recording of information related to IBS and CBS in the national standard NFS-e. Any parameterization of fields, groups, and validation rules for IBS/CBS in the NFS-e must be aligned with these two documents.
Do not confuse with the National Issuer deadline for Simples
A common mistake is mixing up two distinct schedules. The IBS/CBS deadline in NFS-e (October and December for the standard regime, January 2027 for Simples) has no direct relation to the mandatory use of the National Issuer by ME and EPP companies. (cite index="47-4,47-5">Starting November 1, 2026, these companies must issue NFS-e exclusively through the National Issuer, via the Web version or the API. Municipal in-house systems will be prohibited from authorizing these issuances. These are rules that run in parallel, but with different logics and deadlines — and that require separate checklists.
Practical checklist for the coming weeks
For tax, accounting, and IT teams operating an ERP with NFS-e issuance, the recommended roadmap is straightforward. First, map each service provided by its respective sub-item under LC 116/2003 and identify whether it falls into the first phase (October) or the second (December). Second, review the parameterization of the issuing system to ensure that the IBS and CBS fields are being correctly populated starting on the date applicable to each operation, since, as the management committee itself reinforces, (cite index="50-5,50-6">the first step is to identify which schedule scenario each operation falls under. From there, it will be necessary to review the parameterization of the issuing systems and ensure that the fields related to the new taxes are correctly populated starting on the respective date. Third, coordinate with accounting to determine whether the company has joined any compliance program that offers an adjustment period, since (cite index="52-10">the compliance program established by Joint Act RFB/CGIBS No. 5/2026 offers a transition period for companies to complete adjustments without interrupting their operations. Finally, internally document the cutoff date applied to each type of service, for possible proof of good faith before the Tax Authority.
This content is informational and does not replace guidance from your accounting firm, which should assess the specific classification of each service provided by the company. If your team is reviewing the ERP's tax parameterization for the October and December deadlines, talk to Edoo.
NFS-e: An Authorized Invoice Without IBS/CBS Is Not a Compliant Invoice — What Changes in October and December 2026