How Dopusto calculates leave

What Dopusto is — and what it is not

Dopusto is a leave-policy and calculation tool. We give you a sensible starting point based on Slovenian law (ZDR-1), then let you configure the details to match your company's collective agreements, individual employment contracts, and HR decisions. We are not legal counsel and we don't issue authoritative interpretations of the law. Final responsibility for every entitlement figure, every approval and every compliance obligation remains with the employer (admin).

Where the numbers come from

When an employee sees their annual leave entitlement, that number is the sum of several layers computed in this order:

1. Statutory minimum — ZDR-1 Art. 159 guarantees at least 4 weeks (20 days for a 5-day work week). Configured in Leave policy → Annual leave entitlement → Base days.
2. Statutory add-ons — age bands (under 18, 55+), disability, single parent, children under the cut-off age, all per ZDR-1 factor days.
3. First-year proration — 1/12 per month worked when the employee was hired partway through the year.
4. Collective-agreement bonus (KP bonus) — a flat number of extra days granted by your sector or company collective agreement. Tenant-wide default in policy settings, overridable per employee.
5. Seniority bonus — optional extra days per completed year of service, with an optional cap.
6. Per-employee override — when a specific employee's contract differs (union member, key hire, special arrangement), you can layer an override on top of the tenant defaults.

Custom leave types

Next to the statutory ZDR-1 types (annual leave, sickness, maternity, paternity, parental, study, wedding, bereavement, moving, unpaid), you can add your own tenant-scoped types from Leave policy → Manage leave types. A volunteer day, company anniversary day, long-service sabbatical — whatever your contract promises, you model it here and the request flow, balance ledger, approval workflow, calendar, reports and PDF/CSV/XLSX exports all respect it end to end.

End-to-end flow

1. Policy — tenant-wide defaults in /app/settings/leaves.
2. Custom types — optional additions in /app/settings/leave-types.
3. Employee setup — DOB, hire date, dependants (children with birthdates), disability/single-parent flags, and any policy override.
4. Entitlement computed — shown in the employee's profile breakdown and in their personal dashboard.
5. Request → approval — employee requests a leave; operator/manager approves; pending and used day counters update live.
6. Allocation notice (ZDR-1 Art. 161) — issue a legal written notice by 31 March each year, individually or in bulk (ZIP/mail).
7. Carryover (ZDR-1 Art. 162) — rolls unused annual leave into the new year, capped and subject to the 30 June deadline.
8. Reports & exports — admin can export everything to CSV/XLSX/PDF for payroll handoff.

Responsibility rests with the admin

The defaults we ship are convenient starting points, not legal advice. If your collective agreement, a new law, or an individual contract grants rights beyond the ZDR-1 baseline, it is the employer's responsibility to configure those values in Dopusto and to verify every entitlement before using it as a decision. If you're unsure, consult your legal or HR advisor. Dopusto records every change in the audit trail so you always have a defensible history of your decisions.