Custom software development in Colombia
In Colombia an electronic invoice is not a nice PDF: it is an XML with an international structure, validated by the DIAN before it reaches the customer. And if you buy from someone who does not invoice, you have to issue the document yourself.
Let us be clear about Colombia
We do not yet have a client in Colombia. The above is the market's real framework and how we approach it from Spain and Argentina, where we do operate. We say it plainly rather than implying an office that does not exist.
The Colombian electronic invoicing system rests on an international document standard — UBL — and on prior validation: the DIAN checks the document before it becomes valid, and each invoice carries a unique code identifying it. For software this means the invoice is a signed document with a fixed structure, not a template, and that there are more documents than the invoice: adjustment notes, supporting documents and electronic payroll.
How you get paid
The payment method decides the checkout.
Currency: Colombian peso (COP). A checkout copied from another country fails here before it fails anywhere else.
PSE
Direct debit from a bank account, the country's most widespread online payment method. The buyer picks their bank and approves inside their own online banking; the merchant gets confirmation afterwards, asynchronously. A checkout designed for cards does not fit without changes.
Mobile wallets
Wallets tied to the major banks move an enormous share of person-to-person payments and, increasingly, merchant payments. They are identified by phone number, not by IBAN.
Cash on delivery
Cash on delivery remains relevant outside the main cities. It means the order is confirmed with no money collected and that returns are a logistics operation, not a gateway refund.
Tax obligations
What the tax authority demands from the software.
It is not a module bolted on at the end. It shapes the data model, and redoing it later costs far more than getting it right from the start.
| Framework | What it means for the system |
|---|---|
| DIAN · UBL 2.1 | The invoice is an XML following the UBL standard as adapted by the DIAN, digitally signed. The graphical representation the customer sees is a consequence of the XML, not the other way round — and that is the order many systems get wrong. |
| CUFE and prior validation | Each invoice carries a unique code derived from its content, and the DIAN validates the document before it takes effect. As in Mexico, issuance depends on a third party that can fail or stall. |
| Supporting document | When buying from a supplier not required to invoice electronically, it is the buyer who must issue a document supporting the expense. It is a document type most systems brought in from abroad do not even contemplate, and without it the expense is not deductible. |
| Withholding at source · ICA | Beyond VAT there are withholdings and a municipal industry and commerce tax whose rate depends on the municipality and the activity. Like Argentine gross income tax, it is not a single national rate. |
Experience
The document nobody migrates
Almost every invoicing system solves the sales invoice. The supporting document — the one the buyer issues when their supplier is not required to invoice electronically — gets left out again and again, because it does not exist in any of the countries they benchmark against. The result is a company that invoices perfectly what it sells and cannot deduct half of what it buys. It is the exact reason a country page that only swaps the flag and the currency is worth nothing: what breaks a project is not the peso sign, it is a document type you did not know existed.
Regulatory framework
Who regulates the product.
INVIMA
National institute for drug and food surveillance. Its sanitary registration is the identifier anchoring a medicine or food product in a product record, just as the AEMPS registration does in Spain.
ICA
Colombian agricultural institute. It registers veterinary and agricultural products and sets withdrawal periods, the figure that turns a vademecum into a tool rather than a brochure.
Data protection
Act 1581 of 2012, with the Superintendency of Industry and Commerce as authority. It has a quirk that surprises anyone coming from the GDPR: personal databases are registered with the authority, a formality that does not exist in Europe.
Other markets
The figures behind all of the above are on the pricing page, and the terms used here are in the glossary.
FAQ
Custom software in Colombia
Do you have clients in Colombia?
Not yet. We operate from Spain and Argentina. What we bring is experience building for markets where invoicing is validated by the administration and taxes depend on jurisdiction, which is exactly the Colombian case.
Can you integrate DIAN electronic invoicing?
Yes. The invoice is a signed UBL XML validated before taking effect; technically it closely resembles Mexican stamping and the Verifactu record chain in Spain, both of which we work with.
How is PSE integrated into the checkout?
As an asynchronous payment: the buyer approves inside their online banking and confirmation arrives later. The order must exist in a pending state with stock reserved, just as with Mexican cash payments.
Do you account for municipal industry and commerce tax?
It is raised when designing the data model. A single tax rate applied nationwide is the same mistake as Argentine gross income tax, and it costs just as much.
A project in Colombia?
Tell us what you need and we will say what it involves in this market and what we do not know yet.