Installing PoS will change some values on existing operations types.

To reproduce the issue
1. Install stock
2. Operations Types, edit Delivery:
   - Change the barcode
3. Install point_of_sale

Error: the barcode of Delivery is reset

When installing PoS, it will execute a generic method that creates
and updates all operation types:
https://github.com/odoo/odoo/blob/0bc90e7d74bd0792b9af7464256ba8770d894a25/addons/point_of_sale/data/point_of_sale_data.xml#L4
https://github.com/odoo/odoo/blob/14e9a698e333c3d6d2f7830353c34311de9ecb2c/addons/point_of_sale/models/stock_warehouse.py#L45-L50
https://github.com/odoo/odoo/blob/03478253c166238442d2f81f095de9fbcdfb265f/addons/stock/models/stock_warehouse.py#L350-L356
Thanks to this, the PoS operation type will be created. However, as
said in its docstring, the method will also update the existing
operation types. For instance, for Delivery:
https://github.com/odoo/odoo/blob/03478253c166238442d2f81f095de9fbcdfb265f/addons/stock/models/stock_warehouse.py#L1003-L1006
Its barcode and default source location will be reset. The update
will also reset the sequence prefix.

As said by the method name in PoS (`_create_missing_pos_picking_types`),
the idea here is just to create missing PoS types.

Similar issue with repair: the operations types of the user-created
wh will be reset.

OPW-4668505

**Steps to reproduce :**

1) Install Accounting and enable Analytic Accounting from the configuration. 
2) Create an analytic plan under Accounting > Configuration > Analytic Plans. 
3) Add a line with domain set to miscellaneous, applicability as mandatory and a prefix
4) Create an analytic account using the smart button on the plan. 
5) Create an asset record in one company in a multi-company setup. 
6) Switch to another company and try to access the asset created in the first company.

**Issue:**
A traceback occurs
```
AttributeError: 'bool' object has no attribute 'startswith'
```

**Cause:**

- When switching companies, all the chart of accounts records code for the previous company, will set as False.
- 
  When accessing an asset record expects a account code to call .startswith(), 
  but it fails when code is False. This leads to the above traceback.
https://github.com/odoo/odoo/blob/5a321b2327e36f3250b33c669bdb8bb344ab4cbd/addons/account/models/account_analytic_plan.py#L64-L67

**Solution:**
- Add a check to ensure that the account’s code exists before attempting to call .startswith().
  This makes the code more robust across multi-company environments.

opw-4745633

[FIX] account: customer's default invoice template as only attachment

Currently, when the user define an invoice template other than the
standard 'account.account_invoices', both the standard report and the
one defined by the user are attached to the mail when he hits the Send &
Print. We want the template chosen by the user to be the one sent &
printed.

The fix is to remove the default accounting action report from the
dynamic attachments : before, we were just removing the default action
report used for the current move. But e.g. if the partner had a default
report set in the field invoice_template_pdf_report_id, the default
report for the move was this one, and so we weren't removing the
accounting default one. This was causing the duplicate placeholder
because the default accounting report placeholder is already processed
in another method.

Also, we remove the configuration that sets the
'account.account_invoices' report as a default dynamic attachment.

Task-4681142
Runbot : https://runbot.odoo.com/runbot/bundle/18-0-invoice-report-per-partner-roto-361127

**Issue**
When modifying and reposting a vendor payment that does not have the highest sequence number, the payment's name (i.e., number) is regenerated using the next available sequence, rather than preserving the original. This issue only occurs when the Outstanding Payments account is configured for the journal.

**Steps to Reproduce**
1. Install the Accounting module.
2. Go to Accounting > Configuration > Journals, and open a Bank journal.
3. In the Outgoing Payments tab, set an Outstanding Payments Account.
4. Go to Accounting > Vendors > Payments.
5. Create and post two vendor payments (e.g., 00001 and 00002).
6. Reset the first one (00001) to draft, change any field (e.g., amount), and repost it.
7. The number changes to 00003 instead of preserving 00001.

**Root Cause**
When a vendor payment is modified and reposted, Odoo cancels and regenerates the associated account.move. If an Outstanding Payments account is configured — or was configured at any point — this triggers additional logic causing the move name to be reset to '/'. This placeholder indicates that the move is treated as if it were new, prompting Odoo to assign it the next number in the journal’s sequence. As a result, the payment loses its original number even though it conceptually refers to the same transaction.

**Fix**
The fix ensures the original number is preserved by restoring the payment's previous name only when it's clear that the move is being regenerated, not newly created. This is determined by checking that the move is linked to exactly one payment (i.e., a one-to-one relationship) and that its name is '/', indicating the move was regenerated.

Opw-4805870