DataLøn · payroll

DataLøn integration: hours in, payroll out

A DataLøn integration means approved hours in your system land in DataLøn, so the payroll run does not start with a spreadsheet. DataLøn (Vismaravnen / Visma) is still one of the most used payroll systems in Danish SMEs. The value is not “having an integration”. The value is a foreman approving hours in the field, and payroll using that number. You send employee id, hours, allowances, mileage, absence, period and approval status. You do not send half-finished notes. CPR is handled by agreement — never in your URLs. Often an employee number is enough in your layer.

Payroll is automation with consequences. A wrong hour is an awkward conversation. Automation is the right door when roster and jobs already live in your own tool.

Godkendte timer
Man
Tir
Ons
Tor
Fre
Lør

37 timer · klar til DataLøn / Zenegy

An approved week in your system — hours, allowances, mileage — ready for DataLøn before the payroll run starts.

What you send in a DataLøn integration

  • Employee id (CPR handled by agreement — never in your URLs)
  • Hours, allowances, mileage, absence
  • Period and approval status

What you do not send

Half-finished notes, overtime arguments and screenshots. The employee should see the basis in your system before it goes to DataLøn.

1

Capture

Hours are typed or pulled from roster/jobs in the field.

2

Approval

Foreman or project lead locks the week. The employee can see the number.

3

Export

The approved basis lands in DataLøn. The payroll run does not start in Excel.

Approval is the product. The file to DataLøn is a consequence.

May we store CPR in our app? Only if you have a purpose, a legal basis and a deletion habit. Often an employee number is enough in your layer.

DataLøn is one integration. Small: DKK 18,000 + DKK 600/month if hours-in is the only flow. Together with e-conomic that is two. See pricing.

Send how a week is approved today — and who corrects it when someone disagrees. That is the brief. The API is the easy part. Quote within 24 hours.

FAQ: DataLøn integration

May we store CPR in our app?

Only if you have a purpose, a legal basis and a deletion habit. Often an employee number is enough in your layer.

What if an hour is not approved?

Then it is not sent. Payroll must not start on a number the employee has not seen.

Can you integrate DataLøn and Zenegy at the same time?

You have one payroll system. Integrate that. Two payroll systems is a switch, not an integration.

What about mileage and allowances?

They need codes DataLøn knows. The mapping is the project — not the HTTP call.