NFS-e Nacional: How to Integrate into Your System by November

The new NFS-e Nacional deadline and what changes for your company

Knowing how to integrate NFS-e Nacional into my system has become a technical and operational priority for service providers and developers. CGSN Resolution No. 191/2026 established the official postponement of the mandatory deadline from September 1st to November 1st, 2026, for micro-enterprises (ME) and small businesses (EPP) opting for Simples Nacional that provide services subject to ISS. Individual Micro-entrepreneurs (MEIs) have already been required to use the standard since September 1st, 2023.

This change aims to provide breathing room for technological adaptation, but the calendar requires attention. Between November 1st and December 31st, 2026, a transition period will be in effect: companies will start issuing through the national system, but will continue to follow Simples Nacional tax rules, without immediate application of the new IBS and CBS taxes. Collection for IBS and CBS in Simples will become effective from January 1st, 2027, integrating the scenario of Tax Reform in systems in 2026.

Adopting the standard simplifies the routine for those who issue invoices to different municipalities, as it unifies the tax model. Adherence already reaches about 3,000 municipalities, including 19 capitals, which represents approximately 80% of the national volume of service invoices.

Key points

• Final deadline: November 1st, 2026, for MEs and EPPs of Simples Nacional.
• Transition period: from November 1st to December 31st, 2026 (IBS/CBS are valid for Simples from January 1st, 2027).
• Issuance modalities: Web, mobile application, and integration via REST API.
• API technical requirements: TLS with mTLS, ICP-Brasil certificate (A1/A3), XML 1.0 in UTF-8 signed in XMLDSIG, and payload in GZip with Base64.

Issuance methods: website, application, or API integration?

The issuance of invoices in the national standard can only be carried out through the Emissor Nacional provided by the federal government, in three distinct modalities. The choice depends directly on the company's sales volume and the need for automation of operational processes.

The first modality is the web application available at the official address nfse.gov.br/EmissorNacional. The second option is the official mobile application. Both are free and suitable for low volumes of daily invoices, but require manual entry for each transaction. The third modality is the direct integration of your ERP or checkout via Web API, recommended for companies that need to gain scale and automation.

To help with decision-making, check out the comparison between the options in the complete overview of the national standard:

Technical requirements for integrating the NFS-e Nacional API

Integrating the issuer directly into your software requires complying with rigorous security and formatting specifications stipulated by the official documentation. The communication channel is built on a REST architecture with data sent and received in JSON in the main requests.

To establish a secure connection with the servers, it is mandatory to use the TLS protocol with mutual authentication (mTLS). This means that the application must present a valid ICP-Brasil digital certificate (A1 or A3 types) linked to the system's technical responsible during the connection handshake.

The data flow of the tax document itself requires a specific structure. The service payload contains XML 1.0 encoded in UTF-8 and digitally signed in the XMLDSIG standard. Furthermore, before sending via the API, the signed XML must be compressed in GZip format and converted into a Base64 string.

// Exemplo conceitual do fluxo de preparação do payload para a API
import { gzipSync } from 'zlib';

function prepararPayloadNFSe(xmlAssinadoUTF8: string): string {
  // 1. Converter XML para Buffer UTF-8
  const xmlBuffer = Buffer.from(xmlAssinadoUTF8, 'utf-8');
  
  // 2. Compactar o buffer em GZip
  const gzippedBuffer = gzipSync(xmlBuffer);
  
  // 3. Converter para Base64 para envio na requisição JSON
  return gzippedBuffer.toString('base64');
}

The endpoints provided by the webservice cover the entire lifecycle of the tax document. They include NFS-e issuance, batch and individual invoice queries, cancellation of issued documents, receipt of tax events, and automatic generation of DANFSE in PDF format.

Accreditation, homologation environment, and schema validation

The technical accreditation process requires that the application's responsible party has a valid CNPJ and an e-CNPJ or e-CPF digital certificate of the technical responsible. To ensure the protection of private keys during system operations, it is strongly recommended to store credentials in an HSM (Hardware Security Module) or a secure digital vault.

Before sending requests to the production environment, developers have access to a separate homologation environment. On the NFS-e Portal, Swagger files and YAML specifications are available to facilitate API client generation and test routing.

Since December 10th, 2025, the governmental structure has provided a restricted environment focused on the IBSCBS group fields, aligned with Technical Note 004 version 2.0. This environment allows simulating the complete tax structure that will come into effect during the stages of the tax transition.

According to the schema validation and API documentation alerts, the slightest layout error, a missing mandatory field, or an invalid data type immediately interrupts the operation. Therefore, implementing a rigorous XML schema validation layer locally before sending the package to the webservice is an indispensable step to avoid blocking the issuance queue.

Practical implementation roadmap by November

To ensure your system is running smoothly by the November 1st, 2026 deadline, it is worthwhile to follow a structured schedule with four practical steps:

1. Digital certificate audit: Verify that your company or your software's clients have valid A1/A3 ICP-Brasil certificates and configure the digital vault or HSM to manage mTLS access keys.
2. Schema modeling and signing: Develop modules for XML 1.0 UTF-8 conversion, XMLDSIG signing, GZip compression, and Base64 encoding within your application.
3. Tests in the homologation environment: Consume the Swagger documentation on the NFS-e Portal and execute test scenarios covering issuance, query, cancellation, and DANFSE PDF generation.
4. Validation of transition rules: Use the restricted environment with the IBSCBS group (Technical Note 004 v2.0) to ensure that your database structure and APIs are already prepared for future tax changes.

Frequently asked questions

What is the final deadline for MEs and EPPs to adopt NFS-e Nacional?

The final deadline for micro-enterprises and small businesses opting for Simples Nacional is November 1st, 2026. The date was officially stipulated by CGSN Resolution No. 191/2026, changing the initial obligation which was September 2026.

Does MEI need to change the issuance system in November 2026?

No, MEI does not need to make changes on that date. Individual Micro-entrepreneurs have already been required to use the NFS-e Emissor Nacional standard since September 1st, 2023.

What are the security requirements to connect to the National API?

Connecting to the API requires the use of HTTPS with TLS and mutual authentication (mTLS), using an ICP-Brasil A1 or A3 digital certificate from the technical responsible. Requests are transmitted in JSON and require payloads containing XML signed in XMLDSIG, compressed in GZip, and encoded in Base64.

Where can I find the API documentation and test environment?

The official documentation, Swagger files, and YAML specifications are published on the federal government's NFS-e Portal. The portal provides a homologation environment and a restricted environment for code validations.

Conclusion

The migration to NFS-e Nacional is inevitable, and the extended deadline until November 1st, 2026, offers the perfect window to organize the code without rush. Unifying issuance under the national standard eliminates the complexity of dealing with multiple municipal layouts and prepares your structure for the tax requirements of the coming years.

Your practical recommendation for today: access the NFS-e Portal, download the updated API Swagger specification, and configure the company's digital certificate in the homologation environment to perform the first test shots.