Releases YouServe

  Notifications Employees with Employment Start Date in the future from Self Service reversed Why To prepare for future functionality allowing employees with an Employment Start Date in the future to be edited in Self Service, they were imported with a start date equaling the editing date on which the employee was created. Thus, it was possible to edit these employees with this start date in Self Service even before employment commenced. Until the Employment Start Date was reached and the employee transitioned to the associated Employed status, the employment terminated status was forwarded to other parties with an Employment End Date equaling the editing date in Self Service, as retrieved from HR Core. This functionality was reversed because it caused a lot of problems in actual practice. How For customers who experienced problems with this, the data was corrected to the old input date. The employment status is no longer Employment terminated before the employee starts employment. Employees who are entered in Self Service with a future date are transmitted to HR Core the old way once again. Resolved notifications Collective leave 2018 not deducted for new employee (change 1174518) Notification  An employee started employment for the first time in November 2018. It was expected that the collective leave days would be deducted based on his work schedule. However, this did not occur. The relevant employee started employment on November 19, and the collective leave for 2019 was created on that same date. The collective leave days were deducted correctly for another employee whose Employment Start Date was October 15. The collective leave days that were entered last year are no longer in the system, which means they were not allocated to employees starting employment. Solution  The employee started employment after the collective leave for 2019 was created, causing the collective leave days for 2018 to be moved to history. This process for clearing old definitions for collective leave has been modified. As a result, collective leave days are no longer moved to history after one year.  Your action No action is required. Organization structure history unavailable (change 1298321) Notification When opening the organization structure on a specific date in the past, an unexpected error report was displayed: OU with code 60001358 refers to parent OU with code 60001352 as per 10/03/2017. The relevant parent Organization Unit (OU) was not valid until 11/08/2018, however, so the reference pointed to a non-existent OU. Solution The date data for the organization units has been corrected, so the reference to the child organization unit has the same start date as the parent organization unit.  Your action No action is required. Remaining leave not always updated (change 1234723) Notification The remaining leave was not updated automatically for employees who had only registered the statutory leave and/or supplementary leave on December 31, 2018. Solution The remaining leave was not updated automatically if leave was taken on December 31. The remaining leave was corrected after another withdrawal or recalculation. The programming was modified so that the remaining leave is updated correctly immediately when leave is taken on 31 December only. Your action No action is required. Publishing Date : 4/18/2019

  This document describes the new functionality and improvements introduced by this release. Some of these changes have been inspired by messages and reports from customers. Where relevant, we have included a number in the section title to refer to the identification of the message (change .....) in question in our system. Modified and improved Five days of paid paternity leave The regulations on paid paternity leave will change on January 1, 2019. Paternity leave is currently two days. Starting on January 1, 2019, this will be extended to one working week (up to five days). Childbirth leave In the new law that enters into effect in January, maternity leave is now called childbirth leave. The employee must take this leave within four weeks after the birth of her child. This type of leave now falls under special leave, which will continue to exist. Please note: Childbirth leave only works for HR Core Business and not when you purchase Payroll Business Only. Childbirth leave now applies for the entire country. This means that when you open the list of values for leave from 1-1-2019, you will also be able to select Childbirth leave. Your action Maintenance > Repository > Manage Parameters / list of values with inheritance If you have added Maternity leave to the list of values yourself, you will have to change this to Childbirth leave yourself. In Leave request you can also choose Childbirth leave from the list in the field Reason for leave.   Publishing Date : 12/21/2018

