示意预览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.
什么是 Brazil NF-e / NFS-e Electronic Invoicing？
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. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Odoo 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
技术规格
- Odoo 兼容性
- Odoo 17, Odoo 18, Odoo 19
- 版本
- 企业版和社区版
- 许可证
- 许可证需要确认
- Python 要求
- Python 3.10+
- 数据库
- PostgreSQL 12+
关于此产品
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 one working 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.
你得到什么
- 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
这是给谁的
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.
Brazil NF-e / NFS-e Electronic Invoicing 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| 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 | 不包括在内 |
关于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 one working week 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.
相关模块
Brazil NF-e / NFS-e Electronic Invoicing
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.
- 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