This article will help you fix common errors when export payroll data to DATEV or ADDISON for year-end closing preparation. Most errors arise from data discrepancies between Personio and DATEV or from formatting problems in the export file.

Before you begin

• You export payroll data to DATEV via the ASCII import interface in Personio .
• Errors can originate from three sources: problems with your data in Personio, problems that DATEV detects during the audit, or your tax advisor's LODAS settings in DATEV.

Error 17507 or 17509: Several open employment periods

Problem

You see this error message: "There may be only one open employment period at most." The export fails and Personio does not transmit any data to LODAS.

Possible causes

• Employment periods or entry dates differ between Personio and DATEV.
• You rehire an employee and use the same employee number in both systems.
• Duplicate employee profiles exist for the same person .

Possible solution

1. In Personio, check the initial start date and the start date of the current employment period.
2. Compare this data with the information in DATEV.
3. If the data does not match, refresh it in Personio.
4. If the employee appears twice, open the old profile.
5. Set the consideration in Payroll to No.
6. If this is a rehire, create a new employee number instead of using the old one.
7. Export the data to Personio again.

If the problem persists, contact your tax advisor. He or she can correct the employee's data directly in LODAS within DATEV.

Mistake: "Technical errors" or test report without detailed text

Problem

You see the contribution statement "Technical errors" or a test log from DATEV, but no specific error description or error code.

Possible causes

• After a successful technical import into DATEV, there are content errors in your data.
• The error details are only visible in the DATEV log file.

Possible solution

1. In LODAS, open the error list within DATEV.
2. Check the log for detailed error messages.
3. Resolve the data problems identified by DATEV.
4. Restart the test run in DATEV.
5. Contact DATEV Support if you need Help understanding the errors.

Warning: Version note for the ASCII import interface

Problem

You are seeing this contribution statement: "The ASCII import interface is only compatible up to the full version '14.50' from the previous year."

Description

This is an information notice from DATEV regarding your LODAS version compatibility. It does not indicate a problem with your data or your export .

Possible solution

You do not need to take any action. Your export from Personio continues to work normally. Monitor DATEV notifications regarding future interface updates.

Error 17783, 17874 or 17892: Invalid field values

Problem

You are seeing one of these error codes:

• Error 17783: The position text is longer than 20 characters.
• Error 17874: The fixed salary ID or wage type number is zero.
• Error 17892: The concept of order corresponds to zero.

Possible causes

• Recurring payments such as JobRad or private mileage allowances have the ID zero in DATEV.
• The job descriptions are too long.

Possible solution

1. Go to salary and search for the affected recurring compensation entries.
2. For each type of compensation, enter the correct DATEV IDs provided by your tax advisor.
3. Reduce position text to a maximum of 20 characters.
4. Export the data to Personio again.

If the error persists, confirm the IDs with your tax advisor.

Error LN07947: Missing field separators in ASCII file

Problem

You see this error: "LN07947 (missing field separator in ASCII file)".

Possible cause

DATEV expects a uniform field separator in all export files. Master data exports use semicolons (;) as field separators. Movement data exports use the tab key. If the field separator in DATEV does not match the file format, DATEV cannot read the file.

Possible solution

1. In DATEV, check your current field separator settings for each import file type.
2. In DATEV, set the field separator to a semicolon to match the master data file.
3. Import the master data file.
4. In DATEV, change the field separator setting to tab to match the transaction data file.
5. Import the movement data file.

If you are unsure about the separators, please contact DATEV Support.

export fails due to special character (Ä, Ö, Ü, ß) in the verification protocol.

Problem

You will see a verification log error if your data contains German special character such as Ä, Ö, Ü or ß (for example, in employee names or company names).

Possible cause

This is a known problem regarding how the ASCII import interface handles special character in certain contexts.

Possible solution

Once we fix the problem, create a new export from Personio with the corrected data. The test report should no longer show any errors.

Please monitor Personio for updates regarding this issue. If you need a solution while troubleshooting the problem, contact Personio Support.

Do you need further Help?

If you have tried these solutions and the error persists, contact your tax advisor. Some errors require changes to the DATEV or LODAS settings rather than to Personio.