Monday, December 1, 2025
3 changes · 17.0
Enhancements to existing features
This update enhances the way users manage currencies within Odoo. It now allows searching for both active and inactive currencies, and provides a toggle in the mobile kanban view to easily switch between currency states. This simplifies currency management for users and improves data accessibility.
Original PR description
This commit does 2 things: 1. In account.move form view, when the user click on search more of the currency, they would only see active ones they can then show inactive currencies using filters 2. The kanban view of the currency now shows a toggle which can toggle between active and inactive states for the currency so that the users on the mobile view can easily toggle through kanbans without having to go to form view task-5354516 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update ensures Odoo correctly handles German B2G electronic invoices (XRechnungen). It adds a mandatory 'Leitweg-ID' to the invoice format, directing invoices to the appropriate government entity as required by German regulations. This improves compliance and accuracy for transactions in Germany.
Original PR description
*= l10n_account_edi_ubl_cii_tests For B2G transactions in Germany, the Leitweg-ID is a mandatory routing identifier to direct the invoice to the correct public entity. Adding this Leitweg-ID for the UBL syntax. task-5194484 Description of the issue/feature this PR addresses: For electronic invoicing in Germany, for B2G transactions, the Leitweg-ID is a mandatory routing identifier to direct the invoice to the correct public entity. We want to add this identifier for the XRechnung format. Current behavior before PR: The Leitweg-ID is not present in the UBL xml format. Desired behavior after PR is merged: The Leitweg-ID is added in the header of the invoice in the cbc:BuyerReference tag. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This update resolves a problem where invoice counters submitted to the Jordanian tax authority (ISTD) were not consistently sequential. The fix utilizes a new calculation to ensure counters are always in order, meeting ISTD requirements and preventing potential export delays. This improves the accuracy and reliability of our Jordan-specific accounting processes.
Original PR description
Before this commit, the invoice counter in the XML submitted to JoFotara was set to the move id. The problem with the move id is that it's not guaranteed that submitted counters would be sequential; they may contain gaps or even be out of order. The ISTD expects counters to be sequential. This commit solves this issue by relying on a computed field in assigning invoice counter in the EDI XML. task-4632768 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr