Skip to content
Hypamoon

For teams that run on Visma Severa

Visma Severa payroll export of hours and absences

Payroll needs the approved hours, overtime, absences and travel expenses per employee. Severa has a payroll file for a few packages and countries; for the rest someone runs a report and reshapes or retypes it every pay period.

How it goes today

  1. Wait until the hours and absences for the month are approved.
  2. Run a report per employee in Severa and download it.
  3. Reshape it into the codes and columns the payroll package expects.
  4. Type the travel expenses into payroll separately.

How it can go

Approved hours, absences and travel reach payroll per employee, in its own format.

For each pay period, the approved work hours, overtime, absences and travel expenses per employee come together in the file or format your payroll package reads, keyed on the employee number. You check an overview first. Calculating pay and applying collective agreements stay in payroll.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your Visma Severa key in the portal, never in the chat.

Your request

With Hypamoon, at the end of each month, collect the approved hours, overtime, absences and travel expenses per employee from Severa and prepare them in the format our payroll package reads, keyed on employee number. Show me the overview to check before it goes to payroll.

An administrator switches on the REST API in Severa under Subscription, Integrations, accepts its terms once, and creates a client ID and secret under Settings, Integrations, REST API with the scopes this tool needs. The REST API comes with the Business plan and higher. It stays yours.