Daily updates from Odoo
Friday, May 29, 2026
9 changes
1 change
New functionality added to Odoo
This update adds crucial data fields – like price before tax, tax names, and supplier information – to the data sent to Pricer. This improves the accuracy of pricing calculations and supports more complete use cases within our point-of-sale system. The update also ensures Pricer tags are automatically updated when related product information changes.
Original PR description
We are currently missing some fields which must be sent to Pricer for some basic use-case scenarios This PR adds - Price before taxes - Taxes name (ex: 21%) - Supplier product code - Supplier reference - Units of measure of the product The PR also triggers the update of the pricer tags when the models indirectly related to Pricer are modified (taxes name / supplier reference / supplier product code) + cleans up the code a bit task-4506260 Forward-Port-Of: odoo/enterprise#93330 Forward-Port-Of: odoo/enterprise#78009
1 change
New functionality added to Odoo
This update adds crucial data fields – like price before taxes, tax names, and supplier information – to the data sent to Pricer. This enables more accurate pricing calculations for basic sales scenarios. The update also ensures Pricer tags are automatically updated when related product or tax information changes.
Original PR description
We are currently missing some fields which must be sent to Pricer for some basic use-case scenarios This PR adds - Price before taxes - Taxes name (ex: 21%) - Supplier product code - Supplier reference - Units of measure of the product The PR also triggers the update of the pricer tags when the models indirectly related to Pricer are modified (taxes name / supplier reference / supplier product code) + cleans up the code a bit task-4506260 Forward-Port-Of: odoo/enterprise#93330 Forward-Port-Of: odoo/enterprise#78009
1 change
New functionality added to Odoo
This update expands the information sent to Pricer, including price before taxes, tax details, supplier product codes, and units of measure. This addition addresses critical use cases and ensures accurate pricing calculations within the Pricer system. The update also includes minor code cleanup and automated updates to Pricer tags based on related product and supplier information.
Original PR description
We are currently missing some fields which must be sent to Pricer for some basic use-case scenarios This PR adds - Price before taxes - Taxes name (ex: 21%) - Supplier product code - Supplier reference - Units of measure of the product The PR also triggers the update of the pricer tags when the models indirectly related to Pricer are modified (taxes name / supplier reference / supplier product code) + cleans up the code a bit task-4506260 Forward-Port-Of: odoo/enterprise#93330 Forward-Port-Of: odoo/enterprise#78009
2 changes
New functionality added to Odoo
This update introduces support for Indonesian tax returns within the Odoo Enterprise system. The new module, l10n_id_reports, allows users to generate the necessary reports required for tax compliance in Indonesia. This enhancement improves the system's ability to meet local regulations and reporting needs.
Original PR description
Create new module l10n_id_reports and add return type for Indonesia. task-6239169 Forward-Port-Of: odoo/enterprise#118467 Forward-Port-Of: odoo/enterprise#118304
This update introduces new VoIP phone extensions within the Odoo Enterprise system. These extensions route incoming calls directly to Odoo users, utilizing Wazo queues for efficient call management. This enhancement improves communication capabilities for users and allows for better control over phone services.
2 changes
New functionality added to Odoo
This update adds a new report to comply with Vietnamese Accounting Standards (VAS). It ensures the General Ledger accurately reflects counterpart accounts and balances, a key requirement for Vietnamese businesses. A custom SQL query and post-processor are used to handle complex transaction types and maintain report accuracy.
Original PR description
Vietnamese Accounting Standards (VAS) require businesses to generate their General Ledger following a specific format known as Form S03b-DN. A key compliance requirement of this report is the explicit display of the counterpart account for every transaction line, as well as maintaining strictly separated debit and credit balances. To achieve the counterpart mapping, a custom report handler and custom engine are introduced. Because standard journal entries do not strictly bind individual debit and credit lines together, a specialized SQL query was implemented. This query classifies moves by type (1-to-1, 1-to-many, many-to-many, sale/purchase) and uses proportional splitting and label matching to accurately determine the counterpart account for each line. A post-processor is also included to handle uncategorized lines where 1-to-1 matching isn't possible, ensuring the report remains balanced and transparent. task-6092253
This update expands the data sent to Pricer, including price before taxes, tax names, supplier product codes, and units of measure. This allows for more accurate pricing calculations and supports key business scenarios when using the Pricer integration. The update also ensures Pricer tags are automatically updated when related product information changes.
Original PR description
We are currently missing some fields which must be sent to Pricer for some basic use-case scenarios This PR adds - Price before taxes - Taxes name (ex: 21%) - Supplier product code - Supplier reference - Units of measure of the product The PR also triggers the update of the pricer tags when the models indirectly related to Pricer are modified (taxes name / supplier reference / supplier product code) + cleans up the code a bit task-4506260 Forward-Port-Of: odoo/enterprise#93330 Forward-Port-Of: odoo/enterprise#78009
2 changes
New functionality added to Odoo
This update adds the ability to group analytic reports by product category. Previously, reports were limited to grouping by other fields. This enhancement provides more granular insights into spending by product type, improving financial analysis and reporting accuracy.
Original PR description
Add the related (non-stored) 'product_category' field on the account.analytic.line model to make it available in the Analytic Reporting "Group By" task-6219418
This update implements a new system for French businesses to electronically report transactions (B2C and international B2B) to tax authorities. It addresses a legal requirement for structured data reporting via ‘Flux 10’, enhancing compliance and data accuracy. Security enhancements, including 2FA and KYC, have also been added to protect sensitive financial information.
Original PR description
France’s electronic invoicing reform : The tax administration needs structured fiscal data for the transactions , either via E-invoicing for the nationals B2B or E-reporting for the international B2B…
France’s electronic invoicing reform : The tax administration needs structured fiscal data for the transactions , either via E-invoicing for the nationals B2B or E-reporting for the international B2B and the B2C. This creates two complementary obligations: - **E-invoicing** for domestic B2B transactions, where the invoice itself is exchanged through the PA/Peppol flow. - **E-reporting** for transactions outside that domestic B2B scope, mainly B2C and international B2B, where transaction and payment data must be reported to the tax administration through Flux 10 (period-based). ## Scope Domestic B2B remains handled by the existing e-invoicing flow, because the invoice exchange already carries the required structured information. Flux 10 is introduced for transactions that must be reported separately: - B2C transactions, where there is no buyer-side e-invoice exchange. - International B2B transactions, where the counterparty is outside the French domestic B2B mandate. - Payment reporting when VAT exigibility depends on collection. The reporting is period-based and keeps transaction reports separated from payment reports, because they answer different legal obligations and follow different timelines. ## Corrections and Lifecycle Flux 10 supports both: - **Initial reports**, for the first declaration of a period. - **Rectificative reports**, when already reported data must be corrected or completed. This distinction is needed so corrections remain traceable instead of silently mutating a report that may already have been transmitted. ## Security and Eligibility This PR also enforces stronger safeguards before using PDP/PA services. - **2FA is required** because PDP/PA actions expose regulated fiscal flows and should not be available from a simple password-only login. Email-based 2FA is available as a fallback when users have not configured an authenticator app. - **KYC is introduced** because a company must be identified and validated before Odoo can transmit documents or reports on its behalf through the PDP/PA infrastructure. Together, these changes make the French PDP/PA flow usable not only for invoice exchange, but also for the wider e-reporting obligations required by the French reform. Task-4603708