Belgian balance sheet and profit and loss reports now match the latest official versions for companies, associations, and foundations. Users will see the relevant report versions based on their selected chart of accounts, with clearer report selection to avoid choosing the wrong format.

Currently, the BS and P&L version for Belgium was a combination of different old versions and not representing the latest official versions.

In Belgium there are 4 BS versions for companies, depending on the size of the company and the company form. For associations and foundations there are 2 BS versions, depending on the size.

For the P&L we have 2 version for companies and 2 versions for associations and foundations, both depending on their size.

All versions have been implemented and will be available based on the selected CoA (either for companies or associations and foundations).

task-3086473

Related to https://github.com/odoo/odoo/pull/117480
Related to https://github.com/odoo/upgrade/pull/5291

This update adds test coverage for a collaboration scenario in Knowledge where content may be reloaded after a shared editing session starts. It helps ensure editing behavior remains consistent for users working together on the same article.

Add a test to ensure that `_notifyNewBehavior` is correctly executed twice
in case the content is reset because of a resynchronization after opening a
channel in collaboration.

task-3551505

Forward-Port-Of: #49112
Forward-Port-Of: #49164

The Manufacturing Order Overview now brings in key cost analysis information, including employee costs, so users can see production and cost details in one place. The separate Cost Analysis button has been removed from individual manufacturing orders, while multi-order cost analysis remains available from list actions.

The point of the MO Overview is to be a single place where you can
quickly get all info for a single Manufacturing Order. Since there is
currently some common data in both the Overview and the Cost Analysis
report, we fuse the missing data directly from the Cost Analysis into
the Overview.

Then, we remove the single Cost Analysis from the MO form since its
included in the Overview as well, but keep the one usable from the list,
as it's used to aggregate multiple productions.

Part of task-3251506

See odoo/odoo#114536
Upgrade PR: odoo/upgrade#5210

The SEPA payment and payroll SEPA features have been consolidated into their main modules, reducing the number of separate add-ons to maintain. This should make future updates easier while keeping SEPA payment capabilities available in the standard modules.

In an effort to simplify the codebase and enhance maintainability, this commit merges account_sepa_pain_001_001_09 into account_sepa and hr_payroll_account_sepa_09 into hr_payroll_account_sepa.

Task-3455391

The analytic search experience is now aligned between timesheets and accounting. Accountants can access the same relevant fields and filters provided by related modules, making analysis and reporting more consistent.

The aim is to harmonize the analytic search view between `hr_timesheet` and `account` by creating an inheritance from `analytic`. This allows the accountant to have access to all the fields and filters defined in other modules.

task-3463639

This update makes activity views more consistent and useful across Documents, Helpdesk, Events, Manufacturing, Quality, and related apps. Users can access clearer activity information from the systray and see additional context such as ticket status or quality control dates, reducing navigation friction and preventing errors in Documents activity views.

Note that the 2 first commits (fix) are from another task not yet merged but necessary for this task, they will be removed when merged.

[IMP] crm_enterprise, documents: simplifies the systray

The change is related to odoo/odoo#128904 where we simplify the systray and
define the list view as the default view openned from the systray.
Here we override the default for document to open the activity view instead.

We also update the test as we have now only one clickable area for the activity
group instead of multiple one.

[IMP] various: add activity view for different model

