Odoo Changelog — 2026-05-13

Wednesday, May 13, 2026

3 changes · saas-18.4

Bug Fixes(3)

Resolved issues and error corrections

[FIX] l10n_no_reports: fix VAT declaration XML validation errors

Enterprisesaas-18.4l10n_noMedium

This update resolves issues preventing Odoo's Norwegian VAT XML exports from passing government validation checks. The changes ensure accurate decimal formatting, correct mathematical calculations, and the inclusion of required legal notes, allowing businesses to file their VAT returns correctly and avoid delays. This fix directly addresses compliance requirements with Skatteetaten.

Original PR description

Before commit:
The Norwegian VAT XML export fails Skatteetaten validation due to incorrect
decimal formatting, mathematical rounding mismatches between base and tax
amounts, missing mandatory legal notes, and invalid KID number formats.

Fix:
To strictly follow Skatteetaten validation rules for the Norway VAT XML, the
following changes were implemented:
- Ensured standard rates drop the decimal (e.g, `25.0` to `25`), and formatted 
  fractional rates like `11.11` to `11,11` in XML.
- Rounded down the `tax_amount` to align precisely with government mathematical
  expectations.
- `base_amount` converted into absolute value to ensuring the calculation
  (`base * rate = tax`) resolves perfectly.
- Add the mandatory `<merknad>` explaining the reverse charge method for codes
  81, 83, 86, 88, and 91.
- Clean the `company_kid` by safely stripping the 'NO' prefix, and 'MVA' suffix.

Expect:
The generated XML payload now adheres perfectly to Skatteetaten's strict
structural and mathematical rules, allowing the VAT return to pass government
validations successfully.

Related Community PR: https://github.com/odoo/odoo/pull/258390

Task-6033027

Forward-Port-Of: odoo/enterprise#116962
Forward-Port-Of: odoo/enterprise#110792

#vat#norway#compliance#tax

[FIX] documents_project: extend template undo with documents folder management

PR #91595

Enterprisesaas-18.4documents_projectMedium

This update resolves a bug where undoing a template conversion left the project's documents folder in an inconsistent state, preventing further template creation. The fix ensures the original documents folder is properly restored and cleaned up during the undo process, improving workflow reliability.

Original PR description

Steps to Reproduce:
---
1. Create a project with documents.
2. Convert it into a template.
3. Click on "Undo".
4. Try to convert the project into a template again.

Issue:
---
After undoing the template conversion, the project's original documents folder
remained archived while the template's documents folder stayed active. This
inconsistent state prevented subsequent template creation from the same project.

Current behaviour:
---
A UserError is raised: "You cannot duplicate document(s) in the Trash."

Expected behaviour:
---
Undoing template conversion should properly restore original project's
documents folder and clean up template's documents folder.

Fix:
---
- Archive original project's documents folder during template creation
- Implement documents folder unarchival during undo operations

task-4916027

#documents#templates#workflow

[FIX] l10n_pe_edi: prevent error when sending the invoice to Peru UBL

PR #114798

Enterprisesaas-18.4l10n_pe_ediMedium

This update resolves an issue that caused invoices with combo products lacking taxes to generate errors when sent to Peru's UBL system. The fix ensures that combo product invoice lines without taxes are properly validated, preventing the traceback and allowing invoices to be successfully processed. This improves the reliability of the Peru UBL integration.

Original PR description

A traceback occurs when sending an invoice to Peru UBL if a combo product
invoice line does not have any taxes applied.

Steps to reproduce the error:
- Install ``l10n_pe_edi`` module with demo data
- Switch to PE Company
- Create an invoice > Add a Office Combo product > unset the taxes > Confirm
- Process now

https://github.com/odoo/enterprise/blob/d7f71a68fbd5ff9c7cd52f96e1616671a6b8d77c/l10n_pe_edi/models/account_edi_xml_ubl_pe.py#L549-L552
Here, the ``grouping_key`` becomes ``None`` when no taxes are present on the invoice line.
Normally, invoices without taxes are restricted at [1],
but combo products are excluded from this validation at [2].
As a result, combo product lines without taxes bypass the restriction and trigger a traceback.

[1]: https://github.com/odoo/enterprise/blob/d7f71a68fbd5ff9c7cd52f96e1616671a6b8d77c/l10n_pe_edi/models/account_edi_format.py#L928-L929

[2]: https://github.com/odoo/odoo/blob/42b8852df9b323984364c41a13cf27d19fbe04a7/addons/account/models/account_move_line.py#L3433-L3434

sentry-7430552834

Before commit: The Norwegian VAT XML export fails Skatteetaten validation due to incorrect decimal formatting, mathematical rounding mismatches between base and tax amounts, missing mandatory legal notes, and invalid KID number formats. Fix: To strictly follow Skatteetaten validation rules for the Norway VAT XML, the following changes were implemented: - Ensured standard rates drop the decimal (e.g, `25.0` to `25`), and formatted fractional rates like `11.11` to `11,11` in XML. - Rounded down the `tax_amount` to align precisely with government mathematical expectations. - `base_amount` converted into absolute value to ensuring the calculation (`base * rate = tax`) resolves perfectly. - Add the mandatory `<merknad>` explaining the reverse charge method for codes 81, 83, 86, 88, and 91. - Clean the `company_kid` by safely stripping the 'NO' prefix, and 'MVA' suffix. Expect: The generated XML payload now adheres perfectly to Skatteetaten's strict structural and mathematical rules, allowing the VAT return to pass government validations successfully. Related Community PR: https://github.com/odoo/odoo/pull/258390 Task-6033027 Forward-Port-Of: odoo/enterprise#116962 Forward-Port-Of: odoo/enterprise#110792

Steps to Reproduce: --- 1. Create a project with documents. 2. Convert it into a template. 3. Click on "Undo". 4. Try to convert the project into a template again. Issue: --- After undoing the template conversion, the project's original documents folder remained archived while the template's documents folder stayed active. This inconsistent state prevented subsequent template creation from the same project. Current behaviour: --- A UserError is raised: "You cannot duplicate document(s) in the Trash." Expected behaviour: --- Undoing template conversion should properly restore original project's documents folder and clean up template's documents folder. Fix: --- - Archive original project's documents folder during template creation - Implement documents folder unarchival during undo operations task-4916027

A traceback occurs when sending an invoice to Peru UBL if a combo product invoice line does not have any taxes applied. Steps to reproduce the error: - Install ``l10n_pe_edi`` module with demo data - Switch to PE Company - Create an invoice > Add a Office Combo product > unset the taxes > Confirm - Process now https://github.com/odoo/enterprise/blob/d7f71a68fbd5ff9c7cd52f96e1616671a6b8d77c/l10n_pe_edi/models/account_edi_xml_ubl_pe.py#L549-L552 Here, the ``grouping_key`` becomes ``None`` when no taxes are present on the invoice line. Normally, invoices without taxes are restricted at [1], but combo products are excluded from this validation at [2]. As a result, combo product lines without taxes bypass the restriction and trigger a traceback. [1]: https://github.com/odoo/enterprise/blob/d7f71a68fbd5ff9c7cd52f96e1616671a6b8d77c/l10n_pe_edi/models/account_edi_format.py#L928-L929 [2]: https://github.com/odoo/odoo/blob/42b8852df9b323984364c41a13cf27d19fbe04a7/addons/account/models/account_move_line.py#L3433-L3434 sentry-7430552834