Before handling the first leave request, model your absence types: paid, RTT, unpaid, sick, training. Each has its own accrual, supporting documents and payroll impact.
Step-by-step #
-
List your types #
In Settings → Absences → Types, create each type: name, code, colour, unit (day, half-day, hour).
-
Set accrual rules #
For paid leave: 2.5 days/month (FR) or contract pro-rata (CH). For RTT: per agreement. Accrual can be automatic or manual.
-
Seed initial balances #
Bulk-import balances via CSV when migrating from another tool. The balance then shows on the employee profile.
-
Define supporting documents #
Sickness > 3 days = certificate required. Unpaid > 5 days = HR letter. The system enforces upload before approval.
-
Configure payroll impact #
Each type is mapped to a payroll code (PL, SICK, RTT, TRA). Export uses that code.
Common types and rules #
| Type | Accrual | Document |
|---|---|---|
| Paid leave | 2.5 d/m (FR), pro-rata (CH) | None |
| RTT | Per agreement | None |
| Sickness | Outside balance, unlimited | Medical cert > 3 days |
| Unpaid | Outside balance | Written request |
| Training | Per CPF / funds | Convocation |
FAQ #
What happens at year-end?
Unused balance can be carried forward, paid out or lost depending on type. The rule is configurable.
Are 13th month and bonuses impacted?
Salary maintenance depends on type. Sick = 80% by default, leave = 100%, unpaid = 0%.
How to handle special leaves (wedding, bereavement)?
Create a dedicated type with automatic deduction by event.
Switzerland vs France differences?
Illizeo ships two presets (CH/FR) to start quickly. Statutory thresholds and accrual units differ.
