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

# Creating an Asset

> Create a new Asset in the Console — currency, crypto, commodity, or custom — and set the code that Accounts and Transactions use.

An Asset defines the unit of value that Accounts and Transactions use inside a Ledger. Create Assets before you create Accounts, because every Account uses one Asset.

## Before you start

***

You need an existing Organization and Ledger. Decide whether the Asset is a currency, crypto asset, commodity, or another custom unit of value.

<Warning>
  Choose Asset codes carefully. Accounts and Transactions depend on them.
</Warning>

## Create the Asset

***

<Steps>
  <Step>
    From the **Assets** page, click the **New Asset** button.
  </Step>

  <Step>
    The **New Asset** form opens on the right side of the screen.
  </Step>

  <Step>
    Select the **Type** of Asset.

    * *Crypto*: for cryptocurrencies such as Bitcoin, Ethereum, and Ripple.
    * *Commodity*: for tradable raw materials such as gold, natural gas, soybeans, and corn.
    * *Currency*: for currencies such as Brazilian Real, US Dollar, and Euro.
    * *Others*: for any other type of Asset.

    <Danger>
      You **cannot** reuse an Asset name or code in the same Ledger. Both the name and the code must be **unique**.
    </Danger>
  </Step>

  <Step>
    Specify the **Asset Name**.
  </Step>

  <Step>
    Specify the **Code** for the Asset. Use uppercase letters only.

    * If the Asset is a currency, select its code from the [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217#List_of_ISO_4217_currency_codes) list.
  </Step>

  <Step>
    \[Optional] Select the **Metadata** tab to add custom metadata.
  </Step>

  <Step>
    After you fill in the fields, click the **Save** button.
  </Step>

  <Step>
    The Asset appears in the list of available Assets for your Ledger.
  </Step>
</Steps>

<Note>
  Saving an Asset also provisions a system-managed External Account when one does not already exist for that Asset code. Its canonical alias is `@external/<asset-code>`.
</Note>

<Tip>
  The fields in the Metadata tab are open. There are no predefined keys or values. Use consistent key names across your Organization, such as `country`, `settlementNetwork`, or `regulatoryClass`, so you can filter and audit Assets later.
</Tip>

## Field guide

***

| Field          | What to enter                                                                                                                                  | Example             |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- |
| Type           | Asset category. Use `Currency` for fiat money, `Crypto` for crypto assets, `Commodity` for tradable commodities, or `Others` for custom units. | `Currency`          |
| Asset Name     | Human-readable Asset name shown to operators.                                                                                                  | `Brazilian Real`    |
| Code           | Asset code in uppercase letters. For currencies, use the ISO 4217 code.                                                                        | `BRL`               |
| Metadata Key   | Optional classification or integration field name.                                                                                             | `settlementNetwork` |
| Metadata Value | Value for the metadata key.                                                                                                                    | `pix`               |

## What to do next

***

After creating the Asset, create Accounts that use it in [Creating an Account](/en/midaz/console/creating-an-account).

<Card title="API equivalent" type="tip" horizontal>
  [Create an Asset endpoint](/en/reference/midaz/create-an-asset)
</Card>