> 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/automation/triggers/workflow-trigger-payout-validated.md).

# Workflow trigger: Payout validated

The [payout process](/partner-incentives/payouts/payout-process.md) involves different activities, which might make it challenging to keep up, especially when you expect your partner to provide an invoice or validate rewards once the payout has been created. However, you can use the Payout validated trigger to automatically follow up with your partner until they have accepted the payout. We will look at how you can set this trigger.

## Configure Payout validated trigger

Payout validation will be triggered if the status of the payout moves from **Draft** to **Pending**. Follow these steps to get started:

* Go to **Workflows,** click **New Workflow**, **Name** the workflow, and press **Add**
* Open **Choose trigger** and choose the workflow to be triggered when **Payout validated**
* Click **Confirm**

With Kiflo, there are different payout statuses; **Draft, Pending, Ready,** and **Paid status.**

When a payout moves from the **Draft status** to a **Pending status**, it will trigger the workflow as the payout has been validated and requires actions from the partner, like attaching an invoice or reviewing the rewards.

If a payout moves from the **Draft status** and is immediately **Validated** because no actions are required from the partner, it will move to the **Ready status**. This means the workflow won’t be triggered.

## Common use cases

### Ensure a quicker and simpler payout process

To ensure a quicker and simpler payout process for partners, you can use the *Payout validated* trigger. If, for example, the only thing needed to payout is a partner uploading an invoice, you can create a follow-up sequence to ensure the partner uploads it. You could, for example, send two emails and then one task if the partner hasn’t uploaded the invoice.


---

# 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/automation/triggers/workflow-trigger-payout-validated.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.