Daily updates from Odoo
Monday, September 23, 2024
2 changes · master
Enhancements to existing features
Tax closing is now managed separately for each tax report, so closing entries better match the specific report and company context. This improves accuracy, supports report-specific rounding needs, and prevents manual changes from being overwritten when closing moves are posted for branches or tax units.
Original PR description
This commit aim to improve the tax closing. - One tax closing per report - Closing values are now based on the report and not the move lines anymore - Custom expression on the tax report to compute the closing amount - Handling rounding difference out of the box - Use settings per report per companies to set the account for the closing -> removed from `account.tax.group` - Support Tax Rounded value for specific reports such as l10n_fr tax report - [TODO] Handle special cases such as oss report - [TODO] Rewrite a bunch of tests thats use the old system Fixes: - When posting a closing move in a branch or tax unit as the main company, all the move would be refreshed. So any manual modification would be lost Task-4019571 Related Community: https://github.com/odoo/odoo/pull/174001
Code cleanup and technical improvements
The Print & Send flow now lets businesses define a preferred invoice delivery channel per customer, such as email, post, manual download, or Peppol. This reduces duplicate invoice delivery, supports required government declarations, and makes batch invoice sending more reliable and easier for accounting teams.
Original PR description
Refactoring of the Print & Send: Why ? Invoicing communication channels have multiplied with the advent of electronic invoicing. Clients want to receive PDF and electronic formats (UBL, Factur-X,…
Refactoring of the Print & Send: Why ? Invoicing communication channels have multiplied with the advent of electronic invoicing. Clients want to receive PDF and electronic formats (UBL, Factur-X, Factura-e,...) in different ways (email, peppol, post, ...), depending on the localization and their needs. Mandatory B2G declarations of invoices are also multiplying. The current Print & Send allows for that flexibility, but at the cost of becoming: - quite messy: you have many checboxes that you can chose at the same time with different meaning (B2B, B2G, sending method,...) - hard to use in batch: as you can't setup invoice channel by partner, you need to chose each time you click on Print & Send. Then some magical things happen to apply the right checkbox to the right invoices. - technically complicated: because some options are about format, some about how to send, about one or more invoices. - the current solution invites the user to "multiply the channels", by clicking everything and send his invoices to his customers via all the channels possible. This creates a situation where E-Invoicing creates a mess for accountants that receive the same invoice via multiple sources, further causing potential duplicates, double payments, etc. How ? - Choose ONE channel of communication per partner to send his invoice (by Post, manual (download), by Email, by Peppol) - Synchronize mandatory B2G declaration with invoice sending - Choose if a B2B E-invoice format needs to be generated (UBL, Factur-X, Factura-e,...) - Make invoice batching sending easy by applying selected defaults, this also mean B2G declarations will be applied by default if relevant. - We also added at partner level the possibility the select an invoice report template, as well as mail templates. task-4070132