Odoo Changelog — 2026-03-11

Wednesday, March 11, 2026

2 changes · 19.0

Bug Fixes(2)

Resolved issues and error corrections

[FIX] sale_amazon: allow onboarding in multicompany environment

Enterprise19.0sale_amazonMedium

This update resolves an issue preventing users from setting up Amazon accounts in environments with multiple companies. Previously, the onboarding process was limited to the website company, causing errors when the Amazon account didn't match. Now, users can access all their companies during the setup, ensuring a smoother and more reliable experience.

Original PR description

The onboarding return route is a website route with access restricted to the website company only. This causes an error when the company doesn't match the Amazon account being connected.

This commit allows users to access all their companies during Amazon account setup to avoid this mismatch error.

opw-5944078

Forward-Port-Of: odoo/enterprise#109882
Forward-Port-Of: odoo/enterprise#109590

#amazon#onboarding#multicompany

[FIX] account_accountant: allow amount matching for outstanding receipts

PR #109992

Enterprise19.0accountantMedium

This update corrects a bug that prevented automatic matching of bank transactions with invoices when 'Outstanding Receipts' accounts were configured in the bank journal. The fix allows for amount matching, ensuring payments are correctly reconciled, improving financial accuracy. This resolves a previous issue impacting payment reconciliation workflows.

Original PR description

Steps to reproduce
- Have a Bank journal with Outstanding Receipts accounts set
- Create and confirm an invoice with a payment reference
- Create the payment
- Create a bank transaction with:
  - Label: any label
  - Partner: invoice partner
  - Amount: invoice full amount

Issue:
Transaction won't be matched automatically

Analysis:
Transaction will be automatically matched if the outstanding receipts account is not set. It occurs because in case it is set, the sytem will only try to match the communication pattern against the journal item of the payment, without trying amount matching

Note: another solution could be to relax the communication matching. In the user case the invoice payment reference is something like `TEST-12345` and the payment communication `AAAAAAAAAAA /BBBBBBBBBBB TEST 12345`

opw-5872387

Forward-Port-Of: odoo/enterprise#108564

#finance#reconciliation#payments

The onboarding return route is a website route with access restricted to the website company only. This causes an error when the company doesn't match the Amazon account being connected. This commit allows users to access all their companies during Amazon account setup to avoid this mismatch error. opw-5944078 Forward-Port-Of: odoo/enterprise#109882 Forward-Port-Of: odoo/enterprise#109590

Steps to reproduce - Have a Bank journal with Outstanding Receipts accounts set - Create and confirm an invoice with a payment reference - Create the payment - Create a bank transaction with: - Label: any label - Partner: invoice partner - Amount: invoice full amount Issue: Transaction won't be matched automatically Analysis: Transaction will be automatically matched if the outstanding receipts account is not set. It occurs because in case it is set, the sytem will only try to match the communication pattern against the journal item of the payment, without trying amount matching Note: another solution could be to relax the communication matching. In the user case the invoice payment reference is something like `TEST-12345` and the payment communication `AAAAAAAAAAA /BBBBBBBBBBB TEST 12345` opw-5872387 Forward-Port-Of: odoo/enterprise#108564