Danish 5th-week transfer
The Danish 5th-week transfer plugin lets an employee and their employer agree to move untaken statutory vacation into the next holiday year. Under the Danish Holiday Act (ferieloven), up to five days of the fifth holiday week can be transferred, provided the first four weeks have been taken.
Employers are not obliged to offer the transfer, so the plugin is never added by default. Add it to the time-off policy of the employees you offer it to.
When to use
Use this plugin when:
- The policy runs Danish vacation, with days expiring on 31 December
- You let employees transfer the days of the fifth week they could not take
Parameters
| Parameter | Description | Default |
|---|---|---|
| Maximum days | Most days that can be agreed per deadline, across all of the employee’s statements | 5 |
| Days that must be used | Days of the expiring vacation the employee must have taken by 31 December for the transfer to happen | 20 |
| Offered from | First month whose statement offers the transfer. Statements ending from this month up to 31 December offer it | October |
| Entered on behalf by | Roles that may enter the days when submitting the statement on the employee’s behalf, for example HR. Leave it empty so only the employee enters them | Empty |
| Transfer | Who decides the transfer: Agreed on the statement (the employee agrees on their statement) or Automatic (the employer transfers for everyone on the policy) | Agreed on the statement |
How it works
The employee agrees on their statement
When a statement whose period ends in the window is open, the statement sheet shows a Transfer vacation to the next holiday year card. It shows how many days are projected to expire on 31 December, after planned time off. The employee enters how many of them to transfer, at most the plugin’s maximum and never more than are projected to be left. The final approval of the statement is the employer’s agreement, and the approver sees the agreed days on the statement.
- Topping up: a later statement in the window can add days, up to the maximum in total.
- Reopening: reopening an approved statement withdraws the days it agreed. The statement keeps the days that were asked for, so the next submit offers the same number again, and resubmitting agrees them again.
- Submit on behalf: the transfer is the employee’s own agreement. When someone submits the statement on the employee’s behalf, they can enter the days only if they hold one of the roles in Entered on behalf by. Anyone else sees the transfer on the statement without being able to change it.
The days stay usable until 31 December
Agreeing moves nothing yet. The employee can still take the agreed days, and taking them never lowers the agreement, because a vacation can still be cancelled at the last minute. When a time-off request uses days from the agreement, the request and its approval show a note saying how many will still be transferred.
1 January
On 1 January mTime settles the days that expired on 31 December:
- The smaller of the agreed days and the days left moves to a new pot that expires on 31 December of the next year.
- The rest expires as before.
- Nothing moves unless the employee has taken the required days of the expiring vacation (the plugin’s Days that must be used, 20 by default).
The employee’s balance and forecast show the move as a transfer out and a transfer in, so their balance doesn’t change.
December’s statement, approved in January
A monthly December statement is submitted and approved after 31 December, so after the days have been settled. Its approval still concerns December’s days, and it is the employee’s last chance to agree the transfer. The statement is offered the transfer as if it were still December, sized from what was left on 31 December. When it is approved, the agreed days come back out of the expired days and move to next year’s pot.
Automatic transfer
Some employers transfer the fifth week for everyone instead of agreeing it employee by employee. Set Transfer to Automatic and every employee on the policy is treated as if they had agreed the maximum:
- On 1 January the smaller of Maximum days and the days left moves to next year, under the same condition (the required days taken). Nothing is agreed or entered on the statements.
- The employee’s statements in the window show how many days will move automatically and the condition, with nothing to fill in. The approver sees the same on the statement.
- A time-off request that uses those days, and its approval, show how many will still be transferred.
- The employee’s forecast shows the planned transfer.
The policy in force on 31 December decides: switching a policy to automatic, or back, applies to the next deadline.
Days counted
The days in scope are all days that expire on 31 December, including days transferred from the year before. The maximum applies to that whole pool, so transferred days can’t pile up year after year: next year, at most five days can be transferred again.
Example
Your employee has 25 days expiring on 31 December 2026 and has taken 20. Their October statement agrees 2 days, and their November statement tops the agreement up to 5. In December they take one more day.
On 1 January 2027, 4 days are left. All 4 move to a pot that expires on 31 December 2027, and nothing expires.