In October, many companies start looking for unused leave. HR pulls a list, team leads ask around, and in December people negotiate who will still take their days, who pushes them into the new year and what happens to the rest. What is easily overlooked is that leave does not simply lapse at year end on its own. Under the case law of the German Federal Labour Court, statutory leave generally only expires if the employer has first asked the person concerned to take it and has told them clearly and in good time that it will otherwise lapse. The burden of proof for this lies with the employer. A legal question therefore becomes a data question: who received which notice, when, with which balance - and can that still be shown several years from now? This article describes which fields such a notice needs, where they come from, what a notice cycle across the year looks like, how delivery and acknowledgement are recorded and which special cases belong in separate groups. How we map such a workflow inside a company is described under process analysis.
Key takeaways
- Statutory leave generally only lapses at year end if the employer has first asked the person to take it and has clearly pointed out that it will expire. The burden of proof lies with the employer (Federal Labour Court).
- Without a notice, the three-year limitation period does not start either (Federal Labour Court, 9 AZR 266/20). Open balances accumulate and fall due as a payment in lieu at the latest when someone leaves.
- The notice is a record with eight fields: name, entitlement, taken, planned, remaining, cut-off date, delivery channel and timestamp. Once they are defined, it can be generated from time recording and master data.
- A notice at the start of the year and an autumn notice with the current balance achieve more than a group email in December. Carried-over leave needs its own notice before 31 March (Section 7 (3) BUrlG).
- Long-term illness, parental leave, maternity protection, departures and older balances from previous years follow their own rules. They belong in separate case groups with their own cut-off date.
Why unused leave does not lapse without a notice
The German Federal Leave Act (BUrlG) is short and, at first glance, unambiguous. Every employee is entitled to at least 24 working days of leave per year (Section 3 (1) BUrlG), with all calendar days counting as working days that are not Sundays or public holidays. Leave must be granted and taken in the current calendar year. It may only be carried over into the next year if urgent operational reasons or reasons relating to the employee justify this, and in that case it must be taken within the first three months of the following year (Section 7 (3) BUrlG). Anyone reading only the statute would conclude that leave not taken simply disappears on 31 December or, at the latest, on 31 March.
Since 2019 it has not been that simple. Following the case law of the European Court of Justice, the Federal Labour Court ruled that the time limit on leave is tied to the employer's cooperation. The employer must enable the person to actually take their leave: ask them to take it and tell them clearly and in good time that it will otherwise lapse at the end of the calendar year or the carry-over period. Only if the person still chooses not to take the leave despite this notice does the entitlement expire. Without the notice, the open balance remains and is added to the entitlement that arises on 1 January of the following year.
Nor does the limitation period help without a notice. The standard limitation period is three years (Section 195 of the German Civil Code, BGB). According to a Federal Labour Court judgment of 20 December 2022, however, for leave it only starts at the end of the year in which the employer fulfilled its duty to cooperate, that is, asked the employee to take the leave and pointed out that it would lapse (9 AZR 266/20). A company that has not given personal notices for years may therefore carry leave entitlements from many years without them showing up in any staff overview. They typically only become visible when someone leaves and leave not taken has to be paid out.
The burden of proof lies with the employer
Which fields a notice needs
A circular will generally not suffice as a notice. The Federal Labour Court requires specific and transparent information to the individual person; according to its case law, abstract statements for example in the employment contract, in a leaflet or in a collective agreement will generally not satisfy this requirement. For implementation this leads to a simple rule: the notice is generated per person, and it contains their figures, not those of a template example.
What belongs in it comes down to eight fields. Name and staff number assign the notice to a person. The entitlement for the year states the days due, split into statutory minimum leave and contractual extra leave. Taken and planned show the current position, and the remaining balance follows from them. The cut-off date states when the balance lapses if it is not taken. Finally, delivery channel and timestamp record how and when the notice reached the person. Together the eight fields form a record that can be checked later without anyone having to remember anything.
Field Content Source Example
-----------------------------------------------------------------------------------------------
Name name and staff number personnel master data Person A, 1042
Entitlement days per year, statutory and contractual master data, contract 28 (8 contractual)
Taken leave days actually taken time recording 17
Planned approved, not yet taken leave planner 5
Remaining entitlement minus taken minus planned calculated 6
Cut-off date date on which the balance lapses rule set 31 Dec 2026
Channel portal, personal mailbox, paper delivery log portal
Timestamp sent and acknowledged delivery log 6 Oct / 7 Oct 2026Two points deserve particular attention. The first is the unit. The statute counts in working days of a six-day week, most companies count in actual working days, and with part-time staff on changing days the conversion quickly becomes confusing. It belongs in the personnel master data once and properly, not in every individual list. The second point is the separation of statutory and contractual leave. For extra leave above the statutory minimum, employment or collective agreements may set different rules. Anyone who keeps both parts in a single figure can no longer say later which part is supposed to have lapsed on which date.
Where the data for the notice comes from
In most companies the information already exists, just in different places. The entitlement is in the employment contract and, ideally, in the payroll master data. Days taken are in time recording or a leave module, planned days in a leave planner, a team calendar or on a wall chart. Joining and leaving dates, parental leave and changes in working hours are in the personnel file. Unused leave is therefore not a figure you look up but one you assemble from three or four sources - and it looks different on every day of the year.
How working time recording itself is set up is described in digital time tracking 2026: implementing the mandate. For the notice, a small extract is enough: the absence type leave with date and status. What matters is that requested, approved and taken leave are kept apart. A request still waiting for approval is not planned leave, and an approved day on which the person was ill is not leave taken. Under Section 9 BUrlG, days of incapacity for work during leave that are evidenced by a medical certificate are not counted against annual leave. This correction has to change the balance before a notice states it.
The real work lies in bringing the data together. We connect the existing systems rather than introducing another one, as described under data integration. The result is a view per person and year that is recalculated every night and knows its origin: which value comes from which system, as of when? If the balance in a notice is questioned later, that origin is the answer. The same leave data helps elsewhere too, for example in shift rosters that check rest periods upfront.
Entitlement from master data
Annual entitlement, statutory and contractual share, working days per week and changes during the year. Kept properly once, every later step calculates from the same basis.
Taken from time recording
Leave days actually taken, with date and status. Illness during leave is corrected with evidence before the balance is used in a notice.
Planned from the leave planner
Approved days not yet taken are counted separately. Open requests stay out until approved - otherwise the notice states a position that does not yet apply.
Cut-off date from the rule set
Year end for current leave, end of March for carried-over leave, separate dates for special cases. The rule set lives in one place, not in every template.
Delivery with a log
Delivery channel, time sent and acknowledgement are recorded automatically when the notice goes out. Nobody has to piece the evidence together later from mailboxes and memory.
Filed per person and year
Notice and log go into the personnel file. A glance shows for which person and which year a notice is missing.
The notice cycle across the year
The data becomes a workflow once it is settled when a notice is produced. The statute does not name a fixed date. The information has to arrive in good time, meaning early enough for the leave still to be taken in the current year. According to the case law of the Federal Labour Court, the employer can regularly fulfil its duty to cooperate, for example, by informing each person in text form at the start of the calendar year how many working days of leave they are entitled to in that year, asking them to apply for their annual leave in good time, and explaining the consequences if they do not.
A practical option is a cycle with three points in time. The first notice goes to everyone at the start of the year, with entitlement, cut-off date and request. The second goes to everyone with a remaining balance in the autumn, with the then current figures - at the beginning of October there are still enough weeks left before year end to plan leave without everyone being absent at the same time in December. The third only concerns carried-over leave and goes out in January to everyone whose balance moved into the new year for a documented reason, with the cut-off date of 31 March. How such deadlines are calculated per person and linked to an invitation and evidence is also shown in safety briefings scheduled and evidenced; the pattern is the same.
Step 1: Calculate the position per person
Every night, entitlement, days taken and days planned are read per person from the leading systems and turned into a remaining balance. If the sources disagree, a clarification case is raised rather than a silent average.
Step 2: Generate a notice with a cut-off date
At the agreed points in time, a notice is produced per person from an agreed template, filled with their figures and the appropriate cut-off date. The template is agreed once and not reworded every year.
Step 3: Deliver and log
The notice goes out via the agreed channel: personal mailbox, employee portal or paper against signature. Time sent, recipient and content are recorded in a form that cannot be altered.
Step 4: Follow up on acknowledgement
Anyone who has not acknowledged the notice after a set period appears on a list for the line manager or HR. Follow-up happens in person, and that is recorded too.
Step 5: Propose carry-over and lapse
At the cut-off date, the cycle proposes how to treat each balance: lapse if a notice is evidenced, carry-over with a new cut-off date if a reason is documented, otherwise continuation as an older entitlement.
Every night, entitlement, days taken and days planned are read per person from the leading systems and turned into a remaining balance. If the sources disagree, a clarification case is raised rather than a silent average.
At the agreed points in time, a notice is produced per person from an agreed template, filled with their figures and the appropriate cut-off date. The template is agreed once and not reworded every year.
The notice goes out via the agreed channel: personal mailbox, employee portal or paper against signature. Time sent, recipient and content are recorded in a form that cannot be altered.
Anyone who has not acknowledged the notice after a set period appears on a list for the line manager or HR. Follow-up happens in person, and that is recorded too.
At the cut-off date, the cycle proposes how to treat each balance: lapse if a notice is evidenced, carry-over with a new cut-off date if a reason is documented, otherwise continuation as an older entitlement.
The last step is the most delicate because it turns a legal consequence into a booking. A system should not decide on its own here but make a proposal that a named person approves. How such approvals are mapped with deputies and a log is described in digitising approval workflows. We usually build the cycle itself as an automation on top of the existing systems, as described under process automation.
Proving delivery and acknowledgement
A notice whose receipt cannot be shown is of little help in a dispute. The question is therefore not only what the notice says but how it reaches the person and what remains of it afterwards. An email to a large distribution list, a notice on the staff board or a sentence on the intranet are quickly done but cannot be tied to a single person or a specific balance. A personal notice with a log takes more effort to set up once and is routine afterwards.
| Aspect | Personal notice with log | Circular or notice board |
|---|---|---|
| Link to the person | Name, staff number and own balance in the notice | General statement for all employees |
| Content | Entitlement, taken, planned, remaining and cut-off date | Reference to the rule without individual figures |
| Proof of delivery | Time sent, recipient and content in the log | At best a photo of the notice or a distribution list |
| Acknowledgement | Confirmation in the portal or signature, open cases on a list | Generally cannot be established |
| Repetition | Automatic with the current balance at fixed points in time | Another group email, often only in December |
| Retrievability after years | Per person and year in the file | Search through mailboxes and network drives |
There are several workable ways to record acknowledgement. In companies with an employee portal, a confirmation by click that is stored with timestamp and person is the obvious choice. Where many employees have no computer access of their own, for example on building sites or in assembly, paper against signature is often the more pragmatic route; the signed sheet is scanned and assigned to the record. Both routes can be combined as long as there is evidence for each person in the end. Where the evidence is kept and who may access it is described in digital personnel files: access and retention.
That leaves the question of how long such evidence must be kept. The Federal Leave Act does not set a period for this. The limitation rule does, however, give a sensible lower bound: the notice for a year is needed for as long as claims from that year can still be asserted. Anyone who already manages retention by deadline adds the notice as a document type with its own period; how that works is described in meeting retention periods digitally.
Keeping special cases separate
Not every balance arises because someone did not apply for leave. A person who is ill for a long time simply cannot take it. A separate time limit applies here: the leave then generally only expires after a carry-over period of 15 months from the end of the leave year. On 20 December 2022 the Federal Labour Court clarified that, for a year in which the person still worked before falling ill, this in principle only applies if the employer fulfilled its duty to cooperate in good time (9 AZR 245/19). For the data this means: long-term illness does not simply suspend the cut-off date but moves it, and the notice at the start of the year helps decide whether the longer period runs at all.
Parental leave and maternity protection follow their own statutes. Under Section 17 of the Federal Parental Allowance and Parental Leave Act (BEEG), the employer may reduce leave by one twelfth for each full calendar month of parental leave; leave not taken before parental leave must be granted after it ends, in the current or the following leave year. Under maternity protection, periods of absence due to an employment prohibition count as periods of employment, and leave not taken can be claimed after the prohibition ends in the current or the following leave year (Section 24 of the Maternity Protection Act, MuSchG). In both cases, therefore, the cut-off date is not 31 December but a date derived from the end of the absence. The reduction under Section 17 is also a declaration by the employer that should be documented as well.
Leaving the company: payment in lieu instead of lapse
Another special case is the legacy from the past. If a company gave no personal notices in earlier years, the balances from that time have generally not lapsed. The Federal Labour Court has pointed out that the employer can make up for its cooperation regarding leave from previous years in the current leave year. Technically this means: older entitlements get their own line in the record for each year of origin, and the next notice states them explicitly. Anyone who quietly adds them to the current balance can no longer show later what the notice referred to.
One point belongs on the agenda early: setting general leave principles and the leave schedule is subject to co-determination by the works council (Section 87 (1) no. 5 of the Works Constitution Act, BetrVG), and a system that evaluates acknowledgements per person also touches co-determination on technical systems capable of monitoring conduct or performance (Section 87 (1) no. 6 BetrVG). Inviting the works council only at acceptance costs weeks. How such involvement works in practice is described in involving the works council in IT projects.
What a company can prepare itself
Getting started does not require a new system. It requires an inventory that can be compiled in a few days, and answers to four questions: where is the entitlement per person recorded, where are days taken and planned, which rules apply to carry-over and extra leave, and how were notices given in past years? The last question is the most uncomfortable because the honest answer is often: not at all, or only in general terms. Yet it is precisely this answer that determines how large the legacy is that has to be dealt with in the first run.
- Check entitlement per person: annual leave, statutory and contractual share, working days per week, changes during the year. Where master data and employment contract differ, that is already a finding that must be resolved before the first notice.
- Reconcile absences: collect days taken and planned for the current year from time recording, leave planners and team calendars. Duplicate or contradictory entries show which source should lead in future.
- Put the rule set in writing: cut-off dates, reasons for carry-over, treatment of extra leave and responsibility for approvals. Whatever is not in writing is interpreted differently in every department.
- Assess the legacy: list balances from previous years per person and year of origin and record whether a notice can be evidenced for those years. This list belongs before the first run, not after it.
- Agree template and delivery channel: a text that addresses the person directly, states their figures, asks them to apply for leave and explains the lapse, plus a delivery channel that produces evidence per person.
The starting point differs clearly by sector. In the trades, leave is often on the wall chart in the workshop, and many employees spend the day on building sites without their own access to a portal. There, a paper notice handed over with the weekly report and returned signed achieves more than an email; more on those workflows under processes in the trades. For service providers working at customer sites, leave is closely tied to scheduling, and moving leave means moving appointments. We describe the connection points under processes for service providers.
The first run reveals the legacy
The next steps before year end
Starting in October still leaves time for a clean autumn notice before year end - provided the figures are right. That is why the process starts with the calculation, not with sending anything. The route can be taken in stages, and the first stage does not change anything in day-to-day operations yet.
- Stage 1 - calculate the position without sending: combine entitlement, days taken and days planned per person from the existing sources and show the balance per year of origin. The result is a list, not yet a message.
- Stage 2 - autumn notice with a log: generate a personal notice with a cut-off date for everyone with a balance, deliver it and follow up on acknowledgement. Open confirmations go to the responsible line manager.
- Stage 3 - carry-over in January: balances carried over for a reason receive a new notice with the cut-off date of 31 March. Balances without an evidenced notice are continued as older entitlements and named in the next notice.
- Stage 4 - annual cycle in regular operation: notice at the start of the year, reminder in the autumn, carry-over notice in January, special cases with their own cut-off date. The cycle calculates and proposes; HR approves and decides on exceptions.
Leave must be granted and taken in the current calendar year.
To put the effort in context: a process analysis starts at 1,900 EUR net, delivery per automation or interface at 4,900 EUR net, ongoing support at 190 EUR net per month. Prices as of September 2026. The ongoing services can be cancelled monthly; there is no minimum term. The overview is available under pricing, and a first conversation can be arranged via contact. Related reading: verification of payee in supplier payment runs for discrepancies that have to be cleared before an approval, and account access when staff join and leave for handling a departure as an orderly process.
Sources and legal basis
Related Articles
Safety briefings: scheduled and evidenced per person
How triggers from HR and asset data, intervals per legal basis and evidence per person add up to a briefing matrix that reports gaps before anyone is deployed.
Verification of payee in payment runs: handling mismatches
Since October 2025, banks check name and IBAN before every credit transfer. How supplier master data, payment blocks and call-backs handle the bank's responses.
Interim Payments and Variations on Building Sites
How a stage of completion becomes an interim invoice, why a variation is a case with a deadline of its own, and how that produces a final account that can be checked without rework.