> 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-setup-6182503.md).

# Agreement Setup

Setting up the Pay Types used for calculating the Pay Events.

| Topic                               |
| ----------------------------------- |
| [Calculation ID](#field-1)          |
| [Agreement](#field-3)               |
| [Sequence](#field-6)                |
| [Execution](#field-7)               |
| [Skip](#field-8)                    |
| [Description](#field-9)             |
| [Pay Type](#field-10)               |
| [Minimum](#field-11)                |
| [Maximum](#field-12)                |
| [Time Counter](#field-15)           |
| [Factor](#field-21)                 |
| [Condition](#field-50)              |
| [Debug Condition](#field-51)        |
| [Debug Pay Type Formula](#field-52) |
| [Pay Type Description](#field-110)  |

## 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

[Agreement](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/agreement-6182501.md)\
[Agreement Setup Formula](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/agreement-setup-formula-6182505.md)\
[Agreement Pay Counters](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/agreement-pay-counters-6182511.md)

\
\\

<details>

<summary>Calculation ID</summary>

Related Calculation ID.

</details>

<details>

<summary>Agreement</summary>

Code for Areement.

**Related topics**

* [Agreement](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/agreement-6182501.md)

</details>

<details>

<summary>Sequence</summary>

Unique system number which can be used to identify this line.

</details>

<details>

<summary>Execution</summary>

* Default (Create Pay Transactions)
  * The line is enabled for [Create Pay Transactions](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/create-pay-transactions.md).
* Time Calculation(Pre-Pay)
  * The line is enabled for [Time Counter posting](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/pre-pay-time-calculation.md).
* Always
  * The line is enabled for both [Create Pay Transactions](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/create-pay-transactions.md) **and** [Time Counter posting](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/pre-pay-time-calculation.md).

**Related topics**

* [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)

</details>

<details>

<summary>Skip</summary>

When selecting, this entire line/rule is omitted. *Equivalent to deleting the line*.

</details>

<details>

<summary>Description</summary>

Description of the record.

</details>

<details>

<summary>Pay Type</summary>

Number for JobManager Pay Type.

</details>

<details>

<summary>Minimum</summary>

Minimum value for calculation of pay count unit.

</details>

<details>

<summary>Maximum</summary>

Maximum value for calculation of pay count unit.

</details>

<details>

<summary>Time Counter</summary>

Setup a Time Counter for [Time Counter posting](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/pre-pay-time-calculation.md).

**Related topics**

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

</details>

<details>

<summary>Factor</summary>

Enter the factor for the calculation.

</details>

<details>

<summary>Condition</summary>

Conditions can be defined, to control which pay counters to calculate.

Example: You can setup a Pay Type *1215* which is only triggered if Pay Counter *ILL\_ABS* is zero within the relevant period.

Condition is written as a formula:

### Exampel <a href="#field-50-exampel" id="field-50-exampel"></a>

* Formula for the above exampel

  ```
  [ILL_ABS]=0
  ```
* Advanced formula

  ```
  ([OT2]=0) AND (([PAY-06]>0) OR ([PAY-07]>0))
  ```

### Syntax <a href="#field-50-syntax" id="field-50-syntax"></a>

* Pay Counters writes with **\[ ]**
* Use **+ - \* /**
* Use **( )**
* Use **\\> < >= <= =**
* Use **AND &&** or **OR ||**

*Your local language equivalent to **AND** and **OR** can be used, if JobManager is translated into your language.*

### Limitations <a href="#field-50-limitations" id="field-50-limitations"></a>

The logical *parser* has certain limitations:

* A formula **can't** start with **-** *minus*. Can be resolved by using parentheses **( )**.
* Two operators **can't** stand next to each other:
  * `([ILL_ABS]-[ILL_TEST])<-10` solved by using **( )** parentheses: `([ILL_ABS]-[ILL_TEST])<(-10)`
  * `20*-10` solved by using **( )** parentheses: `20*(-10)`

### Troubleshooting <a href="#field-50-troubleshooting" id="field-50-troubleshooting"></a>

See [here](#field-51).

</details>

<details>

<summary>Debug Condition</summary>

Activate debug [Condition](#field-50) during the [Create Pay Transactions](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/create-pay-transactions.md).

During run the result of the formula are shown: true (1) or false (0).

**Related topics**

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

</details>

<details>

<summary>Debug Pay Type Formula</summary>

Activate troubleshooting of the [Formula](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/agreement-setup-formula-6182505.md) during the [Create Pay Transactions](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/create-pay-transactions.md).

Sub total for each step in the [Formula](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/agreement-setup-formula-6182505.md) is shown.

**Related topics**

* [Create Pay Transactions](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/create-pay-transactions.md)
* [Agreement Setup Formula](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/agreement-setup-formula-6182505.md)

</details>

<details>

<summary>Pay Type Description</summary>

Description from the related Pay Type.

**Related topics**

* [Pay Type](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-type-6182551.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-setup-6182503.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.
