Electronic invoice in Colombia

Understand Colombia’s mandatory DIAN clearance model, UBL 2.1 requirements, prior validation process and accredited provider framework.

Select a country

Overview

Colombia has a mature mandatory e-invoicing system built around DIAN — the Dirección de Impuestos y Aduanas Nacionales, the national tax and customs authority. It is a centralised clearance model with prior validation: the structured document goes to DIAN, receives a validation result, and only then counts as properly issued and is passed to the buyer.

Two features set Colombia apart from its neighbours. The XML is UBL 2.1 — familiar syntax to any European provider, though the semantics are entirely DIAN's own. And the country operates a formal national accreditation for service providers, the Proveedor Tecnológico, with capital, asset and certification thresholds that effectively require a Colombian legal presence.

UBL 2.1 + FEV 1.9

OASIS syntax with the DIAN customisation — familiar shape, local meaning

CUFE

the unique invoice code computed on every document before submission

5-year licence

the term of a Proveedor Tecnológico habilitación, renewable on application

Timeline

The invoice mandate is finished. What ran through 2024 was the extension of electronic form to the other documents — POS receipts, tickets, utility bills and the rest.

Already in force

15 June — 1 November 2020

The mass rollout

Resolución DIAN 000042/2020 set the calendar. Registration and transition ran group by group by economic activity; by 1 November 2020 every person in scope had to be invoicing electronically. Public bodies that issue invoices themselves had until 1 December 2020.

1 April 2021

Central government must receive through SIIF Nación

Entities within the Presupuesto General de la Nación began mandatory reception and processing of invoices through the state financial system. See B2G and SIIF Nación.

1 August 2022

Electronic documento soporte

The support document a Colombian buyer raises for purchases from suppliers not obliged to issue an invoice became mandatory in electronic form.

1 May 2024

Anexo Técnico FEV 1.9

Version 1.9 of the technical annex became mandatory. It remains the current version.

May — November 2024

Electronic POS and the equivalent documents

Electronic POS receipts by taxpayer category — 1 May for grandes contribuyentes, 1 June for other income-tax payers, 1 July for everyone else — with the remaining equivalent documents following through to 1 November 2024.

23 September 2025

Resolución 000227 consolidates the rules

DIAN unified roughly seventy earlier resolutions into a single instrument organised by title. The FEV technical annex now sits under Title 5 with the code T5.1 — the practical effect is that you cite one resolution rather than a stack.

The obligation is not defined by transaction type. It attaches to the seller's status as a person obliged to issue a factura de venta. Such a seller must document every relevant sale of goods or supply of services electronically — whether the buyer is a company, a public body or a private consumer.

The clearance model

Colombia is a centralised clearance model with prior validation by the tax authority. It is not Peppol four-corner and — despite the superficial resemblance of having the state as an extra party — it is not a Peppol five-corner model either: documents go to DIAN's central system over a national protocol.

The process

01 The seller builds the structured XML and signs it digitally

02 The unique invoice code CUFE — Código Único de Factura Electrónica is computed

03 The XML is transmitted to DIAN — directly, through DIAN's free solution, or through an accredited Proveedor Tecnológico

04 DIAN checks it against the tax and technical rules

05 DIAN returns either Documento validado por la DIAN or Documento rechazado por la DIAN

06 Once validated, the invoice and the validation document go to the buyer

Legally, the electronic invoice is treated as issued when at least two conditions are met: it has been validated and it has been delivered to the buyer. Neither alone is enough.

Real-time control, and no duplicate reporting

Every document is transmitted individually, before the invoice is given to the buyer, and DIAN checks it as part of issuing. That is transaction-level continuous control — which is precisely why no separate periodic VAT report duplicating the same data is required. The clearance transmission is the reporting.

When the system is down

If DIAN's system fails, the invoice may be delivered to the buyer without a prior validation response, and the documents must be submitted once service is restored. For certain failure scenarios on the seller's side, information about documents temporarily issued on paper must be transmitted within 48 hours of the fault being cleared. Outside these official contingency scenarios, an unvalidated invoice is not properly issued and should not be relied on as tax evidence.

