Odoo Changelog — 2026-08-10

Monday, August 10, 2026

2 changes · 17.0

Bug Fixes(2)

Resolved issues and error corrections

[FIX] l10n_cl_edi: this fix adds new key values returned from SII

Enterprise17.0l10n_cl_ediMedium

The Chilean electronic invoicing module now recognizes five new response codes introduced by SII. This prevents supplier electronic tax documents from getting stuck during claim or acceptance status processing after the SII regulatory update.

Original PR description

**Before this PR:**
After the implementation of Resolution 161 of November 13th 2025, SII responses included keys not supported by the current l10n_cl_edi implementation. This resulted in supplier DTEs not being processed as they were before the change, because the five new keys were not found in Odoo's current `l10n_cl_claim` field, causing that the documents with these responses, were kept in a loop not solved.

**After this PR:**
The five new values from the resolution, along with their translations, were added to the selector field, fixing the process flow.

**SII Reference:**
https://www.sii.cl/normativa_legislacion/resoluciones/2025/reso161.pdf (see Event Code, page 5)

#Chile#SII#electronic invoicing#supplier documents

[FIX] l10n_nl_reports: Handle missing closing entry

PR #125996

Enterprise17.0l10n_nl_reports_sbr_status_infoMedium

This fix prevents one Dutch Digipoort tax return record with missing accounting information from stopping status updates for all other records. The system now handles the missing closing entry gracefully, improving reliability for Dutch tax reporting workflows.

Original PR description

The `l10n_nl_reports_sbr_status_info` contains the `l10n_nl_reports_sbr.status.service` class. The class is responsible for fetching the status of sent Digipoort tax returns. The status is then posted as a chatter message to the tax return's closing entry. Issues can arise when one of the status service records is, for whatever reason, missing a closing entry. In such case, the message cannot be posted, resulting in an exception being raised. Since the records are processed in a loop without a try-catch, this causes the whole action to fail. This can lead to one broken record effectively shutting down the whole module's functionality.

This PR adds some if-else checks to gracefully handle the case where the closing entry is missing.

Related tickets: opw-5901446 and opw-6410082

#Dutch localization#tax reporting#Digipoort#reliability

**Before this PR:** After the implementation of Resolution 161 of November 13th 2025, SII responses included keys not supported by the current l10n_cl_edi implementation. This resulted in supplier DTEs not being processed as they were before the change, because the five new keys were not found in Odoo's current `l10n_cl_claim` field, causing that the documents with these responses, were kept in a loop not solved. **After this PR:** The five new values from the resolution, along with their translations, were added to the selector field, fixing the process flow. **SII Reference:** https://www.sii.cl/normativa_legislacion/resoluciones/2025/reso161.pdf (see Event Code, page 5)

The `l10n_nl_reports_sbr_status_info` contains the `l10n_nl_reports_sbr.status.service` class. The class is responsible for fetching the status of sent Digipoort tax returns. The status is then posted as a chatter message to the tax return's closing entry. Issues can arise when one of the status service records is, for whatever reason, missing a closing entry. In such case, the message cannot be posted, resulting in an exception being raised. Since the records are processed in a loop without a try-catch, this causes the whole action to fail. This can lead to one broken record effectively shutting down the whole module's functionality. This PR adds some if-else checks to gracefully handle the case where the closing entry is missing. Related tickets: opw-5901446 and opw-6410082