🇨🇴 Colombia

This sheet assumes you know the xPOS-Core communication protocol. Here we only document what is specific to Colombia.

Summary

Aspect	Value
country code	co
Tax authority	DIAN
Pattern	C — dual XML (DTE / equivalent DTE)
Supported inputType	json, xml, xdoc, txt
Extra endpoint	–
Output	Signed tax XML

XSLT mapping

XSLT	Use
input_to_dte_co.xslt	json and xml inputs → XML <root> → Gosocket XML.
other_to_dte_co.xslt	txt input → Gosocket XML. Does not go through input_to_dte.
xdoc_to_dte_co.xslt	xdoc input → Gosocket XML. Does not go through input_to_dte.
dte_to_fiscal_co.xslt	Gosocket XML → DIAN tax DTE.
dteEQ_to_fiscal_co.xslt	Gosocket XML → DIAN equivalent DTE (depending on document type).
custom_response_co.xslt	Generates custom_response when applicable.

Document types (typeDoc)

WebSocket example uses typeDoc=01 (electronic invoice).

Colombia-specific response fields

Colombia returns the entire core + full tax echo + two exclusive fields:

Field	Description
docNumber	Series and number of the document (e.g. SETP990044419).
contingencyCode	DIAN contingency code.

countryIdentificationCode in Colombia is CUFE (electronic invoice) or CUDE (equivalent document) depending on the type.

WebSocket example

{
"env": "sbx",
"operation": "consolidate",
"typeDoc": 1,
"country": "co",
"inputType": "json",
"origin": "<issuer taxId>",
"document": { /* factura electronica o documento equivalente */ }
}

Status re-retrieval

The /api/v1/status response in Colombia includes, in addition to the core, these fields:

Field	Description
signedXml	Signed tax XML with folio.
param	test or consolidate.
typedoc	DTE type.
date	Transaction date (yyyy-mm-ddTHH:mm:ss).

Particular notes

• Pattern C: the flow branches the XSLT depending on the document type (electronic invoice vs equivalent document).
• Publishes in Inbox-Gosocket.