Colombia DIAN Electronic Invoicing
DIAN UBL 2.1 · CUFE/CUDE · NIT check digit · QR · BYOK
Issue DIAN-compliant electronic invoices and credit notes for Colombia directly from Odoo. Built on the shared e-Invoicing Core Engine and the DIAN Anexo Técnico de Factura Electrónica (UBL 2.1). Compatible with Odoo 18 and 19.
DIAN UBL 2.1 Generation
Factura Electrónica de Venta and Nota Crédito as OASIS UBL 2.1,
with the full DianExtensions block: InvoiceControl
(authorization number + range), InvoiceSource, SoftwareProvider,
SoftwareSecurityCode and AuthorizationProvider, plus the
ProfileExecutionID production / habilitación flag.
CUFE / CUDE Fingerprint
The official SHA-384 CUFE (and CUDE for notes) computed over the exact DIAN field order — NumFac, FecFac, HorFac, ValFac, the IVA/INC/ICA tax triplets, ValTot, NIT, NumAdq, ClaveTécnica/PIN and TipoAmbiente — so the document validates at the DIAN.
NIT Check Digit
Real DIAN mod-11 dígito de verificación algorithm for the company and every partner, with the prime-weight series from the technical annex. Malformed NITs are caught before submission.
DIAN QR Code
Verification-URL QR resolving to the público catálogo VPFE, plus a PNG for the printed representación gráfica. Habilitación and production catalogues are handled automatically.
BYOK Transport
Sandbox (habilitación) and production endpoints come pre-filled with the public DIAN hosts and stay fully editable — point them at a proveedor tecnológico if you use one. Your token, software-id, PIN, technical key and certificate are bring-your-own-key: stored only in your database, never bundled.
Validation & Onboarding
A DIAN rule set (CUFE present, environment flag, NIT check digit, document type, tax categories) registered into the engine validation framework, and a guided onboarding wizard that verifies the NIT and wires the software credentials and transport in one step.
On the Invoice
Generate, Submit and Open-document buttons on the customer
invoice route through the engine einvoice.document
lifecycle. The CUFE, QR, UBL XML and DIAN status are mirrored on
the invoice for instant visibility.
Disclosure: this module transmits invoice data only to the DIAN gateway (or the proveedor tecnológico) endpoint you configure. Your certificate, software-id, PIN and technical key are bring-your-own-key, used to build the CUFE and signatures locally. No data is sent anywhere else.
Screenshots
Dian Customer Invoice Cufe S
Dian E Invoice Document Ubl
Update date: 2026-07-02