> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-type-rate-6182553.md).

# Pay Type Rate

The table is used for setup rates and overhead on a Pay Type.

| Topic                    |
| ------------------------ |
| [Pay Type](#field-1)     |
| [Type](#field-2)         |
| [Number](#field-3)       |
| [Rate](#field-10)        |
| [Base Rate](#field-11)   |
| [Surcharge %](#field-12) |
| [From Date](#field-21)   |
| [To Date](#field-22)     |
| [Max Rate](#field-23)    |

## See also

[Create Pay Transactions](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/create-pay-transactions.md)

## Reference

[Pay Group](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-group-6182571.md)\
[Pay Group Employee](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-group-employee-6182573.md)

\
\\

<details>

<summary>Pay Type</summary>

Number for JobManager Pay Type.

</details>

<details>

<summary>Type</summary>

Indicates the type of relation for [Number](#field-3):

* Employee
* Group
* All

**Related topics**

* [JobManager Employee](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-employee-6182311.md)
* [Pay Group](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-group-6182571.md)
* [Pay Group Employee](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-group-employee-6182573.md)

</details>

<details>

<summary>Number</summary>

Indicates the related number depending on [Type](#field-2):

| Type     | Number       |
| -------- | ------------ |
| Employee | Employee No. |
| Group    | Pay group    |
| All      | *Blank*      |

**Related topics**

* [JobManager Employee](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-employee-6182311.md)
* [Pay Group](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-group-6182571.md)
* [Pay Group Employee](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-group-employee-6182573.md)

</details>

<details>

<summary>Rate</summary>

Enter the rate.

</details>

<details>

<summary>Base Rate</summary>

Select a Pay Type, from which the rate is derived.

</details>

<details>

<summary>Surcharge %</summary>

Enter (optional) an additional overhead added to the rate.

</details>

<details>

<summary>From Date</summary>

Date from where the line starts.

</details>

<details>

<summary>To Date</summary>

Date to where the line ends.

</details>

<details>

<summary>Max Rate</summary>

Mulighed for at have en max sats på lønarten.

Anvendes til fx sygdom, hvor man ofte får "alm" timesats, men med max antal kroner.

Bruges mest når satsen hentes fra en anden lønart i *Grundsats*. (fx D1213 - Normaltimer)

</details>


---

# 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.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-type-rate-6182553.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.
