Brazil NF-e / NFS-e Electronic Invoicing

Name: Brazil NF-e / NFS-e Electronic Invoicing
Brand: ECOSIRE
SKU: brazil-nfe-nfse-einvoicing

Key Features

NF-e (model 55) XML generation in the current SEFAZ 4.00 layout, digitally signed with your A1 or A3 certificate

SEFAZ authorization workflow with autorização, denegação and rejeição handling, storing the returned protocol number and 44-digit chave de acesso

NFS-e issuance via municipal web-service integration, adaptable to your city's schema (ABRASF-based or proprietary layouts)

DANFE and DANFSE PDF printing as native QWeb reports, including the barcode, access key and fiscal legends

CFOP, NCM, CEST and CST/CSOSN classification fields added to products and invoice lines for correct fiscal coding

Automated ICMS, ICMS-ST, IPI, PIS and COFINS computation via @api.depends compute methods that recalc on any line change

Fiscal position and operation-type driven tax mapping so the same product bills correctly across states and CFOPs

Correction letter (CC-e) and cancellation (cancelamento) events transmitted and logged against the original document

Contingency and retry handling via scheduled automated actions that poll SEFAZ status and resubmit stuck documents

Support for Simples Nacional, Lucro Presumido and Lucro Real regimes, including CSOSN codes and DIFAL where applicable

Role-based security through ir.model.access.csv and record rules restricting who can issue, cancel or view fiscal documents

XML/PDF archival with the signed XML stored per document so it is retrievable for the legally required retention period

JSON-RPC / XML-RPC endpoints so external systems (e-commerce, WMS, POS) can trigger issuance and read authorization status

Compatible with Odoo 17, 18 and 19 on Community or Enterprise, integrating with existing account.move accounting flows

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Selling goods or services in Brazil means every invoice is a legally mandated electronic fiscal document — an NF-e for goods (Nota Fiscal Eletrônica, model 55) or an NFS-e for services (Nota Fiscal de Serviço Eletrônica) — that must be signed, transmitted to SEFAZ (or the relevant municipal web service), authorized, and printed as a DANFE before merchandise can legally circulate. Odoo core does not do this out of the box, and gluing together a generic third-party module rarely survives the reality of 26 states plus the Distrito Federal, hundreds of municipal NFS-e layouts, and the constant SEFAZ layout and rule revisions.

This is a BUILD-TO-ORDER module. It is not an instant apps.odoo.com download. ECOSIRE designs, builds, installs, and supports a Brazil fiscal-invoicing module tailored to your states, municipalities, CFOP/NCM catalog, and tax regime (Simples Nacional, Lucro Presumido, or Lucro Real), running on your Odoo 17, 18, or 19 (Community or Enterprise). You purchase the engagement here; our team then scopes, develops, and deploys over a typical 2–4 week lead time.

Under the hood the module is real Odoo engineering, not a black box. New models (models.Model) extend account.move and account.move.line to carry fiscal fields — CFOP, NCM, CST/CSOSN, origem, and per-tax bases — with computed values driven by @api.depends so ICMS, ICMS-ST, IPI, PIS and COFINS recalculate whenever quantities, prices, or fiscal positions change. XML for NF-e (layout 4.00) and the municipal NFS-e schema is generated and digitally signed with your A1/A3 certificate, then transmitted to SEFAZ or the city web service and reconciled against the returned authorization protocol and access key. Access is locked down with ir.model.access.csv and record rules so only fiscal roles can authorize or cancel documents. The DANFE and DANFSE are rendered as QWeb PDF reports with the barcode and access key. Automated actions and scheduled jobs handle contingency retries and status polling, and a JSON-RPC/XML-RPC surface lets your e-commerce or WMS trigger issuance programmatically. You receive the source, so nothing is locked behind a vendor you can never reach.

What you get

The complete, installable Odoo module source code (models, views, security, QWeb reports) with a documented __manifest__.py declaring dependencies and version

Configuration of your company fiscal profile: certificate installation, SEFAZ/municipal endpoints, tax-regime setup, CFOP/NCM/CST catalog and fiscal positions

Installation and deployment on your Odoo 17/18/19 environment (staging first, then production) with a validation pass in the SEFAZ homologação (test) environment

Technical and user documentation covering issuance, cancellation, correction letters, DANFE printing and the API surface

A live training session for your finance and operations team, with a recording and quick-reference guide

