This article explains security mechanisms and validations that ensure correct data transmission from Personio to DATEV LODAS or wages and salaries via the payroll import data service.
What are Attribute Values Validations?
Validations ensure a successful data transfer from Personio to DATEV LODAS or wages and salaries using the payroll import data service. They verify attribute values that are subject to formatting requirements, such as 11 characters for the attribute Tax identification numberor show duplicate personnel numbers within a legal entity. Format errors of this kind can cause the transfer of an attribute or even of the entire employee to fail. Through validations and the resulting error messages, you can detect incorrectly formatted attribute values in advance and correct them before you complete payroll payroll.
Please note:
Note that the validations mentioned below will only be performed if the attribute Consideration in payroll accounting on Yesand if an attribute is set underPayroll accounting > managing > DATEV LODAS/Payrollin the Employee Master Data & Validationsas Activeis marked and is accordingly included in an export.
Payroll Import Data Service Validations Overview
The following overview describes validations for attributes that are transferred using the Payroll Import Data Service and the impact of format violations on data transfer.
Please note:
Please note that the formats for using DATEV LODAS and wages and salaries differ.
| Attribute | Format | Effect |
| DATEV personnel number | Positive, five-digit number from 1–99999 existing | The affected employee is not exported |
| A unique personnel number per company is available | Employees with the same DATEV personnel number are not exported | |
| Original entry date | The original entry date must be before the termination date (current employment period) | The affected employee is not exported |
Entry date (current employment period) |
The entry date (current employment period) must exist and be before the exit date (current employment period) | The employment period of the affected employee is not exported |
|
Exit date (current employment period) |
The exit date (current employment period) must be after the entry date (current employment period) AND The exit date (current employment period) must be after the original entry date |
|
Different bank account holder |
Maximum 25 characters | Attribute values are not exported for the affected employees |
Address, addition |
Maximum 40 characters | |
| SWIFT CODE | Maximum 11 characters | |
| Place of birth | Maximum 34 characters | |
| Number | Maximum 9 characters | |
| IBAN | Exactly 12 characters, plausibility check of entries | |
| Last name | Maximum 30 characters | |
| City | Maximum 34 characters | |
| Social insurance group key | Valid combinations of social insurance and contribution group keys | |
| Social contribution key | ||
| Position | Maximum 30 characters | |
| Postal code | Maximum 10 characters | |
Address, postcode |
Maximum 10 characters | |
Social security number |
Exactly 12 characters, plausibility check of entries | |
Tax identification number |
Exactly 11 digits, plausibility check of entries | |
| Street | Maximum 33 characters | |
| First name | Maximum 30 characters |
| Attribute | Format | Effect |
| DATEV personnel number | Positive, five-digit number from 1–99999 existing | The affected employee is not exported |
| A unique personnel number per company is available | Employees with the same DATEV personnel number are not exported | |
Hire date |
Hire date must exist |
The affected employee is not exported
|
Original entry date |
The original entry date must be before the termination date (current employment period) | |
Entry date (current employment period) |
The entry date (current employment period) must exist and be before the exit date (current employment period) | |
Exit date (current employment period)
|
The exit date (current employment period) must be after the entry date (current employment period) AND The exit date (current employment period) must be after the original entry date |
|
First name |
Available, with maximum 30 characters | |
Different bank account holder |
Maximum 25 characters | Attribute values are not exported for the affected employees |
| Academic degree | Maximum 30 characters | |
| Address, addition | Maximum 40 characters | |
| SWIFT CODE | Maximum 11 characters | |
|
EU-Sozialversicherungsnummer |
Maximum 25 characters | |
| Place of birth | Maximum 34 characters | |
| Number | Maximum 9 characters | |
| IBAN | Maximum 42 characters, starts with a valid country code according to ISO-3166-1 | |
| Last name | Maximum 30 characters | |
| City | Maximum 34 characters | |
| Social insurance group key | Valid combinations of social insurance and contribution group keys | |
| Social contribution key | ||
| Position | Maximum 30 characters | |
| Postal code | Maximum 10 characters | |
Social security number |
Exactly 12 characters, plausibility check of entries | |
Tax identification number |
Exactly 11 digits, plausibility check of entries | |
| Street | Maximum 33 characters |
Tax Data Validations
With the extension of the DATEV integration to include tax data attributes, you transfer additional wage tax deduction characteristics to DATEV. These validations apply equally to DATEV LODAS and Lohn & Salary.
Please note:
Tax data is only transferred for new employees whose starting date is in the current payroll period. No tax data is sent to DATEV for existing employees, as DATEV obtains the values directly from the tax office via the ELStAM procedure. For more information on this scope, see the article on the Attributes for integration with DATEV.
| Attribute | Format | Effect |
| Tax class | Value between 1 and 6 | Attribute value for affected employees is not exported |
| Factor | Value between 0.00 and 0.999, only allowed if tax class is equal to 4 | Attribute value for affected employees is not exported |
| Child allowance | Value between 0 and 12.5 | Attribute value for affected employees is not exported |
| Employee denomination | Must match one of the selection values stored in Personio | Attribute value for affected employees is not exported |
| Confession: Spouse/civil partner | Must match one of the selection values in your system (e.g. "ev" for Protestant, "ak" for Roman Catholic). The value _issl_ is not supported | Attribute value for affected employees is not exported |
| Annual allowance | Positive integer, cannot be filled together with annual addition amount | Attribute value for affected employees is not exported |
| Annual Added Amount | Positive integer, cannot be filled together with annual allowance | Attribute value for affected employees is not exported |
| Monthly allowance | Positive integer, cannot be filled together with monthly addition amount | Attribute value for affected employees is not exported |
| Monthly Added Amount | Positive integer, cannot be filled together with monthly allowance | Attribute value for affected employees is not exported |
Example:
A new employee joins on the 3rd of a month and, according to his information, has tax class 4 with factor method. To ensure that the transfer to DATEV succeeds, you also enter a factor between 0.00 and 0.999. If the Factor field is left blank, the attribute value for that employee will not be exported.
Please note:
For general questions about the assignment of tax classes or allowances, we recommend consulting with your tax advisor or your payroll department.
Notes on Format Errors
To help you identify format errors in attributes in advance, error messages in both the employee profile and the payroll indicate necessary format changes.
Format Error Indication in the Employee Profile
Attributes for which a validation rule is stored and whose value violates this policy are marked with an error message below the attribute value. This error message informs you which settings are necessary, so that you can adjust the attribute immediately.
Please note:
Note that DATEV-specific error messages are only displayed for those persons who have edit rights for the respective attribute section.
Format Error Indication in the Payroll Table
In the payroll, attributes for which a validation rule is stored and whose value violates this policy are highlighted in red. Click on the respective employee to view the detailed error message and see the required format, and correct the error before you finalize the payroll.
Tip:
For more information, read our article on troubleshooting the Furnishings and Useof the DATEV integration.