Wednesday, March 11, 2026
4 changes · saas-18.4
Resolved issues and error corrections
This update fixes an issue where attendance schedules weren't correctly displayed when employees had multiple working schedules with overlapping contract dates. Now, the system accurately shows the correct schedule for each period, ensuring accurate tracking of employee availability. This improves reporting and scheduling accuracy.
Original PR description
Description of the issue/feature this PR addresses: Based on this feedback : [https://www.odoo.com/odoo/project.task/5436300 ](https://www.odoo.com/odoo/project.task/5436300%C2%A0) When I got two…
Description of the issue/feature this PR addresses: Based on this feedback : [https://www.odoo.com/odoo/project.task/5436300 ](https://www.odoo.com/odoo/project.task/5436300%C2%A0) When I got two versions with different working schedules, normally, in Attendance, the gant view should show the unavaibilities by putting in gray days you're not working. As the feedback shows:- . If you have two different working schedules on two different versions and two different occupations period (contract dates), it's working fine. . If the two versions have the same occupation period (contract date), it's only considering the latest working schedule. . If both versions are under the same contract, then it only shows the working schedule on the latest version. This is not what we expect Instead, it should show the correct working schedule for each period Current behavior before PR: Desired behavior after PR is merged: . Modify _get_calendar_periods() method to return the correct working schedule for each period . Fix version_date to use the specified date instead of the creation date. . Add the corresponding tests task-5473047 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects a technical issue preventing electronic invoices in the RIMPE Emprendedor regime from being properly processed. The change ensures the correct string value is used for the invoice structure, resolving a validation error that was causing invoice processing failures. This ensures compliance with Ecuadorian tax regulations.
Original PR description
Corrected the hardcoded string for the RIMPE Emprendedor regime to match the SRI structure According to SRI technical specifications, the <contribuyenteRimpe> tag only accepts two specific values:…
Corrected the hardcoded string for the RIMPE Emprendedor regime to match the SRI structure According to SRI technical specifications, the <contribuyenteRimpe> tag only accepts two specific values: CONTRIBUYENTE RÉGIMEN RIMPE (Fixed value) CONTRIBUYENTE NEGOCIO POPULAR - RÉGIMEN RIMPE Steps to reproduce: Install l10n_ec_edi module Go to Settings > Invoicing > Ecuadorian Localization In Electronic Invoicing > Regime, select rimpe_emprendedor In Electronic Invoicing > Regime, configure a SRI Connection Post an customer invoice **Validation error occurring during the electronic signing process (using .p12 certificates):** `35 - Se encontró el siguiente error en la estructura del comprobante: cvc-pattern-valid: Value 'CONTRIBUYENTE EMPRENDEDOR - RÉGIMEN RIMPE' is not facet-valid with respect to pattern 'CONTRIBUYENTE RÉGIMEN RIMPE|CONTRIBUYENTE NEGOCIO POPULAR - RÉGIMEN RIMPE' for type 'contribuyenteRimpe'.. - ARCHIVO NO CUMPLE ESTRUCTURA XML - ERROR ` Forward-Port-Of: odoo/enterprise#109147
This update fixes an issue where currency exchange difference values were missing from DATEV exports. The fix correctly uses the line balance instead of the currency amount, ensuring accurate reporting of exchange rates for DE company transactions. This improves the reliability of financial data sent to DATEV.
Original PR description
**Steps to reproduce: 1. Create DE company (EUR currency) 2. Add USD -> EUR exchange rates for XX/01/26 and XX/15/26 (XX is target month) 3. Install l10n_de_reports 4. Make sure bank journal has…
**Steps to reproduce: 1. Create DE company (EUR currency) 2. Add USD -> EUR exchange rates for XX/01/26 and XX/15/26 (XX is target month) 3. Install l10n_de_reports 4. Make sure bank journal has 'outstanding receipts' set for incoming manual payment [Accounting -> Config -> Journals -> Bank] 5. Create USD invoice for XX/02/26 and confirm it 6. Register a Payment for XX/16/26 and confirm it (you should see the exchange difference entry matched alongside the payment) 7. Go to [Accounting -> Reporting -> General Ledger] and export DATEV data **Description of issue: The currency exchange rate difference entries in the exported file are shown as 0 **Expected behavior: The actual currency exchange difference values should be displayed **Why this happens? The DATEV export currently sets the amount based on 'amount_currency'. For currency exchange difference entries, this value is 0.0 in the General Ledger, resulting in 0 values in the export. **The fix: Updated the logic to use the line balance when the entry is identified as a currency exchange difference. opw-5358954 Forward-Port-Of: odoo/enterprise#109655 Forward-Port-Of: odoo/enterprise#107268
This update fixes a previous issue where certain salary deductions (specifically 'ATTACH_SALARY') weren't correctly reflected in employee net pay calculations for the Kenyan payroll module. The changes add four new rules to the deduction line, adjusting their sequence and sign to accurately account for these attachments, ensuring accurate net pay reporting.
Original PR description
**Behavior before this commit** Some salary rules (e.g. `ATTACH_SALARY`) were ignored in the NET calculation. **Behavior after this commit** - Four rules are now added to the "Total deductions" line: their sequence and category has been changed. - The sign of these lines has also been switched: an attachment of salary of a positive amount should be added to the amount of total deductions, which is then deducted from the net.  opw-5894647 Forward-Port-Of: odoo/enterprise#107033