More than a frame monitor.

Eight steps from the schedule to payroll.

This is not a feature list. It is the order in which working time moves through the system — and at each step, what the code actually does. What it doesn't do, we don't write down.

1. 01

   Schedule

   Every employee has a valid schedule: daily and weekly hours, workday pattern, typical shift start and end, breaks. Settings cascade — what is standard for the company need not be set per person — and can be segmented in time: a May schedule change applies from May, and the two segments never overwrite each other.

   In the system5 schedule patterns + custom · cascade: employee → role → unit → company · shift presets and multi-day planning from a pattern

2. 02

   Working-time frame

   The frame length is configured and runs in calendar blocks. The system does not calculate at the end of the frame but every day: where the employee would stand pro rata, and where the frame is heading if things continue this way. Differing monthly workday counts are taken into account.

   In the systempro-rata standing · run-out forecast · the month not yet closed does not distort the picture

3. 03

   Pro-rata calculation

   Partial months, joining or leaving mid-month, a schedule change mid-frame, part-time: all follow the same logic, not manual corrections. The leave quota is prorated too.

   In the systemworkday-proportional norm split · join/leave clipping · 8/6/4-hour norms · per-segment calculation

4. 04

   Rules and deviations

   Labour-law rules are not hard-coded but configured in a table: the value, how severe, whether it blocks saving or only warns. Extra hours (overtime, on-call, standby) sit as a separate layer beside the day, with their own limits.

   In the system11 h daily rest · weekly rest day · 12 h/day, 48 h/week · no leave on public holidays · free Sundays per month · frame deviation with two thresholds

5. 05

   Absence

   Absence types come from data, not code: for each one you set whether it is paid, needs approval, counts against the frame, and which payroll code it carries. Only leave and sick days count in the frame; home office counts as work, not absence.

   In the systemleave · sick · unpaid · exemption · other work — flags per type

6. 06

   Approval

   Single-step: one approver, resolved by the system in cascade — if none is set for the employee, it comes from the role, unit or company level. There is no approval chain or deputy — we say it this way because that is how it is. HR reminds people of unfilled workdays with one click.

   In the systemone approver · cascade resolution · reminder for missing days

7. 07

   Recording and month close

   By hand: day, interval, bulk entry or template copy. By machine: QR scanning from the mobile app, into the same record the frame reads. The month can be closed at two levels: for employees, and for admins too.

   In the systemmanual + QR · one table · month lock: employee and admin level, who closed it and when

8. 08

   Payroll export

   A real, formatted XLSX with several sheets: calendar view, payroll sheet — one row per employee per day, with the absence's payroll code —, signable sheet and frame summary. In a form that external payroll providers have accepted as an import. There is no direct SAP or Nexon integration.

   In the systemmulti-sheet XLSX · with filters · printable weekly schedule · payroll code per absence type

This is what makes an HR or IT person say: they thought this through. It is not the frame monitor that is nice. It is the eight steps underneath that hold.