Monday, September 7, 2026
4 changes · 17.0
Enhancements to existing features
Swiss QR invoices can now be created even when the company or customer address is missing a street or building number, reducing blocked invoice sending. Users are shown an informational banner in the Send & Print popup so they can review affected customers without stopping the process.
Original PR description
In Switzerland, the street and building number is not required to generate a valid QR invoice. To minimize friction, errors are no longer raised if they are missing from the address of the company or the customer during the creation of the QR Code. Instead, an info banner is now displayed in the Send & Print popup indicating to the user that the addresses of some of the customers are missing and allow the user to browse through those customers. task-4349496 opw-4317153
Resolved issues and error corrections
French companies can no longer attempt Peppol registration using FRCTC, which is not supported. This prevents failed registration attempts and reduces related errors during e-invoicing setup.
Original PR description
Previously, we did not prevent FRCTC from registering through Peppol, even though FRCTC is not supported in Peppol. French companies could attempt to register in Peppol with FRCTC, which caused many errors. task-6421930
Documentation and clarification updates
ERPly S.R.L. has signed Odoo's Corporate Contributor License Agreement, confirming the legal terms for its contributions. This clears the CLA requirement for a related contribution whose other checks were already passing.
Original PR description
ERPly S.R.L. (Santo Domingo, Dominican Republic) signs the Corporate Contributor License Agreement v1.0. This unblocks the `legal/cla` check on #286565, where every other CI check already passes. Signed by Rob Cruz (rob.cruz@erply.do, @rob-erply), acting on behalf of ERPly S.R.L.
The GST token refresh process no longer overwrites the saved token with an incorrect empty value. This helps Indian GST reporting integrations keep working reliably when token validity is extended.
Original PR description
Previously, `_cron_refresh_gst_token` updated the value of `l10n_in_gstr_gst_token` when refreshing the GST token using `response.get('txn')`.
However, the response received during a token refresh is: `{'status_cd': '1', 'status_desc': 'If previous Auth Token is found'}`
The GST token itself remains unchanged during a refresh; only its validity is extended. Therefore, writing `l10n_in_gstr_gst_token` with `response.get('txn')` is unnecessary and incorrect.
This commit removes that write operation.
Forward-Port-Of: odoo/enterprise#130313