> 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/agreement-6182501.md).

# Agreement

The table (and related tables) contains relevant setup for Payroll. These are used to transfer to **Lessor Payroll** or export to external Payroll Systems.

Several different Agreements can be setup.

| Topic                             |
| --------------------------------- |
| [Calculation ID](#field-1)        |
| [Agreement](#field-3)             |
| [Description](#field-5)           |
| [Period](#field-7)                |
| [Recreation (Minimum)](#field-21) |
| [Recreation (Period)](#field-22)  |

## See also

[Create Pay Transactions](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/create-pay-transactions.md)\
[Pre-Pay (Time Calculation)](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/pre-pay-time-calculation.md)

## Reference

| Topic                                                                                                                                                                |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Agreement Setup](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/agreement-setup-6182503.md)               |
| [Agreement Pay Counters](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/agreement-pay-counters-6182511.md) |
| [Pay Type](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-type-6182551.md)                             |
| [Pay Export Type](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-export-type-6182597.md)               |

\
\\

<details>

<summary>Calculation ID</summary>

Related Calculation ID.

</details>

<details>

<summary>Agreement</summary>

Code for Areement.

</details>

<details>

<summary>Description</summary>

Description of the record.

</details>

<details>

<summary>Period</summary>

Should match how often to run **Create Pay Transactions**.

</details>

<details>

<summary>Recreation (Minimum)</summary>

Is used for e.g. *11 hour rule*.

Fill in the minimum hours of *Recreation*.

Read more [here](https://docs.dynalogic.com/birds-jobmanager-product-overview/troubleshooting-and-known-issues/q-and-a-11-hours-rule.md).

**Related topics**

* [Q\&A (11 hours rule)](https://docs.dynalogic.com/birds-jobmanager-product-overview/troubleshooting-and-known-issues/q-and-a-11-hours-rule.md)

</details>

<details>

<summary>Recreation (Period)</summary>

Is used for e.g. 11 hour rule.

Fill out the *Period* where the *Recreation* must be kept.

E.g. Fill out *Recreation Minimum* with 11 hours and *Period* fills out with 24 hours (1 day).

Read more [here](https://docs.dynalogic.com/birds-jobmanager-product-overview/troubleshooting-and-known-issues/q-and-a-11-hours-rule.md).

**Related topics**

* [Q\&A (11 hours rule)](https://docs.dynalogic.com/birds-jobmanager-product-overview/troubleshooting-and-known-issues/q-and-a-11-hours-rule.md)

</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/agreement-6182501.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.
