> For the complete documentation index, see [llms.txt](https://docs.diro.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diro.app/en/growth/provider-commission.md).

# Provider Commission

**Master Data → Commission.** Every booking a provider works on records its own commission, automatically, with no spreadsheet.

## Setting up rules

Commission rules can be created per provider, per service, or a combination of both. They take the form of a percentage of the booking value or a fixed amount per booking.

If a booking matches more than one rule, the more specific rule is applied. You can also override the commission amount on a specific booking when there's a special arrangement.

## When commission is calculated

```mermaid
flowchart LR
  A["Booking created"] --> B["Paid"]
  B --> C["Service performed"]
  C --> D["Commission recorded"]
  B -.->|"cancelled"| E["No commission"]
```

A cancelled booking generates no commission and doesn't appear in the report.

## Commission report

The report shows earnings per provider for the period you select, can be filtered by branch and by service, and can be exported. This is what you use for payroll.

{% hint style="info" %}
Only resources of the **provider** kind generate commission. Rooms and equipment don't. See Resources: Providers & Rooms.
{% endhint %}


---

# 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.diro.app/en/growth/provider-commission.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.