- New
- Payslips and annual statements to File API interface added to Manual start of automatic interfaces
- Contract number from now on completed automatically
- Adding data elements to XML of payslips and annual statements for File API
- Modified and Improved
- Loading spinner included in Define merge function screen
- Ending organizational unit without recalculating OU structure
- Organizational units - Linked elements report
- Solved Messages
- Error report did not contain employee error data(3000248)
- Person synchronization sometimes took a very long time (3018772)
- Importing organizational unit with eight-digit code (2944213)
- Role assignments can be imported again (3010272)
New
Payslips and annual statements to File API interface added to Manual start of automatic interfaces
A specific interface can be restarted using Manual start of automatic interfaces to (re)create specific files of a period. As of January 2022 the payslips and annual statements can be retrieved through a File API, which is why the interface concerned can be restarted.
How
Management > Data exchange > Manual start of automatic interfaces
The list of the Interface field in the Manual start of automatic interfaces screen now contains the Payslips and annual statements to File API option. When this option is selected, the screen only displays the last final payroll processing run. Select it and click Restart.
Note
Only the payslips can be retrieved. If the annual statements have to be retrieved, use Management > Annual closure > Request annual statements. Select the year, specify the employees for whom you request the annual statements and click Request.
Further details
Further details about retrieving the payslips and annual statements through a File API can be found in the Payslips and annual statements to File API Help topic, using the search term: File API.
Contract number from now on completed automatically
Why
As of release 2022-01 we ensure that under specific conditions the contract sequence number (Element 7430) is completed automatically based on the information available in HR Core Business. The use of contract sequence numbers and automatic completion thereof has been introduced in preparation of the Chain control function.
Conditions
The contract number is only completed automatically when:
- A customer uses the person level, and
- An employee is hired and a UPI is used (Unique Personal identification)
Person level: by linking each employee to a person it becomes clear how often an employee has been hired by the organization. The use of the person level is particularly useful when the organization has a high staff turnover and many rehirings.
How
Employee > Employee > Contract history
When an employee with a UPI is hired and the person level is activated, it is checked if the UPI or person code already exists.
- If so, the employee will be linked to the already existing person.
- If not, a new person is created in the system and the employee is linked to this new person.
The correct sequence number is automatically specified in the Contract sequence number field in the Contract history screen. A customer or consultant can modify the sequence number manually if necessary.
No conversion takes place
No conversion takes place of existing employees who have been linked to a person. As a result, the contract sequence number for the existing population is not calculated. The customer must do so manually.
The contract sequence number can always be modified.
Note: when a contract sequence number has been modified manually, the consecutive sequence number for the next employee will be calculated automatically.
When the contract sequence number has not been specified yet and one person has multiple employees, the contract sequence number for the next employee will be the total number of employees linked to that person.
Example
- Person 123 - Employee 1 - contract sequence number (not specified)
- Person 123 - Employee 2 - contract sequence number (not specified)
- Person 123 - Employee 3 - contract sequence number (not specified)
Employee 4 is added to person 123:
- Person 123 - Employee 3 - contract sequence number 4
Further details
Further details about the use of contract sequence numbers and the person level can be found in the following Help topics:
- Procedure description > Contract sequence number (search term: contract sequence number)
- Screens and fields > Employee > Person > Person (search term: Person)
Action
No action is required.
Adding data elements to XML of payslips and annual statements for File API
Why
Payslips and annual statements can be imported in a native HR system or portal through the File API for payslips and annual statements. Some HR systems have their own key fields for recognizing an employee. As of this release these key fields can be added to the XML for payslips and annual statements as a data element in order to facilitate recognizing employees.
How
Settings > Recording > Selection properties
The Payslip API key field option has been added to the list of the Selection property field in the Selection properties screen.
Steps
Adding a key field:
- Select the Payslip API key field property in the Selection property field.
- Right-click the Add icon and select Data element in the Type field in the screen where the element is selected.
- Click Search, select the required element and click Add.
This selection property can only be used to add data elements.
Payroll Business only provides the XML of the File API with the first data element of the selection property. This is the element at the top.
Addition to XML file
The group tag CustConf has been added to the XML file and contains:
- Code - the number of the data element
- Description - the description of the data element
- Value - the value of the data element at the employee
Action
When using this function and adding a custom field to the XML file, use the steps specified above.
Modified and Improved
Loading spinner included in Define merge function screen
Why
When a search term was entered in the Define merge function screen, sometimes a blank screen was displayed and it was unclear whether data was being loaded. That is why a loading spinner has been included in the screen.
How
Management > HR Easy Docs > Define merge function
A loading spinner 
Action
No action is required.
Ending organizational unit without recalculating OU structure
Why
When an end date was specified for an organizational unit, this always resulted in recalculation of the whole organizational structure. Recalculation is not necessary when nothing else in the organizational structure has changed. And recalculation sometimes caused the system to become less responsive. Unnecessary recalculations will now no longer be performed.
How
Settings > Staffing and organization > Organizational units
As of release 2022-01 the software has been modified and recalculations following a change in the organizational structure are only performed when necessary.
Action
No action is required.
Organizational units - Linked elements report
Why
The Linked elements pop-up screen can be displayed using the Linked elements icon 
How
Settings > Staffing and organization > Organizational units > Linked elements pop-up screen
The Create report button has been added to the bottom right of the Linked elements screen. With this button the contents of the pop-up screen can be exported to an Excel file that can be viewed in My reports.
Action
No action is required.
Solved Messages
Error report did not contain employee error data (3000248)
The solution has been included in the additional release of 11 December 2021
Message
When sick reports were imported and an error occurred, the processing report could not be used to determine where the error occurred. It was, therefore, not possible to ascertain for which employee additional actions were necessary.
Solution
Management > Import / Export > Import Excel file (Consultant)
Employee > Illness > Sickness absence
This has been resolved in the additional release of 11 December 2021. The processing report has been updated and shows where the error occurred to ensure correct actions can be performed, for example by manually entering the sick report.
As of the September release importing sick reports and recovered reports is done in the same way as entering sick reports and recovered reports using the Sickness absence screen. The outstanding sick reports must be closed before a new one can be entered. It is, therefore, not possible to register both the recovery report and the new sick report in a single import. These reports must be processed using two separate files. This is to ensure no double sick reports are processed.
Action
No action is required.
Person synchronization sometimes took a very long time (3018772)
Message
Sometimes synchronization of data – a background process – to a person and other employees took a very long time. This was caused by the creation of a queue of regular changes.
Solution
The synchronization process has been modified and large numbers of changes are now processed separately to ensure regular changes can be processed without disruption.
Action
No action is required.
Importing organizational unit with eight-digit code (2944213)
Message
When an organizational unit was imported for an employee using the Upload external mutation file function, an error message was displayed stating that the code does not exist.
HR Core Business always regarded a numeric eight-digit OU code as a mutkey: an internal technical number.
Solution
Now when a numeric 8-digit OU code for a customer is imported, it is checked whether this code already exists. If not, it is checked if the technical code exists. If neither of these codes exist for the customer concerned, an error message is displayed.
Action
No action is required.
Role assignments can be imported again (3010272)
Message
The list of available definitions in the following screens:
- HR data import definition
- Create Excel file (Consultant)
- Import Excel file (Consultant)
no longer included the Import Role assignment option.
Solution
Management > Import/Export > HR data import definition
Management > Import/Export > Create Excel file (Consultant)
Management > Import / Export > Import Excel file (Consultant)
The Import Role assignment option is now available again in all languages.
Action
If the role assignments to be added have not yet been entered manually, these can be imported through a spreadsheet as of release 2022-01.
.gif "VISMA"){kind=icon}
Over Visma
Copyright 2022 Visma Community. All right reserved.
Visma Denemarken
Visma Finland
Visma Letland
Visma Nederland
Visma Noorwegen
Visma Zweden
Visma Developers & Partners
Visma Latijns-Amerika