B2G and SIIF Nación

There is no separate Peppol platform and no separate invoice format for the public sector. Public bodies use the same DIAN FEV. What is added is a state reception and budgeting workflow.

For entities inside the Presupuesto General de la Nación, mandatory reception and processing through the financial system SIIF Nación has applied since 1 April 2021. The supplier first obtains DIAN validation and then routes the invoice into the prescribed SIIF channel. SIIF Nación is an additional government workflow for reception and budget accounting — not a replacement for DIAN clearance.

What a public buyer adds

—Correct identification of the contracting authority

—Budget and contract references

—The prescribed SIIF Nación address or workflow

—Downstream processing in the public financial management system

B2C and equivalent documents

Sales to consumers are inside the system too. The seller may use the ordinary Factura Electrónica de Venta (FEV) or one of the permitted Documentos Equivalentes Electrónicos (DEE) — the electronic POS receipt, a ticket, a utility bill and so on. A narrow exception survives: certain non-commercial, rural or community water, sewerage and waste providers with fewer than 2,500 subscribers may still issue the utility equivalent document physically.

A data-protection rule worth building in

If a consumer asks for a FEV or an electronic POS document in their own name, the seller may request only a limited set of data: name, identifier type and number, and an email address if the buyer wants the document by email. DIAN has expressly prohibited demanding unnecessary extras such as address, telephone number or a copy of the RUT. Where the consumer does not ask for a personalised document, the rules for the relevant B2C document apply without collecting excess personal data.

For a checkout integration this is a design constraint, not a nicety — a POS flow that insists on an address to print a receipt is not compliant.

Formats and PDF

The mandatory syntax is OASIS UBL 2.1 XML with the DIAN customisation, governed by the Anexo Técnico de Factura Electrónica de Venta version 1.9, with a separate Anexo Técnico DEE 1.0 for the equivalent documents. UN/CEFACT CII is not an accepted standalone DIAN syntax.

UBL 2.1 does not mean EN 16931. UBL is an XML syntax; EN 16931 is a European semantic model. DIAN applies its own semantics, catalogues, tax fields, codes, signatures and validation rules, and the Colombian system has never been declared a national implementation of the European standard. Peppol BIS Billing 3.0 or standard EN 16931 UBL cannot be sent to DIAN without conversion into the Colombian profile — which is the trap the familiar syntax sets.

Where the PDF sits

A standalone PDF is not an electronic invoice with tax legal force. The legal instrument is the XML; the PDF is a representación gráfica — a human-readable rendering of the XML data. For an electronic buyer the delivered package normally comprises the invoice XML, the DIAN validation response, and the graphical representation. A buyer who is not an electronic invoicer may receive the graphical representation by email or another agreed route.

Language and currency

The legal XML is produced in Spanish with amounts in Colombian pesos. Another currency and another language may be added. In the graphical representation it is permitted to show either the foreign language and currency alone, or Spanish and COP alongside the foreign language and currency. This matters most on export invoices, where the temptation to produce an English-only document is strongest.

Identifiers

The organisation identifier in the DIAN system is the NIT — Número de Identificación Tributaria, registered in the RUT — Registro Único Tributario. Colombia has not established a mandatory Peppol EAS code for domestic invoicing, and the NIT in the Colombian XML should not be treated as a national Peppol electronic address scheme.

A foreign buyer is not required to hold a Colombian NIT. DIAN provides identification types for foreign individuals and legal entities, and those are what an export invoice carries.

Peppol in Colombia

Peppol is not a mandatory or official channel of the Colombian system. Compliance in B2G, B2B or B2C is not achieved by sending a Peppol BIS invoice through an ordinary Peppol Access Point — DIAN-compatible XML and a DIAN validation response are required.

Colombia does not appear in the OpenPeppol list of Peppol Authorities, and DIAN is not one

DIAN does not administer a national Peppol SMP or SML profile

National compliance has no connection to the OpenPeppol Service Provider Agreement

