Electronic invoice in Brazil

Understand Brazil’s mandatory clearance model, DF-e formats, SEFAZ authorisation and evolving IBS/CBS e-invoicing requirements.

Select a country

Overview

Brazil operates one of the most mature electronic tax document systems in the world — but it is not a single system in the European sense. It is a family of Documentos Fiscais Eletrônicos (DF-e), each covering a different transaction type and each administered by a different level of government.

The model is centralised clearance. The supplier builds a structured XML file, signs it with a digital certificate and submits it to the state tax authority SEFAZ, or to a municipal or national NFS-e system. The document only becomes legally valid once the tax infrastructure has authorised it. A PDF does not replace the XML — and Peppol plays no part in any of this.

3 core documents

NF-e for goods, NFC-e for retail, NFS-e for services — plus CT-e, MDF-e and others

ICP-Brasil

every document is signed with a Brazilian certificate tied to the issuer's CNPJ

Authorisation first

goods may not legally ship until SEFAZ has returned an Autorização de Uso

Timeline

Brazil has no single national switch-on date. NF-e arrived in industry waves from 2008; services were unified only recently; and the tax reform is now layering new fields onto documents that have existed for nearly two decades.

Already in force

2005 — 2011

NF-e is created and rolled out in waves

Ajuste SINIEF 07/2005 established the legal basis. Cigarette and liquid-fuel producers went first on 1 April 2008, and obligation then spread by sector, transaction type and CNAE code through 2009–2011.

1 December 2010

States may mandate without a separate protocol

A federally agreed regime let states extend NF-e to new taxpayer categories without negotiating each one. Supplies to public bodies were broadly covered from around the same date.

1 September 2023

National NFS-e for MEI

Individual micro-entrepreneurs supplying services became the first group required to use the national service-invoice platform rather than a municipal one.

1 January 2026

Municipalities join the national NFS-e environment

Every municipality and the Federal District must either use the national platform or transmit its own documents into the national data environment. See the DF-e family.

3 August 2026

IBS/CBS fields become blocking in production

Validation of the new reform fields went live in the test environment on 1 July 2026 and in production on 3 August 2026, initially for CRT 3 taxpayers — the normal regime. The same date applied to the revised DANFSe layout.

Still ahead

1 September 2026

Simples Nacional moves to the national NFS-e issuer

Micro and small service businesses under Simples Nacional must issue through the national NFS-e issuer — web platform or API — rather than a municipal one.

1 January 2027

IBS/CBS validation extends to the remaining regimes

Simples Nacional, Simples excess-sublimit and MEI taxpayers — CRT 1, 2 and 4 — come into the blocking validation rules.

2027 — 2033

The old taxes are phased out

PIS/COFINS end and full CBS begins in 2027–2028; ICMS and ISS are progressively replaced by IBS across 2029–2032; the new model is fully in force in 2033.

The DF-e family

Which document you issue depends on what you sell and to whom — and each is governed at a different level of the federation. This is the single fact that most surprises companies arriving from Europe.

NF-e, model 55Goods. Used for B2B, B2G, exports and the importer's own inbound document. Authorised by the state tax authority SEFAZ

NFC-e, model 65Retail sales of goods to consumers. Also state-authorised, with dedicated contingency modes for point of sale

NFS-eServices. Historically municipal, now converging on the national platform and the national data environment

OthersCT-e for transport, MDF-e for manifests, BP-e for passenger tickets, NF3e for electricity, NFCom for telecoms

What changed for services

Until recently NFS-e was a patchwork: format, portal, API and even the obligation itself varied from city to city. Since 1 January 2026 municipalities and the Federal District must either use the national NFS-e platform or transmit documents from their own systems, in the standardised format, into the Ambiente de Dados Nacional (ADN) — the national data environment.

This does not mean every service provider moved onto one federal web portal on 1 January 2026. A municipality may keep its own system as long as it is compatible with the national standard and feeds documents and events into the ADN. Which system your Brazilian client actually issues through therefore still has to be checked city by city.

The clearance model

NF-e and NFC-e are pre-clearance continuous transaction controls. The tax administration receives the document before the commercial transaction completes, and without authorisation the document simply does not exist in law.

01 The supplier builds the XML in the prescribed Brazilian layout

02 The XML is signed with an ICP-Brasil certificate

03 It is transmitted to the SEFAZ of the relevant state, or to the shared authorisation infrastructure

04 SEFAZ runs structural, registration and tax validations and returns either an Autorização de Uso or a rejection code

