DANFSe v2.0: the Government API Was Shut Down on August 3 — What to Check in Your ERP Now

One month later: DANFSe generation is no longer the government's task—it's now your system's

While the tax market's attention remains focused on split payment, DeRE, and the IBS/CBS timeline for electronic documents, a quiet operational change is already directly affecting the routine of issuing service invoices: the Auxiliary Document for NFS-e, the DANFSe, has gained a new mandatory national standard, and the infrastructure the government maintained to generate it automatically was shut down in August. For tax and IT teams, it's time to confirm whether the ERP and issuance systems have already taken on this responsibility without generating rejections, delays in delivering the document to the service recipient, or visual inconsistencies.

What Technical Note No. 008/2026 changed

The Executive Secretariat of the Electronic Service Invoice Management Committee (SE/CGNFS‑e) published Technical Note No. 008/2026, which defines the new national standard for the Auxiliary Document of the Electronic Service Invoice (DANFSe). NT 008 establishes a mandatory national standard for DANFSe generation by issuing systems, including ERPs and tax solutions. In practice, this ends the visual fragmentation that existed until then: the DANFSe must now follow a single national standard, eliminating the confusion caused by the thousands of different municipal layouts that previously existed.

End of the official API: generation is now each issuing system's responsibility

The most sensitive point of the NT for IT teams is the discontinuation of the API the government maintained to automatically generate the DANFSe. The official government-provided DANFSe generation API was discontinued on August 3, 2026, in version 1.02. After that date, issuing systems, ERPs, and tax software must generate the DANFSe internally. In other words: those who relied on the national service to produce the service invoice PDF had to internalize that routine—and this has already been in effect for nearly a month.

What changed in layout v2.0

The new standard brings detailed formatting requirements that need to be validated line by line in printing engines: mandatory printing on A4 paper size (minimum), single copy, and portrait mode only, with specific fonts used to ensure legibility: Arial for titles and field labels and Microsoft Sans Serif for filled-in content. The header must display the official National NFS-e logo and the clear label DANFSe v2.0.

In the values block, the separation by tax became more explicit: the values block was split into Net Value of the NFS-e, Total IBS/CBS, and Net Value of the NFS-e plus IBS/CBS, which now appear separately. There is also an interesting transition rule for those monitoring the coexistence between the old and new systems: the Federal Taxation block still includes self-assessed PIS and COFINS, but these lines will only be printed for NFS-e with a competency date through the end of 2026; after that, CBS takes their place. This is a detail tax teams should monitor at the turn of the calendar year, to avoid legacy fields improperly appearing in January 2027.

Two other points in the layout deserve checking during testing: the new standard establishes a mandatory QR Code on the DANFSe, which must allow public lookup of the NFS-e through the National NFS-e Portal, using the document's access key. And, for those dealing with physical document receipt routines, the layout provides for an optional receipt stub block, with acknowledgment date, identification, and signature, to record receipt.

Checklist for tax and IT teams in September

With the cutoff date already past, the focus now is compliance auditing. It's worth confirming, with the IT team or the ERP implementation partner:

• Whether the system generates the DANFSe locally, without any call to the discontinued government API;
• Whether the printed or PDF layout is already in the v2.0 standard (fonts, header, portrait orientation, A4 size);
• Whether the three totals (net, IBS/CBS, and net plus IBS/CBS) are being correctly calculated and displayed;
• Whether the QR Code points to the correct access key on the National NFS-e Portal;
• Whether the transition rule from the PIS/COFINS block to CBS is mapped for the competency shift in January 2027.

This type of technical adjustment tends to go unnoticed until it generates a complaint from a client who receives an invoice with an outdated layout, or worse, until an inconsistency arises that makes bookkeeping difficult for the service recipient. It's worth reviewing now, while the quarter's issuance volume still allows for corrections without pressure.

This content is for informational purposes only and does not replace guidance from your company's accounting team, which should always be consulted for specific decisions regarding tax obligations.

If your team wants to confirm whether DANFSe generation and other electronic tax documents are aligned with the Tax Reform timeline, get in touch with Edoo.