> For the complete documentation index, see [llms.txt](https://docs.echevarrisports.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.echevarrisports.com/guia/en/step-by-step/cerrar-mes-entrenador.md).

# Close a coach's month

How a coach's pay for a month is worked out and closed.

{% hint style="info" %}
For: Direction and Financial Control. Direction decides pay conditions and extra hours.
{% endhint %}

## Before you start

The coach's profile needs complete **Pay conditions**: how they're paid (payroll or self-employed), contract hours a week or class hours included per month, and the extra-hour price. If they're missing, the person shows in **Team › Pending** and their month says "No pay conditions yet. Set it up…".

![Pay conditions, in the Profile](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-c3a8a9b1b2b11f3a55043e5ba079e534aa961483%2Fperson-profile.png?alt=media)

## 1. Close the month's classes

A class counts for pay once it's closed, meaning attendance has been taken. Usually the coach does it from their app (`/coach`).

1. Go to **Team**, open the coach and go to **Schedule**.
2. Check **Needs closing**: past sessions not closed yet.
3. Click each one. Group sessions open straight on their attendance register; the rest open in the Calendar. Take attendance and save.

![Step 1: the coach's Schedule](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-30d13c3e66402adccf4badd23b244356c57c935e%2Fperson-schedule.png?alt=media)

## 2. Review the month

Go to the coach's **Pay** tab and pick the month. You'll see:

* **Classes**: the month's classes, closed and not closed.
* **Class hours**: the hours paid and their amount.
* **Other payments or deductions**: bonuses, hours at an event, deductions or days off given back.
* **Salary**: the salary, showing **Payroll pending** until the payslip is uploaded.
* **Extra hours**: extra hours, showing **Draft** until they're validated.

![Step 2: the coach's month](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-ee4913d8a0f15263eb8ed249ce9345f92e1f94d1%2Fperson-pay.png?alt=media)

Direction chooses how to count the extra hours and, if needed, a different price for this month. Add any adjustments under **Other payments or deductions**: each one needs a note, for example "Bonus for objectives" or "Event on 12 Oct". A negative amount is a deduction.

## 3. Validate and close

Direction clicks **Validate & close** under **Extra hours**.

* If an earlier month is still open, close it first.
* Extra hours paid in the payslip or the invoice aren't marked paid: closing is the last step.
* Reopening a closed month needs a reason. Extra hours already paid aren't reopened: correct them in a later month with an adjustment.

## 4. Payslip or invoice

* **On payroll**: upload the payslip PDF under **Payslips**, in the Profile (or several at once from the team list). The CRM reads it and warns you if the salary doesn't match the profile. Once it's uploaded, **Salary** is no longer pending.
* **Self-employed**: enter their invoice amount net of VAT.

## 5. Export

In **Team › Pay** review the whole team for the month and click **Export payroll** to download the payroll for the accountant.

![Step 5: the whole team's pay](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-20f16db6c62a08efc51f93921eac80657e281d12%2Fteam-pay.png?alt=media)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.echevarrisports.com/guia/en/step-by-step/cerrar-mes-entrenador.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.