Friday, June 5, 2026
4 changes · 19.0
New functionality added to Odoo
This update introduces a dark mode theme for Odoo’s back-office interface and refines related chat, table, and text field styling. It gives users a more comfortable visual option while improving readability and consistency across affected screens.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This change restores missing information on delivery slips when using the DIN 5008 document layout. It reverts a recent styling change that caused key delivery details, such as order and shipping date, to disappear for several customers.
Original PR description
This reverts [1] since it breaks the delivery slip To reproduce the issue: (Need `stock`) 1. Configure the document layout as DIN 5008 2. Create and validate a delivery order 3. Print the delivery slip Error: Some information have disappeared (order, shipping date, and so on) Reverting [1] since it's a recent commit, its use case is neither important nor urgent, and it impacts several customers. [1] 8d588f8198d9057311304e596c009a0795ca6ec7 OPW-6250072 OPW-6260066 OPW-6249926 OPW-6264966
This update resolves a critical issue where the company's XBRL reports were failing validation by the NBB due to missing data disclosures. The fix adds necessary data points to the report, ensuring compliance and successful submission. This prevents potential delays or rejections of the financial reports.
Original PR description
This commit adds missing explanatory disclosure datapoints to the generated XBRL report. The missing disclosures resulted in failing validation when report is submitted to NBB. The datapoints are only added if the original value was non-zero. For example, the tangible assets disclosures are only added if the tangible assets in balance sheet is non-zero. Additionally, only disclosures that were reported as causing a failing validation were added. task-5977199
This update resolves a critical issue preventing CFDI (Mexican electronic invoice) stamping for payslips with IMSS incapacity leaves. The fix ensures the required 'ImporteMonetario' attribute is correctly included and the 'DiasIncapacidad' value is formatted as an integer, aligning with SAT regulations and preventing validation errors.
Original PR description
The Incapacidad node in the nomina 1.2 complement had two issues preventing CFDI stamping for payslips with IMSS incapacity leaves: 1. The ImporteMonetario attribute was missing entirely. This is a…
The Incapacidad node in the nomina 1.2 complement had two issues
preventing CFDI stamping for payslips with IMSS incapacity leaves:
1. The ImporteMonetario attribute was missing entirely. This is a
conditional attribute defined in the SAT XSD (nomina12.xsd) to
express the monetary amount of the incapacity. Without it, the
SAT rejects the CFDI with validation error NOM95:
'El atributo Deduccion:Importe no es igual a la suma de los
nodos Incapacidad:ImporteMonetario, ya que la clave expresada
en Nomina.Deducciones.Deduccion.TipoDeduccion es 006.'
2. The DiasIncapacidad attribute was rendered as a float (e.g. '11.0')
instead of an integer ('11'). The XSD defines it as xs:int with
minInclusive=1, so the float representation caused error 301
(XML mal formado).
Per the SAT filling guide, the ImporteMonetario value depends on
the context:
- Default: the amount comes from deduction 006 (Descuento por
incapacidad), which is the discount applied to the worker.
- Exception: when perception 014 (Subsidios por incapacidad) exists,
the amount comes from that perception instead, representing the
subsidy paid to the worker.
When neither deduction 006 nor perception 014 exist on the payslip,
the attribute is omitted (None) to comply with its conditional
nature in the XSD.