We add the activity view for:
- event.event (see odoo/odoo#128904). As it is overridden in event_enterprise
module, we add it here as well.
- mrp.eco
- quality.alert, quality.check, quality.point

[IMP] various: improve activity view

The following activity view have been improved:
- helpdesk.ticket: kanban_state added
- quality.check: control_date added

Technical notes:
- o_text_block added on text that can be long to limit their size on some other
activity view.
- DocumentsActivityRenderer.getDocumentsInspectorProps, added fields in the
object returned otherwise we get a stack trace when going to the activity view
of document.

Task-3300854

Spreadsheet pivot table cells now work with actions such as viewing underlying records and setting filters. This makes pivot-based spreadsheet analysis more consistent and easier to use for business users.

Large bank transaction imports now show an in-progress indicator on the dashboard so users know synchronization is still running. The import process is also split into smaller batches, making it more reliable when handling high transaction volumes.

…number of transactions

When importing a huge number of transactions, it can take a few minutes until the provider is ready for us to import the entirety of transactions, ORM can also be slow at creating the huge number of transactions.
To improve usability, we added a spin on the dashboard while the import is not finished as well as split the import in chunk (commiting in database in between so that it will eventually manage to import everything)

Kiosk draft orders can now be seen from all point-of-sale configurations in the same company. This helps restaurant and sales staff manage incoming kiosk orders more consistently across different counters or sessions.

… with all pos_config

This commit allows to share kiosk orders with all pos_configs. A new pos_session boolean attribute is added to check if there is a kiosk config in the company. In point_of_sale and pos_restaurant, if the company they belong to contains a kiosk config, the ticket_screen will retrieve the kiosk draft orders.

Related: https://github.com/odoo/odoo/pull/138264

This update adds Kenya payroll tax deduction card reporting for employees and refreshes payroll calculations to reflect current local tax requirements. It also adds new payslip inputs and fields for items such as bonuses, non-cash benefits, pension contributions, and employer costs, helping payroll teams produce more complete and compliant records.

Updated labels, help text, translations, and field visibility across several Latin American localization screens. This reduces confusion for users and helps ensure company-specific fields only appear where relevant.

This PR aims at improving the UI by adding some invisible tag to avoid having field leaking on other companies. Also changing tooltip and label of fields.

Adding a commit for translation. 

task: 3270458

Odoo Studio now supports editing visibility, required, and read-only rules after those rules moved to a new expression format. This restores an important configuration workflow for users and prevents fields from embedded views being incorrectly treated as part of the main view.

This update lets teams add and display custom properties in Appraisals and Planning, making records easier to tailor to business needs. It also aligns Helpdesk and Knowledge with the latest property display behavior, so information can appear consistently in cards, calendars, and related views.

### 1. Add properties in hr_appraisal and in planning
This PR adds properties (and related properties definitions) to the
following models:
- hr_appraisal.hr_appraisal (hr_appraisal.hr_department)
- planning.planning (planning.planning_views)

These have been added on the related form, kanban and calendar views when
applicable.

### 2. Remove hideKanbanOption from helpdesk's properties field

In the related community PR, the hideKanbanOption is being removed from
the properties field as there is no more reason to prevent users to
show properties in kanbans and calendar popovers.
This PR removes the usage of this option in the helpdesk module.

### 3. Adapt to "Add Properties" button changes
In the related community PR, hiding the "Add a property" button from
the properties field and using the cog menu to add properties becomes
the normal behavior, so there is no need to create an action to add the
button in the cogmenu for each view anymore.

For the same reason, the "hideAddButton" option has been replaced in
favor of a "showAddButton" option. This commit removes the usage of the
old option and adds the new one in Knowledge (in which case there is no cog
menu).

Task-3458627

Odoo removed an older internal messaging mechanism and updated affected areas to use newer shared communication paths. This reduces outdated code and helps keep features like push notifications and barcode workflows easier to maintain without changing expected business behavior.

This commit removes the legacy global bus (core bus) and the places where it was used.
The main users of this bus were the public widgets, a shared bus has been added on PublicWidget.
Some of the uses were dead code and has been removed.

task: 3439226

Adds New York state payroll tax handling to US payroll so companies can calculate employee wages and withholdings more accurately for NY-based staff. The update also extends related payroll, accounting, employee, contract, demo, and W-2 data so reporting and testing reflect the new state tax rules.

TaskID: 3535163

This update modernizes internal data query handling across accounting, data merge, and manufacturing reporting. It should help keep business reports and data operations reliable as the platform’s underlying database tools evolve, with little direct change for end users.

Companion of https://github.com/odoo/odoo/pull/138019.

Subscription settings are now grouped into reusable plans, making it easier to manage many similar subscriptions consistently. Changes to a plan can apply across related subscriptions, while invoicing setup is simplified by moving journal handling into sales.

This commit aims to improve the usability of subscription by
changing the behaviour of template and recurrence.

Before this commit subscription "so.template" were used after
they had been assigned which was antithetical to what a template
should be. On top of that, subscription and rental share
"sale.temporal.recurrence" but had completly different use and
paradigm for it and it's related pricings.

This commit aims to reduce the complexity and chaos related to those issue
by removing fields that were use after the creation of the subscription
and the billing recurrence realted fields on a new,
subscription-related model "sale.subscription.plan".

This plan will now regroup all the information related to the
subscription using it and any change to this model will be
applied to all related subscriptions. This make subscription
more user friendly for user managing multiple similar subscriptions.

In addition, invoicing journal was removed from subscription and
merged into sale directly. (See community PR : https://github.com/odoo/odoo/pull/133983)

task-id: 3471665

The customer portal has been redesigned across several services to use clearer categories and consistent cards. This makes it easier for customers to find appointments, documents, tickets, subscriptions, signed documents, and knowledge content in one familiar experience.

Odoo Studio now uses the correct report model when opening reports from the reports view, even when it differs from the current action. This prevents incorrect record loading and avoids related crashes or layout issues, including hiding an invalid custom-fields button and improving right-to-left resizing behavior.

From the reports kanban view, delete the filter on model and click on a report that has a different model than that of the action.

Before this commit, the loading of the record ids on which the report applies was wrong.

After this commit, the report's model is retrieved from the initial loading of its data. Hence the model on which it applies is correct.

Expense reports paid by employees can create vendor bills with receipt attachments already populated from the report. This fix prevents OCR from running again on those generated bills, avoiding unnecessary processing and possible duplicate or conflicting data extraction.

When posting entries from a report paid by employee that has receipts attached, a bill is generated with the receipts copied in the bill attachments. Since the vendor bill is already filled with the data from the report, the OCR shouldn't be used again for the bill.

task-3550037

This fixes a case where a fallback pro forma PDF could be saved as the official invoice report after a Send & Print error. Only successfully generated invoice PDFs are now linked, helping prevent incorrect documents from being treated as final invoices.

When triggering the Send & Print with the allow_fallback_pdf=True, if an error occurs (e.g.: no UNSCPC code on the product with CFDI), the proforma PDF is generated instead and is assigned to `invoice_report_file_id`. However, only a successful PDF should be bound to this field.

task-3542881

related-https://github.com/odoo/odoo/pull/138206

The Peruvian electronic invoicing module now reuses Odoo's shared UBL 2.1 invoice format instead of maintaining separate duplicate templates. This simplifies future maintenance and helps keep Peru e-invoicing aligned with common invoice format updates, with little direct change expected for users.

Currently the Peruvian EDI module defines its own UBL templates. Since the Peruvian electronic invoices use UBL 2.1, it makes a lot more sense to inherit from our generic UBL 2.1 format defined in `account_edi_ubl_cii` to remove code duplication and have a single point to edit the generic UBL parts.

[task-3415758](https://www.odoo.com/web#id=3415758&cids=1&menu_id=4720&action=333&active_id=967&model=project.task&view_type=form)

Related to https://github.com/odoo/odoo/pull/132529
Related to https://github.com/odoo/upgrade/pull/5131

Steps to reproduce: ------------------- - create an application for a job; - click on "Generate Offer"; - choose an other date for "Contract Start Date"; - save and open the link in another session; - complete the salary configuration; - open the new contract. Issue: ------ The start date is not correct. Cause: ------ we force the date to be the first of the current month. Solution: --------- Use offer date with a fallback of the first of the month because the field `contra

Steps to reproduce:
-------------------
- create an application for a job;
- click on "Generate Offer";
- choose an other date for "Contract Start Date";
- save and open the link in another session;
- complete the salary configuration;
- open the new contract.

Issue:
------
The start date is not correct.

Cause:
------
we force the date to be the first of the current month.

Solution:
---------
Use offer date with a fallback of the first of the month because the field `contract_start_date` is not required.

opw-3544803

Forward-Port-Of: odoo/enterprise#49165

The fields were not translatable but displayed on the /salary_package/simulation page

The fields were not translatable but displayed on the /salary_package/simulation page

As the timezone is not a required field we should check first that it is set before using it. task-3555709 Forward-Port-Of: odoo/enterprise#48974

As the timezone is not a required field we should check first that it is set before using it.

task-3555709

Forward-Port-Of: odoo/enterprise#48974

Steps to reproduce: - Install l10n_ec_edi - Switch to an Ecuadorian company (e.g. EC Company) - Create a vendor bill: * Vendor: [a contact not in Ecuador] (e.g. Azure Interieur) * Journal: 001-001 Liquidaciones de Compra * Document Type: (03) Liquidación de compra de Bienes o Prestación de servicios * Payment Method (SRI): [any] (e.g. Sin utilización del sistema financiero) * Invoice Lines => Product: [any] - Taxes: [an EC tax] (e.g. IVA 12% (510, 01 Crédito IVA)) - Confirm in

Steps to reproduce:
- Install l10n_ec_edi
- Switch to an Ecuadorian company (e.g. EC Company)
- Create a vendor bill:
  * Vendor: [a contact not in Ecuador] (e.g. Azure Interieur)
  * Journal: 001-001 Liquidaciones de Compra
  * Document Type: (03) Liquidación de compra de Bienes o Prestación de servicios
  * Payment Method (SRI): [any] (e.g. Sin utilización del sistema financiero)
  * Invoice Lines => Product: [any] - Taxes: [an EC tax] (e.g. IVA 12% (510, 01 Crédito IVA))
- Confirm invoice
- Click on "ADD WITHHOLD"
- Add a withhold line with a tax having its l10n_ec_code_base value in L10N_EC_WTH_FOREIGN_GENERAL_REGIME_CODES list
(e.g. 501-422 22% Pago al Exterior - Beneficios Empresariales (Sin Convenio de Doble Tributación)
- Create and post Withhold
- Check the EDI xml linked to the withhold
=> "paisEfecPago" element has a "NA" value, but it should be the "l10n_ec_code_ats" value of the vendor country as we have used a tax having its "l10n_ec_code_base" code in L10N_EC_WTH_FOREIGN_GENERAL_REGIME_CODES list

Cause:
Only the first tax from the withhold lines is checked to determine if it is in L10N_EC_WTH_FOREIGN_GENERAL_REGIME_CODES list or not.
So, if the first tax is not in the list, the system considers that all taxes are not in the list (even if the second one is in the list) and it doesn't populate the correct data for "paisEfecPago" element in the edi xml. (same issue for "aplicConvDobTrib" and "pagExtSujRetNorLeg" elements)

Solution:
Check all the taxes instead of just the first one.

opw-3478597

Forward-Port-Of: odoo/enterprise#48463

The leave wizard was using an older field name for its date widget. The menus for appointment were not ordered properly. And the name of the menus did not match the name of the actions. task-3434098 Forward-Port-Of: odoo/enterprise#44400

The leave wizard was using an older field name for its date widget.

The menus for appointment were not ordered properly. And the name of the menus did not match the name of the actions.

task-3434098

Forward-Port-Of: odoo/enterprise#44400

to make UI less confusing, we hide the processing date field when multi mode is selected, also added a tooltip to the multi mode checkbox to explain what it does Task-3557829 Forward-Port-Of: odoo/enterprise#49069

to make UI less confusing, we hide the processing date field when multi mode is selected, also added a tooltip to the multi mode checkbox to explain what it does

Task-3557829

Forward-Port-Of: odoo/enterprise#49069

Current behavior: When you create an invoice through the QRCode on the tickets, you can select an usage for it. But the usage was never taken into account when creating the invoice, so the invoice was always created with the default usage. Steps to reproduce: - Install l10n_mx_edi_pos - Go in the Mexican company - Create a PoS and activate the QRCode on receipts - Open the PoS - Create an order and pay it but don't invoice it - Scan the QRCode (in private mode so you are not connected

Current behavior:
When you create an invoice through the QRCode on the tickets, you can select an usage for it. But the usage was never taken into account when creating the invoice, so the invoice was always created with the default usage.

Steps to reproduce:
- Install l10n_mx_edi_pos
- Go in the Mexican company
- Create a PoS and activate the QRCode on receipts
- Open the PoS
- Create an order and pay it but don't invoice it
- Scan the QRCode (in private mode so you are not connected to Odoo)
- Fill in the form and select an usage different from the default one
- Validate the form
- Go in the invoices and check the usage of the invoice

opw-3505203

Forward-Port-Of: odoo/enterprise#49116
Forward-Port-Of: odoo/enterprise#48708

Previously, when installing the `pos_restaurant_appointment` module after creating new tables in `pos_restaurant`, the module did not create ppointment resources automatically. Now we've added a `post_init_hook` that will automatically create these resources for tables that don't have any. Forward-Port-Of: odoo/enterprise#49103

Previously, when installing the `pos_restaurant_appointment` module after creating new tables in `pos_restaurant`, the module did not create ppointment resources automatically.

Now we've added a `post_init_hook` that will automatically create these resources for tables that don't have any.

Forward-Port-Of: odoo/enterprise#49103

**Steps:** - Open Planning without demo data - Add a role - Now look at the row containing the 'Total' **Issue:** - The corner of the frame around today's date is missing when the view is empty **Cause:** - Due to the border-left given for cells with not first-of-type, it's not showing the border around the total in all cells and showing just the left border in the first cell. **Fix:** - Remove the border-left given for the cell with not first-of-type because it's better to have a

**Steps:**
- Open Planning without demo data
- Add a role
- Now look at the row containing the 'Total'

**Issue:**
- The corner of the frame around today's date is missing when the view is empty

**Cause:**
- Due to the border-left given for cells with not first-of-type, it's not showing the border around the total in all cells and showing just the left border in the first cell.

**Fix:**
- Remove the border-left given for the cell with not first-of-type because it's better to have a border around the total when it's highlighted.

**Task:** 3446994

Forward-Port-Of: odoo/enterprise#45460

Turns out that commit 25645eb0 only partly fixed the dependency issue as the breadcrumbs template depens on both `Dropdown` and `DropdownItem`. Task: / Forward-Port-Of: odoo/enterprise#49138

Turns out that commit 25645eb0 only partly fixed the dependency issue as the breadcrumbs template depens on both `Dropdown` and `DropdownItem`.

Task: /

Forward-Port-Of: odoo/enterprise#49138

Since the new milk theme, the clickbot for click everywhere, didn't set the filters on the views. Now, the clickbot set all the filters on the views. This commit also add a test suit, to avoid future downgrades. This commit transform the clickbot to a module ES6. task-id 3535596 Forward-Port-Of: odoo/enterprise#49022 Forward-Port-Of: odoo/enterprise#48704

Since the new milk theme, the clickbot for click everywhere, didn't set
the filters on the views.

Now, the clickbot set all the filters on the views. This commit also add
a test suit, to avoid future downgrades. This commit transform the
clickbot to a module ES6.

task-id 3535596

Forward-Port-Of: odoo/enterprise#49022
Forward-Port-Of: odoo/enterprise#48704

When enterprise is installed as a package, importing this `odoo.addons.account_avatax` will raise an `ImportError` due to this missing file. @moduon MT-1075 Forward-Port-Of: odoo/enterprise#48613

When enterprise is installed as a package, importing this `odoo.addons.account_avatax` will raise an `ImportError` due to this missing file.

@moduon MT-1075

Forward-Port-Of: odoo/enterprise#48613

The BACS settings in the account_bacs module were not searchable following a forward port to the saas-16.1 branch. This commit updates the outdated syntax to make the settings searchable and functional again. task-3550949 Forward-Port-Of: odoo/enterprise#49084 Forward-Port-Of: odoo/enterprise#48930

The BACS settings in the account_bacs module were not searchable following a forward port to the saas-16.1 branch.
This commit updates the outdated syntax to make the settings searchable and functional again.

task-3550949

Forward-Port-Of: odoo/enterprise#49084
Forward-Port-Of: odoo/enterprise#48930

[FIX] global_filters: prevent unwanted errors while saving In global filters of type 'relation', changing set domains of model X to model Y, followed by changing the related model from X to Y generated a field validation error while saving. This issue occured because index of type 'number' was passed to `add` method whereas index of type 'string' was passed to `delete` method. As a result, '_wrongFieldMatchingsSet' was never emptied as 'delete' method did not work as intended due to

[FIX] global_filters: prevent unwanted errors while saving

In global filters of type 'relation', changing set domains of model X to model Y, followed by changing the related model 
from X to Y generated a field validation error while saving.

This issue occured because index of type 'number' was passed to `add` method whereas index of type 'string' was 
passed to `delete` method. As a result, '_wrongFieldMatchingsSet' was never emptied as 'delete' method did not work 
as intended due to strict equality. 

This PR fixes the issue by ensuring that the type of index passed in params of `selectedField` method is always `number`.

Task ID : 3272667

Forward-Port-Of: odoo/enterprise#49154
Forward-Port-Of: odoo/enterprise#43424

The commit(6b5eb6961bccd76c6e25948275499bece2f0075c) that creates a support ticket for the user directly has the side effect that user creates too much tickets for the same issue. After discussion with support team and POs, we decide to add the client id in the support ticket title to allow the support finding duplicate tickets. It's clearly not the best solution, but it will do the job in a short term. no task id Forward-Port-Of: odoo/enterprise#49206

The commit(6b5eb6961bccd76c6e25948275499bece2f0075c) that creates a support ticket for the user directly has the side effect that user creates too much tickets for the same issue.
After discussion with support team and POs, we decide to add the client id in the support ticket title to allow the support finding duplicate tickets.
It's clearly not the best solution, but it will do the job in a short term.

no task id

Forward-Port-Of: odoo/enterprise#49206

**Steps to reproduce the bug:** - Activate the packages and lot tracking - Create a new storable product tracked by lot - Add some stock for this product and give a lot and package number - Print the lot (or package) barcode - Open the barcode app and start a new inventory adjustment - Try to create a new line by scanning the lot (or package) barcode **Problem:** A traceback is triggered: “psycopg2.ProgrammingError: can't adapt type 'dict'” When scanning a lot, the function `_proce

**Steps to reproduce the bug:**
- Activate the packages and lot tracking
- Create a new storable product tracked by lot
- Add some stock for this product and give a lot and package number
- Print the lot (or package) barcode
- Open the barcode app and start a new inventory adjustment
- Try to create a new line by scanning the lot (or package) barcode

**Problem:**
A traceback is triggered: “psycopg2.ProgrammingError: can't adapt type
'dict'”

When scanning a lot, the function `_processBarcode` is called:

https://github.com/odoo/enterprise/blob/c0151bce3c60c69e7cadeb719a81c4a702b71c34/stock_barcode/static/src/models/barcode_model.js#L864

In this function, we check if a package has been scanned. If it is the
case, then the function `_processPackage` is triggered. Inside this
function, we call `_createNewLine` with the package ID, which allows
us to use it in the domain, and everything works perfectly:

https://github.com/odoo/enterprise/blob/c0151bce3c60c69e7cadeb719a81c4a702b71c34/stock_barcode/static/src/models/barcode_model.js#L891

https://github.com/odoo/enterprise/blob/c0151bce3c60c69e7cadeb719a81c4a702b71c34/stock_barcode/static/src/models/barcode_quant_model.js#L123

However, in this case, when scanning the lot, we have to check if
the package has been set, and if so, we are retrieving all the package
information into a dictionary instead of just adding his ID to the
barcodeData:

https://github.com/odoo/enterprise/blob/c0151bce3c60c69e7cadeb719a81c4a702b71c34/stock_barcode/static/src/models/barcode_model.js#L976

As a result, when the function `_createNewLine` is called, we try to
use all the package information (dict) into the domain, which generates
an error.

opw-3439193

Forward-Port-Of: odoo/enterprise#48087
Forward-Port-Of: odoo/enterprise#44580

This is the only place where disabled != deactivated Forward-Port-Of: odoo/enterprise#49177

This is the only place where disabled != deactivated

Forward-Port-Of: odoo/enterprise#49177