Daily updates from Odoo
Monday, April 13, 2026
12 changes
2 changes
Enhancements to existing features
This update simplifies the printer LNA (Label Next Available) configuration by consolidating checkbox options. Previously, printers had separate IoT and ePOS checkboxes, which were confusing for clients. Now, a single ePOS checkbox controls the LNA functionality, streamlining the process and improving usability.
Original PR description
The printer model has two checkboxes: one for IoT and one for ePOS. LNA is already hard for clients to understand, we then simplify it by removing the IoT one from the printer model, to use the ePOS one for both. If we check `use_lna` for on a printer type "iot", it will check the checkbox on the IoT Box record. Also, if we check/uncheck `use_lna` on the IoT Box record, it will check/uncheck it on the corresponding printer model.
This update ensures Odoo correctly handles tax exemptions related to international transactions (UBL Cii) by incorporating all required tax exemption reasons defined by Peppol. This improves compliance with international tax regulations and avoids potential issues with cross-border invoicing.
Original PR description
Some tax exemption reasons were missing, This commit ensures having all the tax exemption reasons introduced by Peppol task-6048561 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#258455 Forward-Port-Of: odoo/odoo#254841
1 change
Enhancements to existing features
This update ensures Odoo correctly handles tax exemption reasons required by international standards (Peppol). It adds missing tax exemption reasons, improving compliance and accuracy for tax reporting related to UBL invoices.
Original PR description
Some tax exemption reasons were missing, This commit ensures having all the tax exemption reasons introduced by Peppol task-6048561 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#258455 Forward-Port-Of: odoo/odoo#254841
5 changes
Enhancements to existing features
This update streamlines monthly payroll processing in Belgium by consolidating the structures used for students, PFI (Pension Funds for Individuals), and regular employees. The changes ensure a more consistent and efficient payroll system while adapting to specific Belgian regulations.
Original PR description
Student, PFI and employees will use the same structure, but with adapted rules. task-6051050
This update improves the calculation of provision salary rules for employees in the United Arab Emirates (AE) and Saudi Arabia (SA). These changes ensure accurate payroll processing and compliance with local regulations for these regions.
Original PR description
-Logic has been enhanced for Provision salary rules for AE and SA locs.
This update streamlines the 'End of Collaboration' process for Belgian employees. Instead of manually selecting actions like user deletion or archiving, all actions are now automatically executed on a defined date. This simplifies administration and ensures consistent handling of employee departures.
Original PR description
Improve the UX of the "End of Collaboration" procedure, particularly for Belgium. The option to select which actions are executed upon employee departure (delete user, archive employee, unassign car, etc.) has been removed. All actions are now executed automatically. However, it is still possible to define the date on which they will be applied. Community PR: https://github.com/odoo/odoo/pull/253079 Upgrade PR: https://github.com/odoo/upgrade/pull/9653 task-5958676
This update clarifies the tooltip for the cross-company toggle in Odoo Enterprise, explaining that its behavior depends on the selected companies. The change improves user understanding in both Manual and Automated modes, ensuring consistent and accurate data processing.
Original PR description
The tooltip in the cross-company toggle was unclear and did not properly indicate that its behavior depends on the selected companies. This change updates the tooltip to make it more explicit in Manual and Automated modes. task-6111985
This update enhances the web_studio report creation process by automatically including an address block in newly designed external reports. Previously, this block was not automatically generated. This change improves the presentation of reports by providing a standard location for address information.
Original PR description
When creating a new report with external layout, an address block is created in the report and rendered in html, which was not the case before this commit. task-6072302
2 changes
Enhancements to existing features
This update enhances the processing of point-of-sale transactions related to German tax reporting (l10n_de_pos_cert). Specifically, it ensures accurate transaction timing data and automatically clears active transactions at the end of each session to maintain data integrity and compliance. This improves the reliability of tax reporting.
Original PR description
In this commit: ------------------ - The transactions were shown to be processed within 0-1 seconds as we were used to call start and finish transaction calls on validation so in the case of retails it won't give actual data of start and end time so we need to improve this and called now for `start transaction` when first orderline added to a new order, calling `cancelled` if the order is deleted or all the orderlines are removed manually, and `finished` on validation of the order. - Also will delete all active transactions on the fiskaly at the time of closing of session so that no active order remains (if cleared cache) As a lot things are already handled in v19 Handled https://github.com/odoo/enterprise/pull/99216 pr's remaining updates here.
This update creates a direct link between Documents and Project Tasks, resolving a previous issue where attachments and saved documents weren't automatically connected. Now, documents created from Project Tasks will have a clear link back to the task, improving workflow and document management.
Original PR description
Previously, there was no connection between the Documents app and Project Tasks (`project.task`). Attachments added to a task via the chatter were not synced to the Documents app, and documents manually saved from the chatter lacked a link back to the corresponding task. This commit introduces a link between them by posting a message in the created document's chatter, linking it back to the task. This solution is specifically for stable versions. On `master`, we introduce a proper bridge. task-5941719
2 changes
Enhancements to existing features
This update simplifies the creation of Spanish tax reports (303 and 347) by automatically displaying key information. Specifically, the 'exonerated from 390' field is now visible on the print BOE wizard for relevant periods, and a new grouping is added for audit operations in report 347, streamlining the reporting process.
Original PR description
In this PR: - In tax report 303, the 'exonerated from 390' boolean field is now visible on the print BOE wizard , when period is either last month or last quarter so that user does not have to enable it manually on the AEAT page. - In the annual tax report 347, when a user clicks to audit the operations of the entity, a new group by is added in context to group the reports by move type and date(quarter). task-5863744
This update enhances the reliability of order updates within the German Point of Sale certification module. Specifically, a new system ensures order changes (like line items) are processed sequentially, maintaining data accuracy. Additionally, unnecessary UI validation for ZIP codes and addresses has been removed as the backend handles default assignments.
Original PR description
In this commit: ------------------- - We have added logic to execute API calls using a mutex for order updates (such as line updates and removals). This ensures that each update is processed (sequentially), allowing us to properly track and maintain order consistency. - We removed the ZIP and address validation on the UI since the backend already assigns default values if they are missing. So, there’s no need to restrict the user on the UI. task:5941742