Odoo Changelog — 2026-03-14

Saturday, March 14, 2026

2 changes · saas-19.1

Bug Fixes(2)

Resolved issues and error corrections

[FIX] l10n_mx_edi_pos: Correct refund amount comparison

Enterprisesaas-19.1l10n_mx_edi_posMedium

This update fixes an issue where refund calculations for orders with multiple line items in the Mexican VAT (l10n_mx_edi_pos) module were inaccurate due to incorrect summing of line amounts. The change ensures that refunds are compared correctly against the original order total, preventing errors and ensuring accurate financial processing. This resolves a potential discrepancy in refund amounts.

Original PR description

Before this commit, the some of individual line amounts were being summed to compare against the original order total when processing a refund. This could lead to incorrect comparisons due to rounding issues, resulting in errors when attempting to refund orders with multiple lines.

<img width="626" height="288" alt="image" src="https://github.com/user-attachments/assets/e1bdc126-64d9-4b9a-bd16-2b97ac75e40c" />

opw-5433201

Forward-Port-Of: odoo/enterprise#108827
Forward-Port-Of: odoo/enterprise#105301

#refund#mexican_vat#accounting

[FIX] l10n_de_pos_cert: Fiskaly transaction state conflicts for API v2

PR #110741

Enterprisesaas-19.1l10n_de_pos_certMedium

This update resolves conflicts in how transactions are managed for the German Point of Sale (POS) system, specifically related to Fiskaly reporting. The changes ensure that transactions are correctly cancelled or finished, preventing errors and improving data accuracy. This resolves a previous issue impacting transaction processing.

Original PR description

Changes:
- cancelActiveTransactions: use the TSS-scoped endpoint
  /tss/{tss_id}/tx and filter results by client_id so only orphaned
  transactions from this terminal are cancelled, never those from
  other POS sessions sharing the same TSS
- transactionCall: on non-retryable errors (400 revision conflict or
  terminal state mismatch), call _handleTransactionStateConflict which
  GETs the actual transaction state and recovers:
    - Cancelling already CANCELLED → silent success
    - Finishing already FINISHED → return existing tx data
    - Finishing a CANCELLED tx → create a fresh transaction and finish it
- handleFiskalyCancellation: correctly reset transactionState to
  inactive on the uiState after cancellation

opw-5972708

Forward-Port-Of: odoo/enterprise#110400
Forward-Port-Of: odoo/enterprise#109996

#Fiskaly#POS#Germany#Transaction Management

Before this commit, the some of individual line amounts were being summed to compare against the original order total when processing a refund. This could lead to incorrect comparisons due to rounding issues, resulting in errors when attempting to refund orders with multiple lines. <img width="626" height="288" alt="image" src="https://github.com/user-attachments/assets/e1bdc126-64d9-4b9a-bd16-2b97ac75e40c" /> opw-5433201 Forward-Port-Of: odoo/enterprise#108827 Forward-Port-Of: odoo/enterprise#105301

Changes: - cancelActiveTransactions: use the TSS-scoped endpoint /tss/{tss_id}/tx and filter results by client_id so only orphaned transactions from this terminal are cancelled, never those from other POS sessions sharing the same TSS - transactionCall: on non-retryable errors (400 revision conflict or terminal state mismatch), call _handleTransactionStateConflict which GETs the actual transaction state and recovers: - Cancelling already CANCELLED → silent success - Finishing already FINISHED → return existing tx data - Finishing a CANCELLED tx → create a fresh transaction and finish it - handleFiskalyCancellation: correctly reset transactionState to inactive on the uiState after cancellation opw-5972708 Forward-Port-Of: odoo/enterprise#110400 Forward-Port-Of: odoo/enterprise#109996