Odoo Changelog — 2026-07-10

Friday, July 10, 2026

5 changes · 18.0

New Features(1)

New functionality added to Odoo

[ADD] whatsapp_identifiers: support for business-scoped user IDs

Enterprise18.0whatsappwhatsapp_identifierstest_whatsappMEDIUM

Odoo can now recognize and contact WhatsApp users using Meta's new business-scoped user IDs when phone numbers are not provided. This improves contact matching and helps businesses keep conversations working as WhatsApp changes how user identifiers are shared.

Original PR description

Add support for whatsapp business-scoped user ids as outline in the [documentation](https://developers.facebook.com/documentation/business-messaging/whatsapp/business-scoped-user-ids) for their introduction this June.

This effectively adds a table mapping BSUID to contacts to enable contacting users who contact the business directly, as the business will now not necessarily be provided with their number. Additionally the “whatsapp id”, i.e. the canonical form of the phone number as stored in whatsapp, is stored to help better match contacts regardless of formatting details in odoo and whatsapp.

task-5476552

Forward-Port-Of: odoo/enterprise#117782

#whatsapp#contacts#business messaging#user identifiers

Bug Fixes(4)

Resolved issues and error corrections

[IMP] l10n_cl_edi: limit l10n_cl_company_activity_ids to 4 records

PR #122460

Enterprise18.0l10n_cl_ediMEDIUM

This change prevents Chilean companies from selecting more than four business activities for electronic invoicing. It helps avoid tax authority rejections caused by documents that exceed the allowed activity limit.

Original PR description

The Chilean XML schema supports maximum of 4 activities (l10n_cl_company_activity_ids), but we allow to add more than that. If this happens, it causes rejections since electronic documents are being sent with more than 4 options selected, and returning rejection errors.

Adding constraint to limit l10n_cl_company_activity_ids

task-id: 6329320

#Chile#electronic invoicing#compliance

[FIX] l10n_ar_reports: VAT book export for foreign partners

PR #123576

Enterprise18.0l10n_ar_reportsMEDIUM

The Argentine VAT Book export no longer fails when invoices involve foreign partners marked as external providers. This helps accounting teams generate required VAT ZIP reports without manual workarounds or blocked reporting flows.

Original PR description

Steps to reproduce:
- Create a partner with:
  - State: Ireland
  - Identification Number: Foreign ID 55000004153
  - ARCA Responsibility Type: Proveedor del Exterior
- Create an invoice for the partner
- Accounting > Reporting > Tax report
- Select Report: VAT Book (AR), Tax Type: Sales
- Click on gear icon > VAT Book (ZIP)

Issue:

Action will be blocked with error "No VAT configured for partner [58] <partner>"

Analysis:

Partners with ARCA responsibility type 'Proveedor del Exterior' (code 8) and a ForeignID identification type, causes a UserError when exporting the VAT Book (ZIP).  Code 8 (foreign provider) is the purchase-side counterpart of code 9 (foreign customer), which already fell back to the country-level VAT.  Extend the existing fallback branch to cover both codes.

opw-6316008

Forward-Port-Of: odoo/enterprise#123506

#Argentina#VAT Book#foreign partners#tax reporting

[FIX] l10n_es_reports: ignore negative component taxes in VAT books

PR #123738

Enterprise18.0l10n_es_reportsMEDIUM

Spanish VAT books now correctly show tax amounts for vendor bills that use taxes with negative components, such as certain EU tax setups. This prevents valid tax amounts from incorrectly appearing as zero, improving the accuracy of Spanish VAT reporting.

Original PR description

Problem:
In the Spanish VAT books, taxes with negative component (like 21% EU G) always show their amounts as zero.

Steps to reproduce:
1. Install the l10n_es_reports module and select the Spanish company
2. Create a vendor bill with a vendor from another EU country and add a product
3. Make sure the tax applied to the product has a negative component (like 21% EU G)
4. Confirm the bill
5. Go to Accounting > Reporting > Tax Return
6. Generate the VAT books from the action menu and check the tax amounts
7. Notice how the tax amount is zero, even though the tax was applied to the bill

Cause:
When calculating the tax amounts, the negative component cancels out the positive component, leading to the amount always showing as zero in the VAT books.

opw-6169766

#Spanish VAT#VAT books#tax reporting

[FIX] l10n_it_edi: apply fiscal position to imported bill taxes

PR #274738

Core18.0l10n_it_ediMEDIUM

This update fixes an issue where imported FatturaPA XML invoices weren't correctly applying Italian VAT rules (like partial deductibility) to the line items. Now, the system accurately maps these imported taxes to the fiscal position, ensuring correct VAT calculations for Italian businesses. This improves tax compliance and reporting accuracy.

Original PR description

### Before this PR
When importing a FatturaPA XML, Odoo sets the fiscal position on the bill from the partner but does not apply it to the line taxes so a fiscal position that remaps taxes (partial deductibility, reverse charge, split payment) never map the imported lines.

### After this PR
the fiscal position is correctly applied


### To reproduce

1. Apply to Italian vendor a fiscal position that maps the 22% purchase tax to a partial-deductibility tax (e.g. "22%" →"22% ind. 50%").
2. Import a FatturaPA XML from that vendor with 22% lines.
3. The bill header shows the fiscal position, but the lines keep the plain 22% tax instead of the mapped one.



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

#VAT#Italy#Tax#FatturaPA

Add support for whatsapp business-scoped user ids as outline in the [documentation](https://developers.facebook.com/documentation/business-messaging/whatsapp/business-scoped-user-ids) for their introduction this June. This effectively adds a table mapping BSUID to contacts to enable contacting users who contact the business directly, as the business will now not necessarily be provided with their number. Additionally the “whatsapp id”, i.e. the canonical form of the phone number as stored in whatsapp, is stored to help better match contacts regardless of formatting details in odoo and whatsapp. task-5476552 Forward-Port-Of: odoo/enterprise#117782

The Chilean XML schema supports maximum of 4 activities (l10n_cl_company_activity_ids), but we allow to add more than that. If this happens, it causes rejections since electronic documents are being sent with more than 4 options selected, and returning rejection errors. Adding constraint to limit l10n_cl_company_activity_ids task-id: 6329320

Steps to reproduce: - Create a partner with: - State: Ireland - Identification Number: Foreign ID 55000004153 - ARCA Responsibility Type: Proveedor del Exterior - Create an invoice for the partner - Accounting > Reporting > Tax report - Select Report: VAT Book (AR), Tax Type: Sales - Click on gear icon > VAT Book (ZIP) Issue: Action will be blocked with error "No VAT configured for partner [58] <partner>" Analysis: Partners with ARCA responsibility type 'Proveedor del Exterior' (code 8) and a ForeignID identification type, causes a UserError when exporting the VAT Book (ZIP). Code 8 (foreign provider) is the purchase-side counterpart of code 9 (foreign customer), which already fell back to the country-level VAT. Extend the existing fallback branch to cover both codes. opw-6316008 Forward-Port-Of: odoo/enterprise#123506

Problem: In the Spanish VAT books, taxes with negative component (like 21% EU G) always show their amounts as zero. Steps to reproduce: 1. Install the l10n_es_reports module and select the Spanish company 2. Create a vendor bill with a vendor from another EU country and add a product 3. Make sure the tax applied to the product has a negative component (like 21% EU G) 4. Confirm the bill 5. Go to Accounting > Reporting > Tax Return 6. Generate the VAT books from the action menu and check the tax amounts 7. Notice how the tax amount is zero, even though the tax was applied to the bill Cause: When calculating the tax amounts, the negative component cancels out the positive component, leading to the amount always showing as zero in the VAT books. opw-6169766

### Before this PR When importing a FatturaPA XML, Odoo sets the fiscal position on the bill from the partner but does not apply it to the line taxes so a fiscal position that remaps taxes (partial deductibility, reverse charge, split payment) never map the imported lines. ### After this PR the fiscal position is correctly applied ### To reproduce 1. Apply to Italian vendor a fiscal position that maps the 22% purchase tax to a partial-deductibility tax (e.g. "22%" →"22% ind. 50%"). 2. Import a FatturaPA XML from that vendor with 22% lines. 3. The bill header shows the fiscal position, but the lines keep the plain 22% tax instead of the mapped one. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr