Skip to content
Electronic Invoicing

What is the RUT and how does it affect your electronic invoicing in Colombia?

A misconfigured RUT —with the wrong tax responsibility code or an outdated tax regime— is one of the most common and least understood causes of electronic invoices being rejected by DIAN. We explain exactly what it is, how to read it and why it matters so much to your invoicing software.

7 min read Kevin Castellanos — QENT Founder

Almost every Colombian company has its RUT printed, scanned or saved in some PDF, but very few really understand what information it contains or why that information determines how each of their electronic invoices must be issued. When an invoice is rejected by DIAN or by a customer’s software, the cause is almost never a typo: it is almost always a piece of RUT data that does not match what the electronic invoice is reporting.

What is the RUT?

The Single Tax Registry (Registro Único Tributario, RUT) is the mechanism DIAN uses to identify, locate and classify all individuals and legal entities that are subject to tax, customs or foreign exchange obligations in Colombia. It is not just an identification document: it is the official source from which the tax rules that apply to each taxpayer are derived, including how they must invoice.

Anyone who wants to issue electronic invoices, contract with the State, import or export, or simply operate as a formal merchant in Colombia needs an up-to-date and valid RUT.

The structure of the RUT: beyond the number

The field everyone recognizes is the NIT (Tax Identification Number), but the RUT as a document contains much more information relevant to electronic invoicing:

  • NIT and check digit: the taxpayer’s unique identifier with DIAN, which must match exactly the one reported in each electronic document.
  • Type of person: individual or legal entity, which determines which fields are mandatory in the invoice XML (first and last names vs. company name).
  • Tax responsibilities: a list of codes (for example O-13, O-15, O-23, O-47) indicating which tax obligations the taxpayer has. This is often the least understood part and the one that causes the most problems.
  • Tax regime: VAT filer or non-filer and, where applicable, whether it belongs to the Simple Taxation Regime.
  • Economic activity (CIIU code): classifies the main line of business and can affect withholdings and automatic validations.
  • Tax address and location: the domicile reported as the issuer’s or recipient’s address in each electronic document.

The tax responsibility codes that matter most to your invoice

These are the tax responsibility codes that most often determine how an electronic invoice must be built:

O-13 — Large taxpayer

Companies classified by DIAN as of greater tax relevance, subject to differentiated tax calendars and controls. Their status as a large taxpayer must be correctly reflected in the invoicing software, especially for the withholdings their suppliers apply to them.

O-15 — Self-withholder

Taxpayers authorized to apply withholding tax to their own income themselves, instead of having it applied by whoever buys from them. If your company has this status and your invoicing system is not configured for it, you run the risk of your customers withholding twice or incorrectly.

O-23 — VAT withholding agent

Determines whether the taxpayer acts as a sales tax withholding agent in certain transactions, which changes the tax treatment of the transaction and must be reflected in the corresponding electronic document.

O-47 / O-48 — Simple Taxation Regime

Identifies taxpayers who opted for the Simple Regime (an optional regime that unifies several taxes into a single payment) as opposed to those in the ordinary regime. This classification directly affects how certain taxes included in the invoice are calculated and what information must appear in the XML.

⚠ The most common mistake

A company changes regime —for example, it moves to the Simple Regime or stops being a self-withholder— and updates its RUT with DIAN, but forgets to update that same information in its electronic invoicing software or in that of its technology providers (PAC). The result: invoices that are technically valid in form, but with outdated tax information, which can lead to objections, customer claims or inconsistencies in the income tax return.

Types of taxpayers in Colombia and their impact on the invoice

Beyond the specific tax responsibilities, the RUT also classifies the taxpayer into broader categories that determine the general tax treatment:

  • Individual merchant: a person who carries out commercial activity in their own name. On the invoice, their personal details (first and last names) replace the company name.
  • Legal entity: companies, businesses and legally constituted entities, identified by their company name and NIT.
  • VAT filer vs. non-filer: determines whether the taxpayer must charge and file VAT on its transactions, which directly impacts the tax calculation on each invoice.
  • Large taxpayer: see O-13 above; involves differentiated tax calendars and controls.
  • Simple Taxation Regime: an optional regime designed to simplify tax payment for small and medium-sized companies, with its own invoicing rules.

Why this matters so much to your electronic invoicing software

When you issue an electronic invoice, the XML sent to DIAN (through your authorized technology provider) includes the tax information of both the issuer and the recipient: NIT, type of person, tax responsibilities, tax regime. If any of this data does not match what DIAN has registered in the RUT of either party, the document may be rejected or create inconsistencies that are detected months later, in an audit or in the income tax return.

That is why a good electronic invoicing system should not just ask you for the customer’s NIT: it should let you record their type of person, regime and exact tax responsibilities, and keep that information in sync every time it changes.

Good practices to keep your RUT and your invoicing aligned

  1. Review your updated RUT at least once a year, or immediately after any change of tax regime.
  2. Validate the RUT of your frequent customers and suppliers before invoicing them, especially if they are entities with special tax responsibilities (large taxpayer, self-withholder).
  3. Update your invoicing software every time your own tax responsibility with DIAN changes, not just the RUT on paper.
  4. Check that your technology provider (PAC) automatically validates the RUT data of the issuer and the recipient before sending the document to DIAN, to detect inconsistencies before they cause a rejection.
  5. Train whoever invoices in your company so they understand, at least at a basic level, what the most common tax responsibility codes they will find on their customers’ RUTs mean.

The RUT is not a one-time procedure you can forget about: it is living information that changes with the company’s operations, and every change has a direct effect on what your electronic invoicing must look like. Understanding its structure —beyond the NIT number— is what separates a company that invoices without surprises from one that faces recurring rejections without understanding why.

Ready to put this into practice in your company?

QENT automates exactly this. Book a 30-minute demo and see it in action.