Parties may of course use Peppol voluntarily for international commercial exchange, with an acceptable international identifier. Such a document does not replace the DIAN FEV, does not remove the prior validation requirement, and will normally need conversion between Peppol BIS and DIAN UBL.

Export and import

Exporting from Colombia

There is no separate export mandate or future calendar: if the Colombian seller is obliged to invoice electronically, the export sale is documented on the same DIAN FEV. The seller creates the FEV, submits it for validation, and passes the XML or the graphical representation to the foreign buyer. For commercial convenience the seller may additionally produce an English-language PDF, a Peppol BIS invoice or another EDI document — none of which replaces the legal DIAN XML.

Buying from foreign suppliers

A foreign supplier without Colombian residence and without an obligation to invoice locally does not normally connect to DIAN clearance. Instead the Colombian buyer generates an electronic documento soporte en adquisiciones efectuadas a sujetos no obligados a expedir factura de venta and submits it to DIAN for validation — mandatory in electronic form since 1 August 2022. The foreign commercial invoice on its own is not always sufficient tax evidence.

Importing goods

For an ordinary import of goods the documento soporte does not replace customs documentation. The principal evidence of the transaction, the cost and the import VAT is a properly filed declaración de importación, unless special free-zone rules apply.

ViDA — when it can actually reach a Colombian group

A sale from Bogotá to Madrid is an export from Colombia and an import into the EU; ViDA does not apply. But a sale by the Spanish VAT registration of a Colombian group to a buyer in France is potentially an intra-EU transaction and may fall under the ViDA digital reporting requirements from 1 July 2030. The trigger is an EU VAT registration or establishment — not the fact of exporting to Europe.

Proveedor Tecnológico

Colombia is one of the few countries covered on this site with a genuine national accreditation for e-invoicing service providers. A foreign Peppol Access Point does not acquire the right to serve Colombian clients in that role by virtue of OpenPeppol certification or accreditation in another country.

Two routes in

01 Obtain DIAN habilitación as a Proveedor Tecnológico by meeting the national requirements

02 Supply software to the Colombian client as technology, with the client itself registering as a direct facturador electrónico and carrying the responsibility to DIAN — a structure that must be delimited carefully against actually performing the regulated provider services

What habilitación requires

—Incorporation as a company in Colombia, or a branch of a foreign company, registered in the RUT with the relevant e-invoicing services in its objects

—Accounting capital of at least 20,000 UVT

—Fixed assets of at least 10,000 UVT located in Colombia

—ISO 27001 certification covering the relevant processes and services — if not held at application, an undertaking to provide it within 18 months of habilitación is accepted

—A business continuity and disaster recovery plan, and documented physical, technological and security infrastructure

—Internal and external process architecture, incident classification and SLAs, and a PQRSF channel for petitions, complaints, claims, suggestions and compliments

—Staff with knowledge of accounting, the legislation, UBL, XML and XSD

—Disclosure of directors, board members, owners, controlling persons and key employees

—Successful completion of the DIAN test set, and acceptance of DIAN inspections verifying that the company, its assets and its infrastructure actually exist

The process includes a site visit by a specialised DIAN team before the resolution is issued. DIAN has two months from receipt of a complete application to decide. The authorisation is personal and non-transferable, runs for five years, and renewal must be applied for at least three months before expiry.

The asset requirement is the decisive one. Fixed assets of 10,000 UVT located in Colombia effectively rules out a purely remote entry from Europe. It does not necessarily mean all infrastructure and data must be hosted in Colombia — but the applicant must document a local property, physical and technological base. No national official mailbox of the Slovak e-schránka type is required.

Archiving

What has to be kept in Colombia is not one file but a set, and this is where implementations most often fall short.

The signed invoice XML — the legal original

The DIAN validation response — without it the invoice is not properly issued

The electronic events on credit transactions — acknowledgement of receipt of the invoice and of the goods or services

The graphical representation, where it was the version actually delivered to a non-electronic buyer

