| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4055 |
| Technical Name |
l10n_co_dian_documento_soporte |
| 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 | 4055 |
| Technical Name |
l10n_co_dian_documento_soporte |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Colombia DIAN Documento Soporte
UBL 2.1 · CUDS · Nota de Ajuste · Non-Obligated Suppliers · BYOK
Issue the documento soporte en adquisiciones efectuadas a sujetos no obligados a expedir factura electrónica de venta — and its nota de ajuste — directly from Odoo vendor bills. Built on the shared e-Invoicing Core Engine and the Colombia DIAN Anexo Técnico (UBL 2.1). Compatible with Odoo 18 and 19.
When do you need it?
When you buy from a counterpart that is not obliged to issue an electronic sales invoice — a persona natural no obligada a facturar or a non-resident — the DIAN requires you, the buyer (adquirente), to issue a documento soporte to back the purchase for cost, deduction and VAT purposes. This module generates that document and its CUDS.
DIAN UBL 2.1 Generation
Documento soporte and nota de ajuste 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.
Operation codes 20 / 22 and document
type codes 05 / 95.
CUDS Fingerprint
The official SHA-384 CUDS (Código Único del Documento Soporte) computed over the exact DIAN field order — NumDS, FecDS, HorDS, ValDS, the IVA/INC/ICA tax triplets, ValTot, the adquirente NIT, the vendedor identifier, the ClaveTécnica/PIN and TipoAmbiente — so the document validates at the DIAN.
Role Inversion, Handled
On a documento soporte the roles invert: the UBL supplier party is your company (the obligated issuer) and the customer party is the non-obligated seller, tagged with the DIAN not-obliged concept (natural person or non-resident). The connector wires this automatically from the vendor bill.
BYOK Transport
Sandbox (habilitación) and production endpoints are pre-filled with the publicly documented DIAN hosts and remain fully editable. The API token, software-id, PIN, ClaveTécnica and certificate are bring-your-own-key: stored only in your database, used to build the CUDS and signatures locally, and sent only to the DIAN endpoint you configure.
Validation Before Submission
A documento-soporte rule set registered into the engine validation framework blocks submission of malformed documents: CUDS present, environment flag, adquirente NIT check digit, documento-soporte type and operation codes, the vendor identifier, the not-obliged concept and DIAN tax categories.
Reuses Your DIAN Setup
Builds on the Colombia DIAN Invoice connector: your company NIT, SoftwareID, PIN and ClaveTécnica are reused, so you only enter the separate documento-soporte numbering authorization. A guided onboarding wizard does it in one step.
Compatibility & Disclosure
Compatible with Odoo 18 and 19. This module transmits documento-soporte data only to the DIAN gateway (or the proveedor tecnológico) endpoint you configure. No data is sent anywhere else.
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