Country deep dive
Brazil's NF-e system has run since the mid-2000s with near-universal adoption — the live story today is the consumption tax reform being layered into the existing infrastructure.
Brazil pioneered clearance-model e-invoicing in Latin America — goods cannot legally ship without a SEFAZ-authorised NF-e.
Originally due 3 April 2023, this brought Brazil's smallest formal businesses into structured service-invoice reporting via the emerging national NFS-e framework.
Defines the CST tax codes for the three new consumption taxes — CBS, IBS, and the Selective Tax (IS) — and begins the long process of updating NF-e/NFC-e XML layouts for the reform.
Formally institutes IBS, CBS, and the Selective Tax, replacing PIS, COFINS, IPI, ICMS, and ISS under a Dual VAT model — the legal foundation for everything that follows.
Businesses can trial the new CST codes and CBS/IBS/IS fields against SEFAZ's homologation servers ahead of go-live.
The rule that would reject invoices missing IBS/CBS fields is marked "future implementation" rather than enforced immediately — a technical relaxation, but explicitly not a legal exemption.
Companies under the Normal Tax Regime must include CBS (0.9%) and IBS (0.1%) test-rate data in NF-e/NFC-e documents. Missing data won't cause rejection during this "soft-landing" window (through April 2026), but the underlying legal requirement is already in force.
Authorization systems begin rigorously checking CBS/IBS field consistency — invoices with missing or inconsistent data now risk rejection.
Under Technical Note 2025.002-RTC v1.40, General Tax Regime taxpayers must report IBS and CBS groups with full legal effect — failure risks document rejection in the production environment, which in practice halts the movement of goods.
Actual tax collection under CBS and the Selective Tax starts in 2027, with the legacy taxes (PIS, COFINS, IPI, ICMS, ISS) phased out entirely by 2033 — this is a genuinely multi-year transition, not a single cutover date.
Brazil's XML depth is genuinely unusual — this is a far more granular structure than most European e-invoicing standards.
The DANFE contains less than 10% of the XML's data — treat any AP process that only reads the DANFE as manually re-keying information that already exists in structured form, and likely missing tax detail that affects input credit recovery.
This single key is all you need to verify an NF-e's authenticity, check whether it's been cancelled, or retrieve the full XML directly from SEFAZ — treat it as the universal reference for any Brazilian invoice.
Both certificate types are valid — A1 suits automated high-volume issuance, A3 suits lower-volume or higher-security scenarios, but confirm which your specific ERP integration supports.
Debit and Credit Notes are a genuinely new instrument, not a repurposed old one — but they explicitly cannot be used to adjust legacy ICMS or IPI unless that legislation is separately amended.
Brazil doesn't run one e-invoicing system — it runs several, split by transaction type and level of government, each with its own quirks.
Which system applies depends entirely on what you're invoicing — goods, transport, and retail sit with the state; services sit with the municipality, and municipal requirements vary significantly.
The NF-e is also transmitted to the Receita Federal do Brasil's national repository (Ambiente Nacional) — a federal-level backstop that exists alongside the state-level authorization.
SNNFS-e adoption is gradual and not yet mandatory everywhere — check your specific municipality's current status rather than assuming national standardisation has already happened.
This is an emerging piece of the reform architecture — automatic tax remittance at the point of payment — worth tracking even though it's not yet a live obligation.
Because the tax reform sits on top of a mature existing system, "getting ready" here mostly means upgrading what you already run, not building from scratch.
Choose A1 or A3 depending on your volume and infrastructure, from an accredited certificate authority — this is required before you can sign a single NF-e.
Set up certificate, environment, NF-e version, authority, schema validation, and contingency mode per fiscal establishment in your ERP — this is genuinely per-establishment configuration, not a one-time global setting.
Map the new IBS, CBS, and IS fields and updated CST tax codes into your invoicing layouts — check the version number carefully, as this note has been revised multiple times through 2025–2026.
Use the same certificates as production, pointed at test servers, to validate your new tax-reform fields before they affect real invoices.
Implement the formalised model-55 Debit and Credit Note instruments for CBS/IBS adjustments — remembering they can't be used for legacy ICMS/IPI corrections without separate legislative change.
If you issue service invoices, confirm your municipality's current NFS-e specification and SNNFS-e adoption status separately — don't assume national uniformity yet.
Simples Nacional and MEI businesses generally have an extended transition (through 2027) compared to Normal/General Tax Regime taxpayers — verify which applies to you before assuming the same deadlines.
In Brazil, rejection is often the sharper practical risk — a blocked invoice halts the movement of goods, which frequently matters more than the fine itself.