Teresa closes the month. She needs the numbers to already be right.

SkyRoster runs four independent calculations for extra time worked outside the roster, each resolving its own payroll code: a shift worked on a public holiday, an approved overtime duty, a shift extension before or after a scheduled shift, and an ad hoc work request called in on a day off.

This illustrative employee has all four on the same day, so every pipeline is visible at once. Most real days carry one of these, if any.

Before any of this becomes overtime pay, SkyRoster checks the employee's Bank of Working Hours balance. A balance that covers the whole duty books all of it as banked hours; no balance books all of it as overtime; a partial balance, like this employee's, splits the duty.

The carved-out portion is drawn from the bank rather than priced as overtime, and it is carved out first, ahead of everything below: the day/night split and the first-hour premium only ever see what's left of the duty.

Any overtime that crosses the configured night boundary splits into separate day and night lines, each on its own rate, including a duty that runs across midnight.

That boundary is a setting an administrator configures per site, not a clock time fixed in the code. Try the alternate boundary below: the overtime duty's night hours move; the work request, already deep in the night under either setting, does not.

Many collective agreements pay a higher rate for the very first hour of a period of extra time than for the hours after it. SkyRoster marks that hour on every period independently: the holiday shift, the extension, the remaining overtime duty and the work request each get their own first hour marked.

The night split and the first-hour premium are two independent cuts through the same duty; here they land at different times, so one continuous overtime duty ends up divided into three differently-rated pieces.

This employee's contract banks overtime as time off rather than paying it out, so every paid line above, the holiday shift, the extension, both overtime portions and the work request, is mirrored into a Compensatory Time Off (CTO) line at the contract's configured rate: one and a half hours banked per hour worked, in this illustration.

The Bank of Working Hours line is not mirrored. It was already banked, not paid, so there is nothing left to compensate a second time.

Six configuration tables, Bank Holidays, Bank of Working Hours, Compensatory Time Off, Meal, Overtime and Preventive, map roster and attendance events to the numeric codes the client's payroll system expects. Each table is assigned per employee, so a colleague on a different collective agreement can see different codes for the same hours.

The meal allowance is not one of the four inputs, and it skips the carve-out, the split and the mirroring: it is evaluated once, directly from the holiday shift overlapping the configured meal-time window, and resolved straight to a code here. The Preventive table is not triggered by this employee's day.

A payroll officer can run a Draft export for absences, overtime or prevention at any point in the month, for one unit or the whole organisation, as many times as needed. It recomputes fresh every time and never marks anything reported.

Close of month is the one deliberate, irreversible step: it stamps every contributing record as reported and archives the final file, with a cooldown against re-closing it by accident. Every export, draft or closed, stays archived and can be re-downloaded.