Skip to main content
In Fail Fast you do not type taxes. When you save a document, the system looks at it, applies the country’s tax rules, and writes the result. Nobody keys in 19 % VAT or a 4 % withholding. Your job is to tell the system who your company is, who your stakeholders are, what you buy and sell, and which accounts the taxes post to. With that, every document settles itself. If your company is small, almost all of that resolves on its own: see Cases by company size.

How Fail Fast decides which taxes apply

For each line of a document, the system looks at three things: It also uses the document’s operation date: the rate, the minimum, and the value of the UVT are the ones in force that day. A 2025 invoice that you settle again today uses 2025 values. Each country rule reads this data through conditions. When a condition is not met, the tax does not apply and the system writes down the reason. When nobody answered a piece of data the rule needs, the system does not assume it: it tells you. See Verify taxes.

An example with numbers

You buy cleaning services for 1,000,000 from a company that files income tax, on October 15, 2026, with the line located in Medellín. Your company is an income withholding agent and an ICA withholding agent in Medellín. You pay the supplier 1,000,000 + 190,000 − 40,000 − 1,800 = 1,148,200.
Withholding minimums are in UVT, not in pesos. The system does the math with the UVT of the document’s date, so you do not have to update anything each January. The minimum is compared with the sum of the lines of the same rule in the document.
There are more examples, with the accountant’s figures, in Worked examples.

What Fail Fast does and what is up to you

Do not modify the country’s rates or rules: they are the same for every company and are read-only. What is different in your company is recorded as a tax rule override. See Tax rule override.

Configure taxes step by step

Follow this order: you cannot post a tax that is not calculated yet, nor calculate anything on a product that does not say what it is.
1

Complete your company's tax profile

Open your own company’s stakeholder record and go to the Tax profile (Perfil fiscal) table. To the system your company is one more stakeholder. Its responsibilities are taken from the RUT first; answer the ones that are missing. The rows, their origin, and what happens if you leave them empty are in Tax profile.
2

Set your CIIU and your ICA activity

Register your company’s CIIU, mark the principal one, and, if you operate in a municipality that has an activity table, declare your ICA activity there. See CIIU, ICA activity, and ReteICA.
3

Complete the tax profile of your suppliers and customers

Create the stakeholder with their document and name. The fastest way is to upload their RUT and let AI fill it in: see Load the RUT of a stakeholder. After that you only look at the rows the system marks as missing. A person with an ID card who buys at your shop needs nothing.The stakeholder’s location is not just contact data: with it the system knows whether they are from abroad, and that decides whether the purchase carries VAT. The stakeholder cannot be saved without it.
4

Classify your product types

This is the step that is forgotten most. The tax category and the withholding category go in the product type: they are what connects a line to a tax rule. Without them the document saves, the totals add up, and no tax appears. See Products.
5

Say which account each tax goes to

In the Tax account map (Mapa de cuentas de impuestos) you say, for each tax and each role it plays, which accounting account it posts to. See Tax account map.
6

Register your exceptions, if you need them

When a country rule does not apply to your company, or applies at another rate, register an exception with its validity, scope, and reason. Having no exceptions is normal. See Tax rule override.
7

Verify with the simulator

Before invoicing, try an operation in the Tax simulator (Simulador fiscal). See Verify taxes.

Load the RUT of a stakeholder

Instead of typing the tax profile, you can upload the stakeholder’s RUT and let AI read it.
1

Open the stakeholder record

Open or create the supplier, customer, or stakeholder in its form. RUT reading is available on the form, not in the table view.
2

Upload the RUT

From the AI button on the form’s toolbar, choose Read RUT and upload the file you download from the DIAN, in PDF, PNG, or JPEG, up to 10 MB.
3

Review what AI filled in

AI fills in the document number, the verification digit, the name or company name, the trade name, the email, the phone, the economic activities (CIIU), and the tax responsibilities. Fields filled by AI are marked. Nothing is saved yet: review and correct whatever needs it.
4

Confirm

Choose Confirm the tax data from the RUT. The responsibilities are saved into the Tax profile with origin from the RUT.
  • If you add or remove a responsibility before confirming, it is saved as written by a person and takes precedence over the RUT.
  • A value that came from the RUT is not edited in the Tax profile: you change it in the stakeholder’s tax responsibilities.
  • If the RUT belongs to a different stakeholder, or a stakeholder with that document already exists, the system tells you and does not merge the data.

Settle a supplier invoice

1

Create the invoice

In supplier invoices, create a new one and fill in the header. These fields decide the taxes:
  1. Operation date: decides which rate and which UVT are used.
  2. Line location: decides the municipality and with it ICA and ReteICA.
  3. Supplier: brings in their tax profile. They have to be active.
2

Add the lines

Add the products or services with their quantity and amount. The line’s tax category arrives on its own from the product type. If it comes up empty, classify the product type before saving. Choose the line location: it is the municipality where the purchase happens.
3

Save

On save, Fail Fast settles every tax on the document. It is all or nothing: either all of them are calculated or none is.
4

Review the taxes tab

You will find three grids, in this order:
  • Summary: one line per tax, with its operation (tax, withholding, higher value), base, rate, and amount. This is what goes to accounting.
  • Detail: the same, line by line, with the rule that applied. A tax with no rule was not calculated by the system: someone typed it in.
  • Not applied: the rules that were evaluated and did not apply, each with its reason written out. This is the grid that explains a withholding you expected and did not get.
5

Post it

With the tax account map configured, the invoice posts with its taxes in the accounts you defined.

Pages in this guide

Tax profile

Each row, its origin, and which ones fill themselves.

CIIU, ICA activity, and ReteICA

The principal CIIU and the activity per municipality.

Products

Product type and product fiscal sheet.

Tax account map

Which account each tax goes to.

Tax rule override

Do not apply a rule, or apply another rate.

Verify taxes

Tax simulator and why a tax did not come out.

Cases by company size

What a bakery fills in and what a large company fills in.

Worked examples

Sales, returns, and a purchase with figures.

Bulk uploads with CIIU

Suppliers, customers, and patients.

What is not covered yet

Purchases from abroad, INC on purchases, and tips.

Accounting

The chart of accounts and how to create the accounts that carry taxes.

Electronic invoicing

How documents with their calculated taxes are reported to the DIAN.

Purchasing

Purchase orders and supplier invoices.

Sales

Quotes, orders, and customer invoices.

Multi-book accounting

How the same movement reads in each accounting book.