> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/help-center-v2/guides/accounts/finding-accounts-and-balances.md).

# Finding Accounts and balances

How to find an Account on Ledger Enterprise, what the Accounts list and the Account page show, and what each balance actually means.

**Role: Operators and Administrators.**

## The Accounts list

**Accounts** lists every Account you can see, newest first. Select the **Name** column to sort by name instead.

Each row shows the Account name, its asset and the asset's icon. For a token, the network appears beside the asset name. The total balance appears in the asset and in your countervalue currency. Where your Workspace uses Portfolios, a column shows which ones each Account belongs to.

<table><thead><tr><th width="189.21875">Action on a row</th><th>Who sees it</th></tr></thead><tbody><tr><td>Receive</td><td>Everyone</td></tr><tr><td>Send</td><td>Operators</td></tr><tr><td>Edit</td><td>Administrators</td></tr><tr><td>Add to Portfolios</td><td>Master Administrators</td></tr></tbody></table>

**Edit** can be unavailable. Its tooltip then gives the reason: see [**When editing is blocked**](https://help.enterprise.ledger.com/help-center-v2/guides/accounts/creating-and-editing-accounts.md#when-editing-is-blocked). **Add to Portfolios** appears only where Portfolios are enabled for your Workspace.

Each row also has a menu of more actions, with **Copy link to Account**. For an Operator, the menu also lists the operations they can create on that Account: **Sign message**, **Stake**, **Interact with contract** and **Deploy contract**.

An Account that is not active shows an **INACTIVE** badge in place of these actions. You cannot create operations on it.

An Account on a deprecated network shows a **Deprecated** badge in place of its balance. See [**Deprecated networks**](#deprecated-networks).

A Hedera Account that is not activated shows an **Inactive** tag in place of its balance. See [**Hedera**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/hedera.md).

Search finds an Account by its name or its ID. To narrow by coin or ticker, use the **Asset** filter. The **Groups** filter is always available. The **Users** filter is for Administrators only. **Policies** appears when the Workspace has some. **Portfolios** appears where Portfolios are enabled.

Through the API, you can also filter Accounts by address. The address must match exactly, but letter case is ignored. See the [API documentation](https://help.enterprise.ledger.com/api-documentation-v2).

### Which Accounts you can see

Administrators see every Account in the Workspace. An Operator sees an Account in two cases:

* A Rule of the Account names the Operator, directly or through a group. Any Rule counts, as **Creator** or in an approval step.
* Where Portfolios are enabled: the Account is in a Portfolio that lists the Operator under **Read-only users**. See [**Portfolios**](https://help.enterprise.ledger.com/help-center-v2/administration/governance/portfolios.md).

When an Operator sees no Account, the list shows **No Accounts**. Below it, the message reads "An Administrator must create the first Account. This message shows even when the Workspace has Accounts that the Operator cannot see. To give an Operator access, a Master Administrator names them in the Rules of the Account, or adds them to a Portfolio that holds it.

## The Account page

Every Account has an **Overview**, **Rules** and **Account info** tab. It also has an **Operations** tab, except a Hedera Account that is not yet activated, and an Account on a deprecated or Direct Access network. Other tabs depend on the Account, and on you:

* **UTXOs**: Bitcoin Accounts.
* **Token Accounts**: native Accounts on networks with tokens.
* **Linked Accounts**: native Accounts on EVM networks. See [**Ethereum**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/ethereum.md#linked-accounts).
* **Staking**: native Accounts that support staking. On EVM networks, only where Ethereum staking is available.
* **Messages**: when you can sign messages on the Account.

<table><thead><tr><th width="195.58984375">Account info field</th><th>Meaning</th></tr></thead><tbody><tr><td>Network</td><td>The chain the Account lives on, with its network ID to copy</td></tr><tr><td>Token contract address</td><td>For a token Account, the token's contract</td></tr><tr><td>Derivation path</td><td>The Account's position in the key hierarchy, useful for reconciliation</td></tr><tr><td>xPub</td><td>The extended public key, with a copy button. Bitcoin Accounts only. The tab warns you not to share it</td></tr><tr><td>Address type</td><td>Static or Dynamic (Bitcoin Accounts only)</td></tr><tr><td>Portfolios</td><td>The Portfolios the Account belongs to, or "Not in any Portfolio". Shown where Portfolios are enabled. Master Administrators can link or edit Portfolios from here</td></tr></tbody></table>

**Back** returns you to the list with your filters in place.

### Deprecated networks

When Ledger Enterprise stops support for a network, the network becomes deprecated. Its Accounts stay visible for history and audit, but nobody can create operations on them.

* The Accounts list and the Account header show a **Deprecated** badge. Its tooltip reads "Ledger Enterprise no longer supports", followed by the network name.
* The **Overview** shows the banner **This network is deprecated** in place of the balances.
* The **Operations**, **UTXOs**, **Token Accounts** and **Staking** tabs do not show.
* **Receive**, **Send**, **Edit** and **Add to Portfolios** are unavailable. Their tooltip gives the same reason.

The API refuses new operations, Account edits and Portfolio changes on these Accounts. It returns a balance of 0 for them.

### Direct Access networks

On a Direct Access network, Ledger Enterprise does not track the on-chain status of operations. The **Overview** of the Account shows the banner **Transaction history unavailable**, and the Account has no **Operations** tab. Check each transaction in a block explorer. Through the API, the transaction list of the Account is empty.

## What the balances mean

Every amount appears in the asset's units and in countervalue.

<table><thead><tr><th width="160.60546875">Balance</th><th>Meaning</th></tr></thead><tbody><tr><td>Total balance</td><td>Everything the Account holds</td></tr><tr><td>Pending</td><td>The amount of the Account's transaction Requests that have not completed, plus their maximum fee. On a token Account, the amount only: the parent Account pays the fee</td></tr><tr><td>Available balance</td><td>Total, minus Pending, minus any minimum balance the network requires. It is never below 0</td></tr></tbody></table>

**Available is the figure that governs a transfer.** It can sit below Total because Requests are pending, or because the network keeps a minimum balance. The send form checks the amount plus the maximum fee against it.

The **Overview** also shows figures specific to some networks:

* On Accounts that support staking, a **Total staked** tile. Staking positions have their own figures on the **Staking** tab.
* On Tron, **Bandwidth** and **Energy** tiles. See [**Tron**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/tron.md).
* On Bitcoin, a **Balance details** card. It shows **Strictly available** and **Dust**, and the UTXO confirmation rows **Incoming 0**, **Incoming 1 - 6**, **Incoming 6+** and **Outgoing 0**. See [**Bitcoin**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/bitcoin.md).

## Token Accounts

On networks with tokens, a token Account attaches to a **parent Account**. The parent holds the native asset. It pays the network fees for every token Account beneath it.

The parent's **Token Accounts** tab lists every token the parent holds. Each row shows the token Account name, or the token name where there is no token Account, and the ticker. It shows one balance: the countervalue, with the token amount beneath.

A row with a token Account has the same actions as the Accounts list. A token with no token Account shows a **View only** tag. Its tooltip reads "An Administrator must define the Rules for this token."

Administrators can select **Define Account Rules** on that row to create the token Account.

### Tokens received without a token Account

A parent Account can receive a token that has no token Account. The token then shows on the **Token Accounts** tab with the **View only** tag. Its balance shows, but the row has no **Send** action. The token cannot leave the Account until its token Account exists.

**Role: Master Administrators.** Every Administrator sees **Define Account Rules**, but creating an Account is a Master Administrator task.

1. Open the parent Account.
2. Open the **Token Accounts** tab.
3. On the row of the token, select **Define Account Rules**. The **Create Account** form opens, with the token and the parent Account already set.
4. Name the Account.
5. Set the Rules.
6. Select **Review**.

The result is an Account creation Request that Master Administrators approve. See [**Creating and editing Accounts**](https://help.enterprise.ledger.com/help-center-v2/guides/accounts/creating-and-editing-accounts.md).

**Define Account Rules** is unavailable while a creation Request for that token Account is pending. Its tooltip then reads "A Request to create this Account is already in progress."

A token Account can exist only for a token in Ledger's asset catalog. See [**Networks and tokens in your Workspace**](https://help.enterprise.ledger.com/help-center-v2/reference/networks.md#networks-and-tokens-in-your-workspace).

From a token Account you can see and open its parent. **If a token transfer fails for want of fees, fund the parent**, not the token Account.

## Unspent outputs

On Bitcoin Accounts, the **UTXOs** tab lists the individual unspent outputs that make up the balance. Each row shows the **Address**, **Spendability**, **Height**, **Confirmations** and **Amount**.

Sort the list by **Height**, **Confirmations** or **Amount**. Filter it by **Amount** and **Height**. Select **Hide unspendable** to hide the outputs marked **Not worth spending**.

This is a **read-only** view for reconciliation and for understanding why a transfer's fee is what it is. You cannot choose which outputs fund a transfer. See [**Bitcoin**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/bitcoin.md).

## Governance on an Account

The **Rules** tab shows the Rules applying to this Account: who may perform each operation type, within what amounts, to which destinations, and who approves.

Operators can read this. It is the quickest way to understand why a transaction is or is not possible before attempting it. Operators see their own name, and the names of the groups they belong to. Other users and groups appear as **Anonymized**. Administrators see full detail.

If you do not have access to the Account's Policy, the tab shows "No access to this Policy" in place of the Rules.

If the Account uses a shared Policy, the tab is read-only and names the Policy. See [**Policies**](https://help.enterprise.ledger.com/help-center-v2/administration/governance/policies.md).

## Related

* [**Reviewing operation history**](https://help.enterprise.ledger.com/help-center-v2/guides/transactions/operation-history.md)
* [**Sending assets**](https://help.enterprise.ledger.com/help-center-v2/guides/transactions/sending-assets.md)
* [**Receiving assets**](https://help.enterprise.ledger.com/help-center-v2/guides/transactions/receiving-assets.md)
* [**Networks**](https://help.enterprise.ledger.com/help-center-v2/reference/networks.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.enterprise.ledger.com/help-center-v2/guides/accounts/finding-accounts-and-balances.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
