> 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-6182551.md).

# Pay Type

Use this to define the relevant Pay Types for Pay and Absence.

If JobManager is integrated with Lessor, all the standard Lessor Pay Types can be imported.

| Topic                                     |
| ----------------------------------------- |
| [Pay Type](#field-1)                      |
| [Description](#field-5)                   |
| [Work Type Code](#field-10)               |
| [Same as](#field-11)                      |
| [Qualification Code (Same as)](#field-12) |
| [Factor (Same as)](#field-13)             |
| [Rounding Precision](#field-21)           |
| [Round type](#field-22)                   |
| [Report primo/ultimo](#field-32)          |
| [External No.](#field-50)                 |
| [External Type](#field-80)                |
| [External Unit](#field-81)                |
| [BI Group](#field-8000)                   |
| [BI Group (Caption)](#field-8001)         |

## See also

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

## Reference

| Topic                                                                                                                                                        |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [Pay Type Rate](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-type-rate-6182553.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) |
| [Agreement](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/agreement-6182501.md)                   |

\
\\

<details>

<summary>Pay Type</summary>

Number for JobManager Pay Type.

</details>

<details>

<summary>Description</summary>

Description of the record.

</details>

<details>

<summary>Work Type Code</summary>

This is mandatory, if posting on Job is enables. It is also the connection between JobManager and Lessor in relation to employee rates.

</details>

<details>

<summary>Same as</summary>

Ability to insert an *extra* [Pay Event](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-events-6182591.md) with the selected Pay Type.

By default it follows the chosen *Same as* Pay Type.

However, this can be restricted by the [Qualification Code (Same As)](#field-12) field.

</details>

<details>

<summary>Qualification Code (Same as)</summary>

Used to restrict [Same as](#field-11).

This *extra* [Pay Event](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-events-6182591.md) will only be created if the employee has the chosen *Qualification* on the relevant date.

**Related topics**

* [Employee](https://docs.microsoft.com/en-us/dynamics365/business-central/hr-how-register-employees)

</details>

<details>

<summary>Factor (Same as)</summary>

Used to adjust [Same as](#field-11).

Qty on this *extra* [Pay Event](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-events-6182591.md) will be corrected with *Factor*.

</details>

<details>

<summary>Rounding Precision</summary>

This parameter is used to set up *round off* scenarios for [Pay Events](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-events-6182591.md).

It will cause the system to round up, or round down to the nearest X.

E.g. if all *Qty* be rounded up to the nearest 0.25 - the setting in the two fields should be **0.25** and **Up**.

</details>

<details>

<summary>Round type</summary>

This parameter is used to set up *round off* scenarios for [Pay Events](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-events-6182591.md).

It will cause the system to round up, or round down to the nearest X.

E.g. if all *Qty* be rounded up to the nearest 0.25 - the setting in the two fields should be **0.25** and **Up**.

</details>

<details>

<summary>Report primo/ultimo</summary>

Show as primo/ultimo balances. *Typically used with Flex Balances.*

</details>

<details>

<summary>External No.</summary>

If filled in this will override the number in the export.

*If empty the normal Pay Type are used.*

</details>

<details>

<summary>External Type</summary>

Select the type for exporting. The various Payroll Export formats typical treat Pay and Absence differently.

* Pay
* Absence

**Lines are only exported if one of the above are selected.**

</details>

<details>

<summary>External Unit</summary>

The unit for export:

* Hours
* Days

</details>

<details>

<summary>BI Group</summary>

Select a value from [JobManager BI Group](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-bi-group-6182367.md). Record with the same value is being summed up.

</details>

<details>

<summary>BI Group (Caption)</summary>

Displays *Caption* as found in [JobManager BI Group](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-bi-group-6182367.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/pay-type-6182551.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.
