# Data Enrichment
source: https://developer.mastercard.com/open-finance-europe/documentation/unlicensed/aiia-data/data-enrichment/index.md

Different modules are used to provide as much data as possible.

### Sorting {#sorting}

Aiia Data always attempts to return transactions in chronological order. However, it is not always possible due to data inaccuracies supplied by the provider.

### Text cleanup {#text-cleanup}

Banks add information to the transaction texts describing payment methods, currency exchange rates, reference numbers and much more. Some merchants may also add similar information to the transaction texts. This makes it more difficult to display and categorise them. To handle this, we clean up the transaction text and provide the original text along with the cleaned-up text:

* `originalText`: This is the raw, unchanged text received from the provider.
* `text`: This is the cleaned-up text, which is more user friendly to display.

Examples:

* `Ali Baba Grill 08021` -\> `Ali Baba Grill`
* `SuperB Vesterbro T 57118` -\> `SuperB Vesterbro T`

### Transaction duplication {#transaction-duplication}

With some providers, bigger changes in the state of the transaction mean that new transactions can be created with new transaction IDs. Such cases cause transactions to be duplicated. Aiia Data handles these by detecting duplicates and 'soft deleting' them. By soft deleting them, we mean setting the `isDeleted` property on specific transactions to `true` and excluding them from the results (unless the requester specifically specifies that soft-deleted transactions should be included).