> 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-export-type-6182597.md).

# Pay Export Type

JobManager supports several export formats. These are found in this table.

The type *Lessor NAV* is integrated with NAV internally, the other types exports data to a file.

Som formats require setup in [JobManager Setup](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md).

| Topic                         |
| ----------------------------- |
| [Name](#field-1)              |
| [Active](#field-9)            |
| [Created Manually](#field-30) |
| [Allow Sort Order](#field-31) |
| [Sort Order](#field-32)       |
| [Path](#field-100)            |
| [Filename](#field-110)        |
| [Number](#field-200)          |
| [Pay API](#field-999)         |

## See also

[Export Payroll](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/export-payroll.md)\
[Create Pay Transactions](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/create-pay-transactions.md)\
[JobManager Foundation Setup Guide](https://docs.dynalogic.com/birds-jobmanager-product-overview/getting-started/foundation-setup-guide.md)

## Reference

[Pay API](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-api-6182595.md)\
[Pay Events](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-events-6182591.md)\
[JobManager Setup](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md)

\
\\

<details>

<summary>Name</summary>

Name of Payroll Service.

Describes which systems are available and the possibility of sending a Specification of Time and Payment to employees E-boks, their E-mail or save all on a specific drive.

</details>

<details>

<summary>Active</summary>

Indicates whether the line is active, and therefore included.

</details>

<details>

<summary>Created Manually</summary>

This field shows whether this Payroll Export was created manually. Alternatively inserted via code automatically.

</details>

<details>

<summary>Allow Sort Order</summary>

This field specifies whether the value of [Sort Order](#field-32) can be changed.

If this Export Type is [Created Manually](#field-30) the value can be changed. Alternatively, it is determined by the automatic creation.

</details>

<details>

<summary>Sort Order</summary>

This field indicates whether the lines in the file should be summed, and at what level.

One or more fields can be specified, separated by `,` (comma). The fields are specified with their BC/NAV system name *(overview at the bottom of this help)*.

### Example 1 (daily summation per Pay Type) <a href="#field-32-example-1-daily-summation-per-pay-type" id="field-32-example-1-daily-summation-per-pay-type"></a>

ExpEmployeeNo,Date,ExpPayTypeNo

The summation is per Employee, per Date and per Pay Type.

Rate is the average of the summation. For example `2025-12-19` where there are `6` hours with different rates. The total amount is `1000`, which is why the rate is `1000 / 6` = `166.67`

**Pay Events**

\| Employee | Date | Pay Type | Qty | Rate | Amount | |---|---|---|---|---|---| | AH | 2025-12-19 | 1234 | 3 | 100 | 300 | | AH | 2025-12-19 | 1234 | 1 | 100 | 100 | | AH | 2025-12-19 | 1234 | 2 | 300 | 600 | | AH | 2025-12-20 | 1234 | 8 | 100 | 800 | ##### Result | Employee | Date | Pay Type | Qty | Rate | Amount | |---|---|---|---|---| | AH | 2025-12-19 | 1234 | 6 | 166.67 | 1000 | | AH | 2025-12-20 | 1234 | 8 | 100 | 800 |

### Example 2 (daily summation per wage type and multiple lines if different rate) <a href="#field-32-example-2-daily-summation-per-wage-type-and-multiple-lines-if-different-rate" id="field-32-example-2-daily-summation-per-wage-type-and-multiple-lines-if-different-rate"></a>

ExpEmployeeNo,Date,ExpPayTypeNo,Rate

The summation per employee, per date, per wage type and per rate

Therefore, there will be 2 lines for `2025-12-19` on wage type `1234`.

**Pay Events**

\| Employee | Date | Pay Type | Qty | Rate | Amount | |---|---|---|---|---|---| | AH | 2025-12-19 | 1234 | 3 | 100 | 300 | | AH | 2025-12-19 | 1234 | 1 | 100 | 100 | | AH | 2025-12-19 | 1234 | 2 | 300 | 600 | | AH | 2025-12-20 | 1234 | 8 | 100 | 800 | ##### Result | Employee | Date | Pay Type | Qty | Rate | Amount | |---|---|---|---|---|---| | AH | 2025-12-19 | 1234 | 4 | 100 | 400 | | AH | 2025-12-19 | 1234 | 2 | 300 | 600 | | AH | 2025-12-20 | 1234 | 8 | 100 | 800 |

### Example 3 (summation for the entire pay period per pay type) <a href="#field-32-example-3-summation-for-the-entire-pay-period-per-pay-type" id="field-32-example-3-summation-for-the-entire-pay-period-per-pay-type"></a>

ExpEmployeeNo,ExpPayTypeNo

The summation per employee and per pay type.

Therefore, there will only be one line for `2025-12-19` (first date) on pay type `1234`.

Rate will be the average of the summation. The amount is the sum of `1800` and `14` hours, so the rate will be `1800 / 14` = `128.57`

#### Pay Events <a href="#field-32-pay-events-2" id="field-32-pay-events-2"></a>

\| Employee | Date | Pay Type | Qty | Rate | Amount | |---|---|---|---|---| | AH | 2025-12-19 | 1234 | 3 | 100 | 300 | | AH | 2025-12-19 | 1234 | 1 | 100 | 100 | | AH | 2025-12-19 | 1234 | 2 | 300 | 600 | | AH | 2025-12-20 | 1234 | 8 | 100 | 800 | ##### Result | Employee | Date | Pay Type | Qty | Rate | Amount | |---|---|---|---|---| | AH | 2025-12-19 | 1234 | 14 | 128.57 | 1400 |

### Field overview <a href="#field-32-field-overview" id="field-32-field-overview"></a>

* `Date` for *Date*
* `ExpEmployeeNo` for *Employee External No.*
* `OrgEmployeeNo` for *Employee*
* `ExpPayTypeNo` for *Pay Type External No.*
* `OrgPayTypeNo` for *Pay Type*
* `Qty` for *Qty*
* `Rate` for *Rate*
* `Amount` for *Amount*
* `ExternalType` for *External Type*
* `ExternalUnit` for *External Unit*
* `Dim01`..`Dim20` for dimension fields 1 to 20

</details>

<details>

<summary>Path</summary>

This is only visible in the older versions of NAV. Not visible in Extensions.

</details>

<details>

<summary>Filename</summary>

File name format

**Filename: standard is set up as follows;**

For example: **Payroll\_\[YYYY]\[MM]\[DD].csv**

It is possible to use various variables. \[YYYY] year with 4 digits

\[YY] year with 2 digits

\[WW] week with 2 digits

\[W] week with 1-2 digits

\[MM] month with 2 digits

\[M] month with 1-2 digits

\[MONTH] month written with letters

\[DD] date with 2 digits

\[D] date with 1-2 digits

The variables mentioned below are used in connection with the Specification of Time and Payment.

\[EMP] Employee number. \[#] \[##] \[###]…. Adds a sequential counter number for each operational run. The number of # signs define the amount of prefixed 0’s.

**Destination:** Choose the path where the file is to be saved. \SRV-FILPRINT

</details>

<details>

<summary>Number</summary>

Which *number* / *parameter* should be used, for the employee, in the export.

**Choose between;**

* Employee no. from JobManager employee card.
* Alternative identification, to be used if the employee number is different to the number used in the payroll system. This alternative identification is setup in the JobManager Employee card under “General”
* Social Security No. (CPR-No.) Note that this is only used when sending a Specification of Time and Payment to the employees e-boks. The Social Security No. is necessary for distribution. and is found in the employee card in NAV.

</details>

<details>

<summary>Pay API</summary>

Unique Id for this API.

**Related topics**

* [Pay API](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-api-6182595.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-export-type-6182597.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.
