> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/partner-incentives/payouts/payout-process.md). # What is the payout process? Managing payments can be tricky. You should validate all the rewards, probably ask your partners to send invoices, or even ask them to review the rewards before you can actually do the payments. The payouts workflow on Kiflo is designed to help you manage this process. ## What is a payout? A payout is the aggregation of all earnings/rewards a partner needs to be paid. All payouts in Kiflo are created by channel managers from the rewards that are generated for a partner. A payout is always related to one and only one partner, for one specific currency. ## What is the workflow? Payouts go from one status to another to reflect the current state of the process. Here is what it looks like: ![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-51a03baa48f3ab330e88ca8895a8c1bfdc03660f%2F61a696c4663c7a603de8da1c.png?alt=media) ### In short New payouts are **Drafted**. Then you can **Validate** them once you've reviewed all the rewards, and ask your partners to do additional actions (like sending an invoice). Once you've received the invoice, you can **Accept** the payout, pay the partner, and **Mark as Paid** the payout. ### In details #### Draft Status The payout has been created and has not been validated by the channel manager or the rewards have not been accepted/refused. Draft payouts are not visible to partners. **Validate** the payout, and optionally ask your partner to send an invoice or review the rewards included in the payout. The partner will then be notified and will know they have actions to perform. #### Pending Status The payout has been validated and is waiting for the partner's validation. A **Pending** payout is visible to the partner, and the partner can upload an invoice, or review the included rewards. You have nothing do to in this state, basically, you are waiting for the partner. The partner will then **Validate** the payout, once everything is OK on their side. You will be notified the payout has been validated by the partner. #### Ready Status The payout has been validated by the partner and is **R\*\*\*\*eady** to be paid. The partner sees the same state and knows the payout is ready to be paid. In this state you can choose the export the payout, using the more appropriate export format. Once the payment is done, you can **Mark as Paid** the payout. The payout will move to its final state: **Paid**. #### Paid Status The payout has been paid. At this stage, the partner knows the payment is on its way! ## In practice (short video) {% embed url="" %} --- # 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://docs-vnext.kiflo.com/partner-incentives/payouts/payout-process.md?ask=&goal= ``` `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.