Daily updates from Odoo
Wednesday, December 31, 2025
11 changes
3 changes
Enhancements to existing features
This update adjusts payroll rule parameters to reflect changes in US tax regulations for the 2026 tax year. Ensuring these parameters are current is crucial for accurate salary calculations and maintaining compliance with US payroll laws. This change supports ongoing operational accuracy.
Original PR description
Purpose: Certain US Payroll values changes yearly. The payroll rule parameters must be updated for accurate salary calculation for 2026 for compliance. task-5409739 Forward-Port-Of: odoo/enterprise#102759 Forward-Port-Of: odoo/enterprise#102711
This update reflects changes to Mexican withholding tax rates (ISR) mandated by the latest tax resolution. The update adjusts the ‘Mexico: ISR Table’ parameter in the Odoo system to align with the new tax tables effective January 1, 2026. This ensures accurate tax calculations for Mexican businesses using Odoo Enterprise.
Original PR description
According to the Mexican Tax Resolution (Resolución Miscelánea Fiscal 2026: https://dof.gob.mx/2025/SHCP/SHCP_281225_01.pdf), the ISR withholding tax tables applicable for the fiscal year have changed, effective January 1, 2026. It is necessary to add a new parameter value for “Mexico: ISR Table” to reflect the new values. target: 19.0 task: 5448019 Forward-Port-Of: odoo/enterprise#103009
This update prepares Odoo for Brazil's upcoming shift to a new consumption tax system starting in 2026. Users can enable this new system based on their business location and transaction types. The changes adapt existing tax calculation modules to comply with the new requirements, utilizing Avalara for tax processing.
Original PR description
2026 marks the start of Brazil's 8-year plan to migrate to a completely new consumption tax system [1]. The new system is meant to be simpler than the old one, but we defer to Avalara for tax…
2026 marks the start of Brazil's 8-year plan to migrate to a completely new consumption tax system [1]. The new system is meant to be simpler than the old one, but we defer to Avalara for tax calculation so we don't really notice it technically. The old and new system have to coexist for the foreseeable future because the rollout happens gradually over many years. Whether the new system has to be enabled depends on the federal state the business is in, the type of transactions they do, and other factors. The user has the option to enable it through the l10n_br_is_icbs Boolean flag on the company, which gates all the new functionality. These changes impact both tax calculation and EDI. This set of modules adapts our existing l10n_br* modules to the new requirements set out by Avalara. We are required to send extra values to their API, and in some cases adapt existing ones. task-4939796 [1] https://www.planalto.gov.br/ccivil_03/leis/lcp/lcp214.htm Forward-Port-Of: odoo/enterprise#102706
1 change
Enhancements to existing features
This update prepares Odoo for Brazil's upcoming shift to a new consumption tax system starting in 2026. Users can enable this new system based on their business location and transaction types, and the changes impact both tax calculations and electronic data interchange (EDI) processes. This ensures Odoo remains compliant with evolving Brazilian tax regulations.
Original PR description
2026 marks the start of Brazil's 8-year plan to migrate to a completely new consumption tax system [1]. The new system is meant to be simpler than the old one, but we defer to Avalara for tax…
2026 marks the start of Brazil's 8-year plan to migrate to a completely new consumption tax system [1]. The new system is meant to be simpler than the old one, but we defer to Avalara for tax calculation so we don't really notice it technically. The old and new system have to coexist for the foreseeable future because the rollout happens gradually over many years. Whether the new system has to be enabled depends on the federal state the business is in, the type of transactions they do, and other factors. The user has the option to enable it through the l10n_br_is_icbs Boolean flag on the company, which gates all the new functionality. These changes impact both tax calculation and EDI. This set of modules adapts our existing l10n_br* modules to the new requirements set out by Avalara. We are required to send extra values to their API, and in some cases adapt existing ones. task-4939796 [1] https://www.planalto.gov.br/ccivil_03/leis/lcp/lcp214.htm Forward-Port-Of: odoo/enterprise#102706
4 changes
Enhancements to existing features
This update prepares Odoo for Brazil's upcoming shift to a new consumption tax system starting in 2026. Users can enable this new system based on their business location and transaction types, and it impacts both tax calculations and EDI processes. The changes adapt existing modules to comply with Avalara's requirements.
Original PR description
2026 marks the start of Brazil's 8-year plan to migrate to a completely new consumption tax system [1]. The new system is meant to be simpler than the old one, but we defer to Avalara for tax…
2026 marks the start of Brazil's 8-year plan to migrate to a completely new consumption tax system [1]. The new system is meant to be simpler than the old one, but we defer to Avalara for tax calculation so we don't really notice it technically. The old and new system have to coexist for the foreseeable future because the rollout happens gradually over many years. Whether the new system has to be enabled depends on the federal state the business is in, the type of transactions they do, and other factors. The user has the option to enable it through the l10n_br_is_icbs Boolean flag on the company, which gates all the new functionality. These changes impact both tax calculation and EDI. This set of modules adapts our existing l10n_br* modules to the new requirements set out by Avalara. We are required to send extra values to their API, and in some cases adapt existing ones. task-4939796 [1] https://www.planalto.gov.br/ccivil_03/leis/lcp/lcp214.htm Forward-Port-Of: odoo/enterprise#102706
This update reflects changes to Mexican tax withholding regulations (ISR) effective January 1, 2026. The update modifies the ‘Mexico: ISR Table’ parameter in the Odoo Enterprise system to align with the new tax rates mandated by the Mexican Tax Resolution, ensuring accurate tax calculations for Mexican payroll.
Original PR description
According to the Mexican Tax Resolution (Resolución Miscelánea Fiscal 2026: https://dof.gob.mx/2025/SHCP/SHCP_281225_01.pdf), the ISR withholding tax tables applicable for the fiscal year have changed, effective January 1, 2026. It is necessary to add a new parameter value for “Mexico: ISR Table” to reflect the new values. target: 19.0 task: 5448019 Forward-Port-Of: odoo/enterprise#103030 Forward-Port-Of: odoo/enterprise#103009
This update enables importing data from Codaclean (CODB) files into Odoo. This streamlines the process of bringing in financial data related to legal cases, improving data accuracy and reducing manual effort. The change is part of a larger effort to enhance data integration within the Odoo Enterprise platform.
Original PR description
Support importing SODA (CODB) files from codaclean. IAP PR: https://github.com/odoo/iap-apps/pull/1253 task-5215628
This update adjusts payroll rule parameters to reflect changes in US tax regulations for the 2026 tax year. These updates ensure accurate salary calculations and maintain compliance with current US payroll laws. This is a critical update to avoid potential financial discrepancies.
Original PR description
Purpose: Certain US Payroll values changes yearly. The payroll rule parameters must be updated for accurate salary calculation for 2026 for compliance. task-5409739 Forward-Port-Of: odoo/enterprise#103016 Forward-Port-Of: odoo/enterprise#102711
1 change
Enhancements to existing features
This update prepares Odoo for Brazil's upcoming shift to a new consumption tax system starting in 2026. Users can enable this new system based on their business location and transaction types. The changes adapt our existing modules to comply with Avalara's requirements for tax calculation and EDI.
Original PR description
2026 marks the start of Brazil's 8-year plan to migrate to a completely new consumption tax system [1]. The new system is meant to be simpler than the old one, but we defer to Avalara for tax…
2026 marks the start of Brazil's 8-year plan to migrate to a completely new consumption tax system [1]. The new system is meant to be simpler than the old one, but we defer to Avalara for tax calculation so we don't really notice it technically. The old and new system have to coexist for the foreseeable future because the rollout happens gradually over many years. Whether the new system has to be enabled depends on the federal state the business is in, the type of transactions they do, and other factors. The user has the option to enable it through the l10n_br_is_icbs Boolean flag on the company, which gates all the new functionality. These changes impact both tax calculation and EDI. This set of modules adapts our existing l10n_br* modules to the new requirements set out by Avalara. We are required to send extra values to their API, and in some cases adapt existing ones. task-4939796 [1] https://www.planalto.gov.br/ccivil_03/leis/lcp/lcp214.htm Forward-Port-Of: odoo/enterprise#102706
1 change
Enhancements to existing features
This update prepares Odoo for Brazil's upcoming shift to a new consumption tax system starting in 2026. Users can enable this new system based on their business location and transaction types. The changes adapt our existing modules to comply with the new requirements, primarily impacting tax calculations and EDI processes.
Original PR description
2026 marks the start of Brazil's 8-year plan to migrate to a completely new consumption tax system [1]. The new system is meant to be simpler than the old one, but we defer to Avalara for tax…
2026 marks the start of Brazil's 8-year plan to migrate to a completely new consumption tax system [1]. The new system is meant to be simpler than the old one, but we defer to Avalara for tax calculation so we don't really notice it technically. The old and new system have to coexist for the foreseeable future because the rollout happens gradually over many years. Whether the new system has to be enabled depends on the federal state the business is in, the type of transactions they do, and other factors. The user has the option to enable it through the l10n_br_is_icbs Boolean flag on the company, which gates all the new functionality. These changes impact both tax calculation and EDI. This set of modules adapts our existing l10n_br* modules to the new requirements set out by Avalara. We are required to send extra values to their API, and in some cases adapt existing ones. task-4939796 [1] https://www.planalto.gov.br/ccivil_03/leis/lcp/lcp214.htm Forward-Port-Of: odoo/enterprise#102706
1 change
Enhancements to existing features
This update prepares Odoo for Brazil's upcoming tax system changes in 2026, aligning with a phased rollout impacting consumption taxes. Businesses can enable this functionality based on their location and transaction types, and the update adapts our modules to integrate with Avalara for tax calculations. It ensures continued compliance with evolving Brazilian tax regulations.
Original PR description
2026 marks the start of Brazil's 8-year plan to migrate to a completely new consumption tax system [1]. The new system is meant to be simpler than the old one, but we defer to Avalara for tax calculation so we don't really notice it technically. The old and new system have to coexist for the foreseeable future because the rollout happens gradually over many years. Whether the new system has to be enabled depends on the federal state the business is in, the type of transactions they do, and other factors. The user has the option to enable it through the l10n_br_is_icbs Boolean flag on the company, which gates all the new functionality. These changes impact both tax calculation and EDI. This set of modules adapts our existing l10n_br* modules to the new requirements set out by Avalara. We are required to send extra values to their API, and in some cases adapt existing ones. task-4939796 [1] https://www.planalto.gov.br/ccivil_03/leis/lcp/lcp214.htm