Monday, April 20, 2026
5 changes · 18.0
Enhancements to existing features
The French chart of accounts now separates account 649 into two new accounts, 6491 and 6492. This helps produce a more accurate Profit and Loss report by distinguishing social security charges from salaries.
Original PR description
Splitting account 649 into two new accounts (6491 and 6492) is necessary to handle the Profit and Loss report properly. This ensures we can accurately separate social security charges from salaries in the report. Reference: ANC PCG 2026, page 445, note (h) https://www.anc.gouv.fr/files/anc/files/1_Normes_fran%C3%A7aises/recueil/RECEUIL-PCG-2026-AVEC-COUVERTURE.pdf task-6053784 Forward-Port-Of: odoo/odoo#255038
The French accounting report now separates account 649 into two new accounts, 6491 and 6492. This helps the Profit and Loss report distinguish social security charges from salaries more accurately, improving the quality of financial reporting.
Original PR description
Splitting account 649 into two new accounts (6491 and 6492) is necessary to handle the Profit and Loss report properly. This ensures we can accurately separate social security charges from salaries in the report. Reference: ANC PCG 2026, page 445, note (h) https://www.anc.gouv.fr/files/anc/files/1_Normes_fran%C3%A7aises/recueil/RECEUIL-PCG-2026-AVEC-COUVERTURE.pdf task-6053784 Forward-Port-Of: odoo/enterprise#111420
This update ensures the digital VAT book file includes the required operation code even when the VAT rate is zero. It helps prevent validation errors when uploading the file to ARCA and keeps the report compliant with local tax specifications.
Original PR description
**Description of the issue/feature this PR addresses**: When uploading the digital VAT book txt file to ARCA, the operation code must be reported when the VAT rate is zero. Validation file: https://www.afip.gob.ar/iva/documentos/Libro-IVA-Digital-Especificaciones.pdf page 10, "Campo 20: Código de operación." Specification: https://www.afip.gob.ar/iva/documentos/libro-iva-digital-diseno-registros.pdf (page 4 "Diseño de Registro Compras e Importación de Bienes- Cabecera"). **Current behavior before PR**: The operation code is not being reported in the digital VAT book txt file when the VAT rate is zero. **Desired behavior after PR is merged**: The operation code is being reported in the digital VAT book txt file when the VAT rate is zero. _Task Adhoc side_: 55146 _Task latam side_: 1357
This update ensures the operation code is included in the Argentine digital VAT book file even when the VAT rate is zero. It helps prevent validation errors when submitting the file to the tax authority, making VAT reporting more reliable.
Original PR description
**Description of the issue/feature this PR addresses**: When uploading the digital VAT book txt file to ARCA, the operation code must be reported when the VAT rate is zero. Validation file: https://www.arca.gob.ar/iva/documentos/Libro-IVA-Digital-Especificaciones.pdf page 10, "Campo 20: Código de operación." Specification: https://www.arca.gob.ar/iva/documentos/libro-iva-digital-diseno-registros.pdf (page 4 "Diseño de Registro Compras e Importación de Bienes- Cabecera"). **Current behavior before PR**: The operation code is not being reported in the digital VAT book txt file when the VAT rate is zero. **Desired behavior after PR is merged**: The operation code is being reported in the digital VAT book txt file when the VAT rate is zero. _Task Adhoc side_: 55146 _Task latam side_: 1357 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update makes workcenter graph data much faster to generate, especially when there are many related work orders. It reduces repeated database lookups by checking work orders more efficiently and reusing calendar calculations when several workcenters share the same schedule.
Original PR description
Before this commit, calling the method `_prepare_graph_data` with a recordset of workcenters, would traverse the recordset and then check if all the workcenters has at least one workorder by fetching…
Before this commit, calling the method `_prepare_graph_data` with a recordset of workcenters, would traverse the recordset and then check if all the workcenters has at least one workorder by fetching the field `order_ids` for all the workcenters. This can be too slow in cases where the workcenters have a lot of workorders and in addition to that there is no need to do this repeatedly for every workcenter. In this commit, I have modified the check by invoking a `search_count` on the workorders before iterating over the recordset and in addition to that I have pre-computed the sum of the duration hours of the attendances related to a `resource_calendar` as multiple workcenters might have the same `resource_calendar` The benchmark done below, was on a database that contained 78 workcenters. | Workorders | Before | After | | :--- | :--- | :--- | | 1380828 | 12s | 0.16s | | 138082 | 1.21s | 0.14s | | 13808 | 0.21s | 0.09s | opw-6040077 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr