Thursday, July 31, 2025
2 changes · 18.0
Enhancements to existing features
Saudi e-invoicing setup now sends ZATCA the correct company information depending on whether a business is a standalone company or a branch. It also prevents invoices from being posted with a mismatched journal company, reducing compliance errors and improving test coverage for business-to-business invoicing.
Original PR description
…nches Description of the issue/feature this PR addresses: The current implementation of generating CSR files for EDI doesn't differnetiate between parent companies and branches. ZATCA, however,…
…nches Description of the issue/feature this PR addresses: The current implementation of generating CSR files for EDI doesn't differnetiate between parent companies and branches. ZATCA, however, expects slightly different information depending on whether the company is a branch or a parent. This also includes a refactor of the tests for l10n_sa_edi. Current behavior before PR: The Organization Name, Organization Unit Name, and Organization Identifier of whichever company on the journal were being sent to ZATCA. You could also Onboard/Re-Onboard a journal in different company. The unit tests for EDI document generation were primarily using a partner based in the US, which meant that the b2b invoicing main flow was not being properly tested Desired behavior after PR is merged: Parent/Standalone Company: - Organization Name: The name of the company - Organization Unit Name: First 10 characters of the VAT - Organization Identifier: The VAT of the company Branch: - Organization Name: The name of the parent - Organization Unit Name: The name of the branch - Organization Identifier: The VAT of the parent - Prevent users from posting invoices, credit notes, or debit notes whose invoice company doesn't match the journal company - The tests are easier to read and they test the b2b flow correctly opw-4794842 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#213518
Portal users can now sort their signature requests by their current status, making it easier to find the most relevant or urgent documents. This improves day-to-day navigation for users managing multiple signature requests.
Original PR description
This improvement adds a new sorting option in the user portal to allow sorting sign requests by their current state. This provides users with a more intuitive way to view their requests, prioritizing the most relevant or urgent ones. To support this, a new computed field `state_order` was added to the `sign.request.item` model. It determines the item's sort order based on the state of the linked `sign.request`. The ordering logic follows the definition order of the `state` selection field in the `sign.request` model. Developers should maintain this order when modifying the selection list to preserve consistent behavior. task-4978713