Invoice Requirements in Brazil: Legal Rules for 2026

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.

Penalties

Federal and state agencies may assess tax, fines, and interest for unauthorised documents, late issuance, or misdeclared taxes. Customers may refuse payment until chave validation succeeds in their AP tools. Contingency workflows for SEFAZ outages should still respect statutory issuance windows—document any late batching with your fiscal adviser rather than improvising after the fact.

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; breaks between fiscal and management reporting are where state auditors focus first.

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.