Retention follows the general Colombian tax and commercial rules rather than a single e-invoicing figure, and the period can extend where a return remains open to review. The safe operating rule is to keep the whole set for as long as DIAN can still examine the period concerned, and to confirm the exact term for the taxes involved with a Colombian adviser. What is not safe is archiving only the PDF.

Penalties

Not issuingUnder Article 657 of the Estatuto Tributario, DIAN may close the business premises for three days. In cases the law provides for, closure can be replaced by a monetary sanction calculated on the operating income of the preceding period

Missing mandatory fieldsArticle 652 provides for 1% of the value of the transactions documented by invoices lacking certain mandatory particulars, capped at 950 UVT

Not transmitting to DIANWhere no specific sanction applies, failures in transmitting electronic documents may be assessed under Article 651, which covers failure to supply information, late supply and supply with errors

Not every technical deviation attracts the same sanction: it has to be established whether the error concerns a mandatory particular, a DIAN validation rule, or an additional optional field.

Sanctions on the provider

A Proveedor Tecnológico carries its own escalating exposure for repeated breaches:

—A one-year ban on contracting with new clients

—On the next repetition, a two-year ban

—On a third recurrence, cancellation of the habilitación

—In defined cases, closure of activity for up to 30 calendar days and/or a fine of up to 1% of the value of the affected invoices

After cancellation the provider is removed from the DIAN register, and its clients must change their registered mode of operation or move to another authorised provider. For anyone evaluating a Colombian partner, the register is therefore not a one-time check — it is a monitoring obligation.

VAT deduction

For an ordinary domestic purchase from a supplier obliged to issue a FEV, the correct validated electronic invoice is the principal evidence. On credit or deferred-payment transactions the buyer must additionally send the prescribed electronic events — acknowledgement of receipt of the invoice, and acknowledgement of receipt of the goods or services. Those events can be necessary for the invoice to serve as proper support for costs, deductions and input VAT.

But the legislation recognises other documents too: compliant Documentos Equivalentes Electrónicos, the electronic documento soporte for purchases from persons not obliged to invoice, the import declaration for goods, and documents specific to particular sectors and operations.

For a purchase from a Colombian supplier inside the FEV regime, the validated electronic invoice is normally mandatory tax evidence. It is not, however, the only possible document across every transaction and every VAT deduction scenario.

How we help

The UBL 2.1 syntax makes Colombia look closer to Europe than it is. What the work actually involves:

Conversion between Peppol BIS or EN 16931 UBL and the DIAN profile — semantics, catalogues and tax fields, not just syntax

Anexo Técnico FEV 1.9 and DEE 1.0, with CUFE computation and digital signature

Handling of the DIAN validation response, rejections and the contingency rules

The electronic events required on credit transactions

Bilingual and dual-currency graphical representations for export invoices

The European format the EU counterparty needs on the other side of the trade

Connection by API, SFTP and CSV, with ERP and IDoc source data

Frequently asked questions

Is e-invoicing mandatory in Colombia?

Yes, and the rollout finished on 1 November 2020. The obligation attaches to the seller's status as a person required to issue a factura de venta, not to the type of counterparty — so it covers B2B, B2G, B2C and exports alike. Consumer sales may instead use one of the permitted electronic equivalent documents, whose own transition ran through to 1 November 2024.

Colombia uses UBL 2.1 — does that mean my EN 16931 invoice works?

No, and this is the most expensive misreading of the Colombian system. UBL 2.1 is a syntax; EN 16931 is a semantic model. DIAN applies its own semantics, catalogues, tax fields, codes, signatures and validation rules under Anexo Técnico FEV 1.9, and Colombia has never declared its system a national implementation of the European standard. Peppol BIS Billing 3.0 or standard EN 16931 UBL must be converted into the Colombian profile before submission.

Can I serve Colombian clients from Europe?

Not as a Proveedor Tecnológico without local presence. Habilitación requires incorporation in Colombia or a branch of a foreign company, RUT registration, accounting capital of at least 20,000 UVT, fixed assets of at least 10,000 UVT located in Colombia, ISO 27001 certification, continuity planning, qualified staff, passing the DIAN test set and accepting a DIAN site visit. The alternative is to supply software while the client registers as a direct facturador electrónico and carries the responsibility — a structure that has to be delimited carefully against performing the regulated services.

