| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3329 |
| Technical Name |
l10n_cl_sii_dte_einvoice |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3329 |
| Technical Name |
l10n_cl_sii_dte_einvoice |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Chile SII DTE e-Invoicing
Native SII DTE XML v2.5 — CAF folios, TED stamp, RUT validation, EnvioDTE upload. Certificate and folios are bring-your-own-key.
Issue Chilean Documentos Tributarios Electronicos (DTE) straight from Odoo, following the SII Formato Documentos Tributarios Electronicos 2026-02, version 2.5. The clearance gate never blocks you: your digital certificate, CAF folios and SII session token are all BYOK material you control. Works with Odoo 18 & 19.
Native DTE XML v2.5
Generates the SII DTE schema (not UBL): Encabezado with IdDoc, Emisor, Receptor and Totales; Detalle lines; Referencia blocks. IVA at the Chilean 19% general rate, with automatic affected / exempt resolution.
Document types
33 factura afecta, 34 factura exenta, 39 boleta, 52 guia de despacho, 56 nota de debito and 61 nota de credito — with the mandatory reference to the original document on notas.
CAF folio management
Upload the CAF XML granted by the SII; the module parses the authorised folio range and the embedded RSA key, then allocates folios sequentially with exhaustion guards so you never reuse a number the SII would reject.
TED timbre stamp
Builds the canonical <DD> block in the SII child order and signs it with the CAF private key using SHA1withRSA, producing the <FRMT> stamp and the PDF417 timbre payload for the printed cedible.
RUT validation
Real Modulo 11 check-digit validation for company (Emisor) and partners (Receptor), with normalisation and the dotted display format.
SII upload & status
EnvioDTE upload over a BYOK transport: certification (maullin) and production (palena) hosts pre-filled as editable defaults, Track ID capture, Estado de Envio polling and full transport logging.
Built on a shared engine
Reuses the e-invoice core engine's transport, XML signer, QR engine, validation framework and the einvoice.document / einvoice.profile models — registering a Chile (cl_sii_dte) profile rather than duplicating functionality. An onboarding wizard, configuration model and Generate / Send / Check-status buttons on the customer invoice complete the workflow.
Disclosure: this module transmits signed EnvioDTE envelopes to the SII host you configure (or the documented defaults). Certificates, CAF private keys and the SII session token are stored only on your database and never sent anywhere except, for the token and envelope, to the SII endpoint you select.
Compliance model & licensing
We deliver the software. This connector runs entirely under your own SII digital certificate, your CAF folio files (with their embedded RSA keys) and your SII session token — all bring-your-own-key (BYOK) material that stays in your Odoo database and is sent only to the SII host you configure.
We are not a PAC, an OMA, or an integrator acting on your behalf. The fiscal relationship is strictly between you (the contribuyente) and the Servicio de Impuestos Internos (SII); we issue no DTE for you and hold none of your credentials. You remain the registered emisor electronico.
Support is included, and the purchase is refundable per the Odoo Apps Store policy. (Modelo de cumplimiento: entregamos el software; usted opera con su propio certificado, CAF y token — la relacion fiscal es entre el contribuyente y el SII.)
Screenshots
Factura Electronica Dte 33 G
Nota De Credito Electronica
Generated Dte Xml Document E
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module