Odoo Changelog — 2026-03-28

Saturday, March 28, 2026

2 changes · saas-18.3

Bug Fixes(2)

Resolved issues and error corrections

[FIX] point_of_sale: prevent tax change via price_include_override

Coresaas-18.3point_of_saleMedium

This update fixes a potential inconsistency issue in the Point of Sale (POS) system. Previously, users could modify tax settings while a POS session was open, leading to discrepancies between receipts and invoices. The change now prevents these modifications, ensuring accurate financial reporting.

Original PR description

There is a safeguard in account.tax.write prevents modifying taxes as it is forbidden to modify a tax used in a POS order not posted. This guard only applies for a predefined set of fields in…

There is a safeguard in account.tax.write prevents modifying taxes as it is forbidden to modify a tax used in a POS order not posted. This guard only applies for a predefined set of fields in account_tax.py.

After 18.0, the tax-included behavior is controlled through the `price_include_override` field instead of `price_include`. However, this field was not added in the forbidden fields, allowing users to modify tax inclusion while a POS session is open.

This bypasses the safeguard and can lead to inconsistencies, as the POS caches tax configuration at session start.

For example, changing this setting mid-session may differences between POS receipts and backend invoices.

By adding `price_include_override` to the forbidden fields,
the UserError can properly be raised.

Additional note: test_fiscal_position_between_frontend_and_backend was updated to close the POS session before changing taxes since the safeguard now correctly blocks this.

Related ticket: opw-6042367

Forward-Port-Of: odoo/odoo#254487

#pos#tax#accounting#consistency

[FIX] hr_expense: use the company of the expense for the payment journal entry

PR #256457

Coresaas-18.3hr_expenseMedium

This update resolves a problem where creating payments for expenses linked to a 'Branch' company would trigger an error. The fix ensures the payment journal entries correctly link to the expense's company, preventing these errors and improving the accuracy of financial reporting for multi-company setups.

Original PR description

**Steps to reproduce:**
- Install Accounting and Expenses
- Create a Branch company (e.g. Branch)
- In company selector, select both Branch (as main) and its parent

- In Bank journal settings, make sure that there is an outstanding payment account for "Manual Payment"

- Create an employee in Branch
- Create an expense:
  * Category: [any] (e.g. [EXP_GEN] Expenses)
  * Total: [anything] (e.g. 100.00)
  * Employee: [the created employee]
  * Paid By: company
  * Company: Branch
- Create Report
- Submit to Manager
- Approve

**Issue:**
A UserError is raised because it tries to create a payment in Branch linked to a journal entry in the parent company.

**Cause:**
The payment is initialized with the company of the expense but not the related journal entry.


**(A similar issue happens with an expense paid by the employee when generating the bill upon approval of the expense sheet)**

opw-6007859



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

Forward-Port-Of: odoo/odoo#256172
Forward-Port-Of: odoo/odoo#254434

There is a safeguard in account.tax.write prevents modifying taxes as it is forbidden to modify a tax used in a POS order not posted. This guard only applies for a predefined set of fields in account_tax.py. After 18.0, the tax-included behavior is controlled through the `price_include_override` field instead of `price_include`. However, this field was not added in the forbidden fields, allowing users to modify tax inclusion while a POS session is open. This bypasses the safeguard and can lead to inconsistencies, as the POS caches tax configuration at session start. For example, changing this setting mid-session may differences between POS receipts and backend invoices. By adding `price_include_override` to the forbidden fields, the UserError can properly be raised. Additional note: test_fiscal_position_between_frontend_and_backend was updated to close the POS session before changing taxes since the safeguard now correctly blocks this. Related ticket: opw-6042367 Forward-Port-Of: odoo/odoo#254487

**Steps to reproduce:** - Install Accounting and Expenses - Create a Branch company (e.g. Branch) - In company selector, select both Branch (as main) and its parent - In Bank journal settings, make sure that there is an outstanding payment account for "Manual Payment" - Create an employee in Branch - Create an expense: * Category: [any] (e.g. [EXP_GEN] Expenses) * Total: [anything] (e.g. 100.00) * Employee: [the created employee] * Paid By: company * Company: Branch - Create Report - Submit to Manager - Approve **Issue:** A UserError is raised because it tries to create a payment in Branch linked to a journal entry in the parent company. **Cause:** The payment is initialized with the company of the expense but not the related journal entry. **(A similar issue happens with an expense paid by the employee when generating the bill upon approval of the expense sheet)** opw-6007859 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#256172 Forward-Port-Of: odoo/odoo#254434