Odoo Changelog — 2026-04-03

Friday, April 3, 2026

2 changes · 18.0

New Features(2)

New functionality added to Odoo

[ADD] l10n_ro_saft_stock: Added new module

Enterprise18.0l10n_ro_saft_stockMEDIUM

This update introduces a new module for Romania, specifically designed to generate the required 'On Demand' XML file for SAFT reporting. This file contains inventory valuation data, which is a mandatory submission to the Romanian tax authority (ANAF) as part of their digitalized reporting process. This addition ensures compliance with Romanian regulations.

Original PR description

Baiscally the SAFT for Romania consists of 3 xml files to submit. This commit focuses on the "On Demand" xml to submit, consisting in the inventory valuation of of the company. File with fields and value to export can be found here: https://www.anaf.ro/anaf/internet/ANAF/despre_anaf/strategii_anaf/proiecte_digitalizare/saf_t/ 

task-3748978

#Romania#SAFT#Reporting#ANAF#Inventory

[ADD] l10n_dk_nemhandel_response, account_peppol_response: add the business level responses

PR #243191

Core18.0account_peppol_responseaccount_peppolMEDIUM

This update adds support for Peppol Business Level Responses (BLR) to invoices and credit notes, ensuring compliance with European standards for electronic invoicing. It introduces new response types – acknowledgement, confirmation, and rejection – required for Peppol participants to correctly process documents. This improves Odoo's integration with Peppol and supports international trade.

Original PR description

Peppol offers a response system to the document received through it. These are called Business Level Responses, and their documentation can be found here:…

Peppol offers a response system to the document received through it.
These are called Business Level Responses, and their documentation can be found here:
https://docs.peppol.eu/poacc/upgrade-3/profiles/63-invoiceresponse/#introduction-to-openpeppol-and-bis

The specific BLR implemented in this commit is targeted to invoices and credit notes.

3 types of responses are mandatory for a Peppol participant to correctly adhere to the BLR service: acknowledgement (different to the transport ack), confirmation and rejection. More response's types are available but were not implemented as they're not mandatory/needed (for now).
For rejection, a list of at least one reason must be given, and actions can be suggested to the sender of the document for the eventual next invoice shipment.

Same principle goes for Nemhandel, with some differences: only 2 responses, BusinessAccept and BusinessReject (no Acknowledgement, and no reasons are needed in case of rejection. Instead, the user can send a string message.

iap PR: https://github.com/odoo/iap-apps/pull/1364

task-5237698

#peppol#blr#invoice#account

Baiscally the SAFT for Romania consists of 3 xml files to submit. This commit focuses on the "On Demand" xml to submit, consisting in the inventory valuation of of the company. File with fields and value to export can be found here: https://www.anaf.ro/anaf/internet/ANAF/despre_anaf/strategii_anaf/proiecte_digitalizare/saf_t/ task-3748978

Peppol offers a response system to the document received through it. These are called Business Level Responses, and their documentation can be found here: https://docs.peppol.eu/poacc/upgrade-3/profiles/63-invoiceresponse/#introduction-to-openpeppol-and-bis The specific BLR implemented in this commit is targeted to invoices and credit notes. 3 types of responses are mandatory for a Peppol participant to correctly adhere to the BLR service: acknowledgement (different to the transport ack), confirmation and rejection. More response's types are available but were not implemented as they're not mandatory/needed (for now). For rejection, a list of at least one reason must be given, and actions can be suggested to the sender of the document for the eventual next invoice shipment. Same principle goes for Nemhandel, with some differences: only 2 responses, BusinessAccept and BusinessReject (no Acknowledgement, and no reasons are needed in case of rejection. Instead, the user can send a string message. iap PR: https://github.com/odoo/iap-apps/pull/1364 task-5237698