Monday, April 13, 2026
4 changes · 19.0
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
Resolved issues and error corrections
This update corrects a reporting issue in the Rental app where pickup/return quantities were incorrectly duplicated and the report displayed the wrong start date. The fix addresses a problem with how the database handles timezones and ensures accurate reporting of rental activity. This improves the reliability of rental data analysis.
Original PR description
Steps to reproduce: 1- Install Rental app and create a rental product. 2- Create a Rental Order for that product from Feb 27, 12:00 AM to Feb 28, 11:30 PM. 3- Confirm the order and deliver the…
Steps to reproduce: 1- Install Rental app and create a rental product. 2- Create a Rental Order for that product from Feb 27, 12:00 AM to Feb 28, 11:30 PM. 3- Confirm the order and deliver the quantity. 4- Open the [Rental -> Reporting -> Rental Analysis] Pivot view. 5- Set the measures to "Picked up Quantity" and group by "Date: Day". Description of issue: Two issues occur: 1- The "Picked up Quantity" is duplicated and shown on every single day of the rental period. The same happens for the "Returned Quantity" which is shown on every row. 2- The report shows the start date on the previous day (Feb 26). Expected behavior: 1- The Picked up/Returned Quantity should only appear on the day the pickup/return actually occurred. 2- The start date should be on the same day (Feb 27). Why this happens? 1- The SQL view uses generate_series to expand the rental duration into individual days. The original query was pulling the qty_delivered/qty_returned into every resulting row without a conditional check. 2- Datetime fields are stored in UTC format in the database, and the SQL view was performing a date cast directly on the UTC field without converting to the local timezone. opw-5501263
This update removes an outdated requirement for country information on payment tokens used for subscription invoices. Previously, this restriction caused processing errors, particularly with certain payment providers. This change ensures invoices can be processed correctly, improving subscription billing reliability.
Original PR description
Before this commit, a country was mantadory on the payment token when it was used to pay invoices of subscriptions. This behavior was fetched back from internal code in 15.3. This issue was not visible until recently. Some token are fine without country, the provider allows it but the cron fails to process the sale order when the contract is processed. THis commit remove that old constraint. opw-5268156 task-5349998