Invoice Requirements in Brazil: Legal Rules for 2026

TL;DR: Brazilian invoices operate through the Nota Fiscal Eletronica (NF-e) system with mandatory digital signatures and SEFAZ authorization -- taxes include ICMS, IPI, PIS/COFINS, and ISS at rates that vary by state, municipality, and product. Archive signed XML and DANFE PDFs for at least five years.

Brazilian compliance centres on Nota Fiscal Eletrônica (NF-e) for goods and NFS-e (municipal) or equivalent flows for many services. A PDF without authorised XML, digital signatures, and the access key (chave de acesso) rarely satisfies enterprise accounts payable or a state treasury audit. ICMS varies by state, IPI is federal and product-specific, ISS is municipal on services, and PIS/COFINS follow cumulative or non-cumulative paths—your fiscal document must mirror those layers, not a single “VAT %” footer. This overview targets 2026 practice for growing traders; it is not legal advice. Confirm Simples Nacional, incentives, and ICMS conventions with a Brazilian accountant. Marketplaces and dropship models may require distinct NF-e roles—do not assume one template fits all chain positions.

Required fields

NF-e and NFS-e payloads include issuer CNPJ and address, recipient CNPJ/CPF, series and number, NCM or service codes, taxable bases, applicable ICMS, IPI, PIS, COFINS, and ISS rows, totals, and SEFAZ or municipal authorization protocol. Cartas de correção and credit notes follow strict rules—reference original documents rather than overwriting issued files. Mixed shipments need line-level precision so SPED and state LED reconciliations tie out. Service city codes on NFS-e must match municipal registrations—typos can block authorization for days.

Tax rules (VAT/GST/sales tax rates)

Brazil does not operate a single VAT. ICMS rates and benefits depend on state and product; IPI uses federal tables; ISS is set per municipality for services; PIS/COFINS treatment turns on your regime. Exports may be relieved with documentation chains that customs and tax auditors can follow. ICMS substitution tax (ST) scenarios need explicit line tags—do not collapse them into a single generic percentage footer. Templates that show one generic rate are unsafe—map each SKU or service to the correct statutory combination.

Language requirements

Portuguese is mandatory for official fields, SEFAZ interactions, and municipal NFS-e narratives. English appendices may help foreign parents but cannot replace Portuguese legal identifiers or catalogue codes.

Digital invoicing rules

NF-e XML is signed and authorised through state SEFAZ gateways; NFS-e uses municipal web services. Archive XML, DANFE PDFs, and protocol responses together. SPED and related obligations cross-check totals—keep ERP tax codes aligned with each line on the fiscal document. State incentives sometimes require specific CFOP-style narratives—sync product masters with fiscal teams before go-live.

Invoice numbering rules

NF-e numbering follows a strict structure: each document has a series (serie) and a sequential number (numero) that together, with the issuer's CNPJ, uniquely identify the fiscal document. Numbers run from 1 to 999,999,999 within each series. You may use multiple series (for example, series 1 for regular sales, series 2 for returns) but each must be sequential within itself. The SEFAZ authorization system enforces uniqueness -- attempting to reuse a number within the same CNPJ/series will be rejected. Cancelled NF-e (inutilizacao) numbers must be formally reported to SEFAZ so the gap is explained in the system rather than left unexplained. NFS-e for services follows municipal rules that vary by city -- most municipalities assign the number during authorization rather than letting the issuer choose. Cartas de correcao (correction letters) do not change the number but attach amendments to the original document. Never manually manipulate sequence numbers outside your ERP's fiscal module -- traceability from ERP to SEFAZ is the primary audit control.

Common exemptions and special cases

Simples Nacional is the simplified tax regime for micro and small enterprises with annual gross revenue up to BRL 4.8 million. Businesses under Simples Nacional issue NF-e with a distinct CSOSN (tax situation code) rather than standard CST codes, and their tax is calculated through a unified table (DAS) rather than line-by-line ICMS/PIS/COFINS breakdowns -- however, the NF-e must still contain the correct fiscal codes for the buyer's ERP to process it. MEI (Microempreendedor Individual) with revenue up to BRL 81,000 per year has even simpler obligations but must still issue fiscal documents for B2B sales. ICMS substitution tax (ICMS-ST) shifts the tax collection point upstream in the supply chain -- your NF-e must tag ST items with the correct CST codes and show the retained tax on the face of the document. Export NF-e require specific CFOP codes (such as 7.101 for export of domestically produced goods) and must be linked to customs declarations (DU-E). Tax incentives (such as ICMS reductions for specific products or regions) require CST/CSOSN codes and narrative references to the applicable legislation on the NF-e XML -- generic footers are insufficient. Nota Fiscal de Consumidor Eletronica (NFC-e) is the consumer-facing equivalent of NF-e for retail point-of-sale transactions.

Record retention requirements

