> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/owners-playbook/accounting-and-stripe/revenue-reconciliation/1099s-for-coaches/payment-process-for-coaches.md).

# Payment Process for Coaches

#### Overview

If you are paying a Coach through the PodPlay system, Coaches set up their public profile, availability, rates, and payout Stripe accounts inside the Dashboard, from within their Coach Settings. Once completed, the Coach will receive money to their Stripe account.

* Coaches are paid weekly
* There is a minimum 2-day delay with payments processed on Stripe
* Payouts are on Fridays, with a Thursday - Wednesday pay period

#### Pay a Coach in Two Ways

There are two ways a Coach can make money:

1. **Reservations (private lessons)**
   1. A Customer reserves a Court and adds a Coach to their Reservation.
      1. The Court rate is strictly for the Club, and the Coach Rate (hourly) is set in the Coach Settings
         1. The Coach Rate can be split further between Coach and Club, with either a % value or a $ value
      2. If there is an additional split, i.e. a Lesson is $60 = Court costs $10 (Club receives), Coach costs $50
         1. Revenue to the Club is $20 = $10 for the Court +$10 from Coach Lesson (20% of $50)
         2. And the Coach receives $40
      3. If there is not an additional split, i.e. a Lesson is $60 = Court costs $10 (Club receives), Coach costs $50, with a split of 0% between Club and Coach, then:
         1. Revenue to the Club = $10 for the Court
         2. And the Coach receives $50
      4. For longer Reservations, the cost of both the Court and the Coach goes up as the rates are based on a per-hour basis
   2. The payout method is a letter V shape
      1. The funds move from the Customer and are split between Club and Coach
         1. With another potential split on the funds heading to the Coach
2. **Events (Clinics, Private Events, Parties)**
   1. For any Event where a Coach is added, the rate is set during the process of adding a Coach.
      1. If the Coach rate is set at $50, the Coach receives $50 for lessons during that Event
         1. It doesn't matter if the Event is 1 hour or 2 hours, the rate is static (does not change)
         2. It does not matter if there are 4 Customers who join the Event or 10 Customers, the rate for the Coach is set
      2. The Coach is paid from the Club's Stripe account
   2. The Club decides the cost for the Customer to join the Event
      1. The Club will receive Customer funds, regardless if 4 Customers or 10 Customers join the Event
   3. The payout method is a letter L shape
      1. The funds move from the Customer to the Club, and the Club pays the Coach

<figure><img src="/files/Lauvgdy9mepzRoqFB97z" alt=""><figcaption></figcaption></figure>

***

**Note for PodPlay's International Clients**: Coaches are not paid through the PodPlay system if the Club is located outside of the U.S. The reason for this is that paying a Coach through the system would require a cross-border transfer, resulting in a currency exchange. Coaches at Clubs located outside of the U.S. should still be added properly to all Events and Coaching lessons, then the Club pays the Coach outside of the system. Clubs can easily manage how much a Coach needs to be paid using the Export button on the Coach page in the Dashboard. Data included inside the exported CSV includes:

* A list of all private lessons, clinics, and other activities each Coach taught
* How much money was listed on the Coach's rate during each lesson, clinic, or event

This CSV provides a clear, organized summary of Coach compensation.


---

# 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.podplay.app/owners-playbook/accounting-and-stripe/revenue-reconciliation/1099s-for-coaches/payment-process-for-coaches.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.