Saturday, December 13, 2025
3 changes · saas-18.3
Enhancements to existing features
This update adds a message to the Account Online link, allowing users to easily revoke consent for the Basiq provider widget. This provides greater control over data sharing and aligns with privacy best practices. It redirects users to a dedicated Odoo page for managing their Basiq consent.
Original PR description
This commit will add a message on the account online link chatter for the basiq provider. This message will allow the user to be redirected to an odoofin page with a button to revoke his consent on a basiq widget task-5187621 Forward-Port-Of: odoo/enterprise#101972 Forward-Port-Of: odoo/enterprise#101801
Resolved issues and error corrections
This update corrects a bug in the l10n_es_edi_tbai module that prevented the correct generation of the `FechaOperacion` field in TBAI XML invoices. Specifically, when the invoice date and delivery date are set to a past date, the `FechaOperacion` was missing. This ensures compliance with Spanish tax regulations.
Original PR description
With l10n_es_tbai: - Create an invoice with an `invoice_date` and `delivery_date` that are the same and earlier than today. - In the generated TBAI XML, `FechaOperacion` is missing. In the TBAI XML, `FechaExpedicionFactura` corresponds to the date on which the XML is generated. `FechaOperacion` corresponds to the `delivery_date` and should appear whenever it differs from the issue date. The TicketBAI specs define `FechaOperacion` as: > “Date on which the transaction was carried out, whenever it differs from the issue date.” So when the invoice date and delivery date are equal but set in the past, `FechaOperacion` is not generated, even though it should be. opw-4477135 opw-4477135 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#239189
This update resolves issues related to invoice attachments, specifically when using different EDI formats or sending invoices via email and Peppol. Previously, incorrect display and error messages occurred, now attachments function correctly regardless of the invoice format or sending method selected.
Original PR description
[FIX] account{_edi_ubl_cii, _peppol}: Attachment fix
2 scenarios fixed in this commit :
1:
When a user invoice_edi_format is not 'ubl_bis3' the attachment button is not displayed and the key doesn't exists in the invoice_data. This causes traceback when trying to access the key.
2:
When a user send and print an invoice, with 'email' and 'peppol' as sending_methods, warnings will be displayed next to attachments not supported by peppol.
But if the user uncheck 'peppol', warnings will stay while no sending method requires them anymore.
See odoo/odoo#234339
Forward-Port-Of: odoo/odoo#239769
Forward-Port-Of: odoo/odoo#239684