Electronic invoicing for auto shops in Colombia: DIAN, CUFE and POS

The essentials

Colombia uses prior validation: the DIAN validates the invoice before it's valid and reaches the customer. It's not an informational submission after the fact.
The electronic sales invoice carries a CUFE; the POS equivalent document carries a CUDE. They're different documents with different uses.
The untransmitted paper POS ticket no longer exists as a valid document: the equivalent document is also generated and transmitted electronically.
POS has a value limit per document and doesn't entitle your business customer to deduct costs or claim VAT. If they ask for that, you have to issue a sales invoice.
Before issuing you have to go through the registration process with the DIAN. It's not instant: factor it into your planning.

Of the four countries in this series, Colombia is the one that most resembles a real-time system: the DIAN doesn't receive your invoices at the end of the month, it validates them the moment you issue them. That has a direct consequence for a shop: your software has to be connected, no matter what, and it has to know what to do when something fails.

This guide covers the two decisions that cause the most confusion at the counter — invoice or POS — and what to ask a software provider before contracting them. For your specific tax situation, talk to your accountant; this is about the program.

Prior validation: what it means in practice

The circuit for an electronic sales invoice in Colombia is this: you generate the document, it's transmitted to the DIAN, the DIAN validates it, and only then is it delivered to the customer with its CUFE (Código Único de Factura Electrónica) and its QR code.

The difference from an after-the-fact reporting model isn't theoretical. It means:

No connection, no invoice. There are contingency mechanisms in place, but they're a documented exception, not the normal way of working.
Errors show up instantly, not a month later. It's uncomfortable on day one and an advantage from day two on: you don't build up a problem that blows up at tax-filing time.
Your software has to manage rejection. If the DIAN rejects a document, someone has to find out and fix it. A system that doesn't show you each document's status leaves you blind.

Sales invoice or POS equivalent document: which one you issue

This is the day-to-day decision at a shop, and the one that costs the customer the most money when it's gotten wrong.

The POS equivalent document is meant for sales to end consumers, has a value limit per document, and — this is the important part — doesn't help your business customer: it doesn't entitle them to deduct costs or claim VAT. If you hand a POS document to a fleet, you're handing them a piece of paper that's worthless to them fiscally, and they'll hand it back.

The electronic sales invoice is the one that does support costs, deductions and deductible VAT for whoever receives it.

Situation at your shop	Document
Individual bringing in their car, nothing special requested	POS equivalent document (within the value limit)
Individual with a repair that exceeds the POS limit	Electronic sales invoice
Business, fleet or insurer	Always electronic sales invoice
Customer who needs to back up the expense	Always electronic sales invoice

At a shop the operating rule fits in one sentence: when in doubt, issue a sales invoice. It's always valid; the POS document isn't. And your software should warn you when a sale exceeds the POS limit instead of letting you issue a document you'll later have to redo.

The limit gets updated: the POS document's cap is set in UVT, the tax value unit the DIAN updates every year. In pesos, the figure changes annually. If your software has it hardcoded instead of parameterized, come January you'll start invoicing incorrectly.

Registering with the DIAN: it's not immediate

Before issuing, you have to complete the registration process on the DIAN's portal: sign up as an electronic invoicer, choose the mode (own software, technology provider, or the DIAN's free solution), and pass the corresponding tests.

It's a process with steps and timelines. If you're planning to open a shop or switch systems, it's worth starting it before you need it, not the week you open. A provider who walks you through registration saves you the driest part; one who sends you the manual and disappears is giving you a preview of what support will be like.

What a shop invoice carries

Beyond the general requirements, there are two particulars worth watching at a shop:

Parts and labor share the same document. They're different kinds of things and can have different tax treatment. The software has to allow line-by-line detail, not a single "repair" line for the total.
Detail is what avoids disputes. A customer who sees which part was installed, with which reference, and how many hours were billed, argues much less. A well-made invoice isn't just a tax requirement: it's the best transparency tool a shop has.

What to demand from your shop program

Colombia checklist

Is it registered with the DIAN? As the provider's own software or through a technology provider. Ask which of the two.
Does it issue both the electronic sales invoice and the POS equivalent document? A shop needs both, not just one.
Does it warn you when a sale exceeds the POS limit? And is that limit parameterized or hardcoded? You'll notice in January.
Does it show each document's status? Validated, rejected, pending. Without that, you don't know what happened.
What does it do in contingency? If the DIAN doesn't respond, it should queue and retry, notifying you. Not hand you a document as if it were validated.
Does it issue credit and debit notes referenced to the original document?
Does it itemize parts and labor line by line?
Does the invoice come out of the repair order? If you have to re-enter everything on another screen, the software isn't saving you work, it's just relocating it.

Compliance isn't the same as earning more

Everything above puts you in good standing with the DIAN, which is mandatory and non-negotiable. But it's the last step in the chain, and it's not where a shop loses money. It's lost earlier: in the quote sent over WhatsApp that nobody followed up on, in the customer who wasn't told the car was ready, in the maintenance that was due in six months that nobody remembered.

If you're switching programs because your current one doesn't handle prior validation well, make the change cover the whole journey. It's the same migration effort, and the result isn't comparable. In shop software in Latin America we look at it from a regional perspective.

Sources

Try Promec with your own shop's data

AI quotes, scheduling, mechanic app, inventory and customer portal. 3 months for €1, no lock-in.

Start for €1

FAQ

What's the difference between CUFE and CUDE?

The CUFE (Código Único de Factura Electrónica) identifies the electronic sales invoice. The CUDE (Código Único de Documento Electrónico) identifies other documents in the system, including the POS equivalent document and credit and debit notes. Both are unique codes generated from the document's data, and they let it be verified on the DIAN's public portal.

Can I still give out a paper cash register receipt?

Not as a valid document on its own. The POS equivalent document is also electronic: it's generated, transmitted, and carries its own CUDE and QR code. Untransmitted paper stopped being a valid medium. What does exist is a contingency mechanism for proven technical failures, which is a documented exception, not the normal way of working.

Can I give a POS document to a business bringing in its fleet?

You can issue it, but it won't help them: the POS equivalent document doesn't entitle them to deduct costs or claim VAT. Your business customer will hand it back to you, and you'll still have to issue the electronic sales invoice. At a shop the practical rule is simple: for businesses and anyone who needs to back up the expense, always issue a sales invoice.

What happens if the DIAN doesn't respond when I go to invoice?

There are contingency mechanisms set out for proven technical failures. What matters is how your software handles it: the correct behavior is to queue the document, retry, and clearly show its status. What it should never do is hand you a document as if it were validated when it isn't, because the problem then shows up later, once the customer has already left the shop.

How long does registering with the DIAN take?

It's a multi-step process: registering as an electronic invoicer, choosing the mode of operation, and passing the corresponding tests. It's not instant. If you're opening a shop or switching systems, it's worth starting it ahead of time, not the week you need to invoice. A good provider walks you through the process.

The POS limit is in UVT. How do I know how much that is in pesos?

The UVT is the tax value unit the DIAN updates every year, so the peso equivalent changes annually. It's worth checking the current value on the DIAN's portal at the start of each year. And it's worth checking that your software has that value parameterized rather than hardcoded: if not, come January you'll start invoicing incorrectly without noticing.