DIAN electronic invoicing 2026: what changes and where Colombian SMBs lose money

One-minute summary: the four DIAN documents

Colombia is the toughest Odoo localization in Latin America. Not because of CUFE or UBL: four DIAN documents run on different deadlines, and a 10-day delay on electronic payroll can cost up to USD 13,400 a year in lost deductibility on your books.

If you run an SMB in Bogotá, Medellín or Barranquilla and your accountant insists “facturación electrónica is under control,” read on. Most likely your company today has: lost deductibility on electronic payroll for 2 to 4 months this year, zero supporting document for purchases from non-mandated invoicers, and an unused RADIAN —while your receivables could trade as a liquid título valor at a 4-6% discount.

This is not scare-mongering. It is DIAN arithmetic: 1.7 million formal companies are required to comply with the electronic invoicing system, and roughly 70% have at least one structural compliance gap that surfaces during the first audit.

Before going deep, the picture:

• The DIAN Electronic Invoicing System includes four documents: electronic sales invoice (FEV), supporting document for acquisitions (DS), electronic payroll supporting document (NE) and RADIAN registration. All four are mandatory for most VAT-liable SMBs.
• CUFE is a SHA-384 hash over the document's key fields. Without a validated CUFE the document does not legally exist.
• Electronic payroll = deductibility. The supporting document must reach DIAN within the first 10 calendar days of the following month. Late filing means risk of losing the payroll-cost deduction.
• Resolution 165 of 2023 is the regulatory baseline, updated in 2024-2025 with pre-validation, new UBL fields and RADIAN integration.
• Base penalty (article 651 Tax Statute): 1% of the document value, minimum 10 UVT (~COP 502,000 in 2026), maximum 7,500 UVT (~COP 376M).
• The SMB base is large: 1.5M micro + 103,000 small + medium businesses. 99.5% have compliance obligations; far fewer have a correct setup.

How we got here: 2020-2026 timeline

Mass rollout of electronic invoicing in Colombia started in 2019-2020. Decree 358 of 2020 made electronic invoicing mandatory for every VAT-liable taxpayer. From November 1, 2020, XML transmission to DIAN became compulsory; validation happened post-issuance —DIAN validated the document after it had already reached the buyer.

In 2023 came Resolution 165 of 2023: today it is the governing rule. It consolidated FEV, NE and DS requirements into a single resolution, repealed Resolution 042 of 2020 and set the UBL 2.1 technical specification for the XML structure.

In 2024 came pre-validation: DIAN now validates the document before it reaches the buyer, which prevents accounting discrepancies and blocks malformed documents. The same year, RADIAN went into full operation: a FEV with buyer acknowledgment and acceptance becomes a título valor, sellable to a bank at a 4-6% discount, pledgeable as collateral, or held as a liquid asset.

In 2025 DIAN tightened controls on electronic payroll: validations were added for IBC, contract types and employment termination. In April 2026, through the INCP, DIAN clarified the scope of late transmission: payroll costs filed late retain deductibility only if the delay did not cross the company's annual income-tax deadline. Before the income-tax filing you can still close prior months; after that, it is too late.

For 2026, three concrete changes:

1. January 2026. A new DIAN service allows issuing FEV with only the buyer's document type and number (no full company name and address). It cuts friction in retail and fast B2C operations.
2. During 2026. RADIAN expands to new segments: a pilot for healthcare receivables (EPS-IPS) and real estate.
3. Gradual audit reinforcement on electronic payroll. DIAN announced an automated cross-check between NE aggregates and form 220 (employee income and withholding certificate). Any discrepancy triggers a review.

Reading for SMBs: the “keep going as before” window has closed. Compliance is no longer just about DIAN fines —it is about cash-flow and liquidity predictability.

The four DIAN documents: what each one is and why it matters

Not every document carries the same operational weight. Here is a walk-through with the detail that matters for your Odoo setup and your month-end close.

#1. Factura Electrónica de Venta (FEV)

The base document. Every sale by a VAT-liable taxpayer is issued as a FEV. Technically it is a UBL 2.1 XML signed with a digital certificate, with mandatory fields:

• CUFE (Unique Electronic Invoice Code). SHA-384 hash of document number, date, currency, key totals, issuer and receiver NIT, environment. CUFE changes with any field modification —that is the immutability seal.
• Authorization resolution: the number under which DIAN approved you as an issuer.
• Authorized numbering ranges: the block DIAN assigned (e.g., FE-1 to FE-50000).
• QR code: mandatory visual element on the printed representation; scanning it returns the CUFE and validates the economic fact.
• XML + PDF pair: both formats must reach the buyer.

#2. Documento Soporte en Adquisiciones (DS)

The document you file with DIAN when you buy from someone not required to invoice electronically: an individual without NIT, an unregistered microentrepreneur, a foreign supplier without Colombian residency. Without DS, the purchase cost is not deductible for income tax and does not generate VAT credit.

