Colombia: DIAN validates the invoice before your customer ever sees it
In Colombia, per the guides read, an obliged seller issues a factura electrónica de venta as UBL 2.1 XML, signs it, and sends it to the tax authority (DIAN) for validation before delivering it to the buyer. Each invoice gets a CUFE, a 96-character identifier. Below: how it works as vendor guides report it, where the sources are silent, and a local check of a NIT’s check digit.
How it works (as vendor guides report it)
| Step | What happens |
|---|---|
| Issue | The seller builds the invoice as XML in the UBL 2.1 structure DIAN publishes in its technical annex and signs it with a digital certificate. |
| Validate first | The XML goes to DIAN before it goes to the buyer (“validación previa”). A 2019 Sovos note says this replaced a model where validation followed within 24 hours of generation. |
| Identify | A valid invoice carries a CUFE, a 96-character code that vendor guides say is calculated from the issuer’s NIT, the number, date and time, value, taxes and a technical key. The printed or PDF copy shows the full CUFE and a QR code that opens DIAN’s lookup. |
| Deliver | The seller sends the validated invoice to the buyer. The PDF is a representation of the XML. |
| Buy from a non-invoicer | Obliged invoicers buying from people not required to invoice generate an electronic “documento soporte” (Resolution 167 of 2021, as a law-firm note describes it), per transaction or accumulated weekly per supplier. |
Where it is unsettled: which taxpayers are obliged and from what date, the current technical annex (a search note named Resolution 000165 of 2023 and its amendments; not read), the validation time limit, and how the CUFE hash is computed (the excerpts did not say). Copies of Resolution 0001 of 2019, which first adopted the pre-validation rules, say a later resolution repealed it. The documento soporte start date was moved by Resolution 488 of 2022 and the present date was not read. These are vendor and law-firm summaries, not DIAN’s texts. No penalty is stated because none was read. A summary, not tax advice.
Check a NIT
Tests the shape (eight to ten digits, a hyphen and a check digit) and the check digit (“dígito de verificación”). It does not look anything up, so it cannot say whether the NIT is registered or belongs to the name on the invoice. A NIT typed without its check digit is not accepted; the page shows the digit it would need. The check digit cannot hide a single wrong digit unless the NIT’s own check digit is 1, because remainders 1 and 10 both give 1: about 19% of NITs end in 1, and across 2,000 sample numbers 1.9% of single-digit mistakes went unseen (3,015 of 162,000).
The sample is DIAN’s own NIT. The rule (mod 11, weights 3, 7, 13, 17, 19, 23, 29, 37, 41, 43, 47, 53, 59, 67, 71 from the right) reproduces four NITs I know, including DIAN’s and two large companies’; it was not read from DIAN’s specification.
What this checker does and does not cover
The main checker reads UBL, CII and Factur-X and applies EN 16931 and Peppol rules. Colombian invoices are UBL 2.1 but use DIAN’s own structure and extensions, so it does not apply DIAN’s validations, cannot compute or verify a CUFE or the signature, and has no DIAN catalogues. Treat the NIT test here as a typo catch only.
Test a file before you send it
For a European or Peppol invoice, open the checker, drop your XML and read the findings, each with a rule ID and a fix (the rule reference). No account, nothing uploaded. No invoice yet? The e-invoice creator turns a form into UBL or CII XML and checks it. Other countries: all side by side Mexico Brazil Chile Japan Spain.
Common questions
What is the validación previa?
As vendor guides report it, Colombian electronic sales invoices are sent to the tax authority, DIAN, for validation before they are delivered to the buyer, in the UBL 2.1 structure. The model was announced in 2019. Which taxpayers are obliged and on what dates is in DIAN’s resolutions, which were not read here; confirm with DIAN or your accountant.
What is a CUFE?
The CUFE is the unique 96-character code of an electronic sales invoice. A vendor guide says it is calculated from data such as the issuer’s NIT, the invoice number, date and time, value, taxes and a technical key. The invoice’s graphic copy shows it in full with a QR code that opens DIAN’s status lookup. The hash algorithm was not confirmed in the sources read.
What is the documento soporte?
An electronic supporting document that obliged invoicers generate and send for validation when they buy from sellers who are not required to invoice. A law-firm note describes it per transaction or accumulated weekly per supplier under Resolution 167 of 2021; a later resolution changed its start date, and the current rules were not read.
Can this checker validate a Colombian invoice?
No. It does not apply DIAN’s validations, the CUFE or the signature. It does test a NIT’s shape and check digit on this page, and a clean result is not an acceptance by DIAN.
Open the E-invoice Preflight checker to validate your own invoice file.
More countries
Australia Austria Belgium Brazil Bulgaria Croatia Cyprus Czech Republic Denmark Estonia Finland France Germany Greece Hungary Ireland Italy Latvia Lithuania Luxembourg Malta Netherlands Nigeria Norway Poland Portugal Romania Serbia Singapore Invoicenow Slovakia Slovenia Spain Switzerland Uk India Malaysia Saudi Arabia Sweden Turkey United Arab Emirates Peru Argentina Chile Uruguay Paraguay Ecuador Indonesia Vietnam