Releases YouServe

In een extra release van 11 september 2019 is het volgende gewijzigd. Gewijzigd en verbeterd Zoekfunctie Archief uitgebreid Alle Self Service Waarom Self Service gebruikers controleren meestal mutaties uit de recente geschiedenis. Op basis van de huidige filters worden te veel items getoond. Hoe Het is vanaf nu mogelijk om mutaties te zoeken per ingangsdatum. De zoekfunctie van het Archief is met ingang van 11 september 2019 uitgebreid met een ingangsdatum (vanaf t/m) filter. Naast de gebruikersvriendelijkheid zal dit scherm door het gebruik van de nieuwe filters sneller de gegevens ophalen. Dit filter toont als default waarde de mutaties met een ingangsdatum startend vanaf 3 maanden geleden t/m vandaag. Indien gewenst kunt u een andere tijdsperiode selecteren. Uw selectie wordt bewaard zolang de sessie duurt. Indien u op het rode filter drukt dan maakt u de periode leeg en kunt u een nieuwe periode selecteren. Als u dit scherm verlaat en u daarna ernaar terugkeert, zal de laatst gebruikte selectie weer worden getoond. De ingangsdatum waarop kan worden gezocht is de ingangsdatum die u rechtsboven in de formulieren ziet staan. Publishing Date : 9/18/2019

Changed and improved Sector and Risk group in Digipoort for week 42 sickness notification Why Pursuant to the Labor Market in Balance Act and starting on 1 January 2020, HR Core Business and Payroll Business will no longer use the Risk Group to determine the unemployment insurance (WW) contribution. The UWV (employee insurance agency) still uses this field as an identification key, meaning they still expect to receive it.  How Although you no longer need to register the risk group in HR Core Business, we will continue to transmit it to UWV. Starting on 1-1-2020, we will fill out the following risk premium groups for a new payroll tax number and/or sector code: 07 for the employment agency sector (sector code 52) 03 for the graphics sector (sector code 09) 01 for other sectors Your action No action is required.  Generate work schedule for a maximum of two years Why Until this release it was possible to set the end date for generating a work schedule as 31-12-9999, which meant that work schedules could be generated in advance for thousands of years. This could lead to enormous amounts of work schedule data, which could inundate interfaced systems. It can also be convenient to generate a work schedule for shorter periods to conduct periodic checks from time to time.   How Settings > Work pattern > Generate work schedule  You are now required to enter an end date in the End date (max. 2 years) field. This can be up to two calendar years in advance from the Start date field. If you enter an end date that is more than two calendar years in the future, the system will not accept the date and will delete your entry in the End date (max. 2 years) field. Your action No action is required. Resolved notifications E-mail addresses with certain extensions were no longer stored in HR Core Business (change 1866682) Notification It was no longer possible to save e-mail addresses with the extension @xx.xxx.com in HR Core business, because these were not recognized as a valid e-mail address. However, it is sometimes necessary to save e-mail addresses with the extension @nl.visma.com, as well as e-mail addresses with the extension @visma.com (the extensions shown are examples). Solution This has been resolved. Starting with this release, you can once again save e-mail addresses with a @xx.xxx.com extension.  Your action No action is required. Publishing Date : 1/23/2020

