# The Categorization Taxonomy

In general, each account transaction is assigned exactly one category. The current classification system distinguishes four main sections for the categorization of these transactions:

> K        Expenses attributed to individual consumption (e.g. groceries, rent)\
> E        Received payments (any incoming payment)\
> A        Expenses not attributed to individual consumption (e.g. taxes, alimony payments)\
> N        Neutral positions (turnover amount equals or is close to zero) 

Each section is divided into further categories or subcategories. If a transaction cannot be clearly assigned to a particular (sub)category, it is classified one level higher and, in extreme cases, it may even be categorized under the topmost section. An example of the scheme for insurance expenses is

| Level 1 | Level 2 | Level 3 | Level 4 | Description                                |
| ------- | ------- | ------- | ------- | ------------------------------------------ |
| K.8     |         |         |         | Consumption expenses in the finance sector |
| K.8     | .1      |         |         | Insurance services                         |
| K.8     | .1      | .1      |         | Property insurance                         |
| K.8     | .1      | .1      | .1      | Building insurance                         |
| K.8     | .1      | .1      | .2      | Home contents insurance                    |
| K.8     | .1      | .1      | .3      | Pet insurance                              |
| K.8     | .1      | .2      |         | Asset insurance                            |
| ...     | ...     | ...     | ...     | ...                                        |

Syntactically, the individual levels are separated from each other by dots, so that a categorisation can be used to uniquely determine the root category by reducing the category around the part after the last dot. It is ensured that each category has a valid root category. Syntactically, the categories always follow the Regex scheme:

```python
[AEKN](\.[1-9][0-9]*){0,4}
```

As the standard categorization scheme can be augmented at any time, please make sure to always use a category "and all its sub-categories" whenever you do analyses over a category to get complete results. For instance, if we decided that a category K.8.1.1.4 is needed (whatever it be), turnovers that are now categorised as K.8.1.1 would then be classified to the new K.8.1.1.4. If this possibility is neglected, these turnovers would be excluded from assessment altogether.

{% hint style="info" %}
The full documentation is available for our customers upon request to the sales representative.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guide.xs2a.com/xs2a/integration-cs/additional-guides/the-facts-system/the-categorisation-taxonomy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.