Odoo Changelog — 2026-02-06

Friday, February 6, 2026

3 changes · saas-18.2

Bug Fixes(3)

Resolved issues and error corrections

[FIX] l10n_ch_hr_payroll_elm_transmission_5_3: Fix coordination deduction

Enterprisesaas-18.2hr_payrolll10n_chMedium

This update resolves an issue with the calculation of coordination deductions in the Swiss payroll module (l10n_ch_hr_payroll_elm_transmission_5_3). The fix ensures accurate reporting of deductions related to coordination payments, improving compliance with Swiss tax regulations. This change impacts payroll processing for Swiss businesses using Odoo Enterprise.

Original PR description

Forward-Port-Of: odoo/enterprise#106615

#payroll#switzerland#tax#deduction

[FIX] l10n_es_reports: use correct report period for Modelo 390

PR #106676

Enterprisesaas-18.2l10n_es_reportsMedium

This update resolves an issue where Modelo 390 reports were incorrectly generating empty BOE files. The fix ensures the reports accurately reflect data for the specified year by correctly identifying the report period. This guarantees accurate tax reporting for Spanish companies.

Original PR description

### Issue: When exporting Modelo 390 reports for a past year, the BOE file was empty — all values were 0 ### Cause: In `export_boe()`, the `report_lines` were get based on the `section_report`…

### Issue:
When exporting Modelo 390 reports for a past year, the BOE file was empty — all values were 0

### Cause:
In `export_boe()`, the `report_lines` were get based on the `section_report` options
However, `section_reports` do not store the date
or return periodicity of the selected report
As a result, using their options always fetched data for the current period instead of the specified year

### Note:
`_generate_mod_390_page2()` also had issues:
some lines were missing or incorrectly indexed

The mod 360 format, it strict in the structure with specific index so it may produce invalid documents

The latest documentation for mod 390:
https://sede.agenciatributaria.gob.es/static_files/Sede/Disenyo_registro/DR_300_399/archivos_25/dr390e2025.xlsx

### Steps to reproduce:
- Install `l10n_es_reports` and switch to ES Company
- Create an Invoice and a Bill (Any product, Price: 100.00, Tax: 21%, Invoice Date: 01/01/2025)
- Open Tax Return, switch to Mod 390, and set year to 2025
- You should see data in the 2 first sections
- Use the gear icon, and download the BOE
- Use the gear icon to download the BOE, fill the wizard (Natural Person – Name: Test, Principal activity: Test, Activity Code: 12345), and generate the file Before the fix: all values in the BOE were 0 instead of matching the report

opw-5457374

Forward-Port-Of: odoo/enterprise#106542
Forward-Port-Of: odoo/enterprise#104928

[FIX] l10n_pe_reports_stock: Fix Kardex report logic

PR #106680

Enterprisesaas-18.2stockMedium

This update improves the accuracy of the Kardex report for Peruvian exports by incorporating landed costs and price adjustments, which were previously missing. The changes also address mapping issues and ensure correct operation types are used, leading to more reliable inventory reporting.

Original PR description

Refactored the logic to generate the Kardex report based on `stock.valuation.layer`, for the following reasons: 1. **Landed costs**: These must be considered in the report. Odoo already creates…

Refactored the logic to generate the Kardex report based on `stock.valuation.layer`, for the following reasons:

1. **Landed costs**: These must be considered in the report. Odoo already creates valuation layers for landed costs, and the report must use the date when the landed cost was recorded, not the original stock move date.
2. **Price adjustments**: Product price adjustments generate valuation layers without stock moves. These layers are now included in the report.

Additional fixes and improvements:

- Correctly map columns 18 to 26 in Report 13.1:
- 18–20: Incoming movements
- 21–23: Outgoing movements
- 24–26: Final balance
- Ensure `cost_in` and `cost_out` values are always positive. The sign now depends on the movement quantity, not the unit cost.
- Replace the product list with a dictionary to track accumulated quantities and values per product for accurate balance calculation.
- Extend test coverage to include cases where the report includes opening balances due to past transactions.
- **MRP movements**: MRP processes don’t generate pickings, but their stock moves are linked to operation types. The report now uses codes `19` for incoming and `27` for outgoing MRP-related movements.
- **Reversal of pickings**: Since Odoo copies the original picking and skips reassignment logic, we now override the reversal wizard to set the correct PE operation type:
- `25` for incoming reversals
- `24` for outgoing reversals
- Force operation type `99` for all `A1` lines, as required by the report.
- Ensure report dates are processed in the user's timezone for consistency with the layer view in Odoo.

Forward-Port-Of: odoo/enterprise#88592

### Issue: When exporting Modelo 390 reports for a past year, the BOE file was empty — all values were 0 ### Cause: In `export_boe()`, the `report_lines` were get based on the `section_report` options However, `section_reports` do not store the date or return periodicity of the selected report As a result, using their options always fetched data for the current period instead of the specified year ### Note: `_generate_mod_390_page2()` also had issues: some lines were missing or incorrectly indexed The mod 360 format, it strict in the structure with specific index so it may produce invalid documents The latest documentation for mod 390: https://sede.agenciatributaria.gob.es/static_files/Sede/Disenyo_registro/DR_300_399/archivos_25/dr390e2025.xlsx ### Steps to reproduce: - Install `l10n_es_reports` and switch to ES Company - Create an Invoice and a Bill (Any product, Price: 100.00, Tax: 21%, Invoice Date: 01/01/2025) - Open Tax Return, switch to Mod 390, and set year to 2025 - You should see data in the 2 first sections - Use the gear icon, and download the BOE - Use the gear icon to download the BOE, fill the wizard (Natural Person – Name: Test, Principal activity: Test, Activity Code: 12345), and generate the file Before the fix: all values in the BOE were 0 instead of matching the report opw-5457374 Forward-Port-Of: odoo/enterprise#106542 Forward-Port-Of: odoo/enterprise#104928

Refactored the logic to generate the Kardex report based on `stock.valuation.layer`, for the following reasons: 1. **Landed costs**: These must be considered in the report. Odoo already creates valuation layers for landed costs, and the report must use the date when the landed cost was recorded, not the original stock move date. 2. **Price adjustments**: Product price adjustments generate valuation layers without stock moves. These layers are now included in the report. Additional fixes and improvements: - Correctly map columns 18 to 26 in Report 13.1: - 18–20: Incoming movements - 21–23: Outgoing movements - 24–26: Final balance - Ensure `cost_in` and `cost_out` values are always positive. The sign now depends on the movement quantity, not the unit cost. - Replace the product list with a dictionary to track accumulated quantities and values per product for accurate balance calculation. - Extend test coverage to include cases where the report includes opening balances due to past transactions. - **MRP movements**: MRP processes don’t generate pickings, but their stock moves are linked to operation types. The report now uses codes `19` for incoming and `27` for outgoing MRP-related movements. - **Reversal of pickings**: Since Odoo copies the original picking and skips reassignment logic, we now override the reversal wizard to set the correct PE operation type: - `25` for incoming reversals - `24` for outgoing reversals - Force operation type `99` for all `A1` lines, as required by the report. - Ensure report dates are processed in the user's timezone for consistency with the layer view in Odoo. Forward-Port-Of: odoo/enterprise#88592