How long does accreditation last?

Five years. It is personal and non-transferable, renewal must be applied for at least three months before expiry, and DIAN has two months from a complete application to decide. Note the escalating provider sanctions too: repeated breaches bring a one-year and then a two-year ban on taking new clients, and on a third recurrence cancellation of the habilitación — at which point the provider leaves the DIAN register and its clients must move.

Is a PDF invoice acceptable?

Only as a representación gráfica. The XML has the legal force; the PDF is a rendering of its data. An electronic buyer normally receives a package of invoice XML, DIAN validation response and graphical representation. A non-electronic buyer may receive the graphical representation by email or another agreed route — but the archive still has to hold the XML and the validation response.

What happens if DIAN's system is down?

The invoice may be delivered to the buyer without a prior validation response, and the documents must be submitted to DIAN once service is restored. For certain failure scenarios on the seller's own side, information about documents temporarily issued on paper must be transmitted within 48 hours of the fault being cleared. Outside these official contingency scenarios an unvalidated invoice is not properly issued and should not be used as full tax evidence.

What data can I ask a consumer for?

Very little. If a consumer asks for a FEV or an electronic POS document in their own name, the seller may request the name, the identifier type and number, and an email address if the buyer wants the document by email. DIAN has expressly prohibited demanding extras such as address, telephone number or a copy of the RUT. Where the consumer does not ask for a personalised document, the ordinary rules for that B2C document apply with no excess personal data collected.

Do I need to file a separate VAT report as well?

Not one duplicating the same invoice data. Every document is transmitted individually before it reaches the buyer, and DIAN validates it as part of issuing — that is transaction-level continuous control, so no separate periodic report equivalent to the European digital reporting requirements is needed for the same data. What credit transactions do require is the electronic events: acknowledgement of receipt of the invoice and of the goods or services.

Summary

Colombia is a finished mandate with an unfinished-looking surface. Invoices have cleared through DIAN since 2020, the equivalent documents completed their transition in November 2024, and Resolución 000227 of September 2025 pulled roughly seventy scattered resolutions into one instrument. The technical annex in force is FEV 1.9.

The model is prior validation: sign, compute the CUFE, submit, receive Documento validado por la DIAN, then deliver to the buyer. An invoice is issued only when it has been both validated and delivered — and on credit terms the buyer's electronic acknowledgements are part of what makes it usable evidence.

Two things to take away. UBL 2.1 is not EN 16931, and the familiar syntax hides a wholly local semantic model. And Colombia, unlike Brazil, Chile or China, does regulate the provider directly — 20,000 UVT of capital, 10,000 UVT of assets in Colombia, ISO 27001 and a DIAN site visit. Extending an existing European Peppol Access Point does not meet that; entering the market means a Colombian entity or branch, or partnership with an already authorised Proveedor Tecnológico.

Resources

DIAN — Sistema de Factura Electrónica The official microsite covering the invoice, the equivalent documents, electronic payroll and RADIAN Resolución DIAN 000227 de 2025 — consolidated text The single instrument that now carries the invoicing rules and the technical annex under code T5.1 — cite this rather than the superseded resolutions Proveedores Tecnológicos — the authorised register The public catalogue of providers DIAN has authorised, with NIT and company name — check a partner here before contracting, and again afterwards Step-by-step habilitación as a Proveedor Tecnológico DIAN's own walkthrough of the application, the document upload, the verification visit and the resolution Registering and habilitación as a facturador electrónico What your Colombian client has to do in its own name — the route that stays open without local accreditation DIAN — ¿Cómo facturar? The practical issuing guide, including DIAN's own free solution for taxpayers who do not use a provider

Need support with e-invoicing compliance?

As a certified Peppol Access Point we provide solutions for sending and receiving electronic invoices securely across Europe — including format conversion, validation and integration with national systems.

Start your free trial