Odoo Changelog — 2026-04-17

Friday, April 17, 2026

2 changes · saas-18.4

Improvements(2)

Enhancements to existing features

[IMP] account_edi_ubl_cii: inverse addresses on generated PDF for received XML invoices

Coresaas-18.4account_edi_ubl_ciiMedium

When Odoo generates a PDF for a received Peppol invoice that did not include one, the supplier and customer address areas are now placed more appropriately. The generated document also uses a simpler layout so users can more easily recognize it as an Odoo-created copy rather than the original invoice.

Original PR description

When an invoice is received through Peppol, it may not contain an embed PDF.
If no, we create one. However, due to several complaints, this commit
exchange the place of the issuer and receiver addresses and information.

Company information were rendered in the header of the document through
the external_layout. Switching to the internal layer avoid doing so.

opw-5980655

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#254693

#invoicing#Peppol#PDF#EDI

[IMP] base_vat: switch VIES to IAP

PR #259871

Coresaas-18.4base_vatMedium

EU VAT number validation now uses Odoo's IAP service instead of relying directly on VIES every time. This improves reliability when official VIES services are slow or unavailable, while allowing delayed updates once validation results become available.

Original PR description

Currently, when changing the Tax ID of a partner that is another EU country, we perform a VIES check to know whether it is valid (i.e. can do intra-com).
However, it is often the case that the VIES check fails because of an internal error on their side (timeout, max concurrent update, ...), especially for France.

Instead, we will now use the IAP server which stores the validity of a Tax ID for some time. If the IAP server does not have the info (because VIES is down), we will not actively wait. Instead, IAP will perform a push to a webhook on the client database once it has the information.

For security purposes, an HMAC is generated and sent to IAP so that only IAP can contact the db with the up-to-date info, and not anyone on the internet that calls this new webhook. There is also a cron for polling for OnPrem instances that cannot be contacted via the webhook.

task-5977584

Forward-Port-Of: odoo/odoo#259755
Forward-Port-Of: odoo/odoo#258155

#VAT#VIES#IAP#reliability

When an invoice is received through Peppol, it may not contain an embed PDF. If no, we create one. However, due to several complaints, this commit exchange the place of the issuer and receiver addresses and information. Company information were rendered in the header of the document through the external_layout. Switching to the internal layer avoid doing so. opw-5980655 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#254693

Currently, when changing the Tax ID of a partner that is another EU country, we perform a VIES check to know whether it is valid (i.e. can do intra-com). However, it is often the case that the VIES check fails because of an internal error on their side (timeout, max concurrent update, ...), especially for France. Instead, we will now use the IAP server which stores the validity of a Tax ID for some time. If the IAP server does not have the info (because VIES is down), we will not actively wait. Instead, IAP will perform a push to a webhook on the client database once it has the information. For security purposes, an HMAC is generated and sent to IAP so that only IAP can contact the db with the up-to-date info, and not anyone on the internet that calls this new webhook. There is also a cron for polling for OnPrem instances that cannot be contacted via the webhook. task-5977584 Forward-Port-Of: odoo/odoo#259755 Forward-Port-Of: odoo/odoo#258155