> 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/transactions/sending-assets.md).

# Sending assets

How to create a transfer out of an Account on Ledger Enterprise: recipient, amount, fees, notes, and approving it.

**Role: Operators.**

Sending is a Request. You complete the form, approve it with your own key, and the transfer executes once your governance is satisfied.

## Start the transfer

* **From the Accounts list**, use the **Send** action on the Account's row.
* **From the Account page**, use the **Send** action at the top.

Either way the form opens with the Account already set.

## Choose the recipient

What you may enter depends on the Whitelists attached to your Account's send Rules.

<table><thead><tr><th width="316.1953125">Your Account's send Rules</th><th>What you can do</th></tr></thead><tbody><tr><td>Every send Rule has a Whitelist</td><td>Pick a whitelisted destination. You cannot type a free address</td></tr><tr><td>Only some send Rules have a Whitelist</td><td>Pick a whitelisted destination, or type an address</td></tr><tr><td>No send Rule has a Whitelist</td><td>Type an address</td></tr></tbody></table>

Where more than one Whitelist applies, the picker shows which Whitelist each destination belongs to. That matters, because the Whitelist a destination comes from can determine which Rule your transfer falls under, and therefore who approves it.

Any address you type is checked for correct format for the network and screened against sanctions lists before you can continue.

> **Important:** A whitelisted destination expresses governance intent, that this counterparty is permitted. It is not a statement that the destination is safe. Verify a new counterparty's address through a channel other than the one that sent it to you.

## Set the amount

The amount field opens in your countervalue currency and shows the equivalent in the asset. You can switch which you type in, and the value is preserved when you switch.

**Warnings** mean the transfer is unlikely to succeed as entered:

* The amount is above the available balance
* The amount plus the fee is above the available balance
* The amount is below what the network accepts

**Errors** block the Request:

* The amount falls outside every send Rule that applies to you, so no Rule authorizes it
* The fee could not be retrieved

When the amount is valid the form names the **matching Rule**. That Rule states how many approvals this transfer needs.

## Check the fee

The fee is fetched automatically once there is an amount. It shows in both the network's asset and the countervalue. It refreshes every 15 seconds while the form is open.

The figure is a **maximum**, the ceiling authorized for this transfer, not a prediction. The network usually takes less and the difference is not deducted. If the network needs more than the ceiling at execution, the transfer fails with a fee error rather than silently costing more.

Networks offering a choice of speed present fee strategies: see [**Networks**](/help-center-v2/reference/networks.md).

## Add a note

Optional, up to 1,000 characters in the interface, visible to everyone who reviews the Request. The note is the only context an Approver sees on the Request. State what the payment is for, and the internal reference it settles.

## Approve the transfer

When the form is valid, start the review. In the interface, the transfer's details appear on your Ledger device and you confirm them there. An API user signs the Request instead.

* **If yours is the only approval required**, you get a confirmation and the transfer is broadcast.
* **If others must approve**, you see how many approvals remain and can copy a link to the Request to send them.

Closing the confirmation returns you to where you started.

### If something blocks the transfer

You get a message naming the condition, and the transfer cannot be created while it holds. Common cases are a pending Request on the same Account, and insufficient native asset to cover the fee.

> **Note:** The device display is the authoritative one, not the browser. See [**The security model**](/help-center-v2/concepts/the-security-model.md).

## Related

* [**How governance works**](/help-center-v2/concepts/how-governance-works.md)
* [**Reviewing operation history**](/help-center-v2/guides/transactions/operation-history.md)
* [**Statuses and errors**](/help-center-v2/reference/statuses-and-errors.md)
* [**Networks**](/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.enterprise.ledger.com/help-center-v2/guides/transactions/sending-assets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.