Odoo model · Enterprise

l10n_cl.edi.reference

Cross Reference Docs for Chilean Electronic Invoicing. Defined in module l10n_cl_edi; exists in Odoo 19, 20. Across the upgrade steps we tracked: 0 fields added, 0 removed, 0 renamed.

Odoo 16 not covered
Odoo 17 not covered
Odoo 18 not present
Odoo 19 l10n_cl_edi
Odoo 20 l10n_cl_edi

This is an Enterprise model: Odoo 16 and 17 Enterprise sources are not part of the data, so those versions show as not covered.

Odoo 18 to 19

Community + Enterprise All changes in this step

New model in Odoo 19.

Odoo 19 to 20

Community + Enterprise All changes in this step

No change to this model's own fields in this step.

All fields declared on l10n_cl.edi.reference (8)

Fields this model declares itself in any version, with the versions they exist in. Inherited fields (mail.thread and other mixins) are on the parent model's page.

present not present not covered (Enterprise, Odoo 16 and 17)

Show all 8 fields

Field	Type	Label	Module
date	date	Document Date	l10n_cl_ediE
l10n_cl_reference_doc_internal_type	selection	Internal Type	l10n_cl_ediE
l10n_cl_reference_doc_type_id	many2one l10n_latam.document.type	SII Doc Type Selector	l10n_cl_ediE
move_id	many2one account.move	Originating Document	l10n_cl_ediE
origin_doc_number	char	Origin Document Number	l10n_cl_ediE
picking_id	many2one stock.picking	Originating Delivery	l10n_cl_edi_stockE
reason	char	Reason	l10n_cl_ediE
reference_doc_code	selection	SII Reference Code	l10n_cl_ediE

Related models

Linked by its relational fields: account.move l10n_latam.document.type stock.picking

Coverage. Odoo 16 to 17 and 17 to 18 compare Community modules only (the Enterprise 16 and 17 sources are not available to us). Odoo 18 to 19 and 19 to 20 include Community and Enterprise modules. Everything here comes from a static read of the Odoo source code: a field counts as removed only when no parent model, mixin or delegated model still provides it. Fields created dynamically at run time can be missed, and entries we could not confirm are marked as low confidence.

Planning an Odoo upgrade?

Odoo app Check your own database: Studio Upgrade Checker Scans your Studio fields, views, automations and custom code for everything listed here before you upgrade. See it on the Odoo Apps store Odoo app Fix broken views: Studio View Repair Assistant Finds views that stopped loading after an upgrade and helps you repair the xpaths and fields they point at. See it on the Odoo Apps store Upgrade service Need the upgrade done? Book a call We move databases between major Odoo versions, port custom modules and validate the data. Book a call Free Free upgrade scan, we run it for you Send us a copy of your database or give us access and we report what will break on the target version. Ask for a scan