Daily updates from Odoo
Monday, March 30, 2026
6 changes · 19.0
Resolved issues and error corrections
This pull request fixes inaccuracies in the PEPOL XML files generated for Peru (l10n_pe_edi). Specifically, it adjusts the number of digits used for unit prices and multiplier factors to ensure accurate calculations, resolving discrepancies in tax amounts. This improves the reliability of financial reporting.
Original PR description
PR https://github.com/odoo/odoo/pull/255358 introduce a fix that increase the unit price number of digits in the peppol xml if they are significants. It also increases the precision for MultiplierFactorNumeric, which fixes some xml in l10n_pe_edi. For example, previously: MultiplierFactorNumeric = 0.00965 BaseAmount = 10097.46 Amount = 97.46 But `0.00965 * 10097.46 = 97.440489 ≃ 97.44 != 97.46` Now we have multiplierFactorNumeric = 0.00965193227 `0.00965193227 * 10097.46 = 97.4600000190342 ≃ 97.46` Overall, we are more precise, which means the computation are correct now. opw-6009771
This update resolves an issue where kitchen tickets were being printed multiple times when orders were rejected. The fix prevents duplicate printing by ensuring the print token is properly managed during order rejection, improving the reliability of order processing. Preparation messages are now correctly sent after order acceptance.
Original PR description
Bug fix: - Prevent duplicate kitchen ticket printing on order rejection. When a user rejects an order, the reject RPC triggers a webhook that calls _fetchPlatformOrder on all devices. This led to deleteOrders being called twice (once by the reject flow, once by the webhook). Fix: claim the print token via mark_platform_prep_order_as_printed in _rejectOrder before sending the reject RPC, so no device gets isReadyToPrint=true from the webhook. - Preparation needs to be sent after PoS accepts the order. ticket-6071740
This update strengthens security by adding validation when bank statements are automatically synchronized with a journal. Previously, any bank account linked to a journal using online synchronization was automatically trusted. Now, the system will validate the bank account to improve data integrity and reduce potential risks.
Original PR description
When a journal is configured to register bank statements using online synchronization, the bank account linked to the bank journal is automatically trusted. task-6017819
This update fixes an issue where tax returns for Italian companies incorrectly included pension fund taxes, leading to discrepancies between reports and the backend view. The change excludes these taxes from the tax return calculation, ensuring accurate reporting and alignment with customer data. This resolves a previous inconsistency impacting financial reporting.
Original PR description
The "amount to pay" incorrectly included the Pension Fund taxes, causing inconsistencies between the report and what the customer was able to see in the backend. Now we exclude them from the tax return domain. Steps to reproduce: - Create an Italian company with the Italian CoA - Install `l10n_it_edi_withholding` (not necessary in v19) - Create an invoice - Set the 4% INPS or 4% F.Pens taxes on a line, along with with a normal 22% VAT - Create a tax return Ticket [link](https://www.odoo.com/odoo/project.task/5909407) opw-5909407 Forward-Port-Of: odoo/enterprise#111311
This update fixes an issue where global invoices generated from customer invoices weren't correctly including the issued address's zip code in the XML export. The change ensures that the 'LugarExpedicion' field accurately reflects the shipping address, which is crucial for compliance with Mexican tax regulations. This improves the accuracy of invoice data for reporting and auditing.
Original PR description
**STEP TO REPRODUCE** 1. install l10n_mx_edi_extended. 2. Add an issued address on the customer invoice journal, with a zip code. 3. Create invoices, and create a global invoice with them. 4. download the xml, and notice the field LugarExpedicion is not using the zip from the issued address while it should. opw-5956837 Forward-Port-Of: odoo/enterprise#112107 Forward-Port-Of: odoo/enterprise#108732
This update fixes an issue where users were incorrectly grouping POS orders in the l10n_pe_edi_pos module. The system now validates order groupings, preventing errors and providing clear messages to users attempting to combine invoices that don't meet the required criteria. This ensures accurate reporting and compliance for Peruvian tax requirements.
Original PR description
Joining the values in the selection field with a coma, and then putting everything in another selection field was plain wrong. We now check a bit better what we're generating, and refrain the user with error messages when they try grouping on the same invoices orders that do not share the necessary key values. Forward-Port-Of: odoo/enterprise#111616