Thursday, October 23, 2025
2 changes · 17.0
Enhancements to existing features
Odoo now routes Peppol partner lookup checks through its IAP service so it can support the Peppol network’s upcoming DNS change. This helps keep electronic invoicing partner discovery working after the switch from CNAME to NAPTR records, without requiring unsupported package changes in stable versions.
Original PR description
Starting from 1st November, the Peppol SML will start to use NAPTR records instead of CNAME. This mainly allow them to enforce a specify a scheme (https). To be able to retrieve this specific type of records and follow the replacement record we need `pythondns` package which is not available in stable versions. We therefore will now use IAP to serves as a bridge to query the Peppol network when retrieving a partner services/existence on Peppol. This solution is also good to handle future changes by moving most of the logic into IAP where stable policy is easier to handle. Related: https://github.com/odoo/iap-apps/pull/1203 Documentation: https://docs.peppol.eu/edelivery/changelog/2025-04/Peppol%20CNAME%20to%20NAPTR%20Migration%20Process%20v1.0.0%202025-04-17.pdf task-5059508
Electronic invoices can now use a fallback payment code when no bank account is configured, avoiding validation errors in BIS3 exports. This makes initial setup smoother for businesses that have not added bank details yet.
Original PR description
Backport of commit 026743fb2627edeada5ae2a517b64bf05ae921ae . To generate a valid BIS3 format, if we put 30 - credit transfer as payment means, we need to have a bank account set. If it's not the case, it will raise an error. We improve the usability by changing that code to ZZZ - mutually defined if no bank account is provided to the invoice. This should improve the onboarding flow when no bank account is set yet. task-None Forward-Port-Of: odoo/odoo#232795