The French balance sheet report now presents establishment costs before fixed assets and includes additional impairment accounts in the relevant tangible fixed asset lines. This improves report alignment with expected French accounting presentation and helps ensure these balances are reflected in the right sections.

Move establishment costs before fixed assets in the French balance sheet,
and include the missing 2912, 2913, 2914, and 2915 impairment accounts in
the relevant tangible fixed asset amortization/provision lines.

task-6226138

Forward-Port-Of: odoo/enterprise#117689

Users can now move through the journal creation wizard using keyboard arrow keys. This makes setup faster and more accessible for people who prefer or rely on keyboard navigation.

This commit aims to allow for navigation through the journal create wizard via keybaord arrows.

Related Odoofin PR: https://github.com/odoo/odoofin/pull/502
task-5796200

Forward-Port-Of: odoo/enterprise#105541

Spreadsheet users can now use a new filter label function to display the readable name of a selected global filter value, such as a customer name, instead of only its internal ID. This makes spreadsheet reports easier to understand and share with business users.

Before this commit:
If you use ODOO.FILTER.VALUE and have a customer set in the global filter, it returns the id of the customer. That can be useful in some cases but in others you might simply want the label.

Task: 6167605

Forward-Port-Of: odoo/enterprise#115984

Add the missing 2912, 2913, 2914, and 2915 accounts from the 2026 PCG so the French chart matches the balance sheet impairment mappings for tangible fixed assets. task-6226138 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#265160

Add the missing 2912, 2913, 2914, and 2915 accounts from the 2026 PCG
so the French chart matches the balance sheet impairment mappings for
tangible fixed assets.

task-6226138

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

Forward-Port-Of: odoo/odoo#265160

When a barcode scan matches a specific product variant, the product configurator now behaves the same as when the user searches by barcode: - The `always`-mode attribute (e.g. Color) is preselected from the matched variant instead of being hidden or left blank. - The `no_variant`-mode attributes (e.g. Size) are shown for user input. opw-6220883 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#276543 Forward-Port-Of: odo

When a barcode scan matches a specific product variant, the product configurator now behaves the same as when the user searches by barcode:
- The `always`-mode attribute (e.g. Color) is preselected from the matched variant instead of being hidden or left blank.
- The `no_variant`-mode attributes (e.g. Size) are shown for user input.

opw-6220883

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

Forward-Port-Of: odoo/odoo#276543
Forward-Port-Of: odoo/odoo#265189

When importing an xml, in the notes you can have codes. We don't want them to be shown in the form view of invoice. task-6365267 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#274996

When importing an xml, in the notes you can have codes. We don't want them to be shown in the form view of invoice.

task-6365267




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

Forward-Port-Of: odoo/odoo#274996

Task: 6167605 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#261793

Task: 6167605

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Forward-Port-Of: odoo/odoo#261793

In multicompany, it can happen that one company (let's call it company Origin) cannot handle a payment method in their country, so it uses another company's (company MoneyHandler), even if it's in another country. The accounting flows must be then adjusted: - In company Origin, the invoice must be matched by a clearing entry - In company MoneyHandler, payment must match its move (if it exists) with a clearing entry. The payment move doesn't exist if `account_accountant` is installed but no O

In multicompany, it can happen that one company (let's call it company Origin) cannot handle a payment method in their country, so it uses another company's (company MoneyHandler), even if it's in another country. The accounting flows must be then adjusted:

- In company Origin, the invoice must be matched by a clearing entry
- In company MoneyHandler, payment must match its move (if it exists) with a clearing entry. The payment move doesn't exist if `account_accountant` is installed but no Outstanding account is configured on the payment method line.

Same but opposite thing must happen for credit notes in company Origin that match a reimbursement in company MoneyHandler.

Cancellation of a payment must be reflected on the entries: deleting when feasible, reversing when not (unless a lock date/hash is present, which would block the cancellation)

_(To do: testing/review, credit note, cancellation/reversal of the payment)_

Task [link](https://www.odoo.com/odoo/project.task/6037525)
task-6037525

Forward-Port-Of: odoo/odoo#259197