Odoo Changelog — 2026-02-20

Friday, February 20, 2026

5 changes · 17.0

Bug Fixes(5)

Resolved issues and error corrections

[FIX] web_editor: show undo/redo buttons in mobile view

Core17.0web_editorMedium

This update fixes a usability issue on mobile devices where the undo and redo buttons were hidden in the editor toolbar. The change ensures these buttons are always visible, improving the editing experience for mobile users. This enhancement streamlines the workflow and allows users to easily correct mistakes while editing content on their phones or tablets.

Original PR description

Problem:
On mobile devices, the undo and redo buttons are not visible in the editor toolbar.

Cause:
`showHistory` is not enabled by default in mobile view, which hides the undo/redo controls.

Solution:
Pass `true` as the default value for `showHistory` when in mobile view, ensuring the undo/redo buttons are always visible.

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#editor#mobile#usability

[FIX] timesheet_grid: enforce six-digit limit on negative hours in timesheets

PR #106781

Enterprise17.0timesheet_gridMedium

This update ensures timesheet entries with excessively large negative hours (over six digits) are properly flagged as errors. Previously, these entries could be added without warning, leading to potential data inaccuracies. This fix improves data integrity and prevents incorrect time tracking.

Original PR description

Currently, a user can add a timesheet entry with a negative Hours Spent 
value `exceeding six digits`.

**Steps to reproduce:**
- Install the `timesheet_grid` module.
- Open the `Timesheets` app and click `Add a line`.
- Set Hours Spent to a `negative` value with more than six digits (e.g., -1000000).

**Observation:**
The line is added without any warning, whereas entering a positive 
value with more than six digits correctly raises an `error`.

**Root cause:**
At [1], the constraint validates only positive values exceeding six digits. 
As a result, negative values with more than six digits are not checked 
and bypass the `UserError validation`.

**Fix:**
This commit updates the constraint to ensure the six-digit limit 
applies to both positive and negative values.

[1]:
https://github.com/odoo/enterprise/blob/660905872909405c0a07a8317b4eb0a42e5854ca/timesheet_grid/models/analytic.py#L46-L49

opw-5909417

#timesheet#validation#data integrity

[FIX] account: inherit product category accounts from parent hierarchy

PR #248389

Core17.0accountMedium

This update fixes an issue where invoices weren't correctly using product category accounts. Now, Odoo automatically checks the entire category hierarchy (parent to child) to find an available account, ensuring invoices accurately reflect the intended income or expense classification. This improves financial reporting accuracy.

Original PR description

**Steps to reproduce:**
* Install the **Accounting** module.
* Create a product category hierarchy (grandparent → parent → child).
* Set an **income account** on the grandparent category.
* Set an **expense account** on the child category.
* Leave the parent category without any accounts.
* Create a product assigned to the child category.
* Create a customer invoice using this product.

**Observed behavior:**
* The invoice line uses the **default income account** from settings instead of the grandparent category’s income account.
* The category hierarchy is not checked to retrieve parent accounts.

**Expected behavior:**
* If no account is defined on a category, Odoo should traverse the **parent categories** to find one.
* Only if no account exists in the hierarchy should it fall back to journal or default accounts.

**Cause:**
* Account lookup only checked the **immediate category**.
* Parent categories were not considered.

**Fix:**
* Traverse the product category hierarchy when searching for accounts.
* Use the first account found in the parent chain.

opw-5869592

[FIX] account{_peppol,_edi_ubl_cii,}: allow sending via Peppol after PDF or XML generation

PR #246350

Core17.0accountMedium

This update resolves an issue in version 17.0 where the 'Send via Peppol' option was disabled after sending invoices via email. The previous system prevented the necessary UBL-CII XML file from being generated, blocking Peppol transmission. Now, invoices can be sent via Peppol regardless of whether a PDF was previously generated.

Original PR description

### Issue:
In 17.0, the `Send via Peppol` option becomes unavailable after using `Send by email` on an invoice

### Cause:
The `Send via Peppol` action depends on the UBL-CII XML file
However, the XML generation was conditioned on the absence of a PDF document

After generating the PDF, the invoice was considered as already having all required documents, so no additional EDI documents (including the UBL-CII XML) were generated, which disabled the `Peppol` option

