| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1570 |
| Technical Name |
l10n_co_dian_radian |
| 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) |
| Lines of code | 1570 |
| Technical Name |
l10n_co_dian_radian |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
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
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