Odoo Changelog — 2026-06-14

Sunday, June 14, 2026

3 changes · saas-18.3

Bug Fixes(3)

Resolved issues and error corrections

[FIX] point_of_sale: display positive order change on receipt

Coresaas-18.3point_of_sale

The Point of Sale receipt was previously showing incorrect change amounts as negative values. This update fixes a bug where an unnecessary negation was applied, now correctly displaying the change as a positive amount on the receipt. This ensures customers receive accurate information about their refunds.

Original PR description

**Issue:** The printed receipt in Point of Sale displayed a negative change amount when the customer paid more than the order total. **Before:** The receipt showed the change as a negative value…

**Issue:**
The printed receipt in Point of Sale displayed a negative change amount when the customer paid more than the order total.

**Before:**
The receipt showed the change as a negative value (e.g., `-$5,504.00`), which was misleading for customers.

**After:**
The receipt now correctly displays the change as a positive value (e.g., `$5,504.00`).

**Steps to Reproduce:**

1. Open a Point of Sale session
2. Add products to the cart (example total: `$49,496.00`)
3. Select the **Cash** payment method
4. Enter an amount greater than the order total (example: `$55,000.00`)
5. Observe that the **Change** field displays a negative value
6. Confirm the payment
7. Print the receipt and observe that the change amount is also negative

**Root Cause:**
The issue was caused by an unnecessary negation in the `export_for_printing()` method in `pos_order.js`.

The `get_change()` method already returns the correct positive change amount. However, the code applied an extra negation (`-this.get_change()`), which converted the value into a negative amount before rendering it on the receipt.

**Fix:**
Removed the unnecessary negation in `export_for_printing()` so the receipt now displays the correct positive change amount.

Video reproducing the issue: [[Click here to view the video](https://drive.google.com/file/d/1QnQ47qlTFvv98K0J_NzreBVeIh-J2XcF/view?usp=sharing)]

opw-6211988

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

Forward-Port-Of: odoo/odoo#267278
Forward-Port-Of: odoo/odoo#264681

#pos#receipt#customer experience

[FIX] l10n_fr_pdp: fix is sent condition

PR #269883

Coresaas-18.3l10n_fr_pdpMEDIUM

This update resolves an issue where move records needed to be sent to be processed within the French payroll (l10n_fr_pdp) flow. The fix also corrects a problem with copied zip files being incorrectly identified based on country, ensuring accurate address validation. This improves the reliability of the French payroll processing.

Original PR description

This fix removes the condition that moves must be sent to be part of a flow 10 and correct copy-pasted zip by country_id in address check.

Forward-Port-Of: odoo/odoo#268022

#payroll#french#accounting

[FIX] l10n_fr_pdp: fix KeyError 'messages' when sending invoices in demo mode

PR #269902

Coresaas-18.3l10n_fr_pdp

This update resolves a technical error that prevented French eInvoicing invoices from being successfully sent in demo mode. The fix ensures the system correctly handles responses from the IAP proxy, addressing a mismatch in data formats and logging, ultimately improving the reliability of the demo environment.

Original PR description

**Steps to reproduce:**
* Install `l10n_fr_pdp` module.
* Activate French eInvoicing in demo mode and enable "Participate in the pilot phase".
* Create an invoice for a French client and send it via the French E-Invoicing.

**Observed behavior:**
* A traceback is raised with `KeyError: 'messages'` in `_send_peppol_documents`.

**Cause:**
* `DEMO_ENDPOINTS['send_document']` in `l10n_fr_pdp` was returning `{'ppf_messages': [...]}`, missing the `messages` key that `_send_peppol_documents` in `account_peppol` unconditionally reads for flow 2.
* Additionally, the demo mock was returning `uid` instead of `uuid` inside `ppf_messages`, which does not match the real IAP response structure.
* Finally, in `l10n_fr_pdp/models/pdp_flow.py`, after successfully sending a flow 10 batch, the system attempted to log `response['uid']` despite the `_send_to_proxy()` method returning `uuid`. This caused a crash during the chatter logging step.

**Fix:**
* Fix `DEMO_ENDPOINTS['send_document']` to return `{'messages': [...]}` with `message_uuid` entries, matching the real IAP response structure for flow 2.
* Update `ppf_messages` in the demo mock to return `uuid` instead of `uid`.
* Fix `pdp_flow.py` to correctly access `response['uuid']` instead of `response['uid']` when posting the success message.

IAP Response: https://github.com/odoo/iap-apps/blob/b0462b9dded36a4d6dd45d00ddd13cd36e31807e/iap_services/l10n_fr_pdp_proxy/controllers/message_controller.py#L63

opw-6289723

Forward-Port-Of: odoo/odoo#269515

#french invoicing#demo mode#iap

**Issue:** The printed receipt in Point of Sale displayed a negative change amount when the customer paid more than the order total. **Before:** The receipt showed the change as a negative value (e.g., `-$5,504.00`), which was misleading for customers. **After:** The receipt now correctly displays the change as a positive value (e.g., `$5,504.00`). **Steps to Reproduce:** 1. Open a Point of Sale session 2. Add products to the cart (example total: `$49,496.00`) 3. Select the **Cash** payment method 4. Enter an amount greater than the order total (example: `$55,000.00`) 5. Observe that the **Change** field displays a negative value 6. Confirm the payment 7. Print the receipt and observe that the change amount is also negative **Root Cause:** The issue was caused by an unnecessary negation in the `export_for_printing()` method in `pos_order.js`. The `get_change()` method already returns the correct positive change amount. However, the code applied an extra negation (`-this.get_change()`), which converted the value into a negative amount before rendering it on the receipt. **Fix:** Removed the unnecessary negation in `export_for_printing()` so the receipt now displays the correct positive change amount. Video reproducing the issue: [[Click here to view the video](https://drive.google.com/file/d/1QnQ47qlTFvv98K0J_NzreBVeIh-J2XcF/view?usp=sharing)] opw-6211988 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#267278 Forward-Port-Of: odoo/odoo#264681

**Steps to reproduce:** * Install `l10n_fr_pdp` module. * Activate French eInvoicing in demo mode and enable "Participate in the pilot phase". * Create an invoice for a French client and send it via the French E-Invoicing. **Observed behavior:** * A traceback is raised with `KeyError: 'messages'` in `_send_peppol_documents`. **Cause:** * `DEMO_ENDPOINTS['send_document']` in `l10n_fr_pdp` was returning `{'ppf_messages': [...]}`, missing the `messages` key that `_send_peppol_documents` in `account_peppol` unconditionally reads for flow 2. * Additionally, the demo mock was returning `uid` instead of `uuid` inside `ppf_messages`, which does not match the real IAP response structure. * Finally, in `l10n_fr_pdp/models/pdp_flow.py`, after successfully sending a flow 10 batch, the system attempted to log `response['uid']` despite the `_send_to_proxy()` method returning `uuid`. This caused a crash during the chatter logging step. **Fix:** * Fix `DEMO_ENDPOINTS['send_document']` to return `{'messages': [...]}` with `message_uuid` entries, matching the real IAP response structure for flow 2. * Update `ppf_messages` in the demo mock to return `uuid` instead of `uid`. * Fix `pdp_flow.py` to correctly access `response['uuid']` instead of `response['uid']` when posting the success message. IAP Response: https://github.com/odoo/iap-apps/blob/b0462b9dded36a4d6dd45d00ddd13cd36e31807e/iap_services/l10n_fr_pdp_proxy/controllers/message_controller.py#L63 opw-6289723 Forward-Port-Of: odoo/odoo#269515