Skip to main content
Skip table of contents

FAQs Labelled Transactions

What are labelled transactions?

Labelled transactions are regular financial transactions that have been enriched with additional context using labels. Labels act like “stickers” attached to transactions, making it possible to identify relevant information such as loans, insurances, or tax-relevant payments.

Why is labelling important?

Raw transaction data is usually unstructured and provides little insight into a customer’s life situation or financial obligations. Labelling adds context, making it easier to filter, analyze, and extract meaningful information.

What are “Levels of Detail” (LoD) in labels?

Labels are structured into Levels of Detail to provide different depths of information:

  • LoD 1: Broad, general categories (e.g., INSURANCE, BANKANDCREDIT).

  • LoD 2–4: Increasingly specific details (e.g., BANKANDCREDIT → LOANANDINTEREST → CARLOAN).
    This allows filtering at both a high-level and highly detailed level, depending on the use case.

Can a transaction have multiple labels?

Yes. A single transaction can have several labels across different categories. For example, a car loan transaction could be labeled both under BANKANDCREDIT → CARLOAN and under MOBILITY → CARLOAN, serving different analysis perspectives.

Who defines the label set?

The label set and labelling rules are developed and continuously refined internally. External modifications are not possible. The system uses a combination of expert rules, keyword recognition, and AI-based methods to ensure accuracy and continuous improvement.

What data is required for labelling?

The more information provided, the better the labelling results. The mandatory fields are:

  • transactionId (transaction identifier)

  • accountId (account identifier)

  • amount (transaction amount)

Optional fields (improve accuracy): purpose, counterpartName, type, typeCodeZka, typeCodeSwift, sepaPurposeCode, counterpartCreditorId, counterpartMandateReference, counterpartAccountIban, counterpartBic, accountIBAN, accountHolderName.

How is labelling different from traditional transaction categorization?

Traditional categorization forces a transaction into a single category. Labelling, however, attaches multiple relevant contexts, allowing greater flexibility and better insights into customer behavior and obligations.

Which languagues are supported by labeling?

At the moment, labeling is available for German-language accounts (e.g., DACH region) as well as for Dutch.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.