> 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/payroll-exports/acerta.md).

# Pay Export to Acerta

This is for the Belgian Payroll System *Acerta* and the *Acerta Connect* file.

This export consists of 2 files, which are created separately:

* Payroll (and Absence)
* Addon

Below is special information for this export format. General information is available [here](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/export-payroll.md).

**The&#x20;*****Advanced*****&#x20;field is&#x20;*****EMPTY*****&#x20;for these exports!**

The field *External Payroll No* is retrieved from the field [External Payroll number](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md#field-30) in the [JobManager Setup](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md) table.

#### Payroll (and Absence) file <a href="#payroll-and-absence-file" id="payroll-and-absence-file"></a>

This file includes lines where [External Type](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-events-6182591.md#field-80) equals *Pay* and *Absence*.

The field *Line Prefix* is always `KLX1` (that is fixed value `KLX` followed by `1` for *Update Code* equals *Active*)

#### Addon file <a href="#addon-file" id="addon-file"></a>

This file includes lines where [External Type](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-events-6182591.md#field-80) equals *Addon*.

The field *Line Prefix* is always `LOMD` (that is fixed value `LOM` followed by `D` (equals *origineel: gegeven wordt toegevoegd bij al dan niet aanwezige lijnen in de afwijkende lonen*).

The fields *Afwerkingsdatum*, *Kostenplaats* and *Uitbetalingspercentage* is always empty.

Only one of the fields *Days* or *Qty* is used for each row. The *Days* field is used if [External Unit](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-events-6182591.md#field-81) equals *Days*, otherwise the *Qty* field is used.

### Summation <a href="#summation" id="summation"></a>

A runtime parameter indicates whether this file should sum the lines for the entire selected period, if they have the same *Pay Type* and *Rate*.

If summation, the date on the lines will be set to the first day of the selected period.

### File format <a href="#file-format" id="file-format"></a>

* The **Payroll file** contains the following fields: `Line Prefix, External Payroll No, Export Empl No, Date, Export Pay Type No, Qty`
  * `Line Prefix` 4 characters (left-aligned) at position 1-4
  * `External Payroll No` 7 characters (left-aligned) at position 5-11
  * `Export Empl No` 20 (17+3) characters (left-aligned) at position 12-31
  * `Date` 10 characters at position 32-41
  * `Export Pay Type No` 6 (2+4) characters (right-aligned with leading spaces) at position 42-47
  * `Qty` 6 (2+4) characters (right-aligned with **2** leading spaces) at position 48-53\
    \\
* The **Addon file** contains the following fields: `Line Prefix, External Payroll No, Export Empl No, Date, Afwerkingsdatum, Kostenplaats, Export Pay Type No, Days, Qty, Rate, Uitbetalingspercentage, Amount`
  * `Line Prefix` 4 characters (left-aligned) at position 1-4
  * `External Payroll No` 7 characters (left-aligned) at position 5-11
  * `Export Empl No` 20 (17+3) characters (left-aligned) at position 12-31
  * `Date` 10 characters at position 32-41
  * `Afwerkingsdatum` 10 characters at position 42-51
  * `Kostenplaats` 12 characters at position 22-63
  * `Export Pay Type No` 6 (2+4) characters (right-aligned with leading spaces) at position 64-69
  * `Days` 8 (2+6) characters (right-aligned with **2** leading spaces) at position 70-77
  * `Qty` 8 (2+6) characters (right-aligned with **2** leading spaces) at position 78-85
  * `Rate` 15 (2+13) characters (right-aligned with **2** leading spaces) at position 86-100
  * `Uitbetalingspercentage` 5 characters at position 101-105
  * `Amout` 11 (2+13) characters (right-aligned with **2** leading spaces) at position 106-116\
    \\
* Decimal fields are specified *without* a thousand separator, with 2 decimal places (exept 5 for *Rate* field) and *without a decimal point*. That is 12.34 would be `1234` *(with a maximum of 4 digits)*. The number has leading `0` (zeros).
* Dates are specified as \`DD/MM/YYYY'.

### Sample file (Payroll) <a href="#sample-file-payroll" id="sample-file-payroll"></a>

*External Payroll No*: 99999999\
*Employee*: 11\
28/10-2024 with 8 *normal hours* and 4.25 *overtime*.\
29/10-2024 with 4.75 *normal hours* and 3.25 *absence* (Loopbaan Verlof).

```
KLX1999999911                  28/10/2024  0100   800
KLX1999999911                  29/10/2024  0100   475
KLX1999999911                  28/10/2024  0138   425
KLX1999999911                  29/10/2024  2353   325
```

## See also

[Export Payroll](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/export-payroll.md)

## Reference

\
\\


---

# 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/payroll-exports/acerta.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.
