# Prices with labels

Using pre-defined and configurable labels, you can have more detailed pricing applicable for different types of fees.

Transaction fee types can have multiple related labels. When a transaction is posted with labels, then the related fee is calculated according to the most accurate price according to price hierarchy (See [Special prices](/backoffice-user-guides/iDyT31cW9CYApPltrXUd/accounts-guide/account-price-list/create-prices-for-price-lists/create-special-prices.md)) and the number of matching labels (the more matches, the better).

**For example,** for the price of outgoing SWIFT transactions, you can assign labels for regular or urgent transactions and select counterparty countries.&#x20;

There are different options according to the fee being created. The following table shows the label fields and the respective options present for the fee types.

{% hint style="info" %}
The actual use of these transaction labels depends on the payment module you are running with the Tuum core banking module. Currently, the Tuum payment module supports only one label for SWIFT payments - counterpartyCountry.
{% endhint %}

<table><thead><tr><th width="214.33333333333331">Fee type code</th><th width="174">Labels</th><th>Options</th></tr></thead><tbody><tr><td><p>ACC2INTRA_FEE,</p><p>INTRA2ACC_FEE</p></td><td>accountType</td><td><ul><li>ACC_CURRENCY - Currency account</li><li>ACC_INDIRECT - Indirect account</li><li>ACC_VIRTUAL - Virtual account</li></ul></td></tr><tr><td><p>ACC2LOCAL_FEE,</p><p>LOCAL2ACC_FEE</p></td><td>accountType<br><br><br><br><br>localSchema</td><td><ul><li>ACC_CURRENCY</li><li>ACC_INDIRECT</li><li>ACC_VIRTUAL</li></ul><p></p><ul><li>LOCAL_BACS - UK local payment scheme</li><li>LOCAL_FASTER - UK local payment scheme</li></ul></td></tr><tr><td><p>ACC2SEPA_FEE,</p><p>SEPA2ACC_FEE</p></td><td>accountType<br><br><br><br><br>sepaSchema</td><td><ul><li>ACC_CURRENCY</li><li>ACC_INDIRECT</li><li>ACC_VIRTUAL</li></ul><p></p><ul><li>SEPA_INSTANT</li><li>SEPA_REGULAR</li></ul></td></tr><tr><td><p>ACC2SWIFT_FEE,</p><p>SWIFT2ACC_FEE</p></td><td>accountType<br><br><br><br><br>swiftPriceType<br><br><br><br><br><br><br><br><br>swiftSchema<br><br><br><br><br><br><br><br><br>swiftUrgency<br><br><br><br><br><br><br><br><br>counterpartyCountry</td><td><ul><li>ACC_CURRENCY</li><li>ACC_INDIRECT</li><li>ACC_VIRTUAL</li></ul><p></p><ul><li>PRICETYPE_BEN - Beneficiary type SWIFT payment fee</li><li>PRICETYPE_OUR - OUR type SWIFT payment fee</li><li>PRICETYPE_SHARED - Shared type SWIFT payment fee</li></ul><p></p><ul><li>SWIFT_CHAPS - UK SWIFT payment schema</li><li>SWIFT_CROSSBORDER - SWIFT payment schema Crossborder </li><li>SWIFT_INTRAGROUP - SWIFT payment schema for intragroup payments</li></ul><p></p><ul><li>URGENCY_REGULAR - SWIFT urgency level is regular</li><li>URGENCY_SAMEDAY - SWIFT urgency level is the same day</li><li>URGENCY_URGENT - SWIFT urgency level is urgent</li></ul><p></p><ul><li>COUNTERPARTY_AD - Payment counterparty account country is AD (Andorra)</li><li>COUNTERPARTY_AE - Payment counterparty account country is AE (United Arab Emirates)</li><li>and so on for other countries.</li></ul></td></tr></tbody></table>

## Sample of a transaction fee price with labels

Consider that we want to set up a price for transaction fees for outgoing SWIFT payments based on the following scenario:

* The price is charged to currency accounts.
* The SWIFT fee charge type is SHA (shared). This means that the sender and the beneficiary share the intermediary bank charges for the payment.
* For the first 1000 transactions, €5 fixed fee is charged for each transaction. After that, €10 fee is charged for each transaction.

We are using the sample price list we created before - [**TUUM\_SAMPLE\_PL**](/backoffice-user-guides/iDyT31cW9CYApPltrXUd/accounts-guide/account-price-list/create-price-lists/set-up-a-non-generic-price-list.md). From this price list, we are selecting the **ACC2SWIFT\_FEE** fee type and following these steps:

1. Click the <img src="/files/HKlmjVaU4p5gKJOXiU9t" alt="" data-size="line"> icon to define a price for the fee.\
   The **Create new price for transactional fee** page opens. The **Fee type** and **Price list type code** fields are filled automatically and you cannot edit them.
2. Select the **Fee calculation rule** as **Fixed fee**.
3. Select the **Tier type** as **Amount single**.
4. Select the **Tier application mode** as **Highest**.
5. Select the **Transaction currency code** and **Fee currency code** as **EUR** respectively.
6. Select the date **05.04.2026** for the **Price date from** field. This is the date from which the price is available for fee calculation.
7. **Price date to** is an optional field and you can edit the date later.
8. In the **Labels** section, select the **accountType** as **ACC\_CURRENCY** and **swiftPriceType** as **PRICETYPE\_SHARED**.

<figure><picture><source srcset="/files/EJfEp9NKsivUS48O0q2G" media="(prefers-color-scheme: dark)"><img src="/files/8rUUBtKdC0gIJAYHjKiq" alt=""></picture><figcaption></figcaption></figure>

9. In the **Tiers** section, enter the values as follows:

<figure><picture><source srcset="/files/DZtx7Z8t9kyyAzEhCSUi" media="(prefers-color-scheme: dark)"><img src="/files/p7V6KtFGGCAfWbUbFLnV" alt=""></picture><figcaption></figcaption></figure>

10. Click **Submit**.


---

# 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://docs.tuum.com/backoffice-user-guides/iDyT31cW9CYApPltrXUd/accounts-guide/account-price-list/create-prices-for-price-lists/create-prices-for-transaction-fees/prices-with-labels.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.