On Wednesday September 11th we have put an extra release in production in which we changed the following. Changed and improved Search function Archive extended Why Self Service users usually check for mutations from recent history. Too many items are displayed based on current filters. How It is now possible to search for mutations per effective date. The search function of the Archive has been extended with effect from 11 September 2019 with an effective date (from and including) filter. In addition to the user-friendliness, this screen will retrieve the data faster by using the new filters. This filter shows as default value the mutations with an effective date starting from 3 months ago to today. If desired, you can select a different time period. Your selection will be saved for the duration of the session. If you press the red filter then you clear the period and you can select a new period. If you leave this screen and then return to it, the last used selection will be displayed again. The starting date that can be searched is the starting date that you see in the top right of the forms. Publishing Date : 9/16/2019

  This document describes the new functionality and improvements introduced by this release. Some of these changes have been inspired by messages and reports from customers. Where relevant, we have included a number in the section title to refer to the identification of the message (change .....) in question in our system. Modified and improved 1.  Travel distance calculation parameters – Google Maps to Webservices Why As was specified in the March release notes, we will start using Webservices again instead of Google Maps as of the April release. Below you will find information on the major changes you as a client will experience. What has changed? Calculation of number of kilometers In Google Maps the calculation was always based on the optimum route. In Webservices the calculation is based on the shortest or fastest route. You will have to specify your choice in the set-up once. See Your action. House number and house number suffix When Webservices was used in the past, it was not possible to calculate the distance between the house number of the location and the house number of the employee. This was possible with Google Maps, but house number suffix could not be used. This time Webservices calculates the travel distance using both house number and house number suffix. No house number of location When no house number is specified for a location, the calculation will be based on the central location of the specified postcode. Foreign addresses and Country field The travel distance for foreign addresses can now be calculated as well. When it concerns a location, the field Country must be entered correctly. If no country is specified, the calculation will automatically be based on The Netherlands. When will calculation take place When the transition is made from Google Maps to Webservices, nothing will change in the already calculated data. A distance calculation will take place when: You change the address data of the location. You change the branch of an employee or add a location. You change the employee’s address data. You want to determine the travel distance collectively. You change the field Automatisch berekenen (Calculate automatically) for the employee from No into Yes. Your action Maintenance > Repository > Configurate traveldistance calculation The Route field has been added again to the Send Data for determination of traveling distance screen. With Webservices the route can be calculated based on the fastest or shortest route; the default value is Fastest route. If you want to use the shortest route, you have to modify this field. If the field was already set to Fastest route before Google Maps was used, this value will now also be used. Maintenance > Repository > Determine travel distance collectively (Reisafstand collectief bepalen) The transition from Google Maps to Webservices does not result in automatic recalculations. If you want the travel distance for the entire company to be recalculated to ensure everyone uses the same route calculation, you can have the travel distance determined collectively. Company > Location If there are foreign locations and you want to include these in the automatic travel distance calculation, the Country field must be entered correctly. 2.  Configurate traveldistance calculation – Additional Rounding option (change 530662) Why If you have the commuting distance calculated by Payroll Business automatically, you can now also round the travel distance up to whole kilometers. How Management > Repository > Stuurgegevens reisafstandsbepaling (Travel distance calculation parameters) The Rounding up (whole kilometers) option (Afronden naar boven (hele kilometers) has been added to the Rounding travel expenses commuting km field (Reisk. Afronding km woon-werk) in the Configurate traveldistance calculation screen. Your action Management > Repository > Determine travel distance collectively (Reisafstand collectief bepalen) If you want to use the new option, Payroll Business has to re-determine the commuting distance of all employees. To enable this, you have to specify the required Reference date in the Determine travel distance collectively screen: 1-1-2019 or later. 3.  Travel distance calculation – Block until address changes Why If you had made deviating agreements about the travel distance calculation, or had consciously opted for calculating the one-way trip distance yourself, you could only select No in the Automatisch route berekenen (Calculate route automatically) field in the employee’s Travel expenses screen. As a result, no calculation would ever be made until you changed the field to Yes. As of this release you can have the travel distance calculated automatically when the address of the branch or of the employee changes. How Employee > Terms of employment > Terms of employment > Travel expenses The No, until address change option (Nee, tot adreswijziging) has been added to the Calculate route automatically field (Automatisch Route berekenen) in the employee’s Travel expenses terms of employment screen. When you select this option, the number of kilometers you have specified yourself will be used until the address of the location or of the employee changes. When one of these addresses changes, the No, until address change value in the Calculate route automatically field will be automatically changed to Yes. Your action When you want to use the No, until address change option, you can specify this in the Calculate route automatically field in the employee’s Travel expenses terms of employment screen. 4.  OE code displayed in the organizational structure Why When improvements to the workplace were identified – in lean terminology referred to as the Gemba walk – it was specified that the names of the organizational units were often very similar. This applies in particular to companies with a large organizational tree structure. It is, therefore, preferable to not only display the organizational unit’s description, but also its code. How Management > Repository > Organizational structure > Organizational units When the organizational tree structure opens, you will now see the description of the organizational units followed by a code in between brackets, for example Business Unit Amersfoort (10001).  Your action No action is needed. Resolved notifications 5.  Empty lines in collective leave report (change 431045) Message Company > Leave > Collective leave Sometimes empty lines were included in the report that was generated when entering collective leave. This was due to the fact that a collective day of leave was assigned to employees who were specified as being employed in the future. It was impossible to retrieve the name of such an employee, resulting in an empty line.  Solution The software has been modified. As of this release the names of employees not yet employed are also included in the report for whom a collective leave deduction in the future applies.  Your action No action is needed. 6.  Workflow could not be linked to active notification (change 1289064) Message Management > Active notification When linking a workflow to active notifications, an error message was displayed and linking was no longer possible.  Solution This problem has been solved and the workflow can be linked again as usual. Your action No action is needed. 7.  Leave - Leave date in overview and registration of double hours when not settling (change 1155337)  Message Sometimes double hours were displayed in the Not settled column (Niet verrekend) where leave was concerned that should not be settled. An employee had booked 8 leave hours that should not be settled. However, the overview stated a balance of 16 hours that should not be settled. Solution Employee > Leave > Leave balance  This problem only concerned the Not settled column (Niet verrekend) and has been solved. Your action No action is needed. 8.  Leave requested, other hours than expected are processed (change 1236776) Message Leave request through HR Self Service When leave was requested and a start and end date were specified as well as the hours, half of these hours were booked per day, and 24 hours on the last day of the leave period. This was due to the fact that the work schedule was created twice and the hours were, therefore, divided across both schedules. Because an end date was specified as well as the required leave hours, the remainder of the hours was allocated to the last day of the specified period. (With a maximum of 24 available hours per day.) Solution The software has been modified as of 1 January 2019 and no more double work schedules are created. Your action No action is needed. Publishing Date : 3/22/2019

Announcement Together towards a better performance The stability and performance of Self Service is not on the level you may expect. The professionals (PSA users) in particular may be affected by this. Reliability of our products / applications is very important to us. For this reason we are working intensively with a number of our cusomers to improve this. In the Self Service release notes a new chapter is added: ‘Together towards a better performance’. In this chapter we will inform you about the improvements we are implementing as to stability and performance. In the recent past the following enhancements were achieved. The usage of databases is optimized, making it possible for more traffic to be handled at the same time.  We moved to a new version of the database. This new version is able to handle traffic faster. Monitoring of all databases is improved. This enables us to anticipate and react to possible changes in data traffic in an improved manner. Specific processes concerning the reporting of performance issues were aligned with a number of customers. By being in direct contact with our customer we get more insights in user experience and this contributes to identify and handle the specific causes of underperformance. These steps will lead to an improved user experience. The coming period we will continue to take more steps towards a better performing product. It is possible that you will occasionally experience hindrance. We are working hard to minimize this as much as possible. Publishing Date : 8/23/2019

This document describes the new functionality and improvements introduced by this release. Some of these changes have been inspired by messages and reports from customers. Where relevant, we have included a number in the section title to refer to the identification of the message (change .....) in question in our system. Verbeteringen Betrouwbaardere levering van gegevens voor de HR Data Feed Waarom Veel van onze klanten vertrouwen op de HR Data Feed voor de levering van operationele gegevens voor hun ERP-, CRM-, Procurement-, Fleet Management- of Identity and Access Management-oplossingen en hun financiële oplossingen. Het is gebleken dat de hoeveelheid gegevens en het gebruik van de HR Data Feed steeds intensiever wordt en dat dit van invloed is op de verwerking en tijdige levering van bestanden. Dit willen we graag verbeteren. Daarom hebben we een aantal extra stappen ingevoegd om het verwerken van gegevens en het afleverproces te verbeteren en ervoor te zorgen dat gegevens vóór 06.00 uur 's ochtends beschikbaar zijn. Hoe In komende releases worden verbeteringen doorgevoerd om tijdige levering van gegevens in de toekomst te garanderen. Uw actie Er is geen actie nodig. Opgeloste meldingen Rapportmodel en HR Data Feed zijn uitgebreid met meer dan 130 nieuwe velden (change 1023780, 1027135, 1030221, 1030249, 1030391) Waarom We hebben het rapportmodel en het HR Data-model uitgebreid voor een beter gegevensbereik, door meerdere klantaanvragen tegelijk te groeperen.  Hoe Toevoegingen Alle velden voor de entiteit Garantie Loon zijn toegevoegd Er zijn twee velden aan de entiteit Overuren toegevoegd (G) Uren tijd/tijd extra (Overuren) (L) Uren tijd/tijd extra (Overuren) Velden voor Toeslagen Vast Uitgebreid toegevoegd Veld Z5 en verder Er zijn twee velden aan de entiteit Medewerker toegevoegd UPI Contract volgnummer Er is een veld aan de entiteit Rol Toewijzing UM toegevoegd Het veld Incl onderliggende OE’s Uw actie Er is geen actie nodig. Gegevens in standaardrapporten R-AL-10300 en R-AL-10320 komen niet overeen (change 999473) Melding Wettelijk verlof van vorig jaar ontbreekt in rapport R-AL-10300. Wettelijk verlof van vorig jaar wordt weergegeven in het standaardrapport R-AL-10320. Na analyse is gebleken dat Wettelijk verlof van vorig jaar niet wordt weergegeven in rapport R-AL-10300 vanwege een vervaldatum. Oplossing Het rapport is gewijzigd. Vanaf deze release worden in het standaardrapport R-AL-10300 dezelfde gegevens weergegeven als in het rapport R-AL-10320. Uw actie Er is geen actie nodig. Publishing Date : 1/31/2019

Announcements We have adjusted the june release notes.    Easycruit fields added to the 'Aannemen kandidaat' form On the form 'Aannemen kandidaat' (Accept candidate) there are now 5 fields on the "Aannemen kandidaat" form which are filled in with a (correct) value from Easycruit. However, with the import we are getting a mismatch with Self Service fields because the layout of the self-service fields differ from that of Easycruit. These values on those 5 fields are causing an error message on the form. These error messages are not acceptable. That is why we have decided to remove the automatic filling in of these 5 fields. This will take place in the July release. it's concerning these 5 fields: Gender (Geslacht) Salutation (Aanhef) Nationality (Nationaiteit) Marital Status (Burgerlijke staat) Country (Woonland) New Add attachments in recruitment process All Self Service We have a new functionality available to add attachments from Easycruit. After selecting a candidate, the user can add attachments, with a few clicks, from Easycruit to the Self service process and can now be redirected to the personnel file.  In the July release we will add 2 improvements into this process:  All attachments shall be default selected when entering the form "Kandidaat aannemen" to reduce the step to go back; After clicking on the button "Kandidaat aannemen" you get a message: ""Please note! If you press the" Accept candidate "button, you cannot go back to add attachments from Easycruit." Until the July release these instructions are the way to add the attachements from Easycruit: When a user is in the form 'Aannemen kandidaat', the user can click on the 'paperclip'. A selection screen with all available attachments will now appear. You can select or deselect each attachment on the screen. After clicking on the OK button, the user sees the selected attachments. The user can go back by clicking on the paperclip, to adjust the selection. The selected attachments are processed within the (re)hire process. The user can continue with the (re)hire process by clicking on the button: 'Kandidaat aannemen'. Modified and improved Easycruit fields added to the 'Aannemen kandidaat' form The new fields are placed on the existing 'Aannemen kandidaat' form and are immediately visible and are linked to the corresponding Rubric codes of the HR Core systems. You do not have to take extra steps. We have added the following fields to the 'Aannemen kandidaat' form. The data for these fields is provided by Easycruit: E-mail (E-mail) Telephone (Telefoon) Mobile phone (Mobiele telefoon) Solved changes Rehire: error message when searching for employee (change 1512580) Problem In one specific case, an error message appeared during employee searches. Solution As from this release, the error will not occur anymore. '500' errors in Start menu and no buttons inside a workflow (change 1443182) Problem Clicking the Start menu causes an error message to appear.  Solution As from this release, the error will not occur anymore. Error in rounding totals to exactly zero in spreadsheet (change 1354358) Problem There are some values that are very close to 0 (for instance, 2.2204460492503131E-16 or -2.2204460492503131E-16). Because of the way computers run calculations, the result of 1.1 + 0.6 -1.7 is not exactly zero (0). In this case, the value shown on the spreadsheet could be 0.00000000000000022. The problem is that we are not using twice the value of 0.00000000000000022. Instead, we are changing the value to string (treated as text), which results in 2.22.  Solution Our software will now convert small values like 0.00000000000000022 to valid values, according to the rubric (the decimal property). Note: There is a limit, and values below 0.00000000000000000000000000001 will be converted to 0.00.. Publishing Date : 5/31/2019

This document describes the new functionality and improvements introduced by this release. Some of these changes have been inspired by messages and reports from customers. Where relevant, we have included a number in the section title to refer to the identification of the message (change .....) in question in our system. Improvements Improving reliability of delivery for the HR Data Feed Why Many of our customers rely on the HR Data Feed to consume operational data to drive their ERP, CRM, Procurement, Fleet Management or Identity and Access Management Solutions and Financial Solutions and our monitoring shows we have been experiencing rapid growth of data and usage of the HR Data Feed which is impacting our ability to process and deliver the files in a timely manner. We wanted to improve this, so we have executed on several steps to improve the performance of processing all data, improve the delivery process and make sure that they become available before 06:00 am. How Additional enhancements and improvements further guaranteeing timely delivery are planned for the future and will follow in subsequent releases. Your action No action is required. Resolved notifications Report Model and HR Data Feed have been extended with more than new 130 fields (change 1023780, 1027135, 1030221, 1030249, 1030391) Why By packaging multiple customer requests simultaneously we have extended the report model and the HR data model to provide better data coverage. How Additions All fields related to the Garantie Loon entity have been added Two fields from the Overuren entity have been added (G) Uren tijd/tijd extra (Overuren) (L) Uren tijd/tijd extra (Overuren) Fields from Toeslagen Vast Uitgebreid have been added Fields Z5 and further Two fields from the Medewerker entity have been added UPI Contract volgnummer A field from the Rol Toewijzing UM entity has been added Field Incl onderliggende OE’s Your action No action is required. Data displayed in the standard reports R-AL-10300 and R-AL-10320 do not match (change 999473) Message In report R-AL-10300 there is Wettelijk verlof of last year missing. In the standard report R-AL-10320 the Wettelijk verlof of last year is actually being displayed. Analysis confirmed that Wettelijk verlof of last year is not being displayed in report R-AL-10300 because of an expiration date being taken into account. Solution The report has been modified, and starting with this release standard report R-AL-10300 will present the same data as presented in report R-AL-10320, Your action No action is required. Publishing Date : 1/31/2019

New My Reports notification Why You will now receive a notification to let you know that a report is waiting in My Reports, so you can continue to work on other tasks in the meantime. How Location: Bar at the lower left of the screen > rightmost icon, Notifications A Notifications icon has been added to the bar below the menu at the lower left of the screen.  When you create a report, you will see the number 1 next to the icon as soon as the report is available in My Reports. If there are more reports available that you have not yet viewed, you will see how many next to the Notifications icon. Click on the Notifications icon to open the list. You will then see the notifications of the reports that are ready for you in My Reports, along with their creation date and time. Click on a notification to go straight to My Reports.  The notifications are cleaned up weekly, but you can also remove a notification manually by clicking on the X next to it.  Your action  No action is needed. Modified and improved Codes shown in Employment contract selection screens Why The Employment contract screen fields now show - between brackets - the code that is associated with the chosen value in order to assist users in selecting values in fields with a list or a search function (magnifying glass icon). If the values you can choose from are very similar, the codes may help to distinguish between them. How Path: Employee > Contract > Employment contract Click in a field to make a selection from a list and you will see the corresponding code in brackets after the description. If you use the magnifying glass icon to open a field selection screen, you will see that the Value column with the corresponding code has been added next to the Description column. Your action No action is needed. Notices of recovery with a date in the future are now sent to the Absenteeism Manager Why Notices of recovery entered for a date in the future were not sent to the Absenteeism Manager. How Employee > Illness > Absenteeism This problem has been resolved: as of this release, notices of recovery for dates in the future will be sent to the Absenteeism Manager.  Your action Because previously recorded notices of recovery for dates in the future will not be sent to the Absenteeism Manager, you will have to enter these again. Please delete your old notice of recovery before entering the new one. Publishing Date : 10/25/2019

Notifications Pension entitlement for 2020 based on the state pension agreement Why  In anticipation of the actual modifications in HR Core Business and Payroll Business, this instruction can be used to calculate which employees will reach the state pension age in 2020 of 66 years and 4 months. How Reports > Check > Ad hoc reporting Open the Ad hoc reporting screen and add the Date of birth element to the ad hoc report in Excel. Go to My Reports and open the Excel file of the ad hoc report. Filter by date of birth between 1 September 1953 and 31 August 1954. These are the employees who will reach state pension age in 2020. The age will be displayed in cell D2. Enter the number of months in the cells in column E. For 66 years and 4 months, this is 796 months.  The following formula can be used in the Dutch language version of Excel to calculate state pension age: ZELFDE.DAG(D2;E2). The function can also be used for the underlying cells using the fill handle for automatically populating cells in Excel. To view the correct dates, select column E and change the format of the cells to the correct date type for the location using the right mouse button. Note: when using the English language version of Excel, you should use the following formula: EDATE(D2;E2). Changed and improved The leave of absence requests screen retains employee selection If you wanted to register multiple changes to employee leave of absence requests, you were continually redirected to the original search screen and the employee selection was not retained. This required additional mouse clicks to reselect the employee. How Employee > Leave > Leave of absence request As of this release the Leave of absence request screen works as follows: When an employee has already been selected and the Leave of absence request screen is opened, the selection fields are populated. When you open a leave request and then return to the selection screen, the selection fields are populated but the directional path is reset to company level. If you then go to another page, you will have to reselect the employee. Your action No action is required.  Size of company search panel automatically adjusted Why The company search panel upper left in the application always had a fixed size. This required a lot of scrolling for clients with a large number of companies. As of this release, the size of the search panel has been adjusted to accommodate the number of companies.  How When you click the search panel to look for a company, you will see that the size is automatically adjusted to the number of companies. The size is set to the maximum value; on an average screen that amounts to approximately 29 companies.  Your action No action is required. Resolved notifications Leave balance incorrect (change 1629890) Notification Fixed extra individual leave entitlement with a start date before 2019 was treated as a one-off. If there was a change or leave was taken causing the balance to be recalculated, this individual leave was incorrectly set to zero.  Solution The software has been modified to ensure the fixed extra individual leave entitlement is indeed regarded as fixed, even when the start date is before 2019. Your action We recommend recalculating the leave balance for those employees whose fixed extra individual leave entitlement balance has been set to zero. Individual leave disappears when entering end of employment (change 1653522) Notification When an employee’s end of employment was entered and leave was recalculated, the individual leave entitlement was set to 0. Solution This has been modified. Upon end of employment the leave is no longer set to 0. Your action Perform a recalculation for employees whose leave was incorrectly set to 0. Branch cannot be linked to Organization Unit (change 1650045) Notification It was not possible to link a branch to an Organization Unit (OU) when it had already been linked to a child or parent OU. An error message was displayed, stating that the branch was not unique within the OU.  Solution The program now checks within the OU to see whether or not a branch is unique. The error message is no longer displayed, and a branch can be linked to the selected OU.  Your action No action is required. Publishing Date : 8/23/2019

Announcements Improvements for user experience As announced in the June 2019 release notes, we have worked hard to improve the HR Core Business and Payroll Business user experience, including improving the look and feel. When you log in you will see the following changes: The field to search for a function in the menu is now more prominently at the top of the menu. Our icons have been updated. New nuances have been added to the color scheme within the screens, This gives a more pleasant screen contrast if you work in the application for a long period of time. Modified and improved Leave scheme in days Why To support leave requests of employees in Germany using our HR Core Business Global application, it is now possible to take leave in days. This means that leave accrual can take place in days and the deductions in full or half days. How Settings > Leave > Leave Entitlements  The screen used for creating a leave scheme now includes the Leave Unit field where you can choose between hours or days. The types of leave that are linked to the leave scheme are used based on this unit. The unit cannot be changed once the leave scheme has been created. The title bar of the type of leave indicates whether leave in hours or days is concerned.  If you have opted for days, leave accrual will take place using this leave scheme, based on the days in the work schedule. The number of hours an employee works per day is not taken into account. Example An employee with the following work schedule requests leave from Monday 20 May through to Friday 24 May. Mo Tu We Th Fr 4 hours 0 hours 8 hours 2 hours 0 hours For this period, 3 days will be deducted, irrespective of the number of hours for that day. Leave accrual will take place in the same way. An employee with the work schedule from the example accrues leave based on 3 working days per week, irrespective of the number of hours the employee works per day. Please note The check that is currently taking place on the maximum number per day is still based on hours: this means that the maximum is 24. Example: you want to take leave on one day and you enter as the start date and end date: 4 June 2019. If you also enter a number that is higher than 1, for example 23, the application will write off 23 days, while based on the start and end date only 1 leave day is expected. With an existing leave scheme, changing leave from hours to days is not yet supported. When creating a new leave scheme based on days, this scheme should not be linked to the Continued payment during leave (breakdown) employment benefit. This scheme always uses the hour's option. Your action No action is required.  Manager’s employee code in Organizational Unit detail screen Why Names within an organization are not always unique. It is therefore useful when the employee code of the selected manager is visible in the Organizational Unit detail screen.  How Settings > Formation and Organization > Organizational Units When a manager or backup manager is selected, the manager’s employee code will now be displayed after his/her name in the Organizational Unit detail screen. Your action No action is required.  Branch code in the Organizational Unit detail screen Why In order to determine if the correct branch has been linked to the Organizational Unit, it would be useful to not only include the description of the branch in the Organizational Unit detail screen but also its branch code. How Settings > Formation and Organization > Organizational Units When a branch is selected, the branch code will now be displayed after its description in the Organizational Unit detail screen. Your action No action is required. Values for Gender will be expanded in a next release Why In the January 2019 edition of the data specification for the Fiscal Declaration, the possible values ​​for the Gender field have been expanded, so that it is possible to correctly register persons who do not want to speak out for men or women. How Medewerker > Instroom > Aanmaken medewerker (Stap 1) Medewerker > Medewerker > Medewerkers Medewerker > Medewerker > Medewerker Medewerker > Medewerker > Partnergegevens   To meet the new specifications for the Fiscal declaration, the reference table that belongs to the Gender and Gender Partner fields contains the following values ​​from a next release.   Code Gender Description 0 Onbekend 1 Man 2 Vrouw 9 Niet gespecificeerd   Please note: these codes are passed on to the Fiscal Declaration and Uniform Pension Declaration (UPA). These values ​​are also available in other linked / receiving systems, such as HR Self Service and Management Information. Salutation The content of the Salutation field is automatically generated based on the Gender and Employee Name fields. From a next release, this field is therefore composed as follows:   Gender Name employee Salutation Composite name Onbekend Jansen <Leeg> Jansen Man Jansen De heer De heer Jansen Vrouw Jansen Mevrouw  Mevrouw Jansen Niet gespecificeerd Jansen <Leeg> Jansen   Your action If you import data from HR Core Business into your own systems via interfaces that include the Gender or Salutation fields, check whether your systems can receive the new values correctly and adjust your import process accordingly. Resolved notifications Active Notifications search screen not visible Notification When the search screen was used for Active Notifications by source date, the screen became very small when the Search button was clicked. Solution This has been resolved and following this release the search screen will retain the correct size.  Your action No action is required.  Organizational structure – OU name change not properly processed (change 958019) Notification When the & character was included in the description of an Organizational Unit, it was not always correctly displayed. The description was not processed properly and was therefore also displayed incorrectly in OrgSight.  Solution This has been resolved. As of this release, special characters such as the & character are correctly interpreted and displayed. OrgSight OU name change not properly displayed (change 958019) Notification Descriptions of Organizational Units that include special characters, such as the & character, were not always displayed correctly in OrgSight. Solution The cause of this problem has been resolved in HR Core Business and as of this release, the descriptions with special characters are displayed correctly in OrgSight. Publishing Date : 6/28/2019

This document describes the new functionality and improvements introduced by this release. Some of these changes have been inspired by messages and reports from customers. Where relevant, we have included a number in the section title to refer to the identification of the message (change .....) in question in our system. New (Re)hire (Re)hire is a special function that facilitates the hiring and rehiring process. This process will help you to check if a person has worked for your company before, for how long, and how many contracts he/she had in the past. Using this information, the manager or the person who is starting the hiring process can decide if this person should be hired on a permanent or temporary basis. Important condition You can not do this yourself. Before you can use the (Re)hire process, you have to carry out some configuration steps. Please contact your HCM-consultant for this. It concerns the following that must first be carried out: The Unique Personal ID (this is the unique key that links employment) and the contract sequence number must be correctly entered and correctly kept for the existing population. Configure the special function from Beheer menu > Workflow definition tab > Wijzigen speciale functies. Configuration The name of the new special function is (Re)hire.  Using the Wijzigen button, you can configure which workflows will be available for the users of this process. Authorizations will be taken into consideration, so you should be authorized for the special function and the workflows as well. This process is designed to work only with new workflows. If any other workflow type is configured it will not work. Usage To use the special function, go to the Start menu and the configured tab as you would for any other workflow. When you start the process, the application will guide you through three steps to see the employee’s data. Step 1 -  Search of employee The fields 'Birth name' and 'Date of birth' are mandatory. After introducing the data you can use the button Search to show the results. From this page you can also go to the new workflows that are configured to start the process for an employee who has not worked for the company in the past. When you select an employee from the list, you will be redirected to step number 2. Step 2 -  BSN Check You must enter the selected employee’s BSN number to ensure that you are authorized to see the employee’s contract data. If the BSN number is incorrect, you will receive a message. If you enter an incorrect BSN number three times, you will be redirected to the start page. Step 3 -  Contract history This step shows the contract history of the selected employee and other useful information to help you decide if the person can be rehired and with which contract type. Using the Next button it is possible to access the list of new workflows configured to start the process. Solved messages No error message when using distance calculation with no values or wrong values All Self Service Problem No error message occurs if a wrong or no zipcode, streetname or country has been filled in.   Solution As from this release, we have added several error messages in Self Service when you are filling the field incorrectly for the distance calculations. In case of zero value zipcode the error message will be: An error message occurred when calculating this distance. You have used an incorrect zip code. In case of zipcode does not excist the error messages will be: An error message has occurred when calculating this distance. You have used a not known zip code. An error message has occurred when calculating this distance. The distance calculation could not take place due to an incorrect value.   In case of incorrect zipcode format the error messages will be:  An error message has occurred when calculating this distance. You have used an incorrect zip code. An error message has occurred when calculating this distance. The distance calculation could not take place due to an incorrect value.   In case of incorrect country code format the error message will be: An error message has occurred when calculating this distance. You have used an incorrect country code.   In case the zipcode from is equal to Zipcode to the error message will be: An error message has occurred when calculating this distance. You have used the same zip code.   In case of empty country code the error message will be: An error message has occurred when calculating this distance. Country can not be empty.   Publishing Date : 3/29/2019

Changed and improved Branch linked to organizational unit twice (change 1324877) Notification Sometimes branches were linked to the same organizational unit twice without having been added twice by the same end user. As a result, data was transmitted twice to the systems linked to these branches. Solution Some branches were registered twice because the software did not check for the existence of branches in the future. Now, if a branch already exists at a future date, an error message will appear. Your action No action is required. Profile (703DV) not exported for new employees (change 1579908) Notification To enter new employees in Self Service, profiles were used through the added (703DV) field for the profile on the Contract screen with the aim of managing the employment conditions cluster. Because this field did not record the data at the correct level, it was not exported. Solution This release allows users to send profile data at contract level via the (703PS) field. Your action No action is required. Leave balance after calculation of fixed extra individual leave entitlement sometimes incorrect (change 1629890) Notification Calculating fixed extra individual leave entitlement with a starting date before 2019 did not go well because this was treated as a one-off after the release of 2019-07. As a result, the leave balance is not correct for employees with a fixed extra individual leave entitlement for whom a mutation / leave record has been recorded, so that the leave balance had to be recalculated. If there are no mutations or leave recordings recorded for these employees, the leave balance is correct. Solution From this release, the fixed extra individual leave entitlement will again be treated as a fixed entitlement. Your action If you make use of fixed extra individual leave rights in your organization, we advise you to check the balance with these employees and to perform a recalculation for leave if necessary. Publishing Date : 7/25/2019

  This document describes the new functionality and improvements introduced by this release. Some of these changes have been inspired by messages and reports from customers. Where relevant, we have included a number in the section title to refer to the identification of the message (change .....) in question in our system. New GDPR leave and absence data Why Within the framework of the General Data Protection Regulation (GDPR) it must be possible to purge employee data. In general a storage period of two years following termination of employment applies to most HR data. The storage period of this data is also referred to as the retention period. To support the retention period and deletion of the corresponding data, the Stuurgegevens AVG (GDPR parameters) screen has been included in HR Core Business as of this release. In this screen you can specify the retention period for specific leave and absence data. The selected data will be deleted when the retention period ends. This deletion procedure consists of two steps, with each deletion step taking place every two weeks: First, the data is made inactive. The data can still be viewed in the Change report where it has the Deleted Secondly, the actual deletion is performed. Following this step, the data can no longer be viewed and has been permanently removed from the application. How Maintenance > Repository > Stuurgegevens AVG (GDPR parameters) The Stuurgegevens AVG (GDPR parameters) screen can be used to specify for how many years the leave and absence data should be retained when an employee’s employment has terminated. This can be specified per company using the Add button in the upper right-hand corner of the screen. Field Explanation Gegevens AVG (GDPR data) Select the data for which you want to specify the retention period: Sickness absence Request for leave Retention period Here you can specify the number of years the data should be stored after the employee’s employment has terminated. The storage period or retention period should be at least 2 years to ensure deletion of this data does not result in recalculations. If you enter a figure lower than 2, an error message is displayed at the top of the screen and the data cannot be stored. When the retention period ends, the data is made inactive based on biweekly deletion actions. The Change report can be checked to see what data is concerned: the data in question has the Deleted status. Two weeks after having been made inactive, the data is permanently deleted from the application and can no longer be viewed. Start Bewaartermijn (Start of retention period) This has the standard entry Einde dienstverband (Termination of employment). Your action If you want leave and absence data of your employees to be deleted based on the minimum retention period of two years, you can set up the Stuurgegevens AVG (GDPR parameters) as described above. Excluding employees from data deletion based on GDPR parameters Why Sometimes it may be necessary to exclude employees from general deletion of leave and absence data when the minimum retention period of two years has ended. Therefore, individual employees can be excluded from general deletion to ensure their data will not be automatically deleted when the retention period has ended which has been specified in the Stuurgegevens AVG (GDPR parameters) screen. For this purpose an option has been added to the Employee (supplementary) screen. How Employee > Employee data > Employee (supplementary) If you do not want the data of an employee to be automatically deleted when the storage period or retention period specified in the Stuurgegevens AVG (GDPR parameters) screen has ended, you can exclude that employee by selecting Yes in the Uitsluiten van AVG (Exclude from GDPR) field in the Employee (supplementary) screen. When you leave the Uitsluiten van AVG (Exclude from GDPR) field blank or select No, the employee’s data will be automatically deleted based on a biweekly job. If you select Yes at Uitsluiten van AVG (Exclude from GDPR) and later change the value to No or leave the field blank and the storage period or retention period has already ended, this employee will as yet be included in the next deletion round. Your action If you want to exclude individual employees from deletion of leave and absence data based on the parameters specified in the Stuurgegevens AVG (GDPR parameters) screen, you should select Yes for these employees in the Uitsluiten van AVG (Exclude from GDPR) field in the Employee (supplementary) screen. Modified and improved Contract sequence number field supports periods Why  The Employee screen in HR Core Business includes the Contract sequence number field for the new re-hire process in Self Service. This field had no periods as a result of which it was not possible to specify the contract sequence number with a specific start date. How  Employee > Employees The Contract sequence number field now supports periods, as a result of which the system stores the value with the specified start date. The various values with a start data can, therefore, be seen in the history . Your action No action is needed. Identity check in relation to name and date of birth Why The Identity field is used for authorizations in the portal. Now it is possible to issue the same identities multiple times. The existence of an identity is checked in the portal. To ensure that the identity of a specific employee is unique, the name and date of birth combined with the identity are checked upon identity entry (check at the source). How Employee > Employee data > Employee (supplementary) When the Identity field is entered in the Employee (supplementary) screen, the system will check if the specified Identity already exists. If it does, the system will check if the last name and date of birth of the employee with the existing Identity match those of the employee with the newly entered Identity. This check only takes place when a new Identity is registered. If the name of an employee were to change in the future, the system will not check whether that name belongs to a non-unique Identity. Your action No action is needed. There will be no retroactive check to ensure existing Identities are unique. Resolved notifications Extended Change report for leave is not included in My Reports (change1198351) Reports > Audit summaries > Change report (extended) Message If at Change report (extended) you opted for leave elements at the selection criteria, the system specified that the report had been included in My Reports. However, the requested Change report (extended) was not available in My Reports. This issue only occurred when leave elements were selected. With other elements the change report was indeed available in My Reports. Solution This technical issue has now been resolved. Your action No action is needed. OrgSite – Extended search functionality did not work correctly (change 465756) Message If you wanted to search for a specific term in OrgSite, but not by last name, only approximately matching results were displayed and no exact matches. Solution To make it possible to use other search criteria than just last name, but based on an exact match with the search term, the Expliciet zoeken (Explicit search) option has been added to the search function. Your action You do not have to take any action. Publishing Date : 2/22/2019

Modified and Improved Recruitment fields in 'Accept candidate' form In the release notes of June and July we communicated that we would make a solution for the 5 fields on the 'Accept candidate' form because the layout of the Self Service fields differs from that of Recruitment and Selection. The values in these fields are causing an error message on the form. From now on the import of data for these fields are transferred from the values of Recruitment and Selection automatically to the correct value within the Self Service fields. It concerns the following fields: Title Marital Status Country Gender The field: Salutation is only being presented in the candidate form because the HR Core has no seperated field for this value. Pay attention: When you use the connection with Recruitment and Selection you have to use the standard from Recruitment and Self Service tables. Publishing Date : 8/12/2019

Modified and improved  Reference date and filters – Request for leave screen Why  The Request for leave search screen contained all the requests for leave of all the employees within the selected company. As a result of this, loading the data on the screen and searching the data took a long time. That is why a reference date has been added to the screen that, in combination with a filter, can be used to refine the search for specific requests.   How  Employee > Leave > Request for leave Based on the specified reference date the requests for leave that were active on that date are displayed. For example, if you enter the reference date 1 February 2019, all the requests for leave that start on, are still active on or end on 1 February 2019 are displayed. A search term can be entered in the fields above each column to further refine the search, for example, by specifying (part of) the name of an employee. The same applies to the employee code, the contract, the contract ID or the date the request for leave was submitted.  Your action No action is required.  Resolved notifications Opening the Request for leave screen takes too long (change 901938) Notification  The retrieval of requests for leave often took very long because all the requests for leave, including the historic requests, of all employees had to be loaded in the Request for leave screen. Solution Employee > Leave > Request for leave The Request for leave screen has been modified and the information is displayed quicker. The requests for leave are now filtered based on the reference date. This means you will only see the requests for leave of which the end date of leave is beyond the reference date. The displayed requests for leave can now also be filtered by specifying a specific (part of an) employee name or employee code in the fields at the top of the screen. It is also possible to filter by the date the request for leave was submitted. Your action No action is required. Publishing Date : 5/24/2019

New Holiday clusters Why In order to allow users to enter non-Dutch holiday calendars, it is now possible to create holiday clusters with holidays that are pre-defined at system level. These holiday clusters can then be linked to individual employees.  How  Settings > Work pattern > Holidays clusters In the Holiday clusters screen, you can create a holiday cluster by adding holidays from the predefined list. Employee > Contract > Employment In the Employment screen, you can use the Holiday cluster field to link an employment contract to a cluster. If you do not select a holiday cluster here, the default (Dutch) holiday calendar will remain active. Your action  If you want to use a non-Dutch holiday calendar, you have to create one by following the steps above. Resolved notifications Authorization – custom screens mutable for Read-Only profiles (change 987620) Notification Users with a Read-Only profile were still able to make changes through custom screens.  Solution Custom screens have been included in the Read-Only authorization for this release. This allows users with a read-only profile to view data using custom screens, without being able to make any changes. Your action No action is required. It was not possible to terminate an organizational unit because the unit in question was still linked to a number of employees (change 1629999) Notification While trying to delete an organizational unit, an error message appeared indicating that there were still active employment relationships between the unit and a number of employees. However, it was not possible for the client to identify the employees in question. Solution We identified the employees in question and relayed this information to the client, allowing them to remove the employees/allocate them to a different unit.  Your action No action is required. While trying to open the Employment screen for certain employees, an error message appeared (change 1558042) Notification When opening the Employment screen, an error message appeared for certain employees. Solution The error was caused by a data element that had been changed from a percentage type to a factor because of the Part-time percentage. The conversion to the part-time factor had not been carried out for the employees in question, preventing the client from accessing the Employment screen. The problem was solved by carrying out the conversion for these employees. Publishing Date : 9/19/2019

Changed and improved 1.  From now on, codes will also be displayed in the employment contract’s history screen Why When selecting values in fields with a list or search function, the Employment contract screen field now shows the code between brackets after the description. There is also a need to display this code in the history of the Employment contract screen.  How Employee > Contract > Employment contract > History The Code column has been added to the screen with the history of the Employment contract, and includes the code associated with the description of the values. Your action No action is required. 2.  Now possible to review existing references for organizational units Why Terminating an organizational unit is not possible if there are still active references. These references or links may be valid at any given time, which complicates determining the reference in question. This resulted in a need for information about existing references.  How Settings > Formation and Organization > Organizational Units  In the top right corner, the icon Linked elements has been added to the screen containing information on an organizational unit. When selecting an organizational unit, click on this icon to review current references. The Linked elements screen displays the type of reference that exists, for example, a role assignment, the reference details, and the effective start date. This information simplifies the process of terminating an organizational unit.  Your action No action is required. Resolved notifications 3.  Error message when opening the Organizational units screen (change  1722110) Notification An incorrect error message would sometimes appear when opening the organizational units screen.  Solution This has been resolved. The error message no longer appears. Your action No action is required. Legislation and regulations 4.  Changes to the state pension (AOW) age Why By adopting the Postponement of an increase to the state pension Act, the increase of the state pension age will slow down and the state pension ages for 2020 and in the following years need to be amended. How Employee > Employee > Employees The field old age pension effective start date  for the Employees screen displays the old age pension (AOW) age determined by the system based on the date of birth and the statutory state pension age. The table below shows your former state pension age and your new state pension age based on the new Act.   Year The state pension age was The state pension age becomes 2019 66 years and 4 months 66 years and 4 months 2020 66 years and 8 months 66 years and 4 months 2021 67 years 66 years and 4 months 2022 67 years and 3 months 66 years and 7 months 2023 67 years and 3 months 66 years and 10 months 2024 67 years and 3 months 67 years We will amend the state pension ages in the software as indicated in this table. This process may take some time. We will begin by updating the upcoming AOW dates so employee files with an effective old age pension date in January 2020 will be amended first. Employees with an effective old age pension date in February 2020 and later will then follow. Once the effective old age pension date has been amended for all employees, we will inform you via a message on the Portal. Your action No action is required. Publishing Date : 11/22/2019

  New New field Ping Identity in Mutation report Why In addition to the Portal username of an employee, a new Ping Identity field will be filled with the employee from this release. This Ping Identity is used within Raet to make Single Sign On possible with its own modules or modules from third parties. How A Ping Identity is assigned to the user account of the employee within Raet's IAM module. During a nightly import, this Ping Identity is also stored in the employee's HR Core Business and is therefore visible in the mutation report under the user Service interface. Your action No action is needed. Resolved notifications Organizational structure – errors in OU structure (change 1127999) Management > Repository > Organizational units Message When opening the organizational structure from a specific date, an error message appeared, so that it was not possible to modify the organizational structure.  Solution Underlying attributes of the organizational unit had an earlier start date than the organizational unit itself, and this caused an error message to appear. The problem was solved by bringing the start dates into line.  Your action No action is needed.  Active notifications were not e-mailed to external email address (change 1173241) Management > Active notification Message Active notifications were not emailed when the notification date for the source date was reached. The reason was that, in specific cases, it was not possible to send emails to external e-mail addresses. This problem was caused by a memo field that could not be filled in and saved. The default email text based on the description of the notification definition was not saved. This meant that the email text was empty and no e-mail could therefore be generated.  Solution This problem has been solved. The overdue e-mails on January 8, 2019 have since been sent and the active notifications will be sent again as soon as the source date has been reached. Your action No action is needed.  Start leave year Company > Leave > Grant leave entitlement Message If the leave year 2019 was started for the customer, several leave years were created. Sometimes the new year 2019 was not created. This was reflected in the employee Leave balance screen where the future years were shown. Due to the production of future years, it was not possible to create 2019 yet. Solution This has been resolved. The future leave years have been corrected. Your action No action is needed.  Active signalling (change 1173241) Maintenance > Active signalling Message If e-mail was set up as active signalling, it was not sent. The alerts, however, appeared in the action list. Solution This has been resolved. As of January 7, the outstanding alerts have been sent and the active alerts are sent again as soon as the source date has been reached. Your action No action is needed.  Publishing Date : 2/1/2019