NF-e 5.0 — the e-invoice adapted to the Tax Reform (NT 2025.002)
"NF-e 5.0" is what the market calls the Brazilian electronic invoice (Nota Fiscal Eletrônica) once adapted to the Tax Reform. Officially there is no "layout 5.0": the NF-e layout version stays at 4.00, and the Reform changes are introduced by Technical Note 2025.002 (RTC), which adds dedicated fields for CBS, IBS and the Selective Tax. In 2026 those fields are informative (no rejection); mandatory validation phases in over the second half of 2026 (and January 2027 for Simples/MEI). Brief for tax directors and ERP owners planning the systems migration.
Key changes vs. NF-e 4.0
- New field groups for CBS/IBS/IS: rate, tax base and a specific tax-regime code (CRT) for each of the new taxes.
- Per-item operation identification: CST/CSOSN tax-situation codes updated for special regimes (healthcare, education, agribusiness).
- Split-payment indicator: flags whether the operation is subject to automatic withholding by the financial institution at settlement.
- Cashback operation: fields to identify operations eligible for the CBS/IBS Cashback program for low-income families.
- Dual compatibility: issues the legacy ICMS+IPI+ISS taxes AND the new CBS+IBS+IS during the transition.
Operational impact on ERPs
Adapting systems for NF-e 5.0 is the single largest operational cost of the Tax Reform in the pre-2027 phase:
- In-house / customized ERPs: require a rewrite of the tax modules — a typical 4-8 month project.
- SAP / Oracle / TOTVS: dependent on vendor patches — the release calendar is material to the timeline.
- Product master data: review of NCM codes (Mercosur tariff classification), CEST codes and eligibility for favored regimes (basic-needs basket, healthcare, education, etc.).
- Integrations: NFC-e (retail consumer invoice), MDF-e (freight manifest), CT-e (transport document), BP-e (passenger transport ticket) — all must be revisited.
Companies that postpone the adaptation risk entering 2027 issuing incorrect invoices — an operational-blocking risk, since an invalid invoice prevents the transaction from completing.
Frequently asked questions about NF-e 5.0
Is NF-e 5.0 mandatory already in 2026?
In 2026, populating the IBS/CBS fields in the e-invoice (NT 2025.002) is informative — an invoice is not rejected for leaving them blank. Mandatory validation (rejection) phases in over the second half of 2026 for the standard regime and in January 2027 for Simples/MEI. Exact dates vary by NT release — check the current version on the NF-e Portal. Large companies should adapt the ERP early to reach go-live tested.
Do companies under Simples Nacional need to issue NF-e 5.0?
Yes. All companies required to issue an NF-e (including those under Simples Nacional, the simplified unified regime for small business) must adopt the Reform-ready NF-e (NT 2025.002) — note the layout stays at version 4.00, with no official "5.0". The Reform-specific fields are populated automatically according to the issuer's regime — Simples companies keep their single unified payment (DAS), with mandatory validation from January 2027 for Simples/MEI.
How should in-house ERPs prepare?
Steps: (1) update the official XSD schema from the NF-e Portal; (2) refactor the issuance module to include the CBS/IBS/IS field groups; (3) review the product master data with the new tax classification; (4) integrate with the banking system for split-payment; (5) test in the SEFAZ homologation environment. Typical project timeline: 4-8 months for a customized ERP, 2-4 months for a standard ERP with a vendor patch.
What happens if an NF-e 5.0 is issued with errors during the transition?
Errors can lead to automatic rejection by the SEFAZ (an invalid invoice does not permit the operation). In production, this causes a commercial block. In homologation (sandbox), it allows correction before go-live — which is why mass testing in homologation is an essential part of the project. Penalties for an incorrect invoice may also apply.