Skip to main content
The Danløn integration syncs employees, departments, salary types, and vacation balances into Pike, and sends the pay lines from each closed Pike pay period to Danløn: normal hours for hourly employees, additional hours, overtime with supplements, time off in lieu, and absence. Payroll uses the same approved timesheets you bill from, and nobody types hours into Danløn by hand.

Connect Danløn

  1. Go to Workspace settings → Integrations → Danløn.
  2. Click Add integration.
  3. Sign in to Danløn with a user who has payroll access, and select the company (CVR number) to connect.
Only workspace admins can connect or disconnect Danløn. One Pike workspace connects to one Danløn company.

Import data

On the integration page, click Import data. The stepper runs entities in dependency order, so Pike reads departments before the employees who belong to them, and employees before their balances. It skips entities whose Read toggle is off, names them, and links to sync settings.

What syncs

Employment type and schedule

A Danløn employee on monthly salary becomes a salaried member. An employee on hourly pay becomes an hourly member. Weekly hours from Danløn set capacity per week, spread over Monday to Friday. To give a part-time employee a different schedule, such as four days a week, set the work schedule in Pike. Pike keeps the schedule as long as the weekly total matches Danløn.

Send pay lines

Send pay lines is off by default. When on, closing a pay period in Pike sends each member’s pay lines to the next open payroll in Danløn for their pay frequency. Monthly employees go to the monthly payroll and 14-day employees to the 14-day payroll. Pike fills in Danløn’s standard pay codes for each line when you connect. Change any mapping under Pay codes on the integration page. Days go as the member’s own days, so a part-time employee’s half day reaches Danløn as 0.5 days. If the next Danløn payroll is already approved when the period closes, the lines go to the payroll after it. Danløn confirms receipt, and the Pike pay period shows Sent to Danløn with the payroll date.

Vacation balances

Danløn owns the official vacation and extra holiday balances under the Danish holiday act. After each Danløn pay run, Pike reads both balances and shows them as the member’s balance. Vacation requests made in Pike deduct right away, so members see what they have left before the next pay run. Pike’s own accrual is off for these two types while Danløn is connected. See Time off and vacation. Time off in lieu and flex balances stay in Pike. Danløn receives the hours earned and taken through the pay lines.

Compensation

Sync compensation to cost profiles is off by default. Only admins and finance users can turn it on. When on, monthly salary or hourly rate from Danløn sets the member’s cost profile, with the effective date from Danløn.

Public holidays

Connecting Danløn assigns the Danish holiday calendar to every member who has no calendar yet. Members with a calendar keep it.

Source of truth

Once a record is linked, Danløn owns the linked fields and Pike reads them back. Danløn owns employee fields, salary type, weekly hours, pay frequency, and vacation balances. Pike owns time entries, work schedules, overtime, time off in lieu, flex, and pay lines. Pike-only fields, such as project links, allocations, and cost profiles, are never overwritten.

Schedule

Pike reads employees from Danløn every 24 hours and balances after each Danløn pay run. Pay lines go when a Pike pay period closes. Import data and Refresh always run on demand.

Sync settings

While Danløn is connected, the What syncs with Danløn card sits under the top button row on the integration page. Each entity has a Read toggle (Danløn to Pike) and, where supported, a Send toggle (Pike to Danløn). Toggles save immediately. New connections start with Read on for everything and Send pay lines off.

Synced records

Every synced record shows the Danløn marker, “Last synced ” or “Not synced yet”, and a Refresh action. Refresh shows only while Read is on for that entity.

Sync issues

Records that fail to sync appear in the Sync issues list on the integration page, with the record, the reason, and a Retry action. Common reasons are a member with no Danløn employee number, or a pay line with no pay code. The integration never deletes Pike data on its own. An employee removed in Danløn is marked “Removed in Danløn” in Pike, never deleted.

Disconnect

Disconnecting Danløn stops syncing and keeps all imported data. Vacation balances stay at their last synced value, and Pike’s own accrual takes over from the next month. Pay periods already sent keep their Sent to Danløn status.

Permissions

Synced data respects Pike roles and private projects. Pay lines and balances are visible to admins, HR, and finance users, and to each member for themselves.

Limits

  • Pike does not calculate salary, tax, ATP, pension, or holiday pay (feriepenge and ferietillæg). Danløn does.
  • Only closed pay periods are sent, and only approved time and time off count.
  • Corrections to a period already sent go to the next period as adjustment lines.
  • Contractors are not paid through Danløn. Their hours stay in Pike or go to Deel.