DIAN electronic invoice
Colombia’s UBL-based electronic sales invoice with prior DIAN validation, CUFE/CUDE identifiers and application-response events.
Current version and implementation status
How to recognize the profile
Do not rely on the file extension alone. Inspect the root namespace, customization/profile identifiers, version values and authority-specific envelope.
- CUFE
- DIAN UBL extensions
- ApplicationResponse events
Production validation stack
- 1UBL schema
Confirm that the document is well formed and structurally compatible with the intended DIAN UBL syntax.
- 2DIAN technical annex
Apply semantic and business-rule checks rather than accepting a file merely because it parses.
- 3Digital signature
Validate currencies, countries, tax categories, units, payment means and other controlled values against the correct release.
- 4CUFE/CUDE calculation
Apply the national, network or authority restrictions that narrow the base syntax.
- 5Prior validation response
Apply the current official validation artefact and retain an auditable result.
Common errors and corrective action
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Countries using or referencing this profile
Questions people ask
What is DIAN UBL?
Colombia’s UBL-based electronic sales invoice with prior DIAN validation, CUFE/CUDE identifiers and application-response events.
How is DIAN UBL validated?
A production check normally applies UBL schema, DIAN technical annex, Digital signature, CUFE/CUDE calculation, Prior validation response. Local browser preflight cannot replace the official validation artefacts or authority outcome.
Which version should I use?
The current research note is: Technical annex 1.9; verify later resolutions and annex updates. Confirm release notes at the official source before production deployment.
Inspect and prepare DIAN UBL files
Tax identifier checker
Check the structure of VAT, GST and national business identifiers.
Signature metadata inspector
Locate XML signature, certificate and digest metadata without claiming cryptographic validity.
Invoice reference and UUID checker
Check the structure and, where implemented, checksum of common fiscal invoice references such as UUID, IRN, CUFE and access keys.
Authority and network response decoder
Extract status, identifiers, error codes and messages from common JSON or XML invoice responses.