This fix ensures regular users can no longer create account types through document accounting or subscription workflows. It protects core accounting configuration from unintended changes, while preserving access for the super user when needed.

Nobody should be able to create account types, so no users (except the
super user) is able to do it anymore)

opw:2497616

This update adds performance testing support and related preparation work for the Events area. It helps ensure event features remain fast and reliable as the product evolves, with limited direct impact on day-to-day users.

Enterprise update for community cleaning in event test classes. See linked
community PR for more details.

Task-2703285 (event performance)
Task-2703289 (event testing)

Several app setup files were updated to use the current expected format and remove outdated entries. This helps keep these modules compatible with the platform and reduces maintenance issues without changing day-to-day user workflows.

*: crm_helpdesk, purchase_mrp_workorder_quality, sale_ebay, social_instagram

It is spelled `auto_install`, the `complexity` key is long gone, `qweb`
has been moved to `assets: {'web.assets_qweb': []}`. `js` and `css` are
long gone too.

Companion of odoo/odoo#80988

This fix ensures the Swedish point of sale session opening process correctly uses the chart of accounts check that was already provided. This helps prevent configuration issues from being missed when starting a POS session in Sweden.

Check COA parameter in the open_session_cb was actually never used

opw-2691615

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

This fix corrects the spacing between elements inside warning banners in the Planning area. The banner should now look cleaner and be easier for users to read when warnings appear.

Prior to this commit, the elements inside of the warning banner in the
planning module were not correctly spaced.

task-2703516

The Documents Spreadsheet app was adjusted to stay compatible with recent platform framework changes. This is an internal cleanup that helps keep spreadsheet-related document features stable without changing the user experience.

This commit is the counterpart of odoo/odoo#81031.

--- account_intrastat --- The European Commision has specified new transaction codes in EU 2020/1197. The old codes cannot be removed as they have been used in previous transactions. This adds the new transaction codes. It also sets the ordering of the codes by default to code, such that the user sees '1','11','12' rather than '1','2','3' for instance when they are searching transaction codes. --- l10n_nl_intrastat --- The format of the l10n_nl_intrastat declaration is changed accordin

--- account_intrastat ---
The European Commision has specified new transaction codes in EU 2020/1197. The old codes cannot be removed as they have been used in previous transactions.

This adds the new transaction codes. It also sets the ordering of the codes by default to code, such that the user sees '1','11','12'
rather than '1','2','3' for instance when they are searching transaction codes. 

--- l10n_nl_intrastat ---
The format of the l10n_nl_intrastat declaration is changed according to the changes found here:
https://www.cbs.nl/en-gb/participants-survey/overzicht/businesses/onderzoek/international-trade-in-goods

This means some changes to the intrastat declaration are required to accomodate the new two-digit transaction codes.

The user will be prevented from generating a monthly declaration that uses the old codes if the period is from January 2022 onward and prevented from generating a monthly declaration the new codes if the period is before January 2021.

The user will also be prevented from generating a declaration where both new and old codes are used in the same period.

The user is prevented not from using these codes in the wrong period but from generating a 'standard record layout (SRL)' declaration for submission using the IDEP+ web application. This is to allow some flexibility whilst maintaining the validity of the output file.

task: 2635472

Forward-Port-Of: odoo/enterprise#22736
Forward-Port-Of: odoo/enterprise#21007

latam 665 --- Proper show multiple observations codes when this case happens, show the number of the observation and the related HINT description. In this example we receive two codes 11 and 13, the observations codes are separated by a semicolon ### Before Not HINT message is show because our HINT function this not know how to process `11;13`  ### After HI

latam 665
---

Proper show multiple observations codes when this case happens, show the number of the observation and the related HINT description. In this example  we receive two codes 11 and 13, the observations codes are separated by a semicolon

### Before

Not HINT message is show because our HINT function this not know how to process `11;13`

![multi-osb-before](https://user-images.githubusercontent.com/7593953/140560679-f6f73eaa-f5f2-4f5e-beea-af8eb718e952.png)

### After

HINT message is shown for each observation codes

![multi-osb-after](https://user-images.githubusercontent.com/7593953/140560703-050ac682-d394-4821-a2fe-5eb71de601b3.png)

Forward-Port-Of: odoo/enterprise#22691
Forward-Port-Of: odoo/enterprise#22145

As it is not always a string like object to be converted we need to check before apply some checks expecting bytes or str Info: @wt-io-it PR to supplement my comment on https://github.com/odoo/enterprise/pull/22314 Forward-Port-Of: odoo/enterprise#22735 Forward-Port-Of: odoo/enterprise#22579

As it is not always a string like object to be converted
we need to check before apply some checks expecting bytes or str

Info: @wt-io-it

PR to supplement my comment on https://github.com/odoo/enterprise/pull/22314

Forward-Port-Of: odoo/enterprise#22735
Forward-Port-Of: odoo/enterprise#22579