Daily updates from Odoo
Wednesday, June 24, 2026
12 changes
1 change
New functionality added to Odoo
This update enables automatic retrieval of vendor bills from the Hungarian tax authority (NAV) via API. A new 'Sync with NAV' button allows users to easily import bills, streamlining invoice processing and ensuring accurate record-keeping. This integration supports both automated API updates and direct XML uploads for Hungarian invoices.
Original PR description
In Hungary, we are already sending invoices to NAV(hungarian tax authority). Now this module `l10n_hu_edi_receive` provides functionality of receiving vendor bills through its API and also adds XML…
In Hungary, we are already sending invoices to NAV(hungarian tax authority). Now this module `l10n_hu_edi_receive` provides functionality of receiving vendor bills through its API and also adds XML importer for Hungarian localization. A button `Sync with NAV` is added in vendor bills list view, which opens a wizard where you can select time period and all bills uploaded between that time are fetched from NAV's API. Also directly uploading XML is also supported in the format NAV supports. Flow:- - After selection of time range, we call `queryInvoiceDigest` endpoint with that range and it returns a list of digests(consider each digest as separate invoice) but this digests contains only meta data not all details. - Now for each digest we call `queryInvoiceData` endpoint which returns xml response with `QueryInvoiceDataResponse` as root node. This xml contains some meta data and `InvoiceData` node which has a base64 string, when we decode that string we get an xml with `InvoiceData` as root node and this xml contains all details of the invoice, we parse both these details and create bills and refunds. Also xml importer supports any of the `InvoiceData` or `QueryInvoiceDataResponse` xml. NAV Documentation: https://onlineszamla.nav.gov.hu/files/container/download/2025.10.09.%20EN_Online%20Invoice%20System%203.0%20Interface%20Specification%20.pdf task-5237910 Forward-Port-Of: odoo/odoo#240919
1 change
New functionality added to Odoo
This update allows Odoo to automatically receive vendor bills from the Hungarian tax authority (NAV) via their API. Users can now sync bills from a specific time period or upload NAV XML files directly, streamlining invoice processing and ensuring accurate record-keeping in Hungary. This improves efficiency and compliance with Hungarian tax regulations.
Original PR description
In Hungary, we are already sending invoices to NAV(hungarian tax authority). Now this module `l10n_hu_edi_receive` provides functionality of receiving vendor bills through its API and also adds XML…
In Hungary, we are already sending invoices to NAV(hungarian tax authority). Now this module `l10n_hu_edi_receive` provides functionality of receiving vendor bills through its API and also adds XML importer for Hungarian localization. A button `Sync with NAV` is added in vendor bills list view, which opens a wizard where you can select time period and all bills uploaded between that time are fetched from NAV's API. Also directly uploading XML is also supported in the format NAV supports. Flow:- - After selection of time range, we call `queryInvoiceDigest` endpoint with that range and it returns a list of digests(consider each digest as separate invoice) but this digests contains only meta data not all details. - Now for each digest we call `queryInvoiceData` endpoint which returns xml response with `QueryInvoiceDataResponse` as root node. This xml contains some meta data and `InvoiceData` node which has a base64 string, when we decode that string we get an xml with `InvoiceData` as root node and this xml contains all details of the invoice, we parse both these details and create bills and refunds. Also xml importer supports any of the `InvoiceData` or `QueryInvoiceDataResponse` xml. NAV Documentation: https://onlineszamla.nav.gov.hu/files/container/download/2025.10.09.%20EN_Online%20Invoice%20System%203.0%20Interface%20Specification%20.pdf task-5237910 Forward-Port-Of: odoo/odoo#240919
3 changes
New functionality added to Odoo
This update introduces on-demand printing of kitchen order tickets directly from the kitchen station. When an order moves to a defined stage, the system automatically generates and prints a KOT. The tickets now include barcodes for efficient scanning and streamlined order processing.
Original PR description
*: pos_restaurant_preparation_display, pos_urban_piper In this commit: ------------------- - Introduced functionality to print KOTs on demand from the kitchen. - Added support for automatic printing when an order is moved to a configured stage. - Added barcodes to KOTs printed from the kitchen, allowing kitchen staff to scan them and directly move the order to the next stage. task: 6131467 Community PR: https://github.com/odoo/odoo/pull/266273
This update enables automatic receipt of vendor bills from the Hungarian tax authority (NAV) via their API. A new 'Sync with NAV' button allows users to schedule bill retrieval based on a date range, and supports both API integration and direct XML uploads for seamless invoice processing. This improves efficiency and accuracy for Hungarian businesses.
Original PR description
In Hungary, we are already sending invoices to NAV(hungarian tax authority). Now this module `l10n_hu_edi_receive` provides functionality of receiving vendor bills through its API and also adds XML…
In Hungary, we are already sending invoices to NAV(hungarian tax authority). Now this module `l10n_hu_edi_receive` provides functionality of receiving vendor bills through its API and also adds XML importer for Hungarian localization. A button `Sync with NAV` is added in vendor bills list view, which opens a wizard where you can select time period and all bills uploaded between that time are fetched from NAV's API. Also directly uploading XML is also supported in the format NAV supports. Flow:- - After selection of time range, we call `queryInvoiceDigest` endpoint with that range and it returns a list of digests(consider each digest as separate invoice) but this digests contains only meta data not all details. - Now for each digest we call `queryInvoiceData` endpoint which returns xml response with `QueryInvoiceDataResponse` as root node. This xml contains some meta data and `InvoiceData` node which has a base64 string, when we decode that string we get an xml with `InvoiceData` as root node and this xml contains all details of the invoice, we parse both these details and create bills and refunds. Also xml importer supports any of the `InvoiceData` or `QueryInvoiceDataResponse` xml. NAV Documentation: https://onlineszamla.nav.gov.hu/files/container/download/2025.10.09.%20EN_Online%20Invoice%20System%203.0%20Interface%20Specification%20.pdf task-5237910 Forward-Port-Of: odoo/odoo#240919
This update adds the ability to generate invoice PDF reports in multiple formats (Original, Duplicate, Triplicate) to comply with government regulations regarding GST documentation. Users can now print two or three copies of invoices with distinct titles, catering to different recipient types like transporters and suppliers. This ensures accurate record-keeping and adherence to tax requirements.
Original PR description
The Goverment specifies that invoice should be printed in different formats as per the different parties the invoice is been given to. Invoice should be marked as "Original" for receiver's copy. Invoice should be marked as "Duplicate" for transporter's (incase of goods supply) or supplier's copy. Invoice should be marked as "Triplicate" for supplier's (incase of goods supply) copy. This commit adds two new report actions, for Duplicate and Triplicate on invoice, visible in the Print section under the gear icon. When user prints Duplicate, 2 copies will be printed and for Triplicate, 3 copies will be printed at once, with different titles set on each copy of invoice. task-5899610 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#270813
1 change
New functionality added to Odoo
This update enables automatic receipt of vendor bills from Hungary's tax authority (NAV) via API. A new 'Sync with NAV' button allows users to schedule bill retrieval based on a time period, or directly upload NAV-compatible XML files, streamlining invoice processing.
Original PR description
In Hungary, we are already sending invoices to NAV(hungarian tax authority). Now this module `l10n_hu_edi_receive` provides functionality of receiving vendor bills through its API and also adds XML…
In Hungary, we are already sending invoices to NAV(hungarian tax authority). Now this module `l10n_hu_edi_receive` provides functionality of receiving vendor bills through its API and also adds XML importer for Hungarian localization. A button `Sync with NAV` is added in vendor bills list view, which opens a wizard where you can select time period and all bills uploaded between that time are fetched from NAV's API. Also directly uploading XML is also supported in the format NAV supports. Flow:- - After selection of time range, we call `queryInvoiceDigest` endpoint with that range and it returns a list of digests(consider each digest as separate invoice) but this digests contains only meta data not all details. - Now for each digest we call `queryInvoiceData` endpoint which returns xml response with `QueryInvoiceDataResponse` as root node. This xml contains some meta data and `InvoiceData` node which has a base64 string, when we decode that string we get an xml with `InvoiceData` as root node and this xml contains all details of the invoice, we parse both these details and create bills and refunds. Also xml importer supports any of the `InvoiceData` or `QueryInvoiceDataResponse` xml. NAV Documentation: https://onlineszamla.nav.gov.hu/files/container/download/2025.10.09.%20EN_Online%20Invoice%20System%203.0%20Interface%20Specification%20.pdf task-5237910 Forward-Port-Of: odoo/odoo#240919
1 change
New functionality added to Odoo
This update adds missing translations for various user-facing messages within the Odoo POS modules. This ensures that the POS system is correctly localized for users in different languages, improving the overall user experience and supporting international expansion. The changes cover UI elements, error messages, and internal Python messages.
Original PR description
pos* = All POS module In this commit: -------------------------------- Add missing translations for user-visible strings across POS modules. - Translated dialogs, errors, alerts, and other UI-visible messages - Updated Python-side UserError, ValidationError, and warning messages Task-5406947 Related PR-https://github.com/odoo/odoo/pull/239972 Forward-Port-Of: odoo/enterprise#102094
4 changes
New functionality added to Odoo
This update streamlines connections to remote SaaS databases by automatically authenticating users via OAuth SSO. Previously, users created in remote databases weren't automatically authenticated. Now, when a user connects, their identity is securely written to the remote database, enabling seamless and immediate access.
Original PR description
## [IMP] databases: SSO smooth connection and setup The aim of this commit is to allow databases_user to be directly connected to any remote SaaS database to which they have access. When they click…
## [IMP] databases: SSO smooth connection and setup
The aim of this commit is to allow databases_user to be directly connected to
any remote SaaS database to which they have access.
When they click the "connect" button, they will bypass the login screen and be
authenticated automatically.
To achieve this, when a user tries to connect to an accessible SaaS database, we
quickly write their `oauth_uid` to that remote database right before the
connection is initiated.
Before this commit:
A user that was created in the remote db using the create user feature from the
databases module wouldn't get automatically authenticated through the Odoo
OAuth SSO feature.
After this commit:
Users attempting to connect to a SaaS database will be directly connected if the
settings was activated.
task-id: 6071808
## TODO:
- [x] check if we always have oauth_uid for saas db
- [x] think about making the oauth module autoinstall (make a bridge module? or overkill?)
- We can avoid that and have everything work in place directly, avoiding an inheritance nightmare at installation time.
- [x] handle cases where it isn't there on both the remote db and the managing one
- [x] write some tests to ensure the code is free from traceback
- [x] add a feature allowing to:
- [x] add it to all server on which the user has access
- [x] add it to a specific server (may require the db list view on `res.users`
- [x] remove the previous and do everything when the user click on "connect"
- [x] would be better to put the code in a new module with auto install => people get auto-install + no "hacky" code.
- The "hacky" code is not so hacky and with that we can directly advertise the installation of `auth_oauth` in an action
- [x] add a config in the settings
Forward-Port-Of: odoo/enterprise#112369This update introduces a streamlined process for requesting and managing DMFA reports, allowing for corrections and consultations on employee payroll data. The system now automatically detects changes in payslips and triggers a consultation request, ensuring accurate reporting for tax compliance in Belgium. This improves data integrity and simplifies the reporting process.
Original PR description
- Introduce the ability to create a DMFA consultation and modification reports for all employees or a selected subset - Can be done independently or through a changes detection flow (warning if payslips changes detected -> send a consultation request -> sync data -> send mofication request) - Add NaturalPersonState model to store the latest changes for an employee coming from changes in payslips or consultations - Dynamic fetching of the latest DMFA XSD schema validator instead of being store in the codebase - Dashboard warning in case of payslips changing for a submitted report - Rename declaration_type to declaration_method for better naming of the new variable defining the different types of declarations - Sync DMPI files and Consultation files task-5404502
This update allows businesses to directly generate a BIR 2307 withholding tax certificate for individual vendor bills within Odoo. Previously, these certificates required manual creation. Additionally, the update reduces the number of blank rows in the 2307 report, ensuring the certificate fits on a single page for easier processing.
Original PR description
Add the ability to issue a BIR 2306/2307 withholding tax certificate for a single confirmed vendor bill directly from the bill. task-6219272
This update introduces the ability to track and manage employee mobility budget expenses directly within Odoo. It adds new features to record and categorize these expenses, providing better visibility into employee travel costs and supporting compliance. This enhancement improves financial reporting and simplifies expense management for HR teams.
Original PR description
task-6034871
1 change
New functionality added to Odoo
This update allows us to automatically receive vendor bills from Hungary's tax authority (NAV) via API. A new 'Sync with NAV' button lets you select a time period and fetch bills, or you can directly upload NAV-compatible XML files for import. This streamlines invoice processing and ensures accurate record-keeping.
Original PR description
In Hungary, we are already sending invoices to NAV(hungarian tax authority). Now this module `l10n_hu_edi_receive` provides functionality of receiving vendor bills through its API and also adds XML…
In Hungary, we are already sending invoices to NAV(hungarian tax authority). Now this module `l10n_hu_edi_receive` provides functionality of receiving vendor bills through its API and also adds XML importer for Hungarian localization. A button `Sync with NAV` is added in vendor bills list view, which opens a wizard where you can select time period and all bills uploaded between that time are fetched from NAV's API. Also directly uploading XML is also supported in the format NAV supports. Flow:- - After selection of time range, we call `queryInvoiceDigest` endpoint with that range and it returns a list of digests(consider each digest as separate invoice) but this digests contains only meta data not all details. - Now for each digest we call `queryInvoiceData` endpoint which returns xml response with `QueryInvoiceDataResponse` as root node. This xml contains some meta data and `InvoiceData` node which has a base64 string, when we decode that string we get an xml with `InvoiceData` as root node and this xml contains all details of the invoice, we parse both these details and create bills and refunds. Also xml importer supports any of the `InvoiceData` or `QueryInvoiceDataResponse` xml. NAV Documentation: https://onlineszamla.nav.gov.hu/files/container/download/2025.10.09.%20EN_Online%20Invoice%20System%203.0%20Interface%20Specification%20.pdf task-5237910