Skip to main content
Verify the configuration before invoicing, and review the document after saving it.

Tax simulator

The Tax simulator (Simulador fiscal) settles an operation without saving any document. Use it to test:
  • A new stakeholder, before selling to them or buying from them.
  • A product type you just classified.
  • A tax rule override you just registered.
  • A new municipality in the line location.
Write the operation as you would write it in the document: stakeholder, product, amount, operation date, and line location. The simulator shows the same results the document will show: each tax with its base, rate, and amount, and the ones that did not apply with their reason.

The line location decides the municipality

The municipality of ICA and ReteICA comes from the location of each line, not from the branch. When you change the line location, taxes are recalculated.
  • The selector offers departments and cities.
  • A document can have lines in different municipalities.
  • If a tax changes when you move the location, it is because the new municipality has another rule or because the buyer is not an ICA withholding agent there.

Missing data

When a company, a stakeholder, or a product lacks a piece of data the rules read, the Tax profile shows it as Missing, required for suppliers. Also check:
  • That each product type has a tax category and a withholding category. See Products.
  • That each company or person with several CIIU has one marked as principal. See CIIU, ICA activity, and ReteICA.
  • That each supplier has a CIIU, except foreign non-residents.
  • That the Tax account map has a row, and a counter account when the tax is outside the total. See Tax account map.

Read a document’s taxes

In the document’s taxes tab there are 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 and the activity used and where it came from. 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.
The not-applied grid is long by design: it shows every rule that was evaluated, including ones that are not for your activity. It is not an error.

Why a tax did not come out

Always start with the not applied grid: the reason is written there.
When nobody answered a piece of data the rule needs, the system does not assume it: it leaves the tax in not applied with the message “nobody answered…” and tells you which data to register. The exception is benefits the stakeholder must prove, such as the special regime or self-withholding: while they are not registered, the withholding is made.
An empty data point is read according to the rule’s condition. If the rule asks that the stakeholder “be” a withholding agent, empty means they are not and the withholding does not apply. If the rule asks that they “not be” a self-withholder, empty means they are not and the withholding applies.