---
title: "What built-in transaction types and sides are provided with LUSID?"
slug: "what-built-in-transaction-types-and-sides-are-provided-with-lusid"
tags: ["transaction types"]
updated: 2026-02-16T14:21:01Z
published: 2026-02-16T14:21:01Z
canonical: "support.lusid.com/what-built-in-transaction-types-and-sides-are-provided-with-lusid"
---

> ## 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 built-in transaction types and sides are provided with LUSID?

LUSID has a number of built-in [transaction types](/v1/docs/what-is-a-transaction-type) and [sides](/v1/docs/what-is-a-side) that model basic economic behavior.

These are useful to get started, but we recommend creating your own universe of [custom transaction types](/v1/docs/how-do-i-create-a-transaction-type) for a production system. [See how to remove the built-in types](/v1/docs/how-do-i-remove-the-built-in-transaction-types-and-sides).

> **Note**: Built-in transaction types and sides are domiciled in the `default` scope and in the `default` and `alt1` sources. [More information on scopes and sources](/v1/docs/grouping-related-transaction-types-using-scopes-and-sources).

## Built-in transaction types

LUSID provides a number of built-in transaction types such as `Buy` and `Sell`.

To list the built-in transaction types, [obtain an API access token](/v1/docs/how-do-i-obtain-and-use-a-short-lived-api-access-token-from-okta) and call the [ListTransactionTypes](https://www.lusid.com/docs/api/#operation/ListTransactionTypes) API for the `default` scope, for example:

```json
curl -X GET 'https://<your-domain>.lusid.com/api/api/transactionconfiguration/types?scope=default'
  -H 'Authorization: Bearer <your-API-access-token>'
```

Note it is possible to [domicile your own custom transaction types](/v1/docs/how-do-i-create-a-transaction-type) in the `default` scope.

To get the definition (aliases, movements and sides) of a built-in transaction type such as `Buy`, call the [GetTransactionType](https://www.lusid.com/docs/api/#operation/GetTransactionType) API for the `default` source and `default` scope, for example:

```json
curl -X GET 'https://<your-domain>.lusid.com/api/api/transactionconfiguration/types/default/Buy?scope=default'
  -H 'Authorization: Bearer <your-API-access-token>'
```

For an in-depth explanation of the built-in `Buy` transaction type, see [this article](/v1/docs/understanding-how-lusid-uses-transaction-types-to-generate-holdings#examining-the-built-in-lusid-transaction-types).

## Built-in sides

At the time of writing, LUSID has four built-in [sides](/v1/docs/what-is-a-side): `Side1`, `Side2`, `BondInt` and `Side2WithoutBondInterest`.

These are domiciled in the `default` scope and can only ultimately belong to transaction types also domiciled in the `default` scope. If you want to use a built-in side with your own transaction type in a custom scope, you must [recreate the side](/v1/docs/how-do-i-create-a-side) in that scope.

To get the definition of a built-in side such as `Side1`, call the [GetSideDefinition](https://www.lusid.com/docs/api/#operation/GetSideDefinition) API for the `default` scope, for example:

```json
curl -X GET 'https://<your-domain>.lusid.com/api/api/transactionconfiguration/sides/Side1?scope=default'
  -H 'Authorization: Bearer <your-API-access-token>'
```

For convenience, definitions for the built-in sides are summarised below. See [this article](/v1/docs/what-is-a-side) for more information on the allowed values.

| **Field** | **Side1** | **Side2** | **BondInt** | **Side2WithoutBondInterest** |
| --- | --- | --- | --- | --- |
| `security` | `Txn:LusidInstrumentId` | `Txn:SettleCcy` | `Txn:SettleCcy` | `Txn:SettleCcy` |
| `currency` | `Txn:TradeCurrency` | `Txn:SettlementCurrency` | `Txn:SettlementCurrency` | `Txn:SettlementCurrency` |
| `rate` | `Txn:TradeToPortfolioRate` | `SettledToPortfolioRate` | `SettledToPortfolioRate` | `SettledToPortfolioRate` |
| `units` | `Txn:Units` | `Txn:TotalConsideration` | `Txn:BondInterest` | `BaseOnSeparateBondInterest` |
| `amount` | `Txn:TradeAmount` | `Txn:TotalConsideration` | `Txn:BondInterest` | `BaseOnSeparateBondInterest` |
| `notionalAmount` | `0` | `0` | `0` | `0` |