Odoo Changelog — 2026-02-13

Friday, February 13, 2026

2 changes · master

Bug Fixes(2)

Resolved issues and error corrections

[FIX] pos_iot: fix LNA in POS for IoT devices

Enterprisemasterpos_iotMedium

This update resolves an issue preventing LNA (Line Notifications Available) from working correctly for IoT-connected POS printers. The change adjusts how IoT printer data is loaded, ensuring LNA functionality is properly enabled when using IoT printers. This improves the reliability of receiving notifications from these devices.

Original PR description

This commit fixes an issue where LNA was never being enabled for IoT devices in the POS due to an issue caused by the different way the IoT records are loaded in the POS.

This commit also changes the LNA checkbox in the POS printer form to a related field of the IoT box's LNA checkbox when an IoT printer is used.

#POS#IoT#Notifications

[IMP] account_invoice_extract: don't use past partner names for matching

PR #105664

EnterprisemasteraccountMedium

This update enhances the accuracy of invoice processing by shifting from OCR-based partner name matching to relying on layout IDs. Previously, incorrect OCR results could lead to inaccurate partner matches. This change significantly reduces errors and improves the overall reliability of invoice data.

Original PR description

Before this commit, we were using the partner name identified by the OCR on previous documents to help with the matching of the partner on next bills.

The intended use case was the following:
- User parses a bill from "SNCB" with the OCR.
- OCR identifies "SNCB" as the supplier, but this vendor is encoded as "Societe Nationale des Chemins de fer Belges" in the database, so it isn't able to match it.
- After the user manually sets the proper supplier and validates the bill, it creates a link from OCR partner name "SNCB" to "Societe Nationale des Chemins de fer Belges".
- From this link, the OCR knows that when it finds "SNCB" as supplier, it needs to set the vendor "Societe Nationale des Chemins de fer Belge".

The issue with this kind of matching is that, if the OCR finds an incorrect vendor name (which is quite frequent unfortunately), it can match completly unrelated partners.

Instead, we will now rely solely on the layout ID identified by the OCR to perform this kind of match as it is much more reliable.

task-[5340130](https://www.odoo.com/odoo/project/2068/tasks/5340130)

This commit fixes an issue where LNA was never being enabled for IoT devices in the POS due to an issue caused by the different way the IoT records are loaded in the POS. This commit also changes the LNA checkbox in the POS printer form to a related field of the IoT box's LNA checkbox when an IoT printer is used.

Before this commit, we were using the partner name identified by the OCR on previous documents to help with the matching of the partner on next bills. The intended use case was the following: - User parses a bill from "SNCB" with the OCR. - OCR identifies "SNCB" as the supplier, but this vendor is encoded as "Societe Nationale des Chemins de fer Belges" in the database, so it isn't able to match it. - After the user manually sets the proper supplier and validates the bill, it creates a link from OCR partner name "SNCB" to "Societe Nationale des Chemins de fer Belges". - From this link, the OCR knows that when it finds "SNCB" as supplier, it needs to set the vendor "Societe Nationale des Chemins de fer Belge". The issue with this kind of matching is that, if the OCR finds an incorrect vendor name (which is quite frequent unfortunately), it can match completly unrelated partners. Instead, we will now rely solely on the layout ID identified by the OCR to perform this kind of match as it is much more reliable. task-[5340130](https://www.odoo.com/odoo/project/2068/tasks/5340130)