[19.0][MIG] l10n_it_edi_extension: Migration to 19.0#5083
Open
Borruso wants to merge 55 commits into
Open
Conversation
Borruso
force-pushed
the
19.0-mig-l10n_it_edi_extension
branch
from
0c18978 to
2077472
Compare
Member
|
/ocabot migration l10n_it_edi_extension |
Borruso
force-pushed
the
19.0-mig-l10n_it_edi_extension
branch
4 times, most recently
from
aaf6829 to
9ea8d34
Compare
Borruso
force-pushed
the
19.0-mig-l10n_it_edi_extension
branch
2 times, most recently
from
0a1dce5 to
2d708ee
Compare
Borruso
force-pushed
the
19.0-mig-l10n_it_edi_extension
branch
from
2d708ee to
d61776e
Compare
Contributor
Author
Borruso
force-pushed
the
19.0-mig-l10n_it_edi_extension
branch
from
a90c167 to
fc012e1
Compare
micheledic
approved these changes
Mar 16, 2026
Contributor
Contributor
Author
Contributor
|
Non sto testando funzionalmente, sto solo cercando di far sì che non si disallineino troppo le due versioni (dato che spesso non vengono aperte issue di tracciamento per modifiche alla 18) Credo comunque non sia ideale lasciare a stagionare in balcone tutte queste PR di migrazione alla 19, a sto punto meglio mergiarle (anche con un disclaimer che il focus per l'associazione Odoo Italia è sulla 18) in modo da cercare di portare avanti le modifiche su entrambe e avere anche un riscontro reale su cosa comporta per la community portare avanti due versioni contigue |
Contributor
Sono d'accordo, meglio iniziare a mergiarle |
micheledic
approved these changes
Mar 19, 2026
Borruso
force-pushed
the
19.0-mig-l10n_it_edi_extension
branch
5 times, most recently
from
cce433e to
92d481b
Compare
Borruso
force-pushed
the
19.0-mig-l10n_it_edi_extension
branch
5 times, most recently
from
acfad2d to
87dc8df
Compare
Also align its configuration in the README to what it actually does
…ttoEmittente to be moved to dedicated module
Currently translated at 100.0% (193 of 193 strings) Translation: l10n-italy-18.0/l10n-italy-18.0-l10n_it_edi_extension Translate-URL: https://translation.odoo-community.org/projects/l10n-italy-18-0/l10n-italy-18-0-l10n_it_edi_extension/it/
Currently translated at 100.0% (194 of 194 strings) Translation: l10n-italy-18.0/l10n-italy-18.0-l10n_it_edi_extension Translate-URL: https://translation.odoo-community.org/projects/l10n-italy-18-0/l10n-italy-18-0-l10n_it_edi_extension/it/
…eletion during import
Invalid content was found starting with element 'DatiOrdineAcquisto'. One of '{FatturaPrincipale}' is expected.
…raElettronica/FatturaElettronicaBody/DatiGenerali/DatiGeneraliDocumento/ImportoTotaleDocumento Odoo core commit 0b54f84 (Feb 17, 2026) — [FIX] l10n_it_edi: fix total in company currency — changed ImportoTotaleDocumento from using invoice currency amounts (base_amount_currency/tax_amount_currency) to company currency amounts (base_amount/tax_amount). This is correct per Italian tax law (art. 21, c. 2, lett. l, D.P.R. 633/72): since Divisa must be EUR for Italian-resident issuers, ImportoTotaleDocumento can also be expressed in EUR. For l10n_it_edi_extension, the USD invoice (1068.11 USD at rate 1.0789) now correctly reports 990.00 EUR as the total.
Co-authored-by: Simone Rubino <simone.rubino88@gmail.com>
…t support for XML invoices
When a zip is imported, the customer invoices must use sale taxes.
Core 18.0 took over partner and bank creation during FatturaPA import. Align the module to fill only the Italian extras core does not handle. * Partner update runs on each imported invoice. Core fills name, VAT, address and contact data; this module writes Provincia, EORI, Albo* and the firstname/lastname split via _l10n_it_edi_update_partner. The hook _l10n_it_edi_extension_core_partner_fields lists fields core writes so the override leaves them alone. * Drop the l10n_edi_it_create_partner flag. Core creates the partner itself, so the field, related setting, view and translations are dead code. * _l10n_it_edi_extension_create_partner follows the path core uses for buyer/seller: lookup by Codice Fiscale, delegate to _l10n_it_edi_import_partner, then fill the extras. Used for roles core skips (RappresentanteFiscale). * New _l10n_it_edi_extension_update_partner_bank fills bank_id and acc_holder_name on partner banks core created, reading BIC, IstitutoFinanziario and Beneficiario from DatiPagamento. _l10n_it_edi_extension_get_bank_partner mirrors core's partner selection (invoice partner on incoming, company partner on outgoing). The search filters by company so banks belonging to other companies cannot match. Tests adjusted: VAT arrives with the IT prefix from core, street arrives capitalized through string.capwords, and the obsolete test on the removed flag is gone.
Borruso
force-pushed
the
19.0-mig-l10n_it_edi_extension
branch
from
bcfea19 to
c86e32c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
15 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#4930