Odoo Changelog — 2026-07-17

Friday, July 17, 2026

2 changes · 19.0

Improvements(2)

Enhancements to existing features

[IMP] {account,l10n_be}_reports: sync audit status and improve UI

Enterprise19.0account_reportsl10n_be_reportsMedium

Audit check statuses now update automatically based on the status of their related accounts, reducing manual work and improving consistency. The interface also uses clearer wording, including "Last Comment" and past-tense status labels across working files and tax returns.

Original PR description

Before this commit, the status of an Audit Check (e.g., Fixed Assets)
did not automatically reflect the status of its underlying accounts,
forcing users to update it manually. Additionally, status labels used
inconsistent tenses.

This commit automates the Check status update based on the underlying
account statuses:
- If any account is To Review or Empty or Anomaly -> Check becomes 'To Review'.
- If all accounts are Reviewed -> Check becomes 'Reviewed'.
- If all accounts are Supervised -> Check becomes 'Supervised'.
- If accounts are mixed (Reviewed + Supervised) -> Check becomes 'Supervised'.

This commit also standardizes UI terminology by renaming the "Last Message"
column to "Last Comment" and updating status labels to past tense (e.g.,
"Reviewed", "Submitted") across Working Files and Tax Returns.

task-5388699

#audit#status#user interface#tax returns

[IMP] l10n_pe_edi, product_unspsc: activate SUNAT unspsc codes

PR #124396

Enterprise19.0l10n_pe_ediproduct_unspscMedium

Peruvian e-invoicing now includes the product classification codes required by SUNAT's upcoming validation rules. This helps businesses avoid invoice rejections for affected goods when the new requirements take effect in August 2026.

Original PR description

SUNAT is updating its validation rules 2026-08-01, adding three mandatory annexes (25.1, 25.2, 25.3) to Product Catalog N25. E-invoices for these goods are rejected when the required UNSPSC code is not available in the database.

Most of the required codes already exist and are active. The rest are handled here: two missing UNSPSC codes were added to the shared catalog, while the fourteen codes that exist but are inactive and the SUNAT-only code 11111111 (which is not part of the UNSPSC standard) are activated from the Peru localization instead.

Doing the Peru-specific part in the l10n_pe_edi install hook and upgrade script, the way l10n_mx_edi and l10n_ke_edi_oscu do for their own codes, keeps these activations out of databases that do not use the Peruvian localization.

Task-6366907

Forward-Port-Of: odoo/enterprise#124200
Forward-Port-Of: odoo/enterprise#123577

#Peru#e-invoicing#SUNAT#UNSPSC

Before this commit, the status of an Audit Check (e.g., Fixed Assets) did not automatically reflect the status of its underlying accounts, forcing users to update it manually. Additionally, status labels used inconsistent tenses. This commit automates the Check status update based on the underlying account statuses: - If any account is To Review or Empty or Anomaly -> Check becomes 'To Review'. - If all accounts are Reviewed -> Check becomes 'Reviewed'. - If all accounts are Supervised -> Check becomes 'Supervised'. - If accounts are mixed (Reviewed + Supervised) -> Check becomes 'Supervised'. This commit also standardizes UI terminology by renaming the "Last Message" column to "Last Comment" and updating status labels to past tense (e.g., "Reviewed", "Submitted") across Working Files and Tax Returns. task-5388699

SUNAT is updating its validation rules 2026-08-01, adding three mandatory annexes (25.1, 25.2, 25.3) to Product Catalog N25. E-invoices for these goods are rejected when the required UNSPSC code is not available in the database. Most of the required codes already exist and are active. The rest are handled here: two missing UNSPSC codes were added to the shared catalog, while the fourteen codes that exist but are inactive and the SUNAT-only code 11111111 (which is not part of the UNSPSC standard) are activated from the Peru localization instead. Doing the Peru-specific part in the l10n_pe_edi install hook and upgrade script, the way l10n_mx_edi and l10n_ke_edi_oscu do for their own codes, keeps these activations out of databases that do not use the Peruvian localization. Task-6366907 Forward-Port-Of: odoo/enterprise#124200 Forward-Port-Of: odoo/enterprise#123577