---
title: "What is a transaction type alias?"
slug: "what-is-a-transaction-type-alias"
updated: 2024-12-19T17:09:43Z
published: 2024-12-19T17:09:43Z
canonical: "support.lusid.com/what-is-a-transaction-type-alias"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.lusid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What is a transaction type alias?

An *alias* is a component of a [transaction type](/v1/docs/what-is-a-transaction-type). It defines the name, and certain other characteristics.

A transaction type must have at least one alias, for example `Buy`. It can have any number of additional aliases, for example `Acheter` and `Kaufen`. This enables transactions upserted into LUSID with the same semantic meaning to have an identical economic impact. [See how to set this scenario up](/v1/docs/ensuring-different-transaction-codes-have-the-same-economic-impact).

An alias has the following data fields:

| **Data field** | **Status** | **Explanation** |
| --- | --- | --- |
| `type` | Mandatory | Defines the name of the transaction type, for example `BuyWithCommission`. Note names are case-sensitive. |
| `description` | Mandatory | Describes the transaction type. |
| `transactionClass` | Mandatory | Groups the transaction type with others that have the same economic impact for reporting purposes, in conjunction with the role (below). [More information](/v1/docs/how-do-transaction-type-class-and-roles-work). |
| `transactionRoles` | Mandatory | Groups the transaction type with others that have the same economic impact for reporting purposes, in conjunction with the class (above). [More information](/v1/docs/how-do-transaction-type-class-and-roles-work). |
| `isDefault` | Mandatory (defaults to `False`) | Set to `True` to nominate this transaction type as the default for its source. If a transaction with an unrecognized type is upserted into LUSID, it resolves to this transaction type. [See how LUSID resolves transactions to transaction types](/v1/docs/how-does-lusid-resolve-transactions-to-transaction-types). |