### Note:
If the XML was already generated, it should still be possible to `Send via Peppol`
However, the XML was not attached because it wasn't generated during Peppol sending
This issue is also fixed in this PR

### Steps to reproduce:
- Install `l10n_be` and switch to BE Company
- Enable Peppol and activate the Demo mode in Settings
- Create an invoice for the BE Company
- Add any product with a Tax
- Confirm -> Send & Print -> Email
- Open Send & Print again Before the fix, the `Send via Peppol` option is no longer available

opw-5490217

[FIX] l10n_nl_reports_sbr{,_icp}: update 2026 taxonomy namespace

PR #108126

Enterprise17.0l10n_nlMedium

This update resolves an issue preventing successful processing of Dutch tax (OB) and ICP reports by Digipoort. It replaces outdated report templates with the final 20251210 NT20 taxonomy, ensuring compliance and accurate data submission.

Original PR description

Update the Dutch tax (OB) and ICP report templates from the 20251210.a pre-release to the final 20251210 NT20 taxonomy to ensure successful processing by Digipoort.

Fixes: https://github.com/odoo/enterprise/commit/5becacff48f1a2490ce2f57a4679020615b6b8c2

opw-5911496

#Netherlands#Tax Reporting#ICP#Digipoort

Problem: On mobile devices, the undo and redo buttons are not visible in the editor toolbar. Cause: `showHistory` is not enabled by default in mobile view, which hides the undo/redo controls. Solution: Pass `true` as the default value for `showHistory` when in mobile view, ensuring the undo/redo buttons are always visible. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Currently, a user can add a timesheet entry with a negative Hours Spent value `exceeding six digits`. **Steps to reproduce:** - Install the `timesheet_grid` module. - Open the `Timesheets` app and click `Add a line`. - Set Hours Spent to a `negative` value with more than six digits (e.g., -1000000). **Observation:** The line is added without any warning, whereas entering a positive value with more than six digits correctly raises an `error`. **Root cause:** At [1], the constraint validates only positive values exceeding six digits. As a result, negative values with more than six digits are not checked and bypass the `UserError validation`. **Fix:** This commit updates the constraint to ensure the six-digit limit applies to both positive and negative values. [1]: https://github.com/odoo/enterprise/blob/660905872909405c0a07a8317b4eb0a42e5854ca/timesheet_grid/models/analytic.py#L46-L49 opw-5909417

**Steps to reproduce:** * Install the **Accounting** module. * Create a product category hierarchy (grandparent → parent → child). * Set an **income account** on the grandparent category. * Set an **expense account** on the child category. * Leave the parent category without any accounts. * Create a product assigned to the child category. * Create a customer invoice using this product. **Observed behavior:** * The invoice line uses the **default income account** from settings instead of the grandparent category’s income account. * The category hierarchy is not checked to retrieve parent accounts. **Expected behavior:** * If no account is defined on a category, Odoo should traverse the **parent categories** to find one. * Only if no account exists in the hierarchy should it fall back to journal or default accounts. **Cause:** * Account lookup only checked the **immediate category**. * Parent categories were not considered. **Fix:** * Traverse the product category hierarchy when searching for accounts. * Use the first account found in the parent chain. opw-5869592

### Issue: In 17.0, the `Send via Peppol` option becomes unavailable after using `Send by email` on an invoice ### Cause: The `Send via Peppol` action depends on the UBL-CII XML file However, the XML generation was conditioned on the absence of a PDF document After generating the PDF, the invoice was considered as already having all required documents, so no additional EDI documents (including the UBL-CII XML) were generated, which disabled the `Peppol` option ### Note: If the XML was already generated, it should still be possible to `Send via Peppol` However, the XML was not attached because it wasn't generated during Peppol sending This issue is also fixed in this PR ### Steps to reproduce: - Install `l10n_be` and switch to BE Company - Enable Peppol and activate the Demo mode in Settings - Create an invoice for the BE Company - Add any product with a Tax - Confirm -> Send & Print -> Email - Open Send & Print again Before the fix, the `Send via Peppol` option is no longer available opw-5490217

Update the Dutch tax (OB) and ICP report templates from the 20251210.a pre-release to the final 20251210 NT20 taxonomy to ensure successful processing by Digipoort. Fixes: https://github.com/odoo/enterprise/commit/5becacff48f1a2490ce2f57a4679020615b6b8c2 opw-5911496