> For the complete documentation index, see [llms.txt](https://docs.selcier.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.selcier.xyz/walkthroughs/send-a-payout.md).

# Send a payout to holders

How a company pays dividends and similar amounts through the DistributionVault, using a record block and pro-rata on-chain claims by holders.

A distribution pays the holders of a share class according to what they held at a record block. Dividends, proceeds from selling the company and other pro-rata payouts all use it. Funding the `DistributionVault` is a one-time step for the company, after which holders claim directly. Because holders pull their own payments, gas costs remain predictable at any holder count, and each claim can be audited. Details are in [Shareholder events](/fundamentals/shareholder-events.md).

{% stepper %}
{% step %}

### Set up the distribution

Go to **Distributions** in the Console, choose **New distribution** and complete these settings:

| Setting           | Details                                                                                                                   |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Share class       | Which class receives the payment                                                                                          |
| Asset             | Defaults to USDG; the Console lists other supported assets                                                                |
| Total amount      | The full sum, shared out pro-rata                                                                                         |
| Record block      | Has to be in the past; unless changed, it is the block right before funding. Numbering follows Robinhood Chain L2 blocks  |
| Excluded accounts | Optional. As many as 20 accounts whose shares get no payment, for example treasury shares or the `LiquidityWindow` escrow |
| Claim deadline    | Optional. At least 12 months after funding                                                                                |

Using the current supply and the class's `uiMultiplier`, the Console shows a preview of the per-share amount.
{% endstep %}

{% step %}

### Add the board resolution

This step takes one upload: the resolution from the board approving the payment. Anchoring it in the `DisclosureRegistry` as a `BOARD_RESOLUTION` gives holders a way to connect the payment with the decision that authorized it.
{% endstep %}

{% step %}

### Get sign-off and fund the vault

Send it to **Approvals**. After signers approve, the total moves from the treasury into the `DistributionVault`, which emits `DistributionFunded` carrying the distribution ID, asset, amount and record block. Funding can't be undone: for as long as the distribution is active, the money stays locked in the vault.

`POST /v1/distributions` offers the same create-and-fund path through the API.
{% endstep %}

{% step %}

### Let holders claim

Balances at the record block set entitlements: a holder's portion is their balance at that block divided by the eligible supply, which is total supply less excluded balances. The distribution appears in [Portfolio](/the-platform/holder-portfolio.md), where a holder claims with one action. `DistributionClaimed` is emitted per claim, with gas sponsored. Portfolio is also able to claim for a holder through `claimFor`, and payment still goes to the holder.

Moving tokens after the record block doesn't cost a holder their entitlement, and acquiring tokens after it doesn't earn one.
{% endstep %}

{% step %}

### Follow claims and wrap up

**Distributions** reports the amount claimed and the number of holders who claimed. Holders who have yet to claim get reminders from Portfolio. Unclaimed funds remain claimable until any deadline you set. Once a deadline passes, the company can sweep the remainder back to the treasury.
{% endstep %}
{% endstepper %}

## Exits through acquisition

An acquisition routes the purchase consideration through this same vault. The registrar burns the class's tokens as part of the exit, while holders claim what they are owed of the consideration. Every burn emits `SharesRedeemed` referencing the transaction record, which makes the whole exit traceable in the [Explorer](/the-platform/public-explorer.md).

{% hint style="info" %}
Your own systems can reconcile payouts in real time using the `distribution.funded` and `distribution.claimed` [webhooks](/build-on-selcier/event-delivery.md).
{% endhint %}


---

# 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://docs.selcier.xyz/walkthroughs/send-a-payout.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.