Daily updates from Odoo
Tuesday, October 21, 2025
9 changes · master
Enhancements to existing features
Updates Luxembourg payroll settings to reflect the 2025 minimum social salary and related employee tax credits. This helps businesses calculate payroll in line with the latest official Luxembourg social security and tax parameters.
Original PR description
Sources: - https://igss.gouvernement.lu/dam-assets/publications/param%C3%A8tres-sociaux/2025/par-soc-202501.pdf - https://igss.gouvernement.lu/dam-assets/publications/param%C3%A8tres-sociaux/2025/par-soc-202505.pdf task-5176255 Forward-Port-Of: odoo/enterprise#97468
This update refines how manufacturing planning calculates monthly demand by using exact date ranges, improving accuracy for purchasing and production suggestions. It also streamlines field service product catalog navigation and internal data handling, making the back button behavior clearer and the catalog code easier to maintain.
Company-wide return deadline settings have been removed because deadlines can now be managed directly on each return type. This gives customers more precise control over filing timelines across accounting reports and country-specific returns.
Original PR description
The field deadline on the company is now removed as customers have now a way to override the deadline on the return type directly. task-5153900
Odoo Studio now lets users drag existing selection or stage-like fields onto a form status bar instead of creating only a new selection field. This makes stage setup more flexible and allows better ordering in grouped views, especially when using related stage records.
Original PR description
Before this commit, to add a StatusBar (stages) in a form view, one had to click on the form's editor hook. After some configuration it added a Selection field with some selection values setup by the user. The problem with selection values is that there are ordered lexicographically on the value in the column, that is the technical value of the selection value's tuple. Hence, in a grouped kanban (or list -- via a web_read_group) the groups could not have another order. After this commit, the StatusBar hook behaves as a droppable hook and one can drag and drop a selection field or a many2one, allowing for their respective configuration. If a many2one serves as the field underlying the statusbar, a button allows the user to add records, i.e. stages. task-4744988
This update adds country-specific EC Sales List and Intrastat reporting rules for Austria, Germany, the Netherlands, Italy, Poland, and Portugal. Businesses in these countries can better track required filing deadlines and periodicities directly in Odoo, supporting more accurate tax and trade compliance.
Original PR description
Following the implementation of the Tax returns feature in 18.3 which was focused on the general implementation and Belgium, we want to add the specification for other country and in this case Austria, Germany, The Netherlands, Italy, Poland, and Portugal. Adding EC sales list, Intrastat specific deadlines and periodicities. task-4776236
Studio now stores pipeline stages in a way that preserves their intended order, so kanban columns appear consistently and empty stages remain visible. This improves pipeline setup and editing, including statusbar display and option handling in the form editor.
Original PR description
**Before this PR:** In studio, the pipeline statusbar was modeled as a field selection which prevented the order of the stages to be used to order kanban columns correctly. **After this PR:** The pipeline statusbar is now modeled as a Many2one field pointing to a new model created when adding the statusbar to the form view. This allows the kanban view to be ordered correctly. The edition of the statusbar also works when the model is created with the pipeline option checked. Moreover, when a kanban column is empty, it is still displayed which prevent the user to be prompted for the creation of new stages. **This PR also introduces 2 fixes:** - All statusbar options are parsed when using the add operation. - The statusbar widget is now rendered correctly in the form editor. task-4744988
Argentina IVA Simple tax report exports are now handled directly in the main Argentine reporting module instead of a separate add-on. This simplifies module management while keeping the report export and related tests available for users who need Argentine VAT reporting.
Original PR description
In fe77a6b we merged a new module in stable to be able to support the export of IVA Simple Tax Reports for Argentina. This is no longer necessary in master, as such, the model data for activities have been merged into `l10n_ar` in community, and all of the tests and report exports have been moved to `l10n_ar_reports` in enterprise. task-5027104
The SEPA Direct Debit mandate form has been simplified to show only the most relevant information to everyday users. Date handling, bank account guidance, and scheme explanations are clearer, helping staff complete mandates with less confusion.
Original PR description
- Show identifier only in debug mode. - Use Date Range for start and end date with 'Indefinite' as placeholder. - Placeholder for partner bank 'Provided by customer'. - Make SDD scheme optoins clearer and adding useful help. task-5159986
Uruguayan electronic invoices can now correctly identify and report VAT rates outside the standard exempt, minimum, and basic categories. This improves compliance by adding the required reduced-rate totals and line indicators in the XML, plus a dedicated tax grid for reporting.
Original PR description
1) Detecting "Reduced Tax Rate": * Identify product lines with a VAT rate that is neither 0% (exempt), 10% (minimum), nor 22% (basic). Any VAT rate outside these three should be considered "Reduced…
1) Detecting "Reduced Tax Rate":
* Identify product lines with a VAT rate that is neither 0% (exempt), 10% (minimum), nor 22% (basic). Any VAT rate outside these three should be considered "Reduced Tax Rate".
2) Modifying XML Output:
* In the `<Totales>` section of the XML, include the total amount of VAT under the "Reduced Tax Rate" in the `<MntIVAOtra>` tag.
* Example: ```xml <MntIVAOtra>140</MntIVAOtra> ``` (where 140 corresponds to the VAT calculated at the reduced tax rate, e.g., 20%).
* For each product line using "Reduced Tax Rate," set the `<IndFact>` tag to `4`: ```xml <IndFact>4</IndFact> ```
* Ensure the total amount reflects the base amount plus the VAT under "Reduced Tax Rate".
3) Tax Grid for Configuration:
* Add a new tax grid called Sales Reduced VAT to be used for the tax configuration of the "Reduced Tax Rate."
* This will ensure proper reporting and consistency in tax declarations.
* The new tax grid should be selectable when configuring other taxes.
Odoo Implementation Considerations:
* The tax computation logic in Odoo already supports defining taxes at different rates.
* Adapt the XML generation logic to check for product lines with a non-standard VAT rate and apply the necessary modifications. Ensure the final totals in the XML align with Odoo's computed tax amounts.
Task latam side: 1330
Task Adhoc side: 52999
Forward-Port-Of: odoo/enterprise#97640
Forward-Port-Of: odoo/enterprise#91392