New New Terms of employment for Belgium Why  As of this release, two new terms of employment are available for recording information that companies based in Belgium may need: Terms of employment Belgium and Suspensions Belgium. These terms of employment are only intended for registering this information. The data you record in these screens is not be used for salary processing.  How Settings > General > Term of employment clusters As of this release, you can add the Terms of employment Belgium and Suspensions Belgium terms of employment to a terms of employment cluster by using the Terms of employment cluster function. Enable the Auto selection option if you want these terms of employment to be added by default when assigning the terms of employment cluster to a new employee. Employee > Contract > Terms of employment Use the Terms of employment screen to link the new terms of employment to an employee. Action If you wish to use these new terms of employment, add them to the terms of employment cluster or link them to the relevant employee(s).  Modified and Improved More information on the Leave balance screen Why Customer feedback indicates a need for more information on the Leave balance screen, such as the employee’s date of birth and leave scheme, and the reason for a leave request.  How Employee > Leave > Leave balance As of this release, the following information has been added to the Leave balance screen. At the top of the Leave balance screen, the date of birth and the applicable leave scheme. The Reason column, where you can see why a leave request was submitted. Action No action is required. Improved performance of Leave balance overview per month report and Collective leave report Why In previous release notes we announced that we were working on improving the operational reports, starting with leave reports. Release 2021-01 includes improvements to the final two leave reports: Leave balance overview per month and Collective leave. The functionality of these reports has not changed. How Settings > Leave > Collective leave Settings > Leave > Leave balance overview per month Generating reports is now faster. If you run the Leave balance overview per month report, you will see that Excel is the default value in the Save as field. If necessary, you can change this value to PDF. Action No action is required. Raet HR interfaces > Youforce users extended Why It would be convenient if administrators could arrange for the UPI to be included in the Youforce users extended interface so that the Youforce portal can use it to provide Identity and Access Management (IAM) services based on the unique personal identification (UPI). How Settings> Data exchange> Raet HR interfaces > Youforce users extended interface  The UPI required option has been added to the Youforce users extended interface. If this option is enabled, only those employees will be sent to the portal that have a completed Unique Personal ID (UPI) field. Action If you only want to send employees with a completed UPI field to the Portal, check the UPI required option to enable it. Organizational Unit - Sorting search field to look up manager Why If you had enabled the Search by employee code option at the bottom left of the general screen in User settings , the manager look-up in organizational units feature had not yet been adjusted accordingly and the system still showed the Company field first. We have now made the appropriate software adjustments in this release based on user feedback. How User settings  If you have enabled searching by employee code in the User settings, from now on you will see the employee code as a search parameter instead of the company when searching for the manager in an Organizational unit. Action No action is required. Import sick leave optimized Why It would sometimes take a considerable amount of time to collect all required data when importing sick leave before the entire file was finally processed. This caused an unnecessary interruption in the process when importing multiple files. We have now optimized the import process to resolve this inconvenience.  How We have adjusted the procedures for collecting data during the import to reduce file processing time, meaning imports in HR Core Business are now processed faster. The time savings will be especially noticeable when importing smaller files. Action No action is required. Solved Messages Unlink profile from Profile group Message If you had added a Profile to a profile group and you wanted to remove this profile from this profile group on the same day (e.g. because it was incorrectly linked), the system would not save the change and this profile would remain linked to the profile group after saving. Solution Settings > Recording > Profiles This has been resolved. You can now remove a profile from a profile group on the same day as you added the profile.  Action As of this release, you can remove profile groups that were incorrectly linked from a profile group on the start date. Unknown Organizational unit codes in CSV for employees who were transferred via import (1839613)  Message When exporting the Organizational unit (OU) codes via Export CSV, the file showed strange OU codes instead of the OU codes that were imported and visible in the Employment contract screen.  Solution The strange OU codes only appeared in very specific cases, in which only the code was requested in a report. There was no problem when requesting a report with the OU description. This problem has been resolved as of this release. Now, the Export CSV report displays the correct OU code, which is linked to the employee. Action No action is required. Nationality code table was not up to date (2309997) Message The nationality code table did not match the tax administration’s current codes for 2020. As a result, it was not always possible to record the correct nationality in accordance with the official list.  Solution We have adjusted the nationality code table to reflect the tax administration’s official list for 2021. This means that some nationalities are no longer visible, that the description of a number of nationalities has been changed, and that new nationalities have been added. Action We have informed all customers who have entered these nationalities for employees so that they know what they need to change as of 1-1-2021. This change has no direct impact on other HR Core Business users. Memo field in Pregnancy and maternity leave (WAZO) screen generated an error (2270912) Message Adding text to the memo field when saving an illness report resulted in an error message. You could only add text to the memo field after you had saved the illness report. Solution Employee > Leave > Pregnancy and maternity leave (WAZO) This has been resolved. You can now add a memo in the Pregnancy and maternity leave (WAZO) screen without saving the illness report first. Action No action is required. Publishing Date : 12/23/2020

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

Op deze pagina is alles terug te vinden over de kennissessie Release HR Core /  Payroll Business die gegeven is op dinsdag 31 augustus 2021. - Opname presentatie - Presentatie slide deck

