Monday, August 15, 2022
2 changes · master
Miscellaneous changes
Steps to reproduce: 1- Install mexican localization 2- create an invoice with a registered payment with a CFDI document 3- click on `Force CFDI` 4- now there are 2 CFDI documents for the same payment, this can cause issues in customer's accounting Bug: the domain set on `Force CFDI` invisible attribute doesn't consider if there are already generated edi documents Fix: Edit the domain OPW-2883626 Forward-Port-Of: odoo/enterprise#29695
Original PR description
Steps to reproduce: 1- Install mexican localization 2- create an invoice with a registered payment with a CFDI document 3- click on `Force CFDI` 4- now there are 2 CFDI documents for the same payment, this can cause issues in customer's accounting Bug: the domain set on `Force CFDI` invisible attribute doesn't consider if there are already generated edi documents Fix: Edit the domain OPW-2883626 Forward-Port-Of: odoo/enterprise#29695
Utilise diffrerent uknown country codes depending on the country for which the report is being generated. ---- European geonomenclature provides a series of country codes. These generally follow the ISO standard for the two-letter coutry codes for existing countries. There are also other more sybolic codes, among which are the uknown country codes. https://ec.europa.eu/eurostat/en/web/products-manuals-and-guidelines/-/ks-gq-20-010 (see page 27 in the pdf) As specified in the EU geonom
Original PR description
Utilise diffrerent uknown country codes depending on the country for which the report is being generated. ---- European geonomenclature provides a series of country codes. These generally follow the…
Utilise diffrerent uknown country codes depending on the country for which the report is being generated. ---- European geonomenclature provides a series of country codes. These generally follow the ISO standard for the two-letter coutry codes for existing countries. There are also other more sybolic codes, among which are the uknown country codes. https://ec.europa.eu/eurostat/en/web/products-manuals-and-guidelines/-/ks-gq-20-010 (see page 27 in the pdf) As specified in the EU geonomenclature (linked above), the unknown country code is to be: QU - Countries and territories not specified QV - Countries and territories not specified within the framework of intra-EU trade The issue is that, depending on the authority, the system accepts one of these, or the other. In Belgium, for instace, QU is the expected value and QV is rejected, resulting in an error (see screenshots below, from the onegate Belgian intrastat system)   In the Netherlands QV is expected, and QU will be rejected, resulting in an error (see screenshot in PR https://github.com/odoo/enterprise/pull/29227 , from the Dutch intrastat system). Thus the solution is to utilise a dictionary with the company's country code as the key, and the unknown country code as the value ticket-id: 2922206 Forward-Port-Of: odoo/enterprise#30432 Forward-Port-Of: odoo/enterprise#30072