LATAM · SEFAZ (state) / Receita Federal
Brazil
Updated in last 30 days·Atlas data current as of
World's most complex e-invoicing regime. Each document type (NF-e goods, NFS-e services, NFCom telecom, CT-e transport) has its own clearance flow. National NFS-e standard mandatory 1 Jan 2026 (except Sao Paulo). Technical Note 2025.002-RTC v1.40 adds the IBS/CBS/IS groups for the consumption tax reform: mandatory in NF-e and NFC-e for general-regime taxpayers from 3 Aug 2026. Joint Act RFB/CGIBS 4/2026 (30 Jul 2026) sets the per-document calendar running to 1 Jan 2027.
Cloudare has shipped 1 🇧🇷 Brazil integration · talk to us →// Phased rollout
- 01 Apr 2008 · liveNF-e nationwideGoods invoicing fully clearance-based.
- 01 Apr 2023 · liveNFS-e (municipal then national)Phased adoption of national NFS-e standard via Complementary Law 68.
- 01 Jan 2026 · liveNational NFS-e mandatoryAll municipalities except São Paulo migrate to national standard.
- 01 Jan 2026 · liveIBS/CBS/IS fields operationalTax reform layout with new tax groups via Technical Note 2024.001.
- 01 Dec 2026 · upcomingNF-e for non-ICMS IBS/CBS taxpayersNew NF-e model for IBS/CBS taxpayers that are not ICMS contributors becomes mandatory. Per Joint Act RFB/CGIBS 4/2026.
// Penalties
100% of tax due for non-issuance; ICMS / IPI penalties; suspension of registration.
// What you have to do
- Confirm which of your flows are in scopeB2B is mandatory, B2G is mandatory, B2C is mandatory.
- Emit one of NF-e v4.00 (XML) or NFS-e (national standard) or NFCom or CT-e or MDF-e or CF-eYour ERP must produce this syntax, not a PDF or a print stream.
- Connect via State SEFAZ web services or ICP-Brasil signed XMLThis is the channel, separate from the format. Most projects underestimate it.
- Plan for the Clearance modelThe regulator validates before the invoice is legally issued, so a rejection blocks the sale. Build the rejection path first.
- Retain for 5 yearsArchive the structured original, not a rendering of it.
- Understand the exposure100% of tax due for non-issuance; ICMS / IPI penalties; suspension of registration.
// ERP implementation notes
SAP S/4HANA (incl. DRC) & SAP ECC
SAP DRC Brazil: BR_INVOICE; one of SAP's most mature scenarios; supports all major doc types via partner integrators (Synchro, TOTVS, Mastersaf).
Microsoft Dynamics 365 (F&O + Business Central)
D365 F&O Brazil retains legacy X++ Tax Engine; new ER-based preview discontinued.
Oracle NetSuite
NetSuite Brazil Localization (BRA SuiteApp) covers NF-e, NFS-e and tax reform.
// Implementation playbook
Cloudare has shipped 1 Brazil integrations. We will email you the full implementation playbook for Brazil — typical project plan, ERP-by-ERP gotchas, regulator-specific edge cases, sample test data. No marketing.
// Frequently asked questions
NF-e, NFS-e, CT-e — which apply to me?
Depends on what you sell. NF-e (goods, federal/state-level), NFS-e (services, municipal-level — historically fragmented across 5,500+ municipalities, now being nationalised), CT-e (transport), NFC-e (consumer/retail). Most businesses need NF-e + NFS-e at minimum; service companies primarily NFS-e.
What's the national NFS-e initiative changing?
From 2026, Brazil is rolling out a unified national NFS-e layout to replace the 5,500+ municipal variants. Issuance still happens via municipal portals but with a standardised schema. This dramatically simplifies the integration burden for businesses operating across multiple cities.
How does the Reforma Tributária impact e-invoicing?
Brazil's tax reform (CBS, IBS replacing PIS/COFINS/ICMS/ISS) phases in from 2026 with full implementation by 2033. E-invoicing schemas will need updates to carry the new tax codes. NF-e and NFS-e schemas will iterate; ERPs will need pattern updates over the transition period.
Which ERPs handle Brazilian e-invoicing?
SAP DRC Brazil is foundational — Brazil was one of the earliest DRC countries. Oracle Fusion via Tax Reporting Cloud + Brazilian localisation. Microsoft Dynamics 365 F&O with Brazilian localisation. TOTVS (dominant in Brazilian mid-market) has native NF-e/NFS-e. SAP Localization Hub TaxGov. Senior, Sankhya — Brazilian-native options.
What about cross-state ICMS?
Brazil's complexity isn't just the schemas — it's the tax code logic. ICMS varies by origin state, destination state, product, and contributor type. Substitution rules, DIFAL, FCP layers... an ERP that correctly emits NF-e XML but mishandles ICMS calculation is worse than no integration. Cloudare typically pairs NF-e work with tax-engine selection.