05 Only after authorisation may the goods lawfully move

06 The authorised XML and the authorisation protocol are passed to the recipient

The recipient is not passive. Depending on the transaction they may register a Manifestação do Destinatário — confirming the operation, declaring it unknown, or stating that it did not take place.

Services work slightly differently

For the national NFS-e the software submits a signed DPS — Declaração de Prestação de Serviços. The national system validates it and returns, synchronously, either the finished NFS-e in XML or a rejection message. Municipalities keeping their own systems must forward the resulting NFS-e and its events into the ADN, so a national dataset for services is built either way.

What this is not: it is not periodic reporting, not near-real-time reporting after the fact, and not a Peppol five-corner model. There is no post-audit route. If the state says no, there is no invoice.

B2B, B2G and B2C

B2B

Goods move on NF-e, services on NFS-e. The supplier determines CFOP, NCM and CST or CSOSN codes, rates and tax indicators, clears the document, ships, and hands over the XML. The recipient books it and, where applicable, manifests on it.

B2G

Brazil has no separate national B2G platform comparable to a European procurement portal or a Peppol channel. Supplies of goods to public bodies use ordinary NF-e model 55 with the authority as recipient; public purchases of services use the applicable municipal or national NFS-e.

A public buyer may additionally require a procurement or contract number, an order number, a budget code, the ordering unit, or delivery of the XML through a procurement portal. These are contractual procurement requirements — they sit on top of the tax model, they do not change it.

B2C

Retail goods use NFC-e, authorised by SEFAZ in near real time. States rolled it out on their own schedules, so there is no single nationwide B2C date. São Paulo, for instance, retired the remaining SAT and paper retail models from 1 January 2026, after which NFC-e became the primary retail model there.

The consumer may be identified by CPF or, where the rules for the transaction allow it, remain unidentified. For B2C services the NFS-e obligation depends on municipal rules and the supplier's tax regime — a MEI, for example, is generally exempt from issuing to a private individual unless the consumer asks for the document.

The IBS/CBS reform

Brazil is replacing a thicket of consumption taxes with two: CBS, the federal Contribuição sobre Bens e Serviços, and IBS, the shared Imposto sobre Bens e Serviços. Crucially for anyone building software, the reform does not introduce a new document type — it adds fields, rates, bases and tax classifications to the DF-e that already exist.

2026Transition year at token rates — CBS 0.9% and IBS 0.1%

2027 — 2028PIS/COFINS end and CBS begins in full

2029 — 2032ICMS and ISS are progressively replaced by IBS

2033The new model is fully in force

The technical rollout has moved. Early official material pointed to mandatory DF-e adaptation from 1 January 2026, but the blocking validation rules were staged: 1 July 2026 in homologation and 3 August 2026 in production, and initially only for CRT 3 — the normal regime under Lucro Presumido or Lucro Real. CRT 1, 2 and 4 — Simples Nacional, Simples excess-sublimit and MEI — follow from 2027.

The specifications are still moving. Nota Técnica 2025.002 reached version 1.50 in June 2026 and the corresponding Informe Técnico version 1.60 was published on 23 June 2026. Treat Notas Técnicas as a standing operational subscription, not a one-off project.

Formats and PDF

Brazilian tax invoices do not conform to EN 16931. Neither Peppol BIS Billing, nor UBL 2.1, nor UN/CEFACT CII is a permitted syntax. Brazil uses its own XML schemas, developed by the tax authorities and ENCAT.

NF-e / NFC-eLocal XML schemas governed by the Manual de Orientação do Contribuinte (MOC), the XSD schemas, the Notas Técnicas and the SEFAZ validation rules. The layout remains anchored on version 4.00, extended by technical notes including the new IBS/CBS fields

NFS-eIts own national XML — the inbound DPS, the outbound NFS-e, separate structures for events, cancellation, replacement and correction, plus national service and tax classification catalogues

JSONSome API calls and service messages use JSON, but the legally significant tax document is always the national XML

Converting a European invoice into an NF-e is not a syntax transformation. It is a full tax mapping exercise: CFOP, NCM, CST or CSOSN, cClassTrib and the rest have no European equivalents to map from.

Where the PDF sits

A PDF on its own is never a legally valid electronic invoice in Brazil. What exists instead are auxiliary representations of the XML data: DANFE for NF-e, DANFCE for NFC-e and DANFSe for NFS-e. They make the document readable, travel with the goods and carry the access key for verification.