Notifications Again - Duplicate sick reports were added when importing consultant’s Excel file The September release notes included this message about incorrect addition of duplicate sick reports as described below. Due to a problem with this modified functionality we have revoked the modification on 30 August 2021. The modification has now been improved and will again be available in the October release. Why When an Importing absence file was read in the Import Excel file (Consultant) screen that inadvertently contained duplicate sick reports, the Sick leave screen showed two lines with active sick leave. However, only one sick leave is allowed per contract. In the Sick leave screen it is not possible to enter a new sick leave for an employee with an active sick leave because the system checks for this and an error message will be displayed. When importing sick leave this check was not performed, resulting in duplicate sick reports with the same start date. How Management > Import/Export > Import Excel file (Consultant) Employee > Illness > Sick leave The software has been modified to ensure an Importing absence file with duplicate sick reports no longer results in duplicate active sick reports when it is read using Import Excel file (Consultant). We have also made sure this is not possible through other channels for reporting sick leave, such as API and HR Self Service. Action No action is required. Person level improved – Identity now processed in the same way as UPI We made the following functionality available on 1 September 2021. Why When an employee is hired, the system can determine whether it concerns a new or a returning employee. With a new employee the system assigns a new UPI or Identity. Identity (7013) is used to identify the user in the portal. Unique Personal ID (UPI) (7014) is used to identify a person and can also be used when the person level is not used. With a returning employee the system used to assign the old UPI but not necessarily the old Identity. This resulted in problems in the portal and other systems. That is why the system now processes the UPI and the Identity in the same way. How To enable the system to process the UPI and the Identity in the same way, the software has been modified as follows.  Settings > Recording > Parameters UPI As of 1 September 2021 the name of the Parameters UPI screen has changed to Parameters UPI/Identity. The Fill Identity with field has been added to specify what the employee’s Identity field should contain. When the employee’s Identity is already known in the system, i.e. a person with an Identity already exists for the UPI, the known Identity is used. Note: the preference specified in the Fill Identity with field for Identity applies when a new Identity has to be created. The Fill Identity with field has the following values: Generate automatically The Identity field is to be specified by the system automatically. With this option the Sequence number field and the Leading zeroes option are displayed.  Enter a sequence number if the Identity that is automatically generated should be based on this sequence number +1, this sequence number +2, etc. If the Leading zeroes option is selected, the Total length field is displayed and the leading zeroes are added to the automatically generated Identity up to the maximum length specified in Total length.  Use employee code The Identity field will automatically be filled with the employee code. Use employee UPI The Identity field will automatically be filled with the UPI. Use Identity preference The Identity field will automatically be filled with a preference value. This field will be made available through Self Service. For example, Email address or a value from the organization’s free fields. This field can be modified through an import. When nothing is entered here, the Identity field will remain blank. When Use Identity preference is selected in the Parameters UPI/Identity screen, the Identity preference field can be changed in HR Core Business, or the value will be entered through Self Service when the 10526800PS category is included in the Self Service workflow/processes. In all other cases the Identity preference field remains blank and cannot be changed in HR Core Business. Inflow/Outflow > Create employee Employee > Employee > Employee (supplementary)  The Identity preference field has also been added to the Employee (supplementary) screen and in the Create employee wizard, so it is assured in all our processes. Note: when an Identity is explicitly specified when creating an employee using Self Service category 7013PS, that value will be adopted in HR Core Business without validation. Validation will take place during processing. When in the Parameters UPI/Identity screen it has been specified that the Identity should be assigned automatically, the Identity field can remain blank. The Identity will then be assigned automatically. Action Specify your option in the Fill Identity with field in the Parameters UPI/Identity screen with the required start date to ensure one method is used for the Identity throughout the organization. Include category 10526800PS in the Self Service processes if the Identity preference field is to be used.  Modified and Improved GDPR – Some data was wrongly synchronized between Person level and Employee level Why Some data was wrongly synchronized between the Person level and the Employee level. Some of the data has to be removed or anonymized to comply with GDPR. How  The data that was wrongly synchronized between the Person level and the Employee level has been removed from the synchronization process. The data that had to be removed or anonymized to comply with GDPR has later been added and will be properly removed or anonymized as of the October release. Action No action is required. Work schedule can now be generated for a period longer than 2 years Why Up till now work schedules could only be generated for a maximum period of 2 years. Where parental leave is concerned, for example, work schedules for a period longer than 2 years are useful, which is why as of this release a work schedule can be generated for a longer period. How Settings > Work pattern > Generate work schedule As of the October 2021 release a work schedule can be generated for a maximum period of 4 years. Action No action is required.  Solved Messages List of values only consisted of 20 pages (2851105) Message  The List of values screen only showed a maximum of 20 pages. When the list of an Element consisted of more than 20 pages it was not possible to view all the values.  Solution This has been resolved and as of this release the List of values screen includes more than 20 pages. Action No action is required.  HRSS parental leave failure (2848055) Message  It was not possible to request parental leave with a start date that equaled the date of employment.  Solution The software has been modified and as of this release it is possible to hire an employee on, for example, 01-10-2021 and request parental leave as of 01-10-2021. Action No action is required. Publishing Date : 9/21/2021

