This fix grants payroll officers the necessary permissions to access the payslip menu in the HR Payroll module. Previously, payroll officers were unable to view or manage payslips due to missing menu access rights. This change enables them to perform their core job responsibilities of managing employee payroll information.

task-3497444

Forward-Port-Of: odoo/enterprise#47096

This update adds the new Swiss federal tax scale V that became effective on January 1st, 2024. The payroll system now includes the updated tax rates required by Swiss tax authorities, ensuring accurate tax calculations for employees in Switzerland going forward.

Since 1st January 2024 the tax scale V has been added 
source: https://www.estv.admin.ch/estv/fr/accueil/impot-federal-direct/impot-a-la-source/baremes-is-salaires.html

This update activates the journal filter feature across all European country-specific EC sales reports (Austria, Belgium, Germany, Estonia, Luxembourg, Netherlands, and Sweden). The journal filter allows users to filter EC sales data by specific journals, bringing these localized reports in line with the generic report functionality that already had this feature enabled.

The aim of this commit is setting the journal filter to true on EC sales reports. The generic report already has the filter activated. This commit activates the filter for all the EC sales reports.

no task id (asked by tsb)

Forward-Port-Of: odoo/enterprise#55177

This fix corrects an issue where the system was attempting to auto-detect negative invoice lines on the WSFBE webservice, which doesn't support this feature. The auto-detection now only runs on the WSFE webservice where it is properly supported. This ensures Argentine electronic invoicing processes work correctly without errors.

Before this method we were trying to use the auto detect on WSFBE and it is not supported on that webservice.

Adhoc Helpdesk 68703

Forward-Port-Of: odoo/enterprise#53458

This fix corrects how Odoo validates company relationships when creating records with linked fields. Previously, when a record had no company assigned, the system would incorrectly allow selection of related records from other companies during creation, only to fail when saving. Now the validation properly restricts field options based on company rules from the start, preventing confusing errors and improving the user experience.

of check_company=True fields.

Suppose two models

class A:

    company_id = fields.M2O() # not required

class B:
    _check_company_auto = True

    company_id = fields.M2O() # not required
    a_id = fields.M20(check_company=True)

and the following code:

a = A.create({'company_id': 1})
b = B.create({'a_id': a.id, 'company_id': False})

The creation of B will fail because of the multi-company checks, which is expected.

Nevertheless, since 0d30cc2bc9b9cc2b805d6c2d0a440f185c648da0, the domain of the field a_id would be:

(company_id and ['|', ('company_id', '=', False), ('company_id', 'in', [company_id])] or []) + ([])

which means that through the interface, if you create a record b following the example above (no company_id on b), the evaluated domain would be empty, allowing to select records of class A, even if they belong to another company. Of course, this would lead to a multi-company error when trying to save the record.

This commit makes sure that the right domain is applied on check_company=True fields, even if the current record has no value in its `company_id` field.

opw-3629374

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

Forward-Port-Of: odoo/odoo#146331

This fix enables the duplicate bill warning feature to work properly when editing existing invoices. Previously, the warning would not appear in edit mode. Now it will alert users as soon as they leave the relevant field, helping prevent accidental duplicate bill entries.

The aim of this commit is to make the duplicate bill warning works in edit mode.
This is a backport of some fixes that were done in the following commit: cb694599583f5df1667984fee01bbcc4c8b2d409

Before the commit:
The warning couldn't be triggered in edit mode.

After the commit:
The warning is triggered as soon as the field is unfocused.

task-id: None

Forward-Port-Of: odoo/odoo#149416

This update resolves a technical issue that prevented customers from opening the mobile menu when using online payment methods in self-ordering mode. The fix removes unnecessary image data that was causing system errors, allowing the payment process to work smoothly without affecting functionality.

Prior to this commit, using an online payment method with an image in self-ordering mode resulted in an issue preventing the opening of the mobile menu. The specific error encountered was:
`TypeError: Object of type bytes is not JSON serializable`

This issue arose due to the image field being of type bytes. Since the image field is not necessary for self-ordering, this commit addresses the problem by preventing the loading of the image for a payment method, resolving the serialization error.

opw-3624798

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