Technically it is an XML with CUDS (Unique Supporting Document Code), analogous to CUFE. Transmission deadline: at the time of the purchase or, at the latest, before the close of the same calendar day. Resolution 165 of 2023 regulates this in Chapter IV.

#3. Documento Soporte de Nómina Electrónica (NE)

The supporting document for payroll costs and deductions. It is filed within the first 10 calendar days of the following month, one document per employee. It contains: contract type, IBC (contribution base income), withholdings, social security contributions and labor benefits.

The trap: if NE did not arrive on time, the payroll cost for that employee loses deductibility. For a 20-employee SMB with an average salary of COP 4.5M per month, that is up to COP 54M in lost deductions per year (~USD 13,400 at COP 4,030 per USD), equivalent to about USD 4,700 in extra income tax at the 35% rate.

#4. RADIAN

RADIAN is the Registry of Electronic Invoices — Títulos Valor. When a FEV is registered in RADIAN with the buyer's acknowledgment and express acceptance, it acquires the legal status of a título valor. From there: you can sell it to a bank at a 4-6% discount, use it as collateral for a credit line, or simply hold the option to liquidity.

For a B2B supplier with 30 to 60-day receivables, RADIAN is the cheapest way to substitute for working capital.

When your current setup works —and when it doesn't

Not every SMB needs to weight the four documents equally. Four common scenarios to calibrate priority. If you recognize yourself in one, you know where to open the first diagnostic.

Scenario 1: retail with 1 to 3 stores (FMCG, food, fashion)

Works: basic FEV through any authorized technology provider (Dataico, Carvajal, Facture, Siigo). DS, rarely (most purchases are from formal suppliers). Electronic payroll, mandatory. RADIAN, almost never relevant given the low ticket.

Doesn't work: if you have 3 or more stores and no POS integration with real-time FEV issuance. The cumulative regime (issuing at end of day) is formally allowed, but conflicts with multi-warehouse inventory: you draw stock at the time of sale and DIAN only sees it at night. That discrepancy surfaces at the first full inventory.

Scenario 2: B2B services (consulting, marketing, software)

Works: FEV + RADIAN. RADIAN especially, because tickets tend to run high (COP 5M to 50M) and days-to-pay sit at 30 to 60. A RADIAN-registered invoice sells to a bank and cash arrives in 3 to 4 days instead of 47.

Doesn't work: if you have foreign clients (USA, Mexico). They are not in DIAN, do not sign acknowledgments and RADIAN does not apply. Separate the flow: foreign clients on exportable format, local clients on standard FEV + RADIAN.

Scenario 3: manufacturing with purchases from individuals

Works: supporting document as the critical priority. Without DS, buying raw material from farmers or individuals yields no income-tax deduction and no VAT credit. Classic story in agriculture, textile or mining.

Doesn't work: issuing DS manually through the DIAN portal. With 200+ purchases a month, each DS is 5 minutes in the portal —16 hours a month of accountant work on zero-value tasks. Automation via Odoo and a provider connector is required.

Scenario 4: healthcare and labs

Works: standard FEV + electronic payroll. From 2026 there is a RADIAN pilot for EPS-IPS receivables, but it is not yet broad.

Doesn't work: if your main receivables are tied to EPS contracts with 90 to 180-day payment cycles. Standard FEV does not solve liquidity. Healthcare RADIAN does not yet allow trading invoices against EPS; that is on DIAN's roadmap for end of 2026.

Five common mistakes that repeat in every audit

Collected from Odoo audits across Colombian SMBs since late 2024. These look like details and cost real money every month. For an ordered cross-check, see our dedicated analysis on payroll deductibility that complements this pillar.

#1. “Electronic payroll = form 220, we close it at year-end”

The most expensive mistake. The accountant files form 220 in March of the following year and assumes payroll is closed. It is not. NE is a monthly supporting document; it must reach DIAN in the first 10 calendar days. Form 220 is the annual certification to the employee for their income-tax return. Different documents, different deadlines.

Consequence: on audit, DIAN cross-checks NE aggregates against the deductions reported in the annual income-tax return. Any gap means additional payment plus an inaccuracy penalty (article 647 of the Tax Statute).

#2. Supporting document “whenever I remember”

The accountant issues DS in batch at end of month. Resolution 165, Chapter IV, requires transmission at the time of the operation or, at the latest, before the close of the same calendar day. Batch issuance is a formal violation. Until 2024 DIAN looked the other way; since 2025 it is grounds to reject the VAT credit on that operation.

Consequence: in retail with 50 to 100 DS per month, potential loss of COP 2-4M per month in VAT credit. Over a year: up to COP 48M, from this error alone.

#3. Free-tier issuer plan for every document type

DIAN portal free plans or Dataico/Carvajal free tiers usually cover only FEV. NE, DS and RADIAN are separate subscriptions. Many SMBs use the free plan “for everything” and in practice only transmit FEV, deferring NE and DS.

