In the HR department of a mid-sized service provider with 80 employees, inquiries pile up in January: Who has how many vacation days? An employee working a four-day week discovers she has less vacation than her full-time colleague – despite the same contract. A team lead approves a vacation request based on an incorrect leave balance. And HR spends three hours correcting calculations that should have been automated.
Exactly this scenario plays out in thousands of companies across the DACH region. The consequences: lost working time on explanations, rising frustration on both sides, and in the worst case, labor law disputes.
Where exactly does the problem arise?
The mistake rarely happens due to bad intentions. It happens at the calculation principle level. In many companies, HR manages leave accounts in Excel. Each person gets a row, each year gets a column. Part-time? Rounded down. Model change in July? Retroactively corrected. Residual leave? Carried forward without formula.
This is exactly where the typical errors occur:
Vacation entitlement is calculated based on hours instead of working days.
When the work schedule changes, the annual entitlement is uniformly recalculated instead of being split proportionally by time period.
Fractions are generously rounded up, which under labor law is only permissible in one direction.
Employees do not receive a transparent breakdown of their entitlement.
The result: an average of two to four clarification conversations per part-time employee per year, each requiring 30 to 90 minutes of HR time.
The 5 escalation moments throughout the year
In practice, conflicts don't arise randomly but at recurring process points. When you know where they are, you can proactively address them.
1. Contract start or onboarding
The work schedule is only documented in hours, not in working days. This causes the vacation entitlement to be entered incorrectly.
2. Change of work schedule
Reduction or increase of weekly working days during the year is recalculated in a lump sum, instead of being split proportionally by time period.
3. Year-end and residual leave carryover
Incorrect account balances are carried over into the new year. The error multiplies.
4. Payroll processing
Vacation entitlement in days gets mixed up with vacation pay in hours. Employees question their payslip.
5. Capacity planning in projects
Leave is treated as an HR topic. Project managers don't see utilization and absence in one system.
Those who have these five points under control significantly reduce inquiries, legal risks, and operational friction.
What happens when errors go unnoticed?
If vacation entitlement for part-time employees is systematically calculated too low, this violates the anti-discrimination provision for part-time employees (Section 4 TzBfG). Retroactive claims for multiple years are possible, including loss of trust and increased turnover.
The basic principle: Count days, not hours
The statutory vacation entitlement under Section 3 BUrlG is based exclusively on the number of working days per week. Not on hours worked. Not on the employment level. Only on the days.
Specifically, this means: A part-time employee who works five days per week but only six hours each day has the same vacation entitlement as a full-time employee working eight hours. Both get the same number of vacation days.
What does the law say?
The Federal Vacation Act (BUrlG) does not distinguish between full-time and part-time. It only recognizes employees and working days. Section 3(1) BUrlG sets the minimum vacation at 24 working days based on a six-day week. For the five-day week that dominates in practice, this results in a minimum vacation of 20 working days.
Minimum vacation by weekly schedule at a glance
Where do problems arise in everyday implementation?
The principle sounds simple. In practice, conflicts arise at three points: when the work schedule changes during the year, with irregular weekly schedules, and when vacation entitlement in days is confused with vacation pay in hours.
What happens when errors occur?
Those who systematically miscalculate vacation entitlement risk retroactive claims that can be asserted for up to three years. In addition, there is the risk of an audit finding during a tax office review, which can result in follow-up payments.
Vacation entitlement with a 4-day week: How to calculate correctly
The four-day week is gaining importance in German companies, especially in IT services, agencies, and consulting. The calculation is simpler than many think, as long as the right principle is applied.
Example: A company contractually grants 28 vacation days based on a five-day week. An employee switches to four working days per week.
28 ÷ 5 × 4 = 22.4 vacation days
What applies to fractions?
According to Section 5(2) BUrlG, fractions of at least half a day are rounded up to a full vacation day. 22.4 days are therefore rounded up to 23 days. Rounding down to the disadvantage of the employee is not permitted.
Three practical examples
Example 1: IT service provider, part-time 5 days, 30 hrs/week
Employee works Monday to Friday, six hours each. Contractual vacation entitlement: 28 days. Result: 28 days. Unchanged, because the number of working days remains the same.
Example 2: Agency, four-day week, 32 hrs/week
Employee works four days, eight hours each. Contractual vacation entitlement: 30 days at full-time. Result: 30 ÷ 5 × 4 = 24 days.
Example 3: Consulting firm, three-day week, 24 hrs/week
Employee works Mondays, Tuesdays, and Thursdays. Contractual vacation entitlement: 25 days at full-time. Result: 25 ÷ 5 × 3 = 15 days.
How many hours does a vacation day count for part-time employees?
This is the most common misconception that regularly leads to disputes. Vacation entitlement is calculated in days. Vacation pay – meaning the compensation during vacation – is based on the hours that would have been worked. These are two separate logics.
Separating entitlement and pay cleanly
An employee with a four-hour position working five days per week has the same vacation entitlement in days as a full-time employee. When they take a vacation day, four hours are paid. For a full-time employee, it's eight hours. The entitlement is the same; the pay differs.
The Federal Labor Court (BAG) has confirmed this principle multiple times: Vacation entitlement is based on the number of working days; compensation is based on the specific working hours missed.
For HR administration, this means: You manage leave accounts in days. Payroll calculates in hours. Both logics need a clean connection, but they must never be mixed.
How to stabilize your vacation logic immediately
Before you think about software, you should define the foundation cleanly. These four measures create immediate clarity:
1. Explicitly define work schedules
Document not only weekly hours but the specific working days per week.
2. Establish a binding rounding rule
Fractions of 0.5 and above are rounded up. No individual exceptions.
3. Document schedule change logic in writing
Schedule changes are calculated proportionally by time period. Each period separately.
4. Create transparency
Every part-time employee receives a transparent breakdown:
Period A + Period B = Total entitlement.
This foundation already significantly prevents the most common escalations.
Implementation in everyday business: Three scenarios, one pattern
Scenario 1: IT service provider, multiple part-time models
Problem: 60 employees, 18 of them part-time, various weekly models. HR processes every vacation request manually, inquiries via email, leave accounts in Excel. Results: errors in the calculation, no auditability, frustration among part-time staff.
Manual: Each part-time employee receives an individual calculation. When a model changes, HR must retroactively correct. In 2023, this led to six incorrect vacation balances, which were only discovered during the annual review.
With an integrated solution: Work schedules are set up once in the system. Vacation entitlement is automatically calculated based on the agreed working days. Changes take effect immediately. The balance is always up to date.
Result: Estimated time savings of 40 hours per year. No errors in the base calculation. Clear communication foundation.
Scenario 2: Manufacturing company, permanent four-day week
Problem: 120 employees, one business unit structurally works four days. Minimum vacation is incorrectly transferred annually because the HR system assumes a five-day baseline.
Manual: Excel corrections per quarter. Errors at year-end because residual leave is carried over based on incorrect balances. In an audit scenario, every single balance would need to be recalculated.
With an integrated solution: The system knows the weekly model. The statutory minimum vacation for a four-day week of 16 days is automatically set as the baseline. Deviations upward can be mapped without issues.
Result: Legally compliant standard calculation, no manual corrections, clear audit trail.
Scenario 3: Agency, switch from full-time to part-time during the year
Problem: An employee switches from five to three working days on July 1st. Contractual total entitlement: 28 days. How many days is she entitled to for the entire year?
Calculation:
January to June (6 months, 5 days/week): 28 ÷ 12 × 6 = 14 days
July to December (6 months, 3 days/week): 28 ÷ 5 × 3 ÷ 12 × 6 = 8.4 → rounded up to 9 days
Total entitlement: 23 days
Manual: HR calculates this individually based on estimates. In three out of five cases, the annual entitlement is recalculated as a lump sum, leading to underpayments.
With an integrated solution: Period logic maps both time periods separately. The system sums automatically. Residual leave is correctly carried over to the following year.
Step-by-step to legally compliant leave management
Step 1: Document all work schedules. Not just the hours, but explicitly the weekdays.
Step 2: Link vacation entitlements to models, not to individuals. This way, changes automatically flow through correctly.
Step 3: Give employees access to their own account balances. Self-service demonstrably reduces inquiries by up to 60 percent.
Step 4: Define year-end and model changes as separate triggers. Set up system-side validation routines.
Step 5: Keep reports exportable. Every audit or internal review needs traceable histories.
Defining roles and logic clearly
Clean leave logic only works when responsibilities are clearly defined:
HR: Maintain work schedules and calculation logic
Team lead: Approve absences considering project capacity
Payroll: Calculate vacation pay on an hourly basis
Employees: Self-service access and independent verification
Without clear roles, the typical ping-pong between HR, managers, and payroll ensues.
Ready for compliant time tracking?
Get started today — free for 14 days, no credit card required.
Checklist: Is your leave management future-proof?
Basic requirements (Must have):
Vacation entitlement is tracked in working days, not in hours.
Work schedules are documented with weekdays.
Fractional day rounding follows the statutory regulation.
Extended requirements (Should have):
Work schedule changes are calculated proportionally by time period.
Employees have real-time access to their leave account.
Residual leave is carried over in compliance with regulations.
Optimal requirements (Nice to have):
Vacation entitlement and vacation pay are shown separately but linked in the system.
Exportable reports for payroll and audit are available at the push of a button.
Absence history is archived in an audit-proof manner.
What happens when vacation entitlement is not properly documented?
A leave account is not an internal document that can be discreetly corrected in case of error. If a labor law dispute arises, the employer bears the burden of proof that vacation was granted correctly and documented in full.
The Federal Labor Court has consistently assigned this burden of proof to the employer in its settled case law. If reliable records are missing, the employee's version is presumed correct in case of doubt.
In addition, there is a three-year statute of limitations: Employees can claim their vacation entitlement or compensation for untaken vacation days upon termination retroactively for up to three years.
How ZEP maps part-time vacation entitlements in a legally compliant way
ZEP allows work schedules including weekly working days to be centrally stored. Whether it's a four-day week, three-day part-time, or a mid-year schedule change – the system calculates vacation entitlement based on working days, not hours.
Vacation, sick leave, and other absences are managed in one system. Employees see their current leave balance in the self-service area without having to route every inquiry through HR. Standardized exports are available for payroll, directly supporting the DATEV process.
This eliminates the most common error sources: manual conversion, individual Excel spreadsheets, and lack of transparency during schedule changes.
Those who combine leave management in ZEP with project time tracking additionally gain visibility into how absences affect project capacity. This is especially relevant for IT service providers and consulting firms that need to manage project utilization and availability in parallel.
Practical example: Implementation in everyday work
An employee switches from five to three working days in July.
In the system, two periods are automatically tracked separately. The annual entitlement is calculated precisely by period and displayed transparently in self-service:
Period 1: 14 days
Period 2: 9 days
Total entitlement: 23 days
No Excel corrections. No email inquiries. No manual rounding.
Work schedules are set up once. Changes take effect automatically. HR doesn't need to recalculate. Project managers simultaneously see how absences affect capacity.
For payroll, structured exports are available that cleanly separate vacation entitlement in days and vacation pay in hours.
Part-time vacation entitlement: Act before the error escalates
Companies that manually manage part-time vacation entitlements invest time in tasks that a system handles in seconds. The error risk is not theoretical – it is systemic and cumulative. Every year that incorrect balances are carried forward, the correction effort grows, as does the legal risk.
The cleanest solution is not a better Excel template, but a system that knows work schedules, automatically calculates entitlements, and gives employees transparent access to their leave balance.
Frequently Asked Questions
Do I have to take vacation on days when I wouldn't be working anyway?
No. Vacation days can only be used for days on which there is an actual work obligation. Someone who works three days per week and requests vacation from Monday to Friday uses three vacation days, not five. If a public holiday falls on a regular working day, that day is also not counted as a vacation day.
How many vacation days am I entitled to with a 4-day week if my contract provides for 30 days?
30 days at full-time means 30 days based on five working days per week. If you switch to four days, the calculation is: 30 ÷ 5 × 4 = 24 days. If you are already permanently on a four-day week and the contract explicitly states 30 days for this model, that value applies directly without conversion.
Minimum vacation with a 5-day week: Is it 20 days or more?
The statutory minimum vacation under Section 3 BUrlG is 20 working days based on a five-day week. This value is the absolute minimum. Employment contracts, collective agreements, or works agreements can set a higher entitlement, never a lower one. The industry average in Germany is between 27 and 30 days according to Destatis.
How does the vacation calculator work for part-time, and where are its limitations?
A vacation calculator delivers correct results as long as you make the right inputs: full-time vacation entitlement, full-time working days, and actual part-time working days. Limitations arise with mid-year model changes, irregular weekly schedules, and linking to vacation pay. For these special cases, you need a solution that connects period logic and work schedule models.
What happens to vacation entitlement when working days vary within the week?
With fluctuating weekly work structures, for example three days in week A, four days in week B, the annual entitlement is calculated based on the average working days per week. For this, you count the actual annual working days and apply the formula: Full-time vacation entitlement ÷ Full-time annual working days × Actual part-time annual working days. This average value must be documented and traceable.
Can an employer retroactively reduce part-time vacation entitlement if it was incorrectly calculated?
A retroactive reduction to the disadvantage of the employee is generally not permissible once the entitlement has accrued. This applies especially when the incorrect calculation was on the employer's side. Retroactive corrections that put the employee at a disadvantage violate the anti-discrimination provision under Section 4 TzBfG. Corrections in favor of the employee are possible at any time.