Federal tax law under the Codigo Tributario Nacional requires retention of fiscal documents for five years from the first day of the year following the taxable event. However, state regulations and specific tax incentives may require longer periods -- some states mandate ten years for ICMS-related records. The NF-e XML (digitally signed and authorized by SEFAZ) is the legal document -- the DANFE PDF is merely an auxiliary representation. You must archive the complete XML including the SEFAZ authorization protocol for the full retention period. SEFAZ portals allow downloading NF-e XML for a limited time (typically 180 days after authorization), so establish automated archiving at the time of issuance rather than relying on later retrieval. Municipal NFS-e archives follow local rules -- some municipalities retain the XML on their portals, others require the issuer to archive independently. SPED (Sistema Publico de Escrituracao Digital) filings cross-reference your NF-e data, so your archives must be consistent with what was reported in EFD-ICMS/IPI and EFD-Contribuicoes obligations.

E-invoicing status

Brazil is a global pioneer in mandatory e-invoicing. NF-e has been mandatory for goods since 2008-2010 (phased by sector) and covers virtually all goods transactions today. The NF-e system requires real-time authorization from the state SEFAZ before goods can ship -- the XML is digitally signed by the issuer and countersigned by SEFAZ, with the chave de acesso (44-digit access key) serving as the unique identifier. NFS-e for services has historically varied by municipality, with each city running its own web service, but the federal government has been working on a national NFS-e standard to unify municipal systems -- this is progressively being adopted. CT-e (Conhecimento de Transporte Eletronico) covers transport documents. NFC-e handles consumer retail transactions. Brazil's tax reform (approved in late 2023 as Emenda Constitucional 132/2023) will eventually replace ICMS, IPI, PIS, COFINS, and ISS with a dual VAT system (IBS + CBS), which will bring changes to fiscal document structures -- monitor the implementation timeline and technical specifications as they are published.

Penalties

Federal and state agencies may assess tax, fines, and interest for unauthorised documents, late issuance, or misdeclared taxes. Penalties vary by jurisdiction but are generally significant. For failure to issue NF-e when required, states typically impose fines of 1% to 10% of the value of the operation, with minimums per document that vary by state (often in the range of hundreds to thousands of BRL per NF-e). Incorrect ICMS classification can result in the full tax amount plus fines of typically 50% to 100% of the unpaid tax, plus daily interest (Selic rate). Federal penalties for PIS/COFINS and IPI errors follow similar structures, with fines of 75% of the tax difference for standard cases and 150% for fraud, concealment, or collusion. SEFAZ rejections (when the NF-e XML fails validation) prevent issuance entirely and must be corrected before goods can legally ship -- treat rejection patterns as urgent operational issues. Customers may refuse payment until chave de acesso validation succeeds in their AP tools. Contingency workflows for SEFAZ outages (using contingency NF-e modes like FS-DA or SVC) must still respect statutory issuance windows -- document any deviations with your fiscal adviser.

Run parallel tests whenever you onboard a new SKU cluster so NCM, CFOP, and ICMS benefit flags validate in a sandbox before the first production NF-e leaves your ERP. Name a custodian for XML archives so auditors receive full chains, not email attachments alone. Monthly, reconcile issued access keys to revenue recognition entries.

FAQ

What is the difference between NF-e and NFS-e? NF-e (Nota Fiscal Eletronica) covers goods and some mixed transactions, authorized through state SEFAZ systems. NFS-e (Nota Fiscal de Servicos Eletronica) covers services, authorized through municipal systems. The distinction matters because the tax structures differ (ICMS/IPI for goods versus ISS for services), and the issuing authority, validation system, and XML schema are all different. Some operations involve both -- for example, a sale of goods with installation services may require separate fiscal documents or a combined treatment depending on the contract structure and local rules.

Do I need a Brazilian entity to issue NF-e? Yes. NF-e issuance requires a CNPJ (Brazilian business registration), a digital certificate (e-CPF or e-CNPJ from an ICP-Brasil accredited authority), and registration with the relevant state SEFAZ. Foreign companies selling into Brazil typically work through a Brazilian importer or establish a local legal entity. Direct cross-border e-commerce below certain thresholds may use simplified customs processes, but the NF-e obligation generally applies to the Brazilian importing entity.

How does the upcoming tax reform affect my invoices? Brazil's tax reform (EC 132/2023) will phase in a dual VAT system replacing current indirect taxes. The transition period is expected to run from 2026 through 2033, with the new IBS (state/municipal) and CBS (federal) taxes gradually replacing ICMS, ISS, IPI, PIS, and COFINS. During the transition, you may need to show both old and new tax calculations on fiscal documents. Monitor the technical specifications from the Receita Federal and state SEFAZ systems for updated NF-e schemas.

What happens during a SEFAZ outage? Brazil provides contingency modes for NF-e issuance when the primary SEFAZ is unavailable. These include SVC (Sefaz Virtual de Contingencia), FS-DA (Formulario de Seguranca - Documento Auxiliar), and EPEC (Evento Previo de Emissao em Contingencia). Each has specific rules for when it can be used and how quickly the NF-e must be regularized once SEFAZ comes back online. Your ERP should be configured to switch to contingency mode automatically and to reconcile contingency documents afterward.

Template link

Start from our Brazil invoice template as a human-readable companion to authorised XML—never treat the template alone as Brazilian tax evidence. Read the invoice tax compliance guide and tax rate lookup tool. Official references include the Receita Federal and gov.br services for electronic invoicing. Join InvoiceQuickly early access to organise Brazil billing alongside your other markets.