Odoo Changelog — 2026-02-28

Saturday, February 28, 2026

2 changes · saas-18.3

Bug Fixes(2)

Resolved issues and error corrections

[FIX] account_peppol: fix wrong company_registry value in peppol

Coresaas-18.3accountMEDIUM

This update fixes an issue where invoices generated using the PEPPOL standard were incorrectly using company registry information. Previously, the system didn't verify that company registry data matched the required BCE number. This change ensures invoices comply with PEPPOL regulations, preventing potential errors and improving data accuracy.

Original PR description

We expect people to put BCE number in the company registry. 
But it is not enforced client-side, resulting in invoices in error.




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#251168

#peppol#invoice#company registry#account

[FIX] website_sale_external_tax: add avatax during stripe express checkout

PR #109065

Enterprisesaas-18.3website_sale_external_taxMEDIUM

This update resolves an issue where Avatax taxes weren't being correctly calculated during Stripe Express Checkout, particularly when using Google Pay. The fix ensures that all applicable taxes, including those from Avatax, are accurately reflected in the order total, leading to consistent pricing and payment reconciliation. This improves the accuracy of sales transactions.

Original PR description

## Versions 17.0+ ## Issue Avataxes are not computed during express checkout leading to discrepancies between customer payments and effective price including Avalara taxes. ## Steps to reproduce…

## Versions
17.0+

## Issue
Avataxes are not computed during express checkout leading to discrepancies between customer payments and effective price including Avalara taxes.

## Steps to reproduce
*Ensure the Stripe account has activated Google Pay* *This requires a complete Google profile on Google Chrome (with a valid payment method)*
- Setup Stripe payment method in test mode with Express Checkout;
- In the Settings, in the Accounting section:
  - Setup Avatax;
  - Set main Sales/Purchase taxes to 0.
- Create a new product with 0% selling taxes and any Avatax category;
- Activate fiscal position and enable automatic detection;
- Open a Chrome session with the Google profile:
  - Go to the shop;
  - Add the product you created to the cart;
  - Enter the cart;
  - Click the "Buy with GPay" button:
    - The amount is equal to the sales price excluding taxes.
- Go to the Sales app and open the newly created order:
  - The total amount differs from the amount paid (cf. transaction).

opw-5020793

Forward-Port-Of: odoo/enterprise#108957
Forward-Port-Of: odoo/enterprise#101579

#taxes#stripe#avatax#google pay

We expect people to put BCE number in the company registry. But it is not enforced client-side, resulting in invoices in error. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#251168

## Versions 17.0+ ## Issue Avataxes are not computed during express checkout leading to discrepancies between customer payments and effective price including Avalara taxes. ## Steps to reproduce *Ensure the Stripe account has activated Google Pay* *This requires a complete Google profile on Google Chrome (with a valid payment method)* - Setup Stripe payment method in test mode with Express Checkout; - In the Settings, in the Accounting section: - Setup Avatax; - Set main Sales/Purchase taxes to 0. - Create a new product with 0% selling taxes and any Avatax category; - Activate fiscal position and enable automatic detection; - Open a Chrome session with the Google profile: - Go to the shop; - Add the product you created to the cart; - Enter the cart; - Click the "Buy with GPay" button: - The amount is equal to the sales price excluding taxes. - Go to the Sales app and open the newly created order: - The total amount differs from the amount paid (cf. transaction). opw-5020793 Forward-Port-Of: odoo/enterprise#108957 Forward-Port-Of: odoo/enterprise#101579