Odoo Changelog — 2026-04-06

Monday, April 6, 2026

3 changes · 19.0

Bug Fixes(3)

Resolved issues and error corrections

[FIX] l10n_in: correct sign for TDS report amounts

Core19.0l10n_in

The Indian TDS and TCS 2025 tax reports now show amounts with the correct positive or negative sign after a related tax reporting logic change. This helps businesses avoid misleading report totals and supports more accurate tax review and filing.

Original PR description

In https://github.com/odoo/odoo/commit/17a6117ed88c29b5bc4db0c872bcdbc109a7d98b, the automatic +/- sign handling was removed from the tax grid logic. To stay consistent with this change, the newly added TDS Report 2025 has been updated accordingly.

task-6097997

#india#tax-reporting#tds#tcs

[FIX] pos_urban_piper_enhancements: add account move for future orders

PR #113077

Enterprise19.0pos_urban_piper_enhancements

This update ensures that account moves are automatically created when closing a POS session containing Urban Piper future orders (orders with a delivery date). Previously, these orders were excluded, preventing proper accounting record generation. This fix ensures accurate financial reporting for orders processed through the Urban Piper integration.

Original PR description

Before this commit, when all orders coming from Urban Piper in a POS session are paid future orders (i.e. have a delivery_datetime), closing the session would not generate an account move. The cause was that the code was excluding future orders when creating the account move. The fix is to exclude only unpaid orders instead.

How to reproduce:
- Set up Urban Piper (a test account needed).
- Place an order from the Urban Piper platform.
- Receive the order, accept it, and mark it as ready.
- Close the session.
- The session will not have an account move.

opw-5995985

Forward-Port-Of: odoo/enterprise#113075
Forward-Port-Of: odoo/enterprise#111137

#urban piper#pos#accounting

[ADD] account_reports: error setting tax return journal.

PR #112759

Enterprise19.0account

This update fixes an error where child companies were incorrectly inheriting the tax return journal setting from their parent company. This ensured that each company had its own, accurate tax return journal configuration, preventing reporting discrepancies. Ticket 114344 details this correction.

Original PR description

The objective of this pull request is to show that when the parent company has the tax return journal (account_tax_return_journal_id) set up but the child company does not, then the child company will also have the same tax return journal (account_tax_return_journal_id) set up, but it is incorrect because it is a different company.

Ticket: 114344

#accounting#tax#reporting

In https://github.com/odoo/odoo/commit/17a6117ed88c29b5bc4db0c872bcdbc109a7d98b, the automatic +/- sign handling was removed from the tax grid logic. To stay consistent with this change, the newly added TDS Report 2025 has been updated accordingly. task-6097997

Before this commit, when all orders coming from Urban Piper in a POS session are paid future orders (i.e. have a delivery_datetime), closing the session would not generate an account move. The cause was that the code was excluding future orders when creating the account move. The fix is to exclude only unpaid orders instead. How to reproduce: - Set up Urban Piper (a test account needed). - Place an order from the Urban Piper platform. - Receive the order, accept it, and mark it as ready. - Close the session. - The session will not have an account move. opw-5995985 Forward-Port-Of: odoo/enterprise#113075 Forward-Port-Of: odoo/enterprise#111137

The objective of this pull request is to show that when the parent company has the tax return journal (account_tax_return_journal_id) set up but the child company does not, then the child company will also have the same tax return journal (account_tax_return_journal_id) set up, but it is incorrect because it is a different company. Ticket: 114344