Wednesday, March 18, 2026
3 changes · saas-19.2
New functionality added to Odoo
This update introduces a new report for Polish businesses that still need to generate JPK_FA XML reports even when using the KSeF online invoicing platform. This report ensures compliance with Polish tax regulations by listing outstanding invoices and lines that haven't been validated by KSeF, aligning with JPK-FA(4) norms.
Original PR description
In Poland, if a business chooses to keep B2C invoicing outside of KSeF (online platform), the JPK_FA obligation remains. It is a XML report that lists all the invoices and the invoice lines that have not been validated by KSeF during a desired period of time. The report follows the JPK-FA(4) norms. task-5166047 Forward-Port-Of: odoo/enterprise#103000
This update adds the capability to generate UBL (Universal Business Language) receipts from Point of Sale (PoS) orders. This allows businesses to meet specific tax and regulatory requirements by creating compliant electronic invoices. The changes also improve PoS testing and remove outdated documentation.
Original PR description
task: 4038651 Forward-Port-Of: odoo/odoo#248279 Forward-Port-Of: odoo/odoo#209578
This update enables direct electronic invoicing for POS sales and returns in Colombia, streamlining the process for businesses. It avoids creating intermediate invoices and leverages existing UBL generation, improving efficiency and reducing manual steps. This change is crucial for compliance with Colombian tax regulations.
Original PR description
In Colombia, all POS Sales/Returns must be supported by an Electronic Document. Currently, the only way to connect the DIAN EDI and POS flows is to manage invoices directly in the Accounting App.…
In Colombia, all POS Sales/Returns must be supported by an Electronic Document. Currently, the only way to connect the DIAN EDI and POS flows is to manage invoices directly in the Accounting App. This pr adds the possibility to generate and send the electronic documents directly to DIAN without leaving the POS store. This pr will not create intermediate invoices/credit notes that are supposed to be sent to DIAN, instead we adapted the already existing ubl-generation implementation (in `l10n_co_dian`) to be able to generate the correct files using data from `pos.order` models (implementation can be found in `models/account_edi_xml_ubl_dian.py`). During this process we created some 'common' functions that generate data for the ubl file independent of what model is used (`account.move` or `pos.order`), these common functions are a first step for the future refactoring of the ubl models. An important thing to note here is that the common functions are only used for the pos orders, generating documents for invoices is still done using the original implementation. Another important feature of this implementation is the possibility to share a single sequence, defined on the journal, between pos orders and account moves. This was implemented because in Colombia (and other latam countries) the sequence gets assigned to a company by the government, and can therefore be expensive. Important to note is that sharing a sequence is only possible if the company has never sent documents to DIAN before (~ no existing edi documents). task-4038651 Forward-Port-Of: odoo/enterprise#107170 Forward-Port-Of: odoo/enterprise#78742