Odoo Changelog — 2026-07-25

Saturday, July 25, 2026

3 changes · 18.0

Improvements(1)

Enhancements to existing features

[IMP] l10n_pe_edi: update debit note reasons

Enterprise18.0l10n_pe_ediMEDIUM

The Peru electronic invoicing module updates the available debit note reasons to match new SUNAT requirements effective August 1, 2026. Users creating Peruvian debit notes will see the revised “Other concepts” label and a new “Penalties” reason, helping keep filings compliant.

Original PR description

Purpose: SUNAT has issued new validation rules and database updates for EDI. The changes are mandatory and is effective starting August 1, 2026. To stay compliant, the debit note reasons need to be updated when creating a debit note in Peru. A new code 13 with label "Penalties" is added to the list of reasons. Code 03 reason need its label to be updated to "Other concepts."

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

Forward-Port-Of: odoo/enterprise#122320

#Peru#EDI#SUNAT#debit notes#compliance

Bug Fixes(2)

Resolved issues and error corrections

[FIX] l10n_mx_edi: Fix PAC status cron infinite re-trigger

PR #125317

Enterprise18.0l10n_mx_edil10n_mx_edi_posMEDIUM

This fix prevents Mexican electronic invoice status checks from being repeatedly triggered in a loop, reducing unnecessary processing and keeping scheduled checks under control. It also prioritizes older customer invoices and limits vendor bill checks to the relevant period, helping important documents get reviewed before their deadline.

Original PR description

While trying to fix the SAT cron, we did not think it through it could cause infinite cron triggering. Indeed, the write_date is updated on every record that is handled. Fix is manyfold: - Avoid…

While trying to fix the SAT cron, we did not think it through
it could cause infinite cron triggering.
Indeed, the write_date is updated on every record that is handled.

Fix is manyfold:
- Avoid re-processing what we already check within the last 4 hours/12 hours
depending on the type of the document.
- The domain takes the *static* create date instead of the write_date
to make sure we don't endless re-process the same record and that
the window of 7/60 days applies.
- Limit the Vendor Bill to be checked only during 7 days after their creation.
- Use the create_date in the order of the search to ensure we process older
records first, before their time-window closes.
- Process the Vendor Bills last, this ensure Customer Invoices will be processed
in priority in case we are not able to process everything within the last 4/12 hours.

This is still imperfect and a little fragile, we will find a better solution
in master, most likely by adding a dedicated field to keep track of the
last SAT check.

See https://github.com/odoo/enterprise/pull/123213
See https://github.com/odoo/enterprise/pull/103272

task-none

#mexico#electronic-invoicing#scheduled-actions#performance

[FIX] account_winbooks_import: prevent partner merge on VAT mismatch

PR #125370

Enterprise18.0account_winbooks_importMEDIUM

WinBooks imports now keep supplier and customer contact details separate when their VAT numbers differ, even if they share the same contact number. This prevents imports from failing due to mismatched VAT and country information being combined incorrectly.

Original PR description

When importing a WinBooks zip, contacts sharing the same number might fail VAT validation if distinct contact data is merged incorrectly. Steps to reproduce: - Create a database with the Belgian…

When importing a WinBooks zip, contacts sharing the same number might fail VAT validation if distinct contact data is merged incorrectly.

Steps to reproduce:
- Create a database with the Belgian localization installed
- Install the account_winbooks_import module
- Navigate to Accounting > Configuration > Settings > Initial Setup > Import
- Import the WinBooks zip

Issue:

The import fails with the following error:
The VAT number [AAAAAA] for partner [BBBBBB] does not seem to be valid. Note: the expected format is BExxxxxxx.

Analysis:
In WinBooks, contacts can be of type Supplier or Customer, and it is possible for a supplier and a customer to share the same number. During the import, the system will merge contacts if found with the same number.

In the specific case, the VAT number from one contact without country is combined with the country information from another contact, resulting in a VAT validation error.
This change prevents the merger of partner data if their VAT numbers are explicitly different.

opw-6251772

Forward-Port-Of: odoo/enterprise#119579

#WinBooks#VAT#contacts#import

Purpose: SUNAT has issued new validation rules and database updates for EDI. The changes are mandatory and is effective starting August 1, 2026. To stay compliant, the debit note reasons need to be updated when creating a debit note in Peru. A new code 13 with label "Penalties" is added to the list of reasons. Code 03 reason need its label to be updated to "Other concepts." Task [link](https://www.odoo.com/odoo/project.task/6312025) task-6312025 Forward-Port-Of: odoo/enterprise#122320

While trying to fix the SAT cron, we did not think it through it could cause infinite cron triggering. Indeed, the write_date is updated on every record that is handled. Fix is manyfold: - Avoid re-processing what we already check within the last 4 hours/12 hours depending on the type of the document. - The domain takes the *static* create date instead of the write_date to make sure we don't endless re-process the same record and that the window of 7/60 days applies. - Limit the Vendor Bill to be checked only during 7 days after their creation. - Use the create_date in the order of the search to ensure we process older records first, before their time-window closes. - Process the Vendor Bills last, this ensure Customer Invoices will be processed in priority in case we are not able to process everything within the last 4/12 hours. This is still imperfect and a little fragile, we will find a better solution in master, most likely by adding a dedicated field to keep track of the last SAT check. See https://github.com/odoo/enterprise/pull/123213 See https://github.com/odoo/enterprise/pull/103272 task-none

When importing a WinBooks zip, contacts sharing the same number might fail VAT validation if distinct contact data is merged incorrectly. Steps to reproduce: - Create a database with the Belgian localization installed - Install the account_winbooks_import module - Navigate to Accounting > Configuration > Settings > Initial Setup > Import - Import the WinBooks zip Issue: The import fails with the following error: The VAT number [AAAAAA] for partner [BBBBBB] does not seem to be valid. Note: the expected format is BExxxxxxx. Analysis: In WinBooks, contacts can be of type Supplier or Customer, and it is possible for a supplier and a customer to share the same number. During the import, the system will merge contacts if found with the same number. In the specific case, the VAT number from one contact without country is combined with the country information from another contact, resulting in a VAT validation error. This change prevents the merger of partner data if their VAT numbers are explicitly different. opw-6251772 Forward-Port-Of: odoo/enterprise#119579