---
title: "Taxes"
slug: "guide/configuration/configuration-files/taxes"
sidebar:
  order: 81
---

<a id="ref-b8bff2ac6269"></a>
<a id="ref-73f8938074f7"></a>
<a id="ref-4855e4212586"></a>

The configuration file named `taxes.cfg` is located in `etc/` directory of the EAIWS application. The file contains the tax schemes supported by EAIWS including their categories and rates for different countries.

The file can be replaced without restarting EAIWS.

## Imported tax categories

For tax types with many categories, categories can be imported from CSV files instead of being defined individually in `taxes.cfg`. A `taxType` element may contain one or more empty `taxCategories` elements, each identifying a CSV file and the period for which its categories apply. A tax type cannot combine imported categories with categories defined by `taxCategory` elements.

The following XML fragment illustrates an import within a `taxType` element:

```xml
<taxCategories path="taxes/categories-2026.csv"
               from="2026-01-01"
               to="2026-12-31"/>
```

The `taxCategories` element has these attributes:

| Attribute | Meaning |
| --- | --- |
| `path` | Path to the CSV file, relative to the directory containing `taxes.cfg`. |
| `from` | Inclusive lower bound of the validity period, as an ISO date. Defaults to `0001-01-01` if omitted. |
| `to` | Inclusive upper bound of the validity period, as an ISO date. Defaults to `9999-12-31` if omitted. |

The file name, converted to lower case, must end in `.csv` and is used as the internal table name. Different paths in the tax configuration must not refer to different files with the same file name, ignoring case. The same file may be referenced by multiple `taxCategories` elements, including elements belonging to different tax types.

If a tax type has multiple imports, their validity periods must not overlap. The basket tax scheme's tax date determines which import applies.

### CSV format

Each CSV file starts with a header containing the column names, followed by data rows. It must use one of comma (U+002C), semicolon (U+003B), colon (U+003A), tab (U+0009), or space (U+0020) as its field delimiter. The delimiter is determined from the character following the first column name.

| Column | Meaning |
| --- | --- |
| `Code` | Non-empty category identifier. |
| `Amount` | Condition amount returned by the tax access method for this category. A decimal number with optional sign, decimal point and exponent. |
| `Unit` | Tax rate unit: `%`, or a currency code and UNECE unit of measure separated by `/`, for example `EUR/KGM`. |
| `CalcRule` | Calculation rule encoded as a single uppercase letter, using the same codes as `CALC_RULE` in the pricing procedure table `pr_condtypes`. |

For example, a semicolon-delimited file has this header:

```csv
Code;Amount;Unit;CalcRule
```

Fields end at the next delimiter or end of line. Data fields may be enclosed in double quotation marks (`"`); double quotation marks within a quoted field must be doubled. Header column names must not be quoted.

### Category-specific units and calculation rules

An imported category may supply its own rate unit and calculation rule. The rate unit overrides the tax type's rate unit. It determines whether the tax access method returns a percentage or monetary amount and, for monetary amounts, the unit of the quantity relation; the quantity relation's value is one.

A category-specific calculation rule is used as the condition record's calculation rule. If the category supplies none, the condition record has no calculation rule. In EAIWS 4.20, these category-specific settings are supported for imported categories; they cannot be configured on a `taxCategory` element in `taxes.cfg`.

See also: [TaxCategory](/pCon/configuratorOnline/specs/api/basket/types/taxcategory) and [CalculationRule](/pCon/configuratorOnline/specs/api/basket/types/calculationrule).

### Reloading and tax dates

After modifying a CSV file, update the modification timestamp of `etc/taxes.cfg` to force a running EAIWS to re-import the categories.

A basket tax scheme is created on first access as a copy of the corresponding global scheme. Its tax date is the current date in the session time zone at that time. This date selects the applicable imported categories and cannot be set explicitly. Saving and loading an OBK/BSK file preserves the tax date.

[resetTaxScheme](/pCon/configuratorOnline/specs/api/basket/operations/resettaxscheme) discards a specific basket scheme; [resetTaxConfiguration](/pCon/configuratorOnline/specs/api/basket/operations/resettaxconfiguration) discards all basket schemes. The next access creates a new copy with the current date. Reloading the CSV and refreshing an existing basket scheme's tax date are therefore separate steps.

For the SOAP representation of enumerable and imported categories, see [TaxScheme and TaxType](/pCon/configuratorOnline/specs/api/basket/types/taxscheme).
