> ## Documentation Index
> Fetch the complete documentation index at: https://usepike.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Danløn

> How to connect Danløn to Pike to sync employees, departments, and vacation balances, and send hours, overtime, and absence from closed pay periods to Danløn payroll.

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

| Danløn | Pike | Direction |
| - | - | - |
| Employees | Members, matched by email | Danløn to Pike |
| Employee number | Payroll ID on the member | Danløn to Pike |
| Departments | Teams | Danløn to Pike |
| Salary type (monthly or hourly) | Employment type (salaried or hourly) | Danløn to Pike |
| Weekly hours | Capacity per week on the contract | Danløn to Pike |
| Pay frequency (monthly or 14-day) | Member's pay period | Danløn to Pike |
| Employment start and end date | Contract dates and member status | Danløn to Pike |
| Vacation and extra holiday balances | Vacation and Extra holidays balances | Danløn to Pike, after each pay run |
| Pay lines from a closed pay period | Pay codes on the next Danløn payroll | Pike to Danløn, when **Send pay lines** is on |

### 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](https://usepike.com/docs/members/working-time.md#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](https://usepike.com/docs/members/payroll.md#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 pay line | Sent to Danløn as |
| - | - |
| Normal hours | Hours, for hourly employees |
| Additional hours | Additional hours (merarbejde) |
| Overtime 1 | Overtime with the first supplement |
| Overtime 2 | Overtime with the second supplement |
| Time off in lieu earned | Time off in lieu earned (afspadsering) |
| Time off in lieu taken | Time off in lieu taken |
| Vacation | Vacation days with pay (feriedage) |
| Extra holidays | Extra holidays (feriefridage) |
| Sick | Sick days |
| Child sick day | Child's sick day |
| Unpaid leave | Unpaid leave |
| Public holiday | Public holiday hours, for hourly employees |
| Balance payout | Payout of balance |

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](https://usepike.com/docs/members/time-off.md#balances-owned-by-a-payroll-system).

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](https://usepike.com/docs/members/cost-profile.md), 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.

| Entity | Read | Send |
| - | - | - |
| Employees | Yes | Not available |
| Vacation balances | Yes | Not available |
| Pay lines | Not available | Yes, off by default |

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 {time}" 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](https://usepike.com/docs/integrations/deel.md).

## Related

* [Danløn integration overview](https://usepike.com/integrations/danlon): What syncs, how agencies use it, and FAQs.
* [Working time and overtime](https://usepike.com/docs/members/working-time.md): Norm hours, part-time additional hours, and overtime.
* [Pay periods and payroll](https://usepike.com/docs/members/payroll.md): Period close and pay lines.
* [Time off and vacation](https://usepike.com/docs/members/time-off.md): Balances, accrual, and the Danish holiday act preset.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.