Este módulo permite a criação da base de Notas Fiscais de Serviço Eletrônicas (NFS-e). O documento criado é genérico por isso necessita do módulo do serviço específico de transmissão.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Adds the foundation for issuing Brazilian electronic service invoices (NFS-e) in Odoo, with RPS numbering, service tax data, company NFS-e settings and a printable service invoice report.
This module prepares Odoo to handle Brazilian electronic service invoices (NFS-e). It does not transmit invoices by itself; it provides the data structure and screens that a city-specific transmission module will use.
On a fiscal document of type service (l10n_br_fiscal.document) it adds fields such as RPS number, RPS type, operation nature, special taxation regime, verification code, NFS-e environment, and civil construction code and ART. When the document is a service invoice, the RPS number is generated automatically from the document series. A red banner shows the rejection reason when the document is rejected.
On each document line it adds a Fiscal Deductions value, which can be pre-filled from the product, and an Other Retentions value. These feed the service tax totals (ISS, PIS, COFINS, INSS, IR, CSLL, deductions, net amount) that are assembled for the invoice.
On the company form, a new NFS-e tab lets you set the NFS-e environment, cultural sponsor flag, provider, city logo, website and whether to use the city's PDF. Products get a Fiscal Deductions field.
A PDF report called 'Nota de Serviço' prints the service invoice with provider and customer data, service description, tax codes and federal taxes. The generated PDF is stored as an attachment on the document.
Required by other modules
Models and fields (6)
- res.company · extends an existing modelnfse_website (NFSe Website), provedor_nfse (NFSe Provider), nfse_city_logo (NFSe City Logo), nfse_ssl_verify (NFSe SSL Verify), cultural_sponsor, nfse_environment (NFSe Environment), nfse_use_city_pdf (Use City NFSe PDF), city_taxation_code_id (City Taxation Code)
- res.partner · extends an existing model
- product.template · extends an existing modelfiscal_deductions_value (Fiscal Deductions)
- l10n_br_fiscal.document · extends an existing modelrps_type, rps_number (RPS Number), verify_code, nfse_environment (NFSe Environment), operation_nature, edoc_error_message, civil_construction_art (Civil Construction ART), civil_construction_code, taxation_special_regime
- l10n_br_fiscal.document.line · extends an existing modelother_retentions_value (Other Retentions), fiscal_deductions_value (Fiscal Deductions)
- l10n_br_fiscal.base.wizard.mixin · extends an existing modelrps_number
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. The module is very large and only part of the code was read. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 6 confirmed, 3 with no information of 9 versions.
Sources · Odoo 17.0
Confirmed on 2026-11-03 in branch 17.0 of OCA/l10n-brazil.
terminal Installation and usage
OCA documentation · Odoo 18.0Installation
Source · Odoo 18.0- Este módulo tem uma depedencia do pacote python erpbrasil.edoc
- Este módulo tem uma depedencia do pacote python erpbrasil.assinatura
- Este módulo tem uma depedencia do pacote python erpbrasil.transmissao
- Este módulo tem uma depedencia do pacote python erpbrasil.base
Configuration
Source · Odoo 18.0Após a instalação do módulo, deve ser configurado a empresa nos seguintes pontos:
- Na aba Fiscal -\> Documentos Eletrônicos: Selecionar no campo Processador de Documentos Eletrônicos o registro erpbrasil.edoc.
- Na aba Fiscal -\> Certificados: Atribuir um certificado correspondente.
Usage
Source · Odoo 18.0Após o módulo do serviço de transmissão necessário ser instalado, crie um documento do tipo Notas Fiscais de Serviço Eletrônicas (NFS-e) para ser possível confirmá-lo e transmiti-lo.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.