Website visitor records are now managed more efficiently without relying on browser cookies. This improves performance for visitor-related features such as appointments, events, and push notifications while keeping the user experience consistent.

Counterpart of the community change, where the main changes are:
- Visitor are not handled with cookies anymore.
- Visitor is managed with a raw SQL UPSERT Query

See community PR for more details

task-2867045

Users working with multiple companies can now select one journal group per company when filtering account reports. This makes it easier to apply consistent journal filters across companies while keeping the existing single-company behavior unchanged.

In mono-company, journal groups are exclusive, which makes sense.

However, in multi, the user should be able to select one (and only one) journal group per company.

This would for example allow the user to apply the same filter in the displayed journals for each of the companies.

This PR allows for this behaviour, while not changing the way mono-company works.

task-2784137

Purchase bill recurrence handling has been aligned with the broader recurring entries feature. This helps ensure accounting assets and recurring bills behave consistently as the posting schedule options evolve.

[Task-2855545](https://www.odoo.com/web#id=2855545&model=project.task)

The journal audit report now handles report options more safely when opening, especially when options come from another report or include journal groups. This reduces the chance of errors and helps users access the report consistently.

When opening the report, we are checking if any journal has been
specifically selected to unfold it.
But as we can't be completely sure of what is in the options given
to the report, as they can be from another report, there can
be some issue in specific cases (for example, journal groups in the
journal options).
Thus, replace the condition with a get to better handle use cases
where the selected key could not be in every line of the journal
options.

The bank reconciliation tool has been reworked to use a clearer side-by-side layout and more standard screens. This should make reconciliation results more consistent with the final journal entries while moving automatic validation to a scheduled process to reduce slowdowns when opening the widget.

task: 2555114

This pull request prepares the Enterprise edition for the SaaS 15.4 release. It is a release management update that helps align the product versioning for the next hosted Odoo release, with no specific business feature changes identified from the provided details.

In a BE company Go to Accounting / Reporting / Audit Reports / Tax Report Click Export(XML) Report should always have a value from grid '00' even if 0 opw-2845529 Forward-Port-Of: odoo/enterprise#28007 Forward-Port-Of: odoo/enterprise#27400

In a BE company
Go to Accounting / Reporting / Audit Reports / Tax Report
Click Export(XML)
Report should always have a value from grid '00' even if 0

opw-2845529

Forward-Port-Of: odoo/enterprise#28007
Forward-Port-Of: odoo/enterprise#27400

When generating a SEPA XML file for a Batch Payment non-Latin characters are currently removed from the XML. It is expected as SEPA only supports latin characters. However, no warning is shown to the user which perturbs them as they receive a modified XML (non-Latin chars are replaced by blanks). Step to reproduce the issue: 1. Create an European company. 2. Install the Accounting module and install an European package 3. Go to Accounting > Configuration > Journals > Bank and set an acc

When generating a SEPA XML file for a Batch Payment non-Latin characters
are currently removed from the XML. It is expected as SEPA only supports
latin characters. However, no warning is shown to the user which perturbs
them as they receive a modified XML (non-Latin chars are replaced by blanks).

Step to reproduce the issue:
1. Create an European company.
2. Install the Accounting module and install an European package
3. Go to Accounting > Configuration > Journals > Bank and set an account number
(e.g.: GB33 BUKB 2020 1555 5555 55)
4. Ensure that on the same page, the SEPA is available in the Outgoing Payments
5. Create a new vendor with Latin letters in its address.
6. Make sure that the new vendor has an Account Number in his Accounting tab
(e.g.: GB94 BARC 1020 1530 0934 59)
7. Go to Vendors > Payments and create one with Payment Method set to
"SEPA Credit Transfer" (ensure that Vendor Bank Account has been filled).
8. Go to Vendors > Batch Payments and create an Outbound SEPA payment. Select
the Payment we created in the previous step.
9. Generate the SEPA XML file.
You will see that in the address of the vendor, non-Latin characters have
been replaced by blanks without warning the user.

Solution: SEPA has released a mapping [1] to transform these non-Latin
characters into Latin ones but this mapping will not be directly included into
Odoo. This will be done by the R&D team and thus will take more time to develop
and is expected to arrive in later releases. In the meantime, a warning
message will just be shown to the user so that he knows that his SEPA XML
will be altered to fit the SEPA standards. A previous commit [2] made possible
to warns the user when generating the XML file.

[1] https://www.europeanpaymentscouncil.eu/document-library/guidance-documents/sepa-requirements-extended-character-set-unicode-subset-best
[2] https://github.com/odoo/enterprise/commit/b5d0420cb27aaef225c77b5f2b07657f8b9866a8

opw-2806383

Forward-Port-Of: odoo/enterprise#26894

**The Issue:** After creating a sale order, then create a new invoice with a down payment (percentage option), the invoice doesn't have the referrer_id even though that it was set on the sale order. **The fix** Adding the referrer_id to the invoice created from a sale order. opw-2820420 Forward-Port-Of: odoo/enterprise#27730

**The Issue:**
After creating a sale order, then create a new invoice with a down payment (percentage option), the invoice doesn't have the referrer_id even though that it was set on the sale order.

**The fix**
Adding the referrer_id to the invoice created from a sale order.

opw-2820420

Forward-Port-Of: odoo/enterprise#27730

PURPOSE This commit removes the 'use_visitor_timezone' duplicate field from the form view. LINKS Task-2863947 Forward-Port-Of: odoo/enterprise#27764

PURPOSE

This commit removes the 'use_visitor_timezone' duplicate field
from the form view.

LINKS

Task-2863947

Forward-Port-Of: odoo/enterprise#27764