The recipient of an NF-e must be given the XML together with the authorisation protocol. Sending only the DANFE does not discharge the obligation to provide the electronic tax document.

Identifiers

Brazil uses its own registration numbers throughout. There is no Peppol EAS code in the mandatory national process.

CNPJThe company registration number — the primary identifier of a legal entity

CPFThe individual taxpayer number, used for natural persons including identified retail consumers

Inscrição EstadualState tax registration, relevant to ICMS and therefore to NF-e

Inscrição MunicipalMunicipal registration, relevant to ISS and therefore to NFS-e

idEstrangeiroThe field for a foreign counterparty who has no CNPJ — used on export NF-e

One item worth watching in integration work: Brazil is introducing the alphanumeric CNPJ, and test registrations were published in the homologation environment in July 2026. Any system that validates CNPJ as strictly numeric will need attention.

Peppol in Brazil

Peppol is not part of Brazil's mandatory infrastructure. It is not used to clear NF-e, NFC-e or NFS-e; it is not a required B2B or B2G channel; it does not substitute for SEFAZ or the national NFS-e; and it confers no right to issue a Brazilian tax document.

No Brazilian Peppol Authority has been published in the OpenPeppol list

No national Peppol EAS code applies to the CNPJ in the mandatory tax process

No accreditation requirements exist for Peppol Access Points, because there is nothing for them to be accredited for

A Brazilian company can of course join the international Peppol network through a foreign provider if a trading partner asks for it. That document is a commercial message. It does not replace the mandatory NF-e or NFS-e, and it carries no weight with SEFAZ.

Export and import

Exporting goods

The Brazilian exporter issues an NF-e with an export CFOP and the foreign recipient in the idEstrangeiro field. The NF-e proves the Brazilian tax side and supports logistics and customs — but it does not necessarily replace the commercial invoice the foreign customs authority or buyer requires. In practice an exporter often produces the NF-e, a commercial invoice, a packing list and, where the buyer needs it, a Peppol or EDI document as well.

Importing goods

A foreign supplier does not issue a Brazilian NF-e. After customs clearance the Brazilian importer issues an entrada NF-e in its own name, carrying the foreign supplier's details, the customs declaration, import duties, ICMS, IPI and PIS/COFINS or the future IBS/CBS, plus freight, insurance and any other amounts in the taxable value. The foreign commercial invoice remains a commercial and customs document — it is not a substitute.

Exporting services

Service exports are documented on a full NFS-e, not a simplified one, carrying the foreign customer, a NIF or an explicit statement that none exists, the foreign address, the service code, the place of supply or consumption, and the indicators that establish entitlement to export relief. Having a foreign client does not automatically make a service an export for tax purposes — what matters is where the economic result arises.

ViDA does not apply

ViDA is EU legislation. Brazil has no 2030 date equivalent to the EU digital reporting requirements and does not treat EU trade as intra-EU — a sale to Germany is an ordinary export. The Brazilian side follows export rules; the European buyer separately satisfies its own jurisdiction, including any future ViDA obligation. Neither changes the NF-e or NFS-e model.

Requirements for providers

There is no national accreditation for e-invoicing providers in the sense of the Slovak digitálny poštár or an Australian Peppol accreditation — because Peppol is not the mandatory infrastructure. What Brazil accredits is the taxpayer as issuer, not the software vendor as an intermediary.

What the taxpayer must have

—The right to issue the relevant DF-e, and registration and accreditation as an NF-e issuer with SEFAZ

—Valid tax registrations — CNPJ or CPF, plus Inscrição Estadual or Municipal where applicable

—An appropriate ICP-Brasil certificate for signing, or an authorised signature and authorisation arrangement

—Software that observes the XSD schemas, the MOC, the Notas Técnicas and the SEFAZ validation rules

Can a foreign provider serve Brazilian clients?

Technically yes. A foreign company may supply the ERP, middleware or cloud platform, generate the XML, run validation and tax mapping, provide API integration and transmit documents on the client's behalf under granted authority. The national NFS-e explicitly contemplates connecting in-house or commercially purchased software through its API.

But the document is always issued using the Brazilian taxpayer's data and rights — its CNPJ or CPF, its state or municipal registration, its SEFAZ or municipal authorisation, and its certificate. A European Peppol certification confers no privileges whatsoever in the NF-e or NFS-e process.

Local presence

