This module adds ecotax amount on invoice line. furthermore, a total ecotax is added at the footer of each document.
To make easy ecotaxe management and to factor the data, ecotaxes are set on products via ECOTAXE classifications. ECOTAXE classification can either be a fixed or weight based ecotax.
A product can have one or serveral ecotax classifications. For example, wooden window blinds equipped with electric motor can have ecotax for wood and ecotax for electric motor.
This module has some limits : - The ecotax amount is always included in the price of the product. - The ecotax amount is not isolated in an specific accounting account but is included in the product income account.
If one of these limits is an issue, you could install the submodule account_ecotax_tax. This second module lets you manage the ecotax as a tax, so you can configure if you want it to be included or excluded of product price and also configuring an accounting account to isolate it. The main consequence of this approach is that the ecotax won't be considered in the turnover, since it is considered as a tax.
This module version add the possibility to manage several ecotax classifications by product. A migration script is necessary to update from previous versions.
There is the main change to manage in migration script:
renamed field model old field new field account.move.line unit_ecotaxe_amount ecotaxe_amount_unit product.template manual_fixed_ecotaxe force_ecotaxe_amount
changed fields model old field new field product.template ecotaxe_classification_id ecotaxe_classification_ids
added fields model new field account.move.line ecotaxe_line_ids product.template ecotaxe_line_product_ids
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Manage ecotaxes (environmental fees) on products and customer invoices. Define ecotax classifications, attach them to products, and see the ecotax amount per invoice line and as a total on the invoice.
This module lets you set up ecotax data once and reuse it on products and invoices.
In Accounting > Configuration > Ecotax you get four menus: Category, Classification, Sector and Collector. A Classification defines how the ecotax is calculated: either a fixed amount or a weight-based amount (a coefficient multiplied by the product weight). It also stores the category, sector, collector, product status (Domestic/Professional), supplier status, Intrastat code and scale code, and can be limited to one company.
On a product (product.template and product.product) you can attach one or more ecotax classifications, each with an optional forced amount. Odoo then computes the fixed ecotax, the weight-based ecotax and the total ecotax amount for the product. A product can have several classifications, and a variant can add extra ones on top of the template's. A search filter "Has ecotax" helps find such products.
On customer invoices and credit notes (out_invoice, out_refund, out_receipt), each invoice line gets ecotax lines that are created automatically from the product's classifications. You can open the "Ecotax" button to review or force the unit amount. Each line shows the ecotax per unit and the ecotax subtotal, and the invoice shows the total included ecotax near the tax totals. The ecotax is included in the product price and posted to the product's income account.
Depends on
Required by other modules
Menus it adds
Models and fields (11)
- account.move · extends an existing modelamount_ecotax (Included Ecotax)
- ecotax.sector · new modelname, active, description
- product.product · extends an existing modelfixed_ecotax, ecotax_amount, weight_based_ecotax, all_ecotax_line_product_ids (All Ecotax Lines), additional_ecotax_line_product_ids (Additional Ecotax Lines)
- ecotax.collector · new modelname, active, partner_id
- product.template · extends an existing modelfixed_ecotax, ecotax_amount, weight_based_ecotax, ecotax_line_product_ids (Ecotax Lines)
- account.move.line · extends an existing modelecotax_line_ids (Ecotax Lines), subtotal_ecotax (Ecotax), ecotax_amount_unit (Ecotax Unit)
- ecotax.line.mixin · new modelquantity, product_id, amount_unit, currency_id, amount_total, classification_id, force_amount_unit
- ecotax.line.product · new modelamount, product_id, currency_id, display_name, force_amount, product_tmpl_id (Product Template), classification_id
- account.ecotax.category · new modelcode, name, active, description
- account.move.line.ecotax · new modelquantity, product_id, currency_id, account_move_line_id (Journal Item)
- account.ecotax.classification · new modelcode, name, active, categ_id (Category), sector_id (Ecotax sector), company_id, scale_code, ecotax_coef, ecotax_type, collector_id (Ecotax collector), intrastat_code, product_status, supplier_status, default_fixed_ecotax
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: 4 confirmed, 5 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/account-fiscal-rule.
terminal Installation and usage
OCA documentation · Odoo 19.0Usage
Source · Odoo 19.0- Add an ecotax classification via the menu Accounting \> Configuration \> Taxes \> Ecotax Classification.
- The ecotax classification can be either a fixed ecotax or a weight-based ecotax.
- Ecotax classification information can be used for legal declarations.
- For the fixed ecotax, the ecotax amount is used as a default value, which can be overridden on the product.
- For the weight-based ecotax, define one ecotax by a coefficient applied to the weight (depending on the product's materials).
- Assign one or more ecotax classifications to a product.
- The ecotax amount can also be manually overridden on the product.
- Create an invoice with this product
No verified information in OCA: Installation, Configuration.
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.