Monday, September 21, 2026
2 changes · saas-19.3
Enhancements to existing features
Invoice sections that hide their detailed composition now group amounts by tax consistently in Accounting PDFs and XML exports. This makes invoice presentation and electronic invoice data align better with Sales behavior and improves tax clarity for customers and compliance workflows.
Original PR description
Before this commit, collapsing composition in Accounting did not behave the same as in Sales. In Accounting PDFs, when a section was created and its composition was hidden, taxes were removed from…
Before this commit, collapsing composition in Accounting did not behave the same as in Sales. In Accounting PDFs, when a section was created and its composition was hidden, taxes were removed from individual lines and displayed on the section line as a comma-separated list. This commit aligns the behavior with the Sales app: - When collapsing composition, sections are grouped by tax. - When hiding prices, taxes are removed from the section line and kept on each individual line. Also, hiding composition in sections wasn't taken into account while exporting the XML. This commit introduces this behaviour for the XML invoices : - when we export section that hides the composition, we first group the sections by tax, then we create an invoice line with the section's name, with the right tax and amounts calculations. NOTE: This commit does not introduce price hiding in XML exports. task-6101592 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#288317 Forward-Port-Of: odoo/odoo#258959
The Romanian eTransport workflow can now create declarations for supported domestic and international consumer dropship deliveries. This helps businesses using dropshipping comply with Romanian transport reporting requirements, while unsupported business-to-business dropship cases now receive clear error messages.
Original PR description
Before this commit: Dropship operations were not supported by the Romanian eTransport integration. As a result, eTransport declarations could not be generated for dropshipping flows. After this commit: eTransport declarations can now be generated for dropship operations, allowing the supported dropshipping scenarios to be processed through the Romanian eTransport workflow. task-6391489 Forward-Port-Of: odoo/odoo#288913 Forward-Port-Of: odoo/odoo#280199