Op deze pagina is alles terug te vinden over de kennissessie Release HR Core /  Payroll Business die gegeven is op dinsdag 01 juni 2021. - Opname presentatie - Presentatie slide deck - Vraag en Antwoorden vanuit presentatie

De releases van zaterdag 29 januari zijn afgerond. Alle applicaties zijn weer beschikbaar.

Notifications 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 uniqueness 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. New Request for supplementary childbirth leave when registering the child Why 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. How 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 Why 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.  How 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. Example 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 Why 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. How 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 Why 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.  How 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 Message 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. Solution 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

Hierin vind je de opgenomen video van de presentatie

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

Mededelingen Online release sessies  Diverse klanten hebben ons gevraagd om naast de release notes een online release sessie te organiseren, waarin wij de aanpassingen van de betreffende release nader toelichten. Wij geven hieraan graag gehoor. Zoals reeds in de release notes van februari aangegeven, starten we als pilot in de week na de release een kennissessie van één uur, waarin we de belangrijkste zaken uit de release nader toelichten. Tijdens de sessie besteden we extra aandacht aan de zaken waarvoor je actie moet ondernemen om gewijzigde of nieuwe functionaliteit juist en volledig te gaan gebruiken. Hiermee hopen we de release notes en de acties die bij bepaalde onderwerpen zijn vermeld te verduidelijken. De eerste release sessie zal plaats vinden op dinsdag 2 maart om 14.00 uur. Als je hieraan wilt deelnemen, kun je je aanmelden via de Evenementenkalender van Payroll Business. Nieuwe interface 'Loonstroken naar Dynamic Payslip' nog niet actief  We zijn bezig met functionaliteit te maken zodat je dynamische loonstroken kunt aanbieden aan je medewerkers. Op dit moment zie je in het scherm Beheer - gegevensuitwisseling - interfaces de nieuwe interface 'Loonstroken naar Dynamic Payslip' al staan. Deze nieuwe interface wordt echter alleen getoond en is nog niet beschikbaar. In de volgende release zullen wij meer uitleg hierover geven.  Opgeloste meldingen UPI’s kunnen niet worden ingelezen (2486778) Melding  We hebben geconstateerd dat in sommige situaties de UPI niet ingelezen kan worden als bij een medewerker twee geboortedatums in het systeem voorkomen. Dit wordt veroorzaakt door een aanpassing van een geboortedatum per andere peildatum. Voor elke geboortedatum wordt ook een pensioendatum berekend en dit veroorzaakte een foutmelding. Oplossing Vanaf de maart release is de code aangepast waardoor UPI's worden ingelezen zonder dat hierbij een foutmelding wordt getoond. Mocht er toch 2 (afwijkende) geboortedatums zijn voor 1 medewerker, dan worden deze datums gekopieerd naar de persoon in chronologische tijdvolgorde. Actie Er is geen actie nodig. Verlof over jaargrens met invoering Wet Wieg (2179372) Melding  Als je aanvullend geboorteverlof over 2 kalenderjaren wilt opnemen is dit niet mogelijk omdat het systeem aangeeft dat er onvoldoende saldo is. Oplossing Na de release van maart is het mogelijk om aanvullend geboorteverlof over de jaargrens heen op te nemen. Actie Als het aanvullende geboorteverlof over de jaargrens nog niet is aangevraagd, dan kan je dit nu wel indienen. Anders is er verder geen actie nodig.  Contactpersoon 2 wordt niet verwijderd (2441425) Melding Indien er vanuit Self Service werd doorgegeven dat er 2 contactpersonen verwijderd moesten worden bij de medewerker leverde dit een uitgevallen mutatie op.  Oplossing Na de maart release zal de mutaties voor het verwijderen van een tweede contactpersoon correct worden verwerkt en niet meer in de uitval terechtkomen.  Actie Er is geen actie nodig. Publishing Date : 2/19/2021