Which data to synchronize between Visma and Humand
There's no need to sync every field in the employee record. In practice, the integration typically covers the fields Humand needs to maintain its organizational structure and employee profiles:
Unique employee identifier (employee ID or national ID, depending on the cross-reference key defined between both systems).
Basic data: full name, email, phone number.
Organizational data: department, team, direct manager, branch or location.
Status: active, on leave, terminated.
Start date and, when applicable, end date.
Two ways to integrate the systems
Visma and Humand don't connect to each other natively: a middleware layer is needed to translate events from one system into the format the other expects. There are two main integration approaches:
Scheduled synchronization (batch)
A process runs on a schedule (e.g., every hour or once a day), compares the current state in Visma against the last known state, calculates what changed, and applies the updates to Humand. It's simpler to implement and works well when near-real-time sync isn't a hard requirement.
Event-driven integration (near real-time)
When Visma exposes webhooks or another change notification mechanism, it's possible to react as soon as the event occurs: the moment a new employee is registered in Visma, Humand is updated within seconds. This approach requires a more robust architecture but delivers a better experience, especially for onboarding flows where timing matters.
Use cases resolved by this integration
Automatic onboarding: when an employee is created in Visma, they appear in Humand with the correct team, manager, and permissions — without HR having to enter them again.
Automatic offboarding: when a departure is recorded in Visma, the Humand account is deactivated automatically, preventing former employees from retaining access.
Role or branch changes: when an employee moves to a new department or location in Visma, the organizational structure in Humand updates automatically.
Manager change: when the reporting line changes in Visma, Humand reflects the new hierarchy without manual intervention.
Common mistakes when integrating Visma with Humand
Using an unstable cross-reference key (e.g., full name) instead of a unique identifier that never changes.
Not accounting for soft-delete departures — employees who become inactive in Visma but aren't formally deleted, leaving them active in Humand.
Not handling API errors gracefully, causing sync processes to fail silently without alerts.
Syncing too many fields initially, increasing complexity without proportional value.
Not defining a reconciliation process to detect and correct drift between both systems.
What you need before starting the project
Technical access (API or export mechanism) to the Visma instance in use.
An admin account in Humand with an enabled API key and appropriate permissions.
A clear definition of the cross-reference key between both systems.
A map of all the events to handle (hire, departure, role change, branch transfer, manager change).
A test environment or staging instance in both Visma and Humand.
At Granweb we build custom integrations between Visma, Humand, and other HR systems — including synchronization logic, error handling, monitoring, and reconciliation processes. Contact us to evaluate your specific setup.
