# Standard Finance payout procedure

## Standard Finance payout procedure

## **Standard Payout Procedure Guide for Clients**

This document outlines the current **standard payout procedure** and options available for clients requesting financial settlements for their events. It also addresses considerations around report frequency, payment timelines, and potential customizations.

***

### **Standard Payout Procedure**

The following is our **default payout workflow**, used by most clients:

1. **Client sends payout request via email to Finance**
   * This typically happens **after the event has ended**.
2. **Finance sends confirmation of the total payable amount**
3. **Client reviews and confirms the amount**
4. **Finance processes payment within 20 working days**
   * The timeline starts **after client confirmation**

***

####

### Weekly Report + Monthly Payout (Required: Minimum total ticket amount: USD 150,000)

* This is only available if the client's expected total amount is USD 150,000 or more.
* The amount can be based on the client’s expected value.
* A hybrid model that allows:
  * **Weekly reporting** for transparency
  * Monthly payout until fully settled, reducing admin effort while offering regular visibility
* Payment would be processed **within 15–20 working days after monthly confirmation**.

***

### **Platform Dashboard Limitations**

While clients may refer to the platform dashboard for real-time registration data, please note:

* **The dashboard does not include refunds** or cancellations
* Therefore, it **does not reflect the actual payable amount**

> 🔍 The dashboard should be used as a **reference only**, not a payment source of truth.

***

### **Recommendations**

* For most clients, we recommend **weekly reporting + monthly payout**, which balances operational efficiency and client needs.
* **Weekly payouts** should only be considered if the **registration amounts are large enough** to justify the effort and ROI.
* Continue using the **dashboard as a reference**, but rely on **Finance-generated reports** for accurate data.

***

If clients have custom requirements outside of the above models, please escalate to Finance or Operations for assessment and approval.


---

# Agent Instructions: 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:

```
GET https://eventx-hq.gitbook.io/knowledge-base/registration-and-ticketing/order-and-finance/standard-finance-payout-procedure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.