Monday, July 6, 2026
5 changes · 17.0
Resolved issues and error corrections
Bank statement imports that contain only zero-amount transactions now show a specific error instead of being mislabeled as duplicates. This helps users understand the real issue with the file and take the correct action faster.
Original PR description
When importing bank statements, files containing only zero-amount transactions trigger the same generic "duplicate" UserError as files that have already been imported. We now explicitly check for zero-amount lines separately to raise a distinct UserError. opw-6237659
This update corrects a bug in the Odoo journal entry preview. Previously, if a currency wasn't specified, the preview incorrectly displayed the debit amount in both columns. This change ensures the preview accurately reflects the credit and debit values, improving the reliability of financial reporting.
Original PR description
In _move_dict_to_preview_vals(), when no currency is provided, the credit column falls back to the line's debit value, so any caller omitting currency_id would show the debit amount in both columns of the journal entry preview. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects formatting issues with numbers in various languages, including Indian languages and Burmese, ensuring correct decimal separators and grouping symbols. It addresses inconsistencies in number formatting to improve the user experience for international customers and users.
This update resolves an issue where Nilvera invoices occasionally got stuck in an 'Unknown' status. The fix ensures Odoo continuously polls Nilvera for the latest invoice status, preventing delays in reporting and reconciliation. This improves the reliability of e-invoice processing with Nilvera.
Original PR description
## Short fix summary:
Nilvera reports `Unknown` as a normal, transient `StatusCode` value (their own e-Archive API docs
list the enum as `unknown`/`waiting`/`succeed`/`error`) right after a document is sent, before their
daily batch resolves the final status. But `_cron_nilvera_get_invoice_status`'s search domain only
matches `l10n_tr_nilvera_send_status in ('waiting', 'sent')`, so once an invoice lands on `unknown` it
is never polled again — even after Nilvera later resolves the real status on their side. This adds
`unknown` to that domain so these invoices keep getting polled until Nilvera reports a final status.
task-6328589
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update fixes a formatting issue with numbers displayed in Portuguese (pt_PT) and Hindi (hi_IN) languages within Odoo. It ensures numbers are grouped correctly according to international standards – three digits for Western countries and two digits after the first three for India – improving readability and accuracy. This change ensures consistent and appropriate number formatting for our users in these regions.
Original PR description
Currently the number grouping for Portuguese and Hindi is missing. Number grouping is used to separate long numbers in logical groups to make then easier to read. In Western countries, the grouping is usually done in groups of three digits (e.g. `1,000,000` instead of `1000000`), while in India, the grouping is done in groups of two digits after the first three digits (e.g. `10,00,000` instead of `1000000`). Source: https://www.unicode.org/cldr/charts/48/by_type/numbers.number_formatting_patterns.html#24a93b3d14ba17b2 All languages will be revised in a follow-up `master` PR. [task-6320391](https://www.odoo.com/odoo/project.task/6320391)