POS Equivalent Document (DIAN Type 11)

The POS Equivalent Document (Type 11) is the electronic receipt DIAN requires for point-of-sale sales to end consumers. It replaces old paper receipts and is reported electronically just like the electronic invoice.

contable.io generates, signs and reports this document automatically for every POS sale, with no extra action from the cashier.

Who must issue it?

DIAN requires VAT-responsible and non-responsible taxpayers to issue Type 11 equivalent documents for end-consumer POS sales. If your company already invoices electronically, you must also report POS sales through this channel.

Before you start

For the POS to issue equivalent documents you need:

1. Company enabled as electronic invoicer before DIAN, either in production or testing.
2. Active DIAN resolution for Type 11 with its numbering range. Configure it in Settings → DIAN → Resolutions.
3. Valid digital certificate loaded in the system.
4. POS warehouse linked to the right resolution (if you have multiple branches, each can have its own).

If you sell at the POS before having an active resolution, the system will record the sale but not send the document to DIAN. You’ll need to reprocess them later.

What the system generates per sale

For every confirmed POS sale, contable.io:

1. Numbers the document with the next consecutive of the resolution.
2. Calculates taxes (VAT, INC) based on products sold.
3. Signs the XML with the company’s digital certificate.
4. Sends the XML to DIAN services.
5. Saves the CUDE (unique equivalent document code) and QR.
6. Prints the receipt with CUDE, QR and required legal data.

All of this happens in less than 2 seconds. If the DIAN connection fails, the document queues for automatic retry and the sale is not blocked (see Offline mode).

Customer data

Type 11 is built for end consumer sales, so capturing customer data is not mandatory. If you don’t assign a customer, the document is issued to “End Consumer” with generic NIT (222222222222).

However, if the customer requests it —for example to support an expense— you can assign them from the cart before charging. In that case the document includes the customer’s name, document and address.

Document states

Each POS sale can be in one of these states, visible in Sales → POS receipts:

State	Meaning
DIAN pending	Not yet sent (internal queue).
Accepted	DIAN accepted the document. Valid CUDE.
Rejected	DIAN returned an error. Review and reprocess.
Not applicable	Company without resolution, sale only local.

Reprocessing rejected documents

If a document ends up Rejected, go to Sales → POS receipts, filter by state, open the sale and check the rejection reason (common errors: duplicate numbering, expired resolution, expired certificate).

After fixing the cause, use the Resend to DIAN button to retry. The consecutive is preserved.

See also

• Selling at the counter
• Offline mode