The federal regulation reviewed contains no general requirement for a software provider to incorporate a Brazilian entity, hold a local shareholder, operate a local access point, maintain an official delivery mailbox, or obtain a single nationwide e-invoicing licence. The client, however, must be properly registered in Brazil — and individual states, municipalities, public buyers or regulated industries may impose their own contractual and technical requirements.

One development to watch

In 2026 the NF-e portal began publishing documents on the PAA — Provedor de Assinatura e Autorização model, with Nota Técnica 2026.001 reaching version 1.02a on 23 June 2026. This is a specifically Brazilian signature-and-authorisation mechanism. It is not a variety of Peppol Access Point and should not be described as one.

Archiving

Both parties must retain the authorised electronic documents and the associated authorisation protocols for the applicable tax limitation period. Because the retention rules sit across federal, state and municipal legislation and vary with the tax in question, the practical rule is to keep the XML for the longest period any of the relevant authorities can still assess — and to confirm the exact term with a Brazilian adviser for the specific taxes involved.

What is archived is the authorised XML plus the authorisation protocol — not the DANFE

The supplier must give the recipient access to the XML once it has been authorised

Cancellations, replacements, corrections and recipient manifestation events belong in the archive alongside the invoice itself

A public lookup on the NF-e or NFS-e portal proves a document existed; it is not a substitute for holding the file. See Resources for both verification tools.

Penalties and tax credit

There is no single federal penalty tariff. What applies depends on the tax, the state for ICMS matters, the municipality for ISS, the nature of the breach, the transaction value, whether it was voluntarily corrected, and whether there was intent or actual loss of revenue.

São Paulo as an illustration

—Up to 50% of the transaction value for failing to issue a required tax document

—Separate penalties for a document with incorrect or incomplete information

—Penalties for late transmission or late authorisation requests

—Minimum amounts expressed in UFESP, the state's index unit

Money is often not the worst of it. Missing authorisation can mean goods travelling without a valid document, cargo being detained, the buyer refusing delivery, tax credit being denied, and additional tax, interest and surcharges being assessed. Where missing or falsified documents are used to conceal turnover, the matter can move from administrative penalty to tax offence or crime.

Is the e-invoice the only basis for a tax credit?

Under the current system there is no single Brazilian VAT — ICMS, ISS, IPI and PIS/COFINS coexist. For ICMS, an authorised NF-e is normally the principal documentary basis for credit, but holding the XML is not sufficient on its own: the transaction must be real, the item must confer a right to credit, the tax must be stated correctly, the document must be booked, and no exemption or credit restriction may apply.

Under IBS/CBS the legislation ties the ordinary credit directly to a valid electronic tax document, recognised as valid and usable by the tax authorities, with the amount reflected in the tax system and the settlement conditions met along the chain.

A valid electronic tax document is the mandatory foundation of an ordinary input credit — but it does not by itself guarantee the credit, and it does not exclude the special bases the law provides for: special regimes, presumed credits, dedicated documents for particular operations, adjustments and returns.

How we help

Brazil is the clearest case in the world of a market where EN 16931, Peppol BIS and UBL support buys you nothing on its own. What a platform actually needs:

Generation of the local NF-e, NFC-e and NFS-e XML in the current layouts

Brazilian tax coding — CFOP, NCM, CST, CSOSN, cClassTrib and the rest

Integration with SEFAZ and with the national or municipal NFS-e

Handling of authorisation protocols, rejections, events, cancellations and contingency modes

Continuous implementation of Notas Técnicas and the IBS/CBS transition rules through 2033

Conversion between Brazilian documents and European formats for the EU side of the trade

Connection by API, SFTP and CSV, with ERP and IDoc source data

Frequently asked questions

Is e-invoicing mandatory in Brazil?

Yes, and it has been for years — but not through one instrument or one date. NF-e for goods became obligatory in industry waves from 1 April 2008; NFC-e for retail was rolled out state by state; NFS-e for services was municipal until the national platform began consolidating it. There is no post-audit alternative: a document that has not been authorised is not a valid tax document.

Can I use my European Peppol Access Point in Brazil?

Not for the mandatory process. Peppol is not used to clear NF-e, NFC-e or NFS-e, no Brazilian Peppol Authority has been published, and there is no national EAS for the CNPJ. A Peppol document exchanged with a Brazilian company is a commercial message that sits alongside — never instead of — the cleared tax document. A European Peppol certification grants no rights before SEFAZ.

Can a foreign software provider serve Brazilian clients?

