Colombia DIAN RADIAN - Título-Valor Events
Turn your electronic sales invoices into traceable, factorable negotiable instruments by registering every RADIAN event with the DIAN.
What is RADIAN?
RADIAN is the DIAN registry that gives legal certainty and full traceability to an electronic sales invoice (FEV) treated as a título valor (negotiable instrument), so it can circulate and be factored. Every relevant act over the invoice - acknowledgement, acceptance, registration, endorsement, guarantee, mandate, payment - must be lodged as an event identified by a fixed DIAN code (Anexo Técnico RADIAN, Resolución DIAN 000085 de 2022; Decreto 1154 de 2020). This module builds those events as UBL 2.1 ApplicationResponse documents and transmits them using your own DIAN credentials.
Complete event catalogue
The full set of RADIAN título-valor events is modelled, validated and serialised:
- 030 - Acuse de recibo de la FEV
- 032 - Recibo del bien o prestación del servicio
- 033 - Aceptación expresa / 034 - Aceptación tácita
- 036 - Reclamo (rechazo)
- 037/038/039 - Endoso en propiedad / garantía / procuración
- 040 - Cancelación del endoso
- 041/042 - Limitaciones a la circulación y su terminación
- 043/044 - Mandato y terminación del mandato
- 045 - Inscripción en RADIAN / primer endosatario
- 047 - Informe para el pago · 048 - Protesto
- 050 - Transferencia de derechos económicos · 052 - Aval
Built-in event state machine
The module enforces the DIAN ordering rules locally, before anything is sent, so you avoid avoidable rejections:
- 032 requires a prior 030.
- Acceptance / claim require a prior 032.
- Registration (045) requires acceptance (033/034).
- Endorsements, mandates, aval and payment require the invoice to be registered in RADIAN first.
- Terminations require their originating event.
- Endorsement / aval / transfer / mandate events require a counterparty (endosatario, avalista, mandatario, beneficiario).
Feature highlights
| Feature | Detail |
|---|---|
| UBL ApplicationResponse builder | Deterministic UBL 2.1 XML with the DIAN CustomizationID (event code), ProfileID/ProfileExecutionID, DocumentResponse, referenced invoice by CUFE, and sender/receiver parties. |
| CUDE computation | SHA-384 unique event code derived from the documented field concatenation (event id, dates, code, NITs, CUFE, software PIN/ID). |
| NIT verification digit | DIAN modulus-11 check-digit (DV) computed and validated on companies, partners and every event. |
| Business-rule validation | Layered error/warning rule set covering parties, CUFE, amounts, counterparties and event ordering. |
| BYOK DIAN transport | SOAP SendEventUpdateStatus client to the DIAN reception service (habilitación / producción), DIAN response parsing, signature- ready WS-Security and UBLExtensions slots. |
| Invoice integration | RADIAN status on customer invoices, one-click event wizard, event list per invoice, and a circulating/factored indicator. |
| Automation | Optional scheduled job that transmits signed events automatically. |
Bring-your-own-key boundary
This module is a format and event builder. It generates the UBL ApplicationResponse the DIAN expects and can transmit it using your own DIAN software credentials and certificate. The XAdES signature is produced by your signing component with your DIAN-issued certificate; the module emits an empty, signature-ready slot for it. We are not a certified provider and never impersonate one - your credentials stay in your database and your data is sent only to the DIAN endpoint you configure.
Compatibility
Odoo 18 and Odoo 19, Community and Enterprise. Built on the standard account module - no Enterprise-only dependencies.
Screenshots
Connections
Events
Update date: 2026-07-02