Mijn Communities

HR Core Business 2020-06 EN

25-05-2020 22:48 (Bijgewerkt op 31-01-2022)
  • 0 Antwoorden
  • 0 kudos
  • 250 Weergaven


Unique Personal ID (UPI)

Unique persons must be identifiable in interface applications, including Medical Leave Management and Talent Management. That is why in future the use of a Unique Personal ID (UPI) will be mandatory. By means of this UPI (copied) employees can be linked. Mandatory use of the UPI will be implemented in phases:

  • Phase 1
    Checking the UPI’s uniqueness. Refer to the Checking the Unique Personal ID’s
    section in these Release Notes.
  • Phase 2
    Option to enable auto-population of the UPI field of new employees with the employee code.
  • Phase 3
    The ability to update existing employees with the employee code (individually and through import) when the option to populate the UPI field with the employee code has been enabled. The new Update UPI field will be introduced for this purpose.
  • Phase 4
    Final phase for unspecified UPIs and mandatory use of UPIs.

We will keep you informed about the progress through the Release Notes.


Request for supplementary childbirth leave when registering the child


With the introduction of the Dutch Supplementary Childbirth Leave Act (Wet Invoering Extra Geboorteverlof (WIEG)) an employee may opt to take 5x the number of contract hours in supplementary childbirth leave. This request always concerns whole weeks. As of this release the requested number of weeks of childbirth leave can be specified when registering the child.


Settings > General > HR parameters

To enable automatic generation of the extra individual leave entitlement to supplementary childbirth leave, the type of leave to be used must be specified in the Verlofsoort aanv. geboorteverlof (Supplementary childbirth leave) field in the HR parameters screen.

Employee > Employee > Child data

As of July 1, 2020 the Aanvraag aanv. geb.verlof (weken) (Supplementary childbirth leave request (weeks)) field has been added to the Child data screen. Here the number of requested weeks of supplementary childbirth leave must be specified in whole weeks. 5 weeks at most can be requested. The relevant child data of the child for which supplementary childbirth leave is requested can also be specified.

Due date of birth in the future: as of this release a due date of birth in the future can be specified. The date must be updated when the actual date of birth differs.

The description of the generated supplementary childbirth leave contains the child’s name and date of birth, so it is easy to see to which child the leave applies.

GDPR and registration of the child’s name: the GDPR, however, stipulates that the child’s name may only be registered when the parent has given explicit consent to do so. That is why a description instead of the child’s name is registered.

Generating extra individual leave entitlement: when the data has been registered and stored, an extra individual leave entitlement is generated automatically.
Note: it may take a few minutes before the extra individual leave entitlement has been generated.

Employee > Time off > Extra individual entitlement

When the child data and the requested number of weeks of supplementary childbirth leave have been specified, the extra individual leave entitlement is generated automatically. This leave entitlement has an entry date that matches the child’s date of birth. The number of hours is the requested number of weeks of leave x contract hours per week. The expiration date is entered automatically and is 6 months after the date of birth.

Your action

Add the supplementary childbirth leave type to the time off policies and link it to the supplementary childbirth leave through the HR parameters as described above.

New function - GDPR - delete employee


The GDPR stipulates that it must be possible to delete employees after the retention obligation has expired. As of this release a function for removing the personal data of employees has been included in HR Core Business. 


Employee > Employee >AVG Verwijderen medewerker (GDPR - delete employee)

As of this release the Employee option in the Employee menu includes the AVG Verwijderen medewerker (GDPR - delete employee) function. When the screen is opened, employees who have left employment more than 7 years ago are displayed. The list can be filtered by employee name.

Mark the employees whose personal data should be deleted and click the Delete button. Persons whose data has been deleted only have the GDPR removed, xx. description.

Note: employees cannot be undeleted. The data is deleted from the database as well and cannot be retrieved.

In the Extended Transaction Report, these removed employees are included with the description AVG removed, x (AVG verwijderd, x) and the Value AVG removed. (Waarde AVG verwijderd) Personal data is no longer available for employees who have been removed via AVG Delete employee, so that it is not possible to trace which employees are involved.

It is important to realize that the removal of an employee via the AVG delete employee function is considered a change to the employee data. This ensures that adjacent applications are informed about the removal of the employee, see also the example below. If you request changed data after removal via an interface or reports, it may be that employees who have been out of service for 7 years are again included in a selection, because there has been a change in the employee data, namely that the status of GDPR Deleted is active. This obviously does not apply if the selection only contains active employees.

Employee J. Janssen, personnel number 100, has been out of service for 7 years. His data has been deleted via GDPR delete employee (AVG verwijderen medewerker).
With this delete action, the data element AVG mask data (AVG maskeren gegevens) is created in the background and filled with the value Masked (Gemaskeerd). As a result in the mutation report (Mutatieverslag (uitgebreid)) you will see the employee as AVG Deleted (AVG verwijderd).

Suppose a customer uses its own interface, which requests all employees whose data has been changed. Because the data element AVG mask data (AVG maskeren gegevens) has been created and has the value Masked (Gemaskeerd), former employee J. Jansen, personnel number 100, is sent to the interface as employee x. AVG Deleted (x. AVG Verwijderd).

Your action

If adjacent systems use HR Core data, it may be that the deleted employee, including the deleted data, is sent again to this system. It may therefore be necessary to adjust these systems before using the new functionality for deleting personal data.

Modified and Improved

Checking the Unique Personal ID’s uniqueness


In future the use of a Unique Personal ID (UPI) will be mandatory in order to identify persons in interface applications such as Medical Leave Management and Talent Management. Refer to Unique Personal ID (UPI) at the beginning of these Release Notes. As of this release the uniqueness of the Unique Personal ID will be checked.


Employee > Employee > Employees

When a new Unique Personal ID is specified in the Employee screen, the uniqueness of the value entered in the field will be checked. When it matches an existing value of the client, an error message will be displayed when the last name and date of birth of the employee do not match.

Your action

Ensure the UPI is unique to each person, i.e. employee and the same (copied) employee across companies. An employee is considered to be the same single person when the last name and date of birth are identical.

Exporting time off requests


The Time off request screen was modified in 2019 to improve filter options and performance. It was no longer possible to export time off requests. However, clients have indicated they require the export function. That is why as of this release it is possible to export time off requests again. 


Employee > Time off > Time off request

The Export button is again available in the Time off request screen (bottom right). When this button is clicked, the file type can be specified at the top of the screen, and whether all pages should be exported.

Your action

No action is required.

Solved Messages

Name of organizational unit incorrectly displayed in OrgSight


When searching for an organizational unit in OrgSight, the name was incorrectly displayed. When the organizational unit was selected, the name sometimes included a strange symbol. This was due to the fact that special characters such as the ampersand (&) were mistakenly interpreted as HTML code.


This problem has been resolved: as of this release the names of organizational units are displayed correctly.

Your action

No action is required.

Publishing Date : 5/25/2020

Actieve onderwerpen