Consequence: on paper everything is “electronic,” but DIAN only sees sales. Purchases and payroll stay uncovered. At audit comes the panic, the search for someone to blame and a penalty-laden correction.

#4. The CUFE flow is not configured in Odoo

The standard l10n_co module from Odoo S.A. covers chart of accounts and tax mapping, but does not perform synchronous validation against DIAN. The document is created in Odoo with a local number, queues to the technology provider (Dataico, Carvajal, Facture…) and only later receives a CUFE.

If the flow is not set up correctly:

• The document hangs in “pending CUFE” for weeks.
• The customer receives a PDF with no QR —invalid for their bookkeeping.
• At month-end, the sales report does not match what DIAN sees.

Consequence: the “sales in Odoo vs. sales in DIAN” gap becomes a monthly headache. In one of our audits —Cali distributor, 1,200 FEV per month, 4% hung in pending— about 48 invoices per month never reached DIAN: COP 19M per month “lost” in synchronization.

#5. “RADIAN is for banks, we don't need it”

A massive strategic mistake. Registering an invoice in RADIAN is technically free for the issuer. The buyer accepts and the invoice becomes a título valor. From there you can sell it at a discount, pledge it as collateral or simply keep the option.

An SMB that does not use RADIAN forfeits the optional value of its receivables. With average accounts receivable of COP 200M, that represents COP 1 to 2M of available liquidity per month at minimal risk.

Real case: cosmetics retailer in Bogotá

Anonymized, rounded numbers. Company: 8 stores in Bogotá and Medellín, annual revenue ~COP 4,200M, 47 employees. Before the audit: Defontana ERP + manual issuance through the DIAN portal.

What we found:

• 12% of FEV were issued more than 24 hours after the operation (Resolution 165 violation).
• Electronic payroll was transmitted in batch once per quarter, which technically meant zero deductibility for 8 of the 12 months of the year.
• Supporting documents were not issued at all: packaging purchases and services from local designers entered with no support.
• RADIAN was not used —with average receivables of COP 380M.

What we did:

1. Migration to Odoo Community 17 + customized l10n_co + Dataico connector. Details on Odoo Implementation.
2. POS module that issues FEV at the time of sale with synchronous CUFE validation.
3. HR module that auto-generates NE on the first business day of the month for the 47 employees.
4. Purchases module that auto-creates DS for any purchase from a supplier without electronic NIT.
5. RADIAN connector that registers every B2B FEV; customers receive an email with an acknowledgment proposal.

9-month results (anonymized, rounded):

• Recovered ~COP 187M of payroll deductibility for fiscal year 2025 via amended return.
• COP 42M of additional VAT credit through regular DS issuance.
• First factoring operation via RADIAN: COP 58M received in 4 days instead of 47.
• Cash-flow improvement: ~COP 287M in the first year.

Implementation cost: ~COP 34M (Odoo licenses + customization + integrations + training). Payback under two months.

Checklist: 7 actions for the next 30 days

If you are not sure your DIAN setup is in order, this is the minimum diagnostic. Your accountant can run each step without hiring anything new. To go deeper, there is an Excel checklist with verification formulas.

1. Ask accounting for the list of NE transmissions over the last 6 months with their DIAN receipt dates. Compare against (last day of the month + 10).
2. Reconcile total payroll deductions in the annual income-tax return against the IBC total in NE. A gap above 2% is an alarm.
3. Count how many DS you issued last quarter. If it is less than the number of individual suppliers, you have a gap.
4. Check “pending CUFE” status with your technology provider. Any value greater than zero at month-end close is a problem.
5. Take your top 20 customers by receivables. How many have a FEV acknowledgment in RADIAN? Target: 80% or above.
6. Ask IT for an “invoices issued vs. invoices validated by DIAN” report for the month. They must match.
7. If you use Odoo, check the l10n_co version and the presence of an issuance connector. The free l10n_co does NOT cover DIAN validation.

What to do now

If you made it this far, two paths.

First: keep going, hoping a DIAN audit will not hit you. Given that since 2025 DIAN automatically cross-checks NE, forms 110/210/220 and the income-tax return, that path gets more expensive every month.

Second: in 30 days, run a diagnostic, close the gaps and sleep better. We run Odoo audits focused on DIAN compliance and analytics for SMBs. The Audita tu Odoo format is a structured 30-minute diagnostic that surfaces at least three concrete gaps in your DIAN configuration.

Free steps:

• Download the DIAN 2026 SMB checklist —Excel, PDF and video walkthrough.
• See how Odoo operates in Colombia and the sector-specific risks.
• For regional context, there is also our SUNAT Peru 2026 guide and the AFIP Argentina guide.

Paid step:

• Audita tu Odoo —diagnostic plus written report with three concrete gaps. From USD 480.

Frequently asked questions