A post-go-live support and bug-fix window to stabilize real transmissions and resolve SEFAZ rejection codes

Source handover and a short maintenance/updates plan so you can track future SEFAZ layout and municipal-schema changes

Who this is for

Brazilian SMB finance lead

A controller or fiscal manager at a company operating in Brazil who must issue compliant NF-e or NFS-e for every sale and needs the process inside Odoo instead of a separate emissor, with the right ICMS/IPI/PIS/COFINS logic for their regime.

LATAM Odoo implementation partner

An Odoo partner delivering ERP to a Brazilian client who needs a reliable, source-available fiscal layer they can hand off, rather than betting the project on an unmaintained community module they cannot fully support.

E-commerce / omnichannel operations manager

Runs high order volume and needs invoices issued and authorized automatically at fulfillment time via the API, with contingency retries so a SEFAZ outage never blocks shipping.

Multi-state distributor / importer

Sells across several Brazilian states and municipalities and needs correct CFOP, ICMS-ST and DIFAL handling plus both NF-e for goods and NFS-e for any service lines from one Odoo instance.

How Brazil NF-e / NFS-e Electronic Invoicing Compares

Criterion	ECOSIRE	Custom Build	Competitor
NF-e + NFS-e issuance out of the box	Included	Built from scratch — long and error-prone	Varies; often NF-e only or partial NFS-e
SEFAZ + municipal transmission and authorization	Included	You must implement signing, transmission and protocol handling	Usually yes for NF-e; municipal coverage inconsistent
ICMS / IPI / PIS / COFINS + CFOP/NCM/CST logic	Included	Hand-coded per regime — high risk of gaps	Present but hard to adapt to your regime
DANFE / DANFSE QWeb PDF printing	Included	Must design the report yourself	Generic layout, limited customization
Tailored to your states, municipalities and regime	Included	Included	Not included
Source code ownership and adaptability	Included	Included	Partial support
Odoo 17 / 18 / 19, Community + Enterprise	Included	Depends on your build	Often lags new Odoo versions
Expert support for SEFAZ rejections & layout changes	Included	Your team alone	Ticket queue, no code context

Frequently Asked Questions about Brazil NF-e / NFS-e Electronic Invoicing

How long until the module is delivered and live?

This is a build-to-order engagement, not an instant download. Typical lead time is 2–4 weeks from kickoff, depending on how many states and municipalities you operate in and how complex your tax regime is. We start in the SEFAZ homologação (test) environment, validate real authorizations there, then cut over to production. You will get a scoped timeline with milestones before development begins.

What ongoing support and updates do I get after go-live?

Every engagement includes a post-go-live support window to stabilize live transmissions and resolve SEFAZ rejection codes. Because SEFAZ periodically revises the NF-e layout and municipalities change their NFS-e schemas, we also offer a maintenance plan to keep the module current with those changes. You receive the full source code, so you are never locked to us — but our team knows the codebase and can update it fastest.

Does this work with my Odoo version and edition?

Yes. The module targets Odoo 17, 18 and 19 and works on both Community and Enterprise. It extends the standard account.move / account.move.line accounting flow rather than replacing it, so your existing invoicing, journals and reporting continue to work. We confirm your exact version and installed apps during scoping so the __manifest__.py dependencies match your environment.

Does it handle both NF-e for goods and NFS-e for services?

Yes. NF-e (model 55) covers goods and is transmitted to your state SEFAZ; NFS-e covers services and is transmitted to the relevant municipal web service. Because municipal NFS-e layouts vary widely across Brazilian cities, we adapt the NFS-e integration to the specific municipalities you invoice from — tell us which cities during scoping.

What do you need from me to build and configure it?

Your A1 or A3 digital certificate (or coordination to install it), your tax regime (Simples Nacional, Lucro Presumido or Lucro Real), the states and municipalities you operate in, your product catalog with NCM codes, and access to a staging Odoo instance. We handle the CFOP/CST mapping, fiscal positions, SEFAZ and municipal endpoints, and the DANFE/DANFSE report layout.

Can external systems trigger invoice issuance automatically?

Yes. The module exposes JSON-RPC / XML-RPC endpoints so your e-commerce store, WMS or POS can create and authorize documents programmatically at order or fulfillment time. Scheduled automated actions poll SEFAZ for status and retry documents caught in contingency, so a temporary SEFAZ outage does not block your operations.