Yes. A foreign company can supply the platform, generate and validate the XML, map the taxes, integrate by API and transmit on the client's behalf under granted authority — the national NFS-e explicitly allows connecting purchased software through its API. No general federal requirement was found for a Brazilian entity, a local shareholder, a local access point or a nationwide provider licence. But the document is always issued with the Brazilian taxpayer's registrations, authorisations and certificate, and states, municipalities and public buyers may add their own conditions.

Do Brazilian invoices comply with EN 16931?

No. EN 16931, Peppol BIS Billing, UBL 2.1 and UN/CEFACT CII are not permitted syntaxes for Brazilian tax invoices. Brazil uses its own XML schemas developed by the tax authorities and ENCAT, governed by the MOC, the XSD schemas and the Notas Técnicas. Converting a European invoice into an NF-e is a tax mapping exercise, not a syntax transformation — CFOP, NCM, CST, CSOSN and cClassTrib have no European source fields to map from.

Is a PDF invoice acceptable?

Not as the invoice. DANFE, DANFCE and DANFSe are auxiliary visual representations of the XML — useful for reading, for travelling with the goods and for checking the access key, but they do not replace the authorised XML. The recipient of an NF-e must be given the XML together with the authorisation protocol; sending only the DANFE does not discharge the obligation.

What does the tax reform change for my invoicing system?

Not the document type — the fields. IBS and CBS are being added to the existing DF-e as new groups, rates, bases and classifications. The blocking validation rules went live in homologation on 1 July 2026 and in production on 3 August 2026, initially only for CRT 3 taxpayers under the normal regime; CRT 1, 2 and 4 follow from 1 January 2027. The full tax transition then runs to 2033, so expect Notas Técnicas throughout.

What happens if SEFAZ is unavailable?

Brazil has built-in contingency arrangements, including the shared SVC environments that states switch to when their own authoriser is down, and dedicated contingency modes for NFC-e at the point of sale. The NF-e portal publishes both active and scheduled contingency, so an operational integration should monitor it rather than discovering an outage from failed submissions. Contingency changes how the document is authorised — it does not remove the requirement to authorise it.

Who archives the invoice?

Both parties. Each must retain the authorised XML and the authorisation protocol for the applicable limitation period, along with cancellations, replacements, corrections and recipient manifestation events. Because retention rules sit across federal, state and municipal law and vary by tax, the safe approach is to keep the file for the longest period any relevant authority can still assess, and confirm the exact term locally. A public portal lookup proves a document existed — it is not a substitute for holding it.

Summary

Brazil is a mandatory, real-time, pre-clearance country — and has been for far longer than most of Europe. Goods clear through the state SEFAZ on NF-e or NFC-e, services through the national or municipal NFS-e, and nothing ships or counts until the authorities have said yes. There is no post-audit route and no PDF fallback.

The current work is the tax reform. IBS and CBS are not a new document — they are new field groups inside the documents that already exist, and their validation became blocking in production on 3 August 2026 for the normal regime, extending to the remaining regimes from January 2027. Services are converging in parallel, with Simples Nacional moving to the national NFS-e issuer on 1 September 2026.

For a European provider the honest summary is this: nothing you already have transfers. Not the format, not the identifier scheme, not the certification, not the network. What does transfer is the client relationship — a foreign platform can serve Brazilian clients perfectly well, provided it issues under their registrations and certificates and keeps pace with the Notas Técnicas.

Resources

Portal da Nota Fiscal Eletrônica The official NF-e portal — legislation, manuals, XML schemas, Notas Técnicas and the state SEFAZ portals Notas Técnicas — NF-e The technical notes that actually drive implementation work, including the IBS/CBS reform series and the PAA model SEFAZ availability monitor Live and scheduled contingency by state — the page to watch before assuming a rejection is your own fault Portal da Nota Fiscal de Serviço eletrônica The national NFS-e portal — municipal adoption monitoring, the implementation plan and the CGNFS-e resolutions NFS-e technical documentation and APIs Layouts, schemas and the production and restricted-production APIs, plus the dedicated reform (RTC) section NFS-e public lookup Verify a service invoice by its access key — the practical counterpart to the NF-e lookup on the NF-e portal Emissor Nacional de NFS-e The national service-invoice issuer that MEI already use and Simples Nacional taxpayers move to on 1 September 2026

Need support with e-invoicing compliance?

As a certified Peppol Access Point we provide solutions for sending and receiving electronic invoices securely across Europe — including format conversion, validation and integration with national systems.

Start your free trial