El Salvador DTE for Odoo
Ministerio de Hacienda electronic invoicing — build, sign and clear all eleven DTE JSON document types directly from Odoo.
What It Does
This module makes Odoo compliant with El Salvador's Documento Tributario Electronico (DTE) regime, the JSON pre-clearance model operated by the Ministerio de Hacienda (MH). From each customer invoice or credit note it builds the canonical DTE JSON, validates it against the MH business rules, signs it through your local firmador, and submits it to the MH recepciondte web service to obtain the sello de recepcion clearance stamp — all on top of the shared e-Invoice Core Engine.
All Eleven DTE Document Types
- 01 — Factura (consumidor final)
- 03 — Comprobante de Credito Fiscal
- 04 — Nota de Remision
- 05 — Nota de Credito
- 06 — Nota de Debito
- 07 — Comprobante de Retencion
- 08 — Comprobante de Liquidacion
- 09 — Documento Contable de Liquidacion
- 11 — Factura de Exportacion
- 14 — Factura de Sujeto Excluido
- 15 — Comprobante de Donacion
Key Features
Canonical DTE JSON
Deterministic JSON with the correct schema version per document type, the official numeroControl (DTE-NN-XXXXXXXX-{15 digits}) and uppercase codigoGeneracion UUID, reusing the engine's decimal policy.
Firmador Signing & MH Clearance
Sign locally through the MH firmador, authenticate against the MH portal and submit to recepciondte, capturing the selloRecibido. Invalidation (anulacion) supported.
Real NIT / NRC / DUI Validation
14-digit NIT, NRC and the 9-digit DUI with its genuine mod-10 check digit, enforced on company, partners and the document rule set.
MH Business-Rule Validation
numeroControl / codigoGeneracion format, receptor identity per document type, 13% IVA coherence, total reconciliation and the related-document requirement for adjustment notes.
Consultation QR
Each DTE carries the Ministerio de Hacienda public-consultation URL as a QR for buyer verification.
BYOK Transport & Onboarding Wizard
Sandbox / production MH endpoints pre-filled with the official hosts (always editable). Credentials are never bundled; a guided wizard captures issuer identity and transport in one step.
Requirements
- Odoo 18.0 or 19.0 (Community or Enterprise).
- The e-Invoice Core Engine module (shared foundation).
- A registered MH DTE issuer account and a local firmador with your signing certificate.
- Python libraries: lxml, qrcode, requests, cryptography (standard with most Odoo deployments).
Screenshots
Posted Dte Customer Invoice
Generated Dte Document Mh Js
Update date: 2026-07-02
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3301 |
| Technical Name |
l10n_sv_mh_dte_einvoice |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
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