Visma.net Employee Data Import

Modified on Tue, 25 Aug at 4:09 PM

>>>Submitted by: Carsten Gondorf



Overview

Simployer One can import employee data from Visma.net (inbound). The employee import retrieves employee information from Visma.net and brings it into Simployer One, so you can create or update employee records based on data already maintained in Visma.net. It covers personal data, employment data, and compensation data.

The import is manual, not scheduled. It is intended for getting your existing Visma.net workforce into Simployer One when you first set up, so onboarding starts with correctly mapped data instead of manual re-entry. Before anything is written, the admin previews the field-level differences and confirms.

Start small. For all new integration setups, run your first import with only a few users in the import scope. This helps ensure data accuracy and a smooth onboarding before you include your whole organization. We recommend importing in batches rather than your whole organization in one run.


What this article covers

1. How It Works
Import flow explained
2. Prerequisites
What you need first
3. What Gets Imported
Fields and matching
4. Run an Import
Step-by-step
5. Import Results
Tabs, statuses, results
6. Key Rules
Matching, limits, timing


How It Works

This is an inbound integration: employee data flows from Visma.net into Simployer One. Employees are matched between the two systems using their employee number. The import reads employees and their positions from Visma.net, compares them with Simployer One, and shows a preview of what will be created or updated. Nothing changes in Simployer One until you confirm.

The import never deletes employees in Simployer One, and absence data is not part of the employee import.

Inbound Employee Flow

Visma.net
employees with positions
Import Preview
review changes, then confirm
Simployer One
employee records

For each matched employee, the values from Visma.net update the corresponding fields in Simployer One. Employees that exist only in Simployer One are left untouched.

This is not a two-way sync. The employee import (inbound, Visma.net to Simployer One) is a one-time setup step. The ongoing employee data flow runs the other way, outbound from Simployer One to Visma.net, through the standard integration. For the outbound direction, see Visma.net Integration (employee data export).


Prerequisites

Employee import enabled for your company. The feature is turned on per company. If you do not see Employee import under Settings > Export/Import, contact Simployer to have it enabled
The initial Visma.net integration setup completed, including the general setup guide and approval in the Visma App Store
Admin/Owner access to Simployer One (to run imports)
Employee numbers aligned. The employee number must match between Simployer One and Visma.net for the same person, and be unique within the import scope. If they differ, align them before importing
Complete employee records in Visma.net. Review records before importing so required data is present
Supported position setups. Draft employees and employees with more than one position or an unsupported position type are blocked from import (see Import Results)


What Gets Imported

Employees are matched on their employee number. The import covers personal, employment, and compensation data:

Personal
First and last name, birth date, social security number / identification number, address, work email, work phone
Employment
Employee number, employment start and end date, employment rate, employment type
Compensation
Bank account details, salary information, payout period, effective salary date
Full history is imported, not just the current values. For employment and compensation, the import brings in the complete history held in Visma.net, for example earlier employment records and past salary changes, not only the latest one. Each record is created in Simployer One so the timeline matches Visma.net.
Salary and bank account details are optional. If an employee has no salary or bank details in Visma.net, they are still imported and those fields are simply left empty. An employee is not blocked from import for missing salary or bank data.


Run an Import

Imports are run manually and always start with a preview, so you can review before anything is written. Find it in Simployer One under Settings > Export/Import > Employee import.

1
Open Employee import
Go to Settings > Export/Import > Employee import. Until you select an integration and preview, the tabs show zero and the page prompts you to start.

2
Select the integration
From Select integration, choose the Visma.net account to import from. If you have more than one Visma.net account connected, each appears as its own option (for example, Visma.net - Main account and Visma.net - 2nd account).


3
Click Preview
Simployer One fetches employees from Visma.net and compares them with your existing records. Results are grouped into three tabs: Existing employees, New employees, and Other. Within a tab, the Importable group lists rows that can be imported as-is; click a row to review the full details and the Differences from Visma.net.

4
Choose who to import
Tick the employees you want, or use the header checkbox to select all in view. Start with a small number for your first run.

5
Import
Click Import selected to import the ticked rows, or Import all to import every importable row. Each button shows its count, for example Import selected (4).
6
Review the result
Each row shows its result: Imported, or Failed with a reason (for example, Work email is already used). Fix the cause in Visma.net or Simployer One and re-run the import for any failed rows.





Understanding Import Results

The preview sorts every employee into three tabs so you can see what will happen before you import.

TabWhat it containsWhat happens on import
Existing employeesThe same employee number exists in both systems.The Simployer One record is updated, field by field, with the values from Visma.net.
New employeesIn Visma.net and in the import scope, not yet in Simployer One.A new record is created.
OtherEverything that cannot be matched or created: employees only in Simployer One, records with no employee number in Visma.net, or employees outside the import scope.Not imported. Employees only in Simployer One are left untouched and are never deleted.

Within the Existing and New tabs, rows that can be brought in as-is appear under Importable. After you import, each row shows its result in the status column: Imported, or Failed with a reason (for example, Work email is already used).

Updates are field by field. For a matched employee, only the fields that actually differ are changed in Simployer One. A field that is empty in Visma.net does not overwrite an existing value in Simployer One, so data such as bank account is preserved when it is not present in Visma.net. Salary values update as a set: if one salary field changes, the salary group is written together.
Some employees are handled manually, not through the import. The import does not bring in employees who are a draft in Visma.net, have more than one position, or use a position type that is not supported (only ordinary positions are imported). This reflects what the import currently supports, not a problem with the data in Visma.net. Add or manage these employees manually in Simployer One.
Partial results. An import can partially complete for one employee (for example, the record is created but a later step such as compensation fails). Review the result and re-run the import for that employee after correcting the data.


Key Rules and Limits

Employee number is the key
Matching is by employee number. Two employees with the same number in the same import scope will be matched to the wrong record, so keep numbers unique within the import scope and aligned across both systems.
Import in batches
Start with a small group and review the result before importing more.
One-time setup, not a sync
The import bootstraps Simployer One at setup. Afterward, the ongoing flow runs outbound from Simployer One to Visma.net.
Scheduling is not available. The import must be triggered manually each time. It does not run on a schedule.
Large imports can take a while. The import runs in a single operation, so for a large group the screen may show a timeout or error even though the import actually completed. If that happens, check the result in Simployer One before running the import again.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article