Build-to-order Odoo module to issue NF-e & NFS-e in Brazil: SEFAZ authorization, DANFE/DANFSE printing, and full ICMS/IPI/PIS/COFINS tax logic. One-time license from $599.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Build-to-order Odoo module to issue NF-e & NFS-e in Brazil: SEFAZ authorization, DANFE/DANFSE printing, and full ICMS/IPI/PIS/COFINS tax logic.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
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.
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
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.
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.
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.
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.
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.
Buy the license on ecosire.com and download the Brazil NF-e / NFS-e Electronic Invoicing module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Brazil NF-e / NFS-e Electronic Invoicing, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| NF-e + NFS-e issuance out of the box | Built from scratch — long and error-prone | Varies; often NF-e only or partial NFS-e | ||
| SEFAZ + municipal transmission and authorization | You must implement signing, transmission and protocol handling | Usually yes for NF-e; municipal coverage inconsistent | ||
| ICMS / IPI / PIS / COFINS + CFOP/NCM/CST logic | Hand-coded per regime — high risk of gaps | Present but hard to adapt to your regime | ||
| DANFE / DANFSE QWeb PDF printing | Must design the report yourself | Generic layout, limited customization | ||
| Tailored to your states, municipalities and regime | ||||
| Source code ownership and adaptability | ||||
| Odoo 17 / 18 / 19, Community + Enterprise | Depends on your build | Often lags new Odoo versions | ||
| Expert support for SEFAZ rejections & layout changes | Your team alone | Ticket queue, no code context |
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.
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.
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.
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.
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.
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.
Build-to-order Odoo module to issue NF-e & NFS-e in Brazil: SEFAZ authorization, DANFE/DANFSE printing, and full ICMS/IPI/PIS/COFINS tax logic.