> For the complete documentation index, see [llms.txt](https://market-launchpad-com.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://market-launchpad-com.gitbook.io/docs/fees/fee-status-and-receipts.md).

# Fee states and payment receipts

A number beside a business is useful only when its meaning is clear. Planned, attributable, claimable and paid amounts must be read separately.

> Public business payouts are currently closed. Business requests are open for review. This guide does not confirm any balance, approved claim or payment entitlement.

## Read the state before the amount

| State                   | Meaning                                                                    | What it does not establish                     |
| ----------------------- | -------------------------------------------------------------------------- | ---------------------------------------------- |
| Planned policy          | The intended fee rate and allocation                                       | A deployed configuration or a collected amount |
| Estimated fees          | A calculation based on stated assumptions                                  | Fees actually received                         |
| Collected fees          | An amount actually received under the relevant collection rights           | That all of it belongs to the business         |
| Business share reserved | An attributable business allocation recorded under the applicable policy   | Verified authority or a completed payment      |
| Claim available         | The applicable prerequisites allow a verified recipient to request payment | That payment has been sent                     |
| Payment pending         | A payment is being processed or awaits confirmation                        | A finalized transfer                           |
| Paid                    | The actual transfer is finalized and supported by its receipt              | A promise that future fees will exist          |

## What a payment receipt should explain

A useful receipt identifies the asset, amount, recipient, covered period or claim, and finalized transaction. Check that the destination matches the verified payment recipient and that the explorer shows a successful transfer.

Amounts in different assets cannot be silently added together. A converted display value needs its own valuation context; it does not change the assets actually transferred.

## Corrections and disputed records

Verification can reveal a duplicate business, the wrong branch, an incorrect authority claim or an attribution error. The affected record may require review before a claim or payment can proceed.

An information correction does not reverse a finalized blockchain transfer. Do not treat a pending review as a promise of recovery or compensation.

## Citizen payout achievement

**First Business Payout** requires an actual finalized payment through the verified workflow. A reserved share, a claim submission or an estimated amount does not unlock it.

See [claiming fees](https://market-launchpad-com.gitbook.io/docs/business/claiming-fees), [the achievement catalog](https://market-launchpad-com.gitbook.io/docs/citizens/achievement-catalog) and [worked examples](https://market-launchpad-com.gitbook.io/docs/fees/examples).