Odoo Changelog — 2026-06-18

Thursday, June 18, 2026

1 change

Refactoring(1)

Code cleanup and technical improvements

[REF] account,*: multi ID - remove company_registry

Enterprisemasteraccountl10n_ae_fafl10n_at_saftl10n_be_intrastataccount_saftMEDIUM

This update streamlines how partner identifiers are managed within Odoo, consolidating them into a single JSON field. Removing the outdated 'company_registry' field and standardizing routing identifiers improves compatibility with e-invoicing standards like UBL and Peppol, simplifying reporting and integration. This change enhances data accuracy and reduces complexity for users.

Original PR description

We previously replaced the scattered, country-specific partner
identifier fields with one JSON field `additional_identifiers`.
This commits continues to clean up after that change, mainly:

- Move the additional_identifiers JSON field into base: some modules
(l10n_xx_hr_payroll) don't depend on `account` yet still have similar
contact's identifiers.
- Drop the company_registry field as now, everything should be more
specific, and stored in the JSON field.

Smaller changes:
- add base helpers selecting a partner's preferred legal-entity, tax and
routing identifier, reused by UBL/CII EDI, SAF-T and Peppol/PDP
- rename peppol_eas/peppol_endpoint to routing_scheme/routing_endpoint
(+ computed routing_identifier) so any e-invoicing network can route
using this fields => less confusing.
- Some countries have non-stored compute/inverse for convient access
(l10n_fr_siret/siren, SG UEN, NO Brønnøysund, ...),
- adapt UBL/CII exports, SAF-T reports and invoice reports after the
removal of the company_registry.
- cleanup of the scheme/endpoint validation so that's it's more coherent. There
was 3 different validation before, of only a subset of schemes.

task-6140750

#e-invoicing#reporting#UBL#Peppol#identifiers

We previously replaced the scattered, country-specific partner identifier fields with one JSON field `additional_identifiers`. This commits continues to clean up after that change, mainly: - Move the additional_identifiers JSON field into base: some modules (l10n_xx_hr_payroll) don't depend on `account` yet still have similar contact's identifiers. - Drop the company_registry field as now, everything should be more specific, and stored in the JSON field. Smaller changes: - add base helpers selecting a partner's preferred legal-entity, tax and routing identifier, reused by UBL/CII EDI, SAF-T and Peppol/PDP - rename peppol_eas/peppol_endpoint to routing_scheme/routing_endpoint (+ computed routing_identifier) so any e-invoicing network can route using this fields => less confusing. - Some countries have non-stored compute/inverse for convient access (l10n_fr_siret/siren, SG UEN, NO Brønnøysund, ...), - adapt UBL/CII exports, SAF-T reports and invoice reports after the removal of the company_registry. - cleanup of the scheme/endpoint validation so that's it's more coherent. There was 3 different validation before, of only a subset of schemes. task-6140750