**Steps to reproduce**:
1. Install the `accounting` module.
2. Activate a foreign currency form `Accounting -> Configuration -> Currencies` and fetch its exchange rate.
<img width="599" height="267" alt="image" src="https://github.com/user-attachments/assets/34e7c719-20f7-4cd0-a1d6-0e94764461ba" />

3. Create an invoice using the company’s default currency (e.g., USD).
4. Register a payment using the foreign currency (e.g., VES).
5. Reconcile the payment with the invoice.
6. Print the payment receipt PDF.

**Observations**:
In the printed PDF, under the `Amount In Currency` column, the amount is incorrectly displayed.

For example, suppose `1 USD` = `100 VES`.
- An invoice of `100 USD`  is created.
- A payment of `10,000 Bs` is registered (equivalent to 100 USD).
- When the payment receipt is printed, the output appears as:

```
| Invoice Number     | Reference         | Amount In Currency | Amount      |
|--------------------|-------------------|--------------------|-------------|
| INV/2025/00001     |                   |                    |  100.00 USD |
| PBNK1/2025/00001   | INV/2025/00001    | -100.00 Bs         | -100.00 USD |
```
Here, the `Amount In Currency` for the payment line shows **100 Bs** instead of the correct **10,000 Bs**.

**Issue**:
The payment receipt uses the `_get_reconciled_invoices_partials()` method to fetch details about reconciled invoices. However, the report incorrectly uses the `amount` field (in company currency) for the `Amount In Currency` column, leading to this mismatch.

**Solution**:
The report now uses `(debit/credit)_amount_currency` instead of `amount` to correctly reflect the foreign currency values in the `Amount In Currency` column.

opw-4898706

Forward-Port-Of: odoo/odoo#219439

Steps to reproduce:
- Go to Invoicing > Configuration > Accounting > Currencies:
    - Enable the Euro currency
- Set company currency to USD
- Go to any partner form (e.g. Azure Interior):
    - In Sales & Purchase tab: - Set Supplier Currency to Euro
- Create a purchase order from the UI:
    - Select Azure Interior → Currency is correctly updated to Euro (via onchange)

- Install the Approvals module
- Create a storable product "P1":
    - Under Purchase tab: - Vendor: Azure Interior - Price unit: 5 EUR
- Create an approval request:
    - Request Owner: Marc Demo
    - Product: P1
    - Approver: Mitchel Admin
- Submit and approve the request
- Click on "Create Purchase Order"

Issue:
The purchase order is created with the correct partner and product. But the currency is incorrectly set to the company currency (USD), instead of the supplier's currency (Euro).

Cause:
The currency was updated via an `@onchange`, which is only triggered in the UI.
When creating a PO programmatically (e.g. via approvals or in a test), the onchange is not executed and the currency falls back to the company default.

Solution:
Replace the `@onchange` logic for `currency_id` with a stored compute field.
This ensures that the correct currency is always computed, regardless of how the purchase order is created.

opw-4938390

**Before this commit:**
When creating an invoice payment with the "automatic invoice" option enabled in Sales settings and using a saved payment token, an email is sent to the customer before the transaction move is posted and the invoice payment status is updated to "In Payment." This results in the email incorrectly asking the customer to remit payment, even though the payment is already being processed.

**Steps to Reproduce:**
1. Enable "Automatic Invoicing" from Sales settings.
2. Enable and publish any payment provider (e.g., Demo) in test mode.
3. Create an invoice and generate a payment link. Open the link in a new incognito tab and pay using any dummy card number (ensure the "Save my payment details" checkbox is checked). This saves the payment token for the partner.
4. Create a new invoice with the same partner, then register payment. Select the payment method and the previously saved token, then confirm.
5. Observe that the payment status is "In Payment," but the email sent to the customer incorrectly asks them to remit payment.

**Fix:**
This change prevents payment notification emails from being sent automatically when the payment is manually created from the payment register wizard.

Ticket [link](https://www.odoo.com/odoo/project/967/tasks/4850293)
opw-4850293

Forward-Port-Of: odoo/odoo#221587

Problem:
When `s_carousel` is placed inside an `s_table_of_content` and the navbar of the TOC is hidden (visibility set to "Hide" on desktop), saving and reopening the editor results in a traceback.

Cause:
The traceback occurs due to the following sequence: In `WysiwygAdapterComponent.startEdition`, calling `await super.startEdition()` will invoke `createInvisibleElement()` if the navbar is hidden. This, in turn, activates the scroll spy by calling `_activateScrollSpy()` while starting the TOC snippet. That triggers `widgets_start_request`, which starts the `s_carousel` snippet.

However, at this point the `wysiwyg` instance has not yet been attached to the `wrapwrap` element. That happens later, at: https://github.com/odoo/odoo/blob/f12050f75ae9ae1125c0c01ec504a24bd401b1ea/addons/website/static/src/components/wysiwyg_adapter/wysiwyg_adapter.js#L318 and only after the `await super.startEdition()` call at: https://github.com/odoo/odoo/blob/f12050f75ae9ae1125c0c01ec504a24bd401b1ea/addons/website/static/src/components/wysiwyg_adapter/wysiwyg_adapter.js#L232

This delay causes a race condition when starting widgets like `s_carousel` that rely on the presence of the `wysiwyg` instance.

Solution:
Attach the `wysiwyg` instance to the DOM before
`await super.startEdition()` in
`WysiwygAdapterComponent.startEdition`.

Steps to reproduce:
- Add a Table of Content block
- Insert a Carousel inside the content
- Set the TOC navbar visibility to "Hide" on desktop
- Save the page
- Reopen the editor
- A traceback occurs

opw-4971409

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

Forward-Port-Of: odoo/odoo#221200

**Before this commit:**
When creating an invoice payment with the "automatic invoice" option enabled in Sales settings and using a saved payment token, an email is sent to the customer before the transaction move is posted and the invoice payment status is updated to "In Payment." This results in the email incorrectly asking the customer to remit payment, even though the payment is already being processed.

**Steps to Reproduce:**
1. Enable "Automatic Invoicing" from Sales settings.
2. Enable and publish any payment provider (e.g., Demo) in test mode.
3. Create an invoice and generate a payment link. Open the link in a new incognito tab and pay using any dummy card number (ensure the "Save my payment details" checkbox is checked). This saves the payment token for the partner.
4. Create a new invoice with the same partner, then register payment. Select the payment method and the previously saved token, then confirm.
5. Observe that the payment status is "In Payment," but the email sent to the customer incorrectly asks them to remit payment.

**Fix:**
This change prevents payment notification emails from being sent automatically when the payment is manually created from the payment register wizard.

opw-4850293

Forward-Port-Of: odoo/enterprise#91570