Este módulo integra a parte fiscal do módulo l10n_br_fiscal com o módulo de compra purchase do Odoo. O módulo permite o cálculo dos impostos brasileiros já no pedido de compra e propaga a operação fiscal até a nota fiscal de compra, deixando ela com a tributação mais correta possível para seu financeiro (sendo que vocẽ poderia também importar o XML da nota depois).
O relatório de compra também é estendido para apresentar os impostos brasileiros.
Este módulo é indicado para a compra de itens com NFe's. Mas se você quer gerenciar suas notas de entradas de acordo com o recebimento do material, você pode também ter interesse no módulo l10n_br_purchase_stock que permite isso.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Adds Brazilian fiscal operations and tax calculation to purchase orders, so purchase taxes (ICMS, IPI, PIS, COFINS, etc.) are computed on the order and carried through to the vendor bill.
This module brings Brazilian tax rules into the purchasing flow. When the company is Brazilian, a Fiscal Operation field appears on the purchase order and on each order line, with a default taken from the company settings. Only approved operations of type purchase, other or purchase_refund can be chosen.
On each order line, users pick a fiscal operation and an operation line; the related Brazilian taxes are then filled in automatically and the line and order totals are recalculated from those fiscal amounts instead of the standard taxes. Extra cost fields (freight, insurance, other costs) and a discount value are available, and the order form shows gross amount, discount and the freight/insurance/other totals.
When the order is turned into a vendor bill, the fiscal operation, document type and final-consumer flag are copied to the bill, and the fiscal data of each line is transferred too. A company setting defines the default fiscal operation for purchases.
The purchase analysis report gains Brazilian columns (fiscal operation, CFOP, NCM, NBM, CEST, product fiscal type, ICMS, ICMS ST, IPI, PIS, COFINS, II, freight, insurance, other costs and total with taxes) and new grouping filters. The printed purchase order also shows gross, discount, freight, insurance and other costs.
A user group controls whether order lines open in a popup with the full Brazilian fiscal details. On installation, purchase journals are linked to the standard purchase fiscal operations for the demo companies.
Depends on
Required by other modules
Models and fields (5)
- res.company · extends an existing modelpurchase_fiscal_operation_id (Default Fiscal Operation for Purchase)
- account.move · extends an existing model
- purchase.order · new modelcomment_ids (Comments), fiscal_operation_id, active_company_country_id (Active Company Country)
- purchase.report · extends an existing modelnbm_id (NBM), ncm_id (NCM), cest_id (CEST), cfop_id (CFOP), ii_value (II Value), ipi_value (IPI Value), pis_value (PIS Value), icms_value (ICMS Value), fiscal_type (Tipo Fiscal), other_value, cofins_value (COFINS Value), icmsst_value (ICMS ST Value), freight_value, insurance_value, total_with_taxes, fiscal_operation_id (Fiscal Operation), fiscal_operation_line_id (Fiscal Operation Line)
- purchase.order.line · new modeluom_id (Mixin UOM), quantity (Mixin Quantity), comment_ids (Comments), tax_framework (Tax Framework), delivery_costs, fiscal_operation_id, fiscal_operation_line_id (Operation Line)
Text generated by AI (DeepSeek) from reading the Odoo 19.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: 7 confirmed, 2 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/l10n-brazil.
terminal Installation and usage
OCA documentation · Odoo 19.0Installation
Source · Odoo 19.0This module depends on:
- purchase
- l10n_br_account
Configuration
Source · Odoo 19.0No configuration required.
No verified information in OCA: Usage.
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.