Skip to main content

Balances for SaaS customers

For SaaS customers, the balances are kept only in codeto report. There is no second system, such as a payroll system, that supplies its own values. The balance shown by codeto report is the valid balance.

How the balances are made up​

Every employee has three balances: Holiday, Prior-year hours and Overtime. Each of them consists of a starting value, what is added and what is deducted.

BalanceStarting valueAddedDeducted
Holidaythe holiday for the whole year, including holiday left over from the previous yearnothingholiday taken
Prior-year hoursovertime carried over from the previous yearnothingprior-year hours taken
Overtimeusually 0hours above the expected work timemissing hours when the expected work time is not reached

All values are kept in hours. How the starting values come about is shown in the holiday example.

Starting values​

codeto enters the starting values for each employee:

  • Holiday: the holiday for the whole year in hours, together with any holiday left over from the previous year
  • Prior-year hours: any overtime carried over from the previous year
  • Overtime: usually 0

If no other information is available, codeto enters the holiday according to the collective labour agreement (GAV) of the electrical industry, see below. Prior-year hours and overtime then start at 0. If the balances feature is switched on during the year, codeto deducts holiday already taken from the starting value.

Holiday according to the GAV

Without other information, holiday for SaaS customers follows the GAV of the electrical industry, Art. 29. At a workload of 100 % it is:

  • up to and including the 50th year of age: 27 working days
  • from the 50th year of age: 30 working days

What counts is the calendar year in which the age is reached. For part-time work, codeto calculates the hours proportionally. If an employee joins or leaves during the year, holiday is granted proportionally.

What changes a balance​

For overtime, codeto report first deducts the expected work time for every past working day and for today. Everything reported for the day is added back. Anyone who reports exactly the expected work time is therefore at zero for that day. No expected work time is deducted for future days.

What happensEffect on the balance
An employee reports holidayHoliday decreases by the hours reported
An employee takes prior-year hoursPrior-year hours decreases by the hours reported
Nothing has been reported yet for a past working day or for todayOvertime decreases by the expected work time of that day
Work or an absence is reported for the dayOvertime increases again by the hours reported
A public holidaycounts as expected time fulfilled for overtime; a half-day holiday counts half
Up to and including today

Expected work time is deducted up to and including today. If a past day or today has not been reported yet, overtime temporarily shows less. Once the days are reported, the balance is correct again. Future days deduct nothing. A report for a future day, however, counts immediately.

Public holidays and absences are not counted twice for the same period. Anyone who additionally reports 8 h of holiday on a full public holiday does not receive an extra credit on overtime.

A report counts immediately once it is recorded, not only after approval. If a report is changed or deleted, the balance adjusts immediately as well.

Holiday and prior-year hours are taken by reporting an absence, see Record absence hours. Which absence affects which balance is set by the admin in Absence management.

Example: holiday​

An employee under 50 works 100 % and, according to the GAV, has 27 holiday days per year at 8 h each, i.e. 216 h. They carry over 12 h of holiday from the previous year. codeto enters a starting value of 228 h.

DateWhat happensShown
1 Januarystarting value: 216 h for the whole year plus 12 h left over228 h
10 Februarythe employee reports 8 h of holiday220 h
3 Marchthe employee books 16 h of holiday for July in advance204 h

Holiday booked in advance is deducted immediately, not only in July.

Example: overtime​

An employee has an expected work time of 8 h per day. Their overtime is 0 h at the start of Monday.

DayReportedExpected work timeOvertime after the day
Monday9 h work8 h+1 h
Tuesday8 h work8 h+1 h
Wednesday6 h work8 h−1 h
Thursdaypublic holidaycounts as fulfilled−1 h
Friday8 h holiday8 h−1 h

Reporting exactly the expected work time leaves the balance unchanged. Reporting less draws from the balance, reporting more builds it up.

Turn of the year​

At the end of the year, the permitted part of the overtime is transferred to prior-year hours, and overtime starts at 0 in the new year. The holiday for the new year is entered as well. Which part may be transferred is described under Overtime, excess time and vorholzeit.

Change of workload​

If an employee's workload changes during the year, for example from 80 % to 60 %, codeto must be notified at support@codeto.ch. codeto then adjusts holiday and expected work time. In future, this can be adjusted directly in user management.

Good to know​

  • Approval: approval does not change any balance.
  • No drawing into the negative: by default, holiday and prior-year hours can only be taken as long as the balance is sufficient. This can be changed per absence with Allow negative balance.
  • Pending absence requests: a holiday request that has not yet been approved does not reduce the balance shown. The hours requested are, however, already reserved. If an employee has 40 h of holiday left and requests 32 h, they can only request 8 h in a second request, even though 40 h are still shown. The balance shown only decreases once the request is approved.
  • Hourly wage: no balances are kept for employees paid by the hour; the value stays 0.