Illizeo’s Annualised working time module counts each employee’s working time over their reference period: target, worked time, absences, overtime and controls, all the way to the period review and the quantities for payroll. You describe your schemes; Illizeo keeps the counters.
Modulated · Seasonal · Modulated part-time · Days-based · Exceptional hours · Overtime quota · Controls · Simulation · Reviews and closing · Payroll quantities · Monthly records · API and webhooks
With annualised hours, a busy week offsets a quiet one. You still need to know, at any time, where each employee stands against their target, which limits are getting close and what will be left to pay or to recover at period end. Without a tool, this tracking lives in spreadsheets, matched by hand against time entries, absences and payroll.
Time entries, absences, public holidays: every month, someone rebuilds each employee’s counter in a spreadsheet, with the risk of error that comes with it.
A multi-week average or an overtime quota exceeded shows up at the review, when it is too late to adjust the schedules.
At period end, the surplus to pay or to recover is argued over for lack of a record: which hours, which weeks, which rate?
You describe your annualisation schemes; Illizeo assigns the contracts, counts approved hours and absences, checks the limits and establishes the review of each period. HR closes it, and payroll receives quantities.
Each scheme has its reference period, target, thresholds, premiums and closing rules. Nothing is hard-coded: you follow your company agreement, your collective agreement or your country’s law.
Working time varies through the year around a target. Hours above the scheme’s weekly threshold are counted each week, the rest at the review.
A period matched to the season. Contracts in the same season can be chained, and a new seasonal contract takes over the previous one’s scheme.
Working time varies from week to week within the scheme’s bounds. Above the target, additional hours; below the floor, a dated agreement.
A scheme counted in days worked, read from the badge (full or half day), otherwise from the schedule. Day buy-backs, carry-over and workload interview.
Hours in a category excluded from the scheme, such as a call-out or a rescue, are declared separately and carry their own rate.
When you switch, what your previous tool had counted for the current period is carried over by file, simulated before import and reversible.
Each step is dated and logged. The employee, their manager and HR read the same figures, each within their own scope.
A closed review can be reopened with a reason: the treatment is undone and the review recalculated. An approval workflow can require a second HR person to confirm the closing.
HR sets the rules once, the counter keeps itself up to date, and the end of the period takes a few actions.
Your schemes, their versions and their controls, with no value imposed.
Everyone sees the counter that concerns them, up to date with approved time.
At period end, the review is ready; closing remains an HR action.
A typical scenario over the calendar year: high weeks in spring, quieter in summer. Hours above the weekly threshold set in the scheme are counted each week; the rest is settled at the review.
Léa’s contract is assigned to the workshop scheme on 1 January. Her counter follows her approved time entries and her leave, a control blocks an overloaded schedule, and the year-end review goes to payroll in hours.
Thresholds come from the scheme. For each control, you choose whether it alerts, blocks the schedule or stays disabled, for everyone, a sub-company or a population.
Maximum weekly duration, average over several weeks, number of high weeks and counter drift: each control is read on worked time as well as on the schedule.
Weekly threshold on actual work, premium bands, period quota and compensation beyond it, replacement by time off: as the scheme’s rules set them.
Cap raised by buy-backs, daily and weekly rest, justified rest reductions, carry-over with a deadline and a reminder of the workload interview.
Each month, a working time record is filed in the employee’s documents and kept for at least 12 months. A monthly register by sub-company is available, and every action is logged.
Annualised working time reads the time entries, absences and schedules already in Illizeo, and hands its quantities to payroll preparation.
Worked time comes from approved time entries in the Attendance module, which is required; hours awaiting approval are shown separately. See Attendance.
Approved absences are credited to the counter, and a surplus converted into time off credits the chosen absence balance. See Absences.
Published shifts feed the projection, and a blocking control prevents publishing a schedule that breaches the scheme. See Scheduling.
The Annualisation tab hands over quantities by rate; a reopened review is adjusted the following month. Amounts are still calculated by your payroll. See Preliminary salaries.
An installed law or agreement pack can pre-fill the rules it covers; you check them before publishing. See Laws and agreements.
Schemes, counters and reviews to read, assignments to write through the API; period-end and closing webhooks; full export in JSON, CSV and PDF. See the REST API.
Billed per active employee per month, at the same sliding-scale price as the Performance module. It relies on the Attendance module, which must be active.
Counters, controls, reviews and payroll quantities, in your HRIS, for all your countries.
Your schemes, your controls, your reviews and quantities ready for payroll, in your HRIS. Try the module with your own rules.
Start free trial