In Altamira HRM, remaining balances are automatically calculated for the following categories, known as counter groups: Vacation, Leave, ROL (Reduced Working Hours), Time Bank, and Holidays in lieu.

Additional balances beyond those listed above can be managed using generic counter groups, which can be linked to the relevant reason code in the field (e.g. Counter Group 01, etc.).

The calculation differs depending on whether the client has the Attendance product enabled or not.

Clients with the Attendance product

Planned for the year
Sum of absence requests linked to that counter group where the end date has not yet passed or the related attendance has not yet been processed.

Therefore:

• Approved absence requests with an end date in the future are counted as planned.
• Approved absence requests with an end date in the past are counted as planned if the related attendance record is still pending or in error.

Used (calculated in the platform)
Sum of attendance details with reasons linked to the counter group, processed after the group’s last update date.
For counters measured in days, the system uses the maximum daily duration from the attendance model; if not set, it refers to the “Conventional number of hours per day” field in the weekly model.
+
Sum of figurative absence requests linked to that counter group, approved after the group’s validity date.

Accrued (calculated in the platform)
Sum of authorized overtime details linked to the overtime destination reason of that counter group, processed after the last update date.
+
Sum of details of reasons that increase counter balances for that group, processed after the last update date.
For day-based counters, the same duration logic as above applies.
+
Sum of automatically accrued values after the counter group validity date.
+
Sum of figurative reasons linked to that counter group, approved after the last update date.
+
Only for “At request date” expiry: accrued values before the validity date that were used to cover usages after the last update date.

Note: Counters measured in days work only if the attendance model includes a defined “Maximum daily working time (hh:mm)” or the “Conventional number of hours per day” in the weekly model.
The absence duration is divided by that value to determine the number of days.
Example: 8/8 = 1 vacation day.

Clients without the Attendance product

Planned for the year
Sum of requests linked to that counter group whose start date has not yet passed and end date does not belong to the current year — requests for future years are also included.

Used (calculated in the platform)
Sum of approved absence requests linked to that counter group, after the group’s validity date.

Accrued (calculated in the platform)
Sum of approved requests linked to that counter group that increase the counters and whose date has already passed.
+
Sum of automatically accrued values after the last update date.

Total Balance Fields

Residuals (calculated in the platform)
The current balance available to the employee, excluding planned and future accruals.
Formula:
Previous year + Accrued (payroll) + Accrued (calculated) - Used (payroll) - Used (calculated)

Expected year-end balance
Balance expected at the end of the year.

• If the annual accrual rate field is filled:
  Previous year + Annual Accrual - Used (payroll) - Used (calculated) - Planned for the year
• If the annual accrual rate field is empty:
  Previous year + Accrued (payroll) + Accrued (calculated) - Used (payroll) - Used (calculated) - Planned for the year

Note: The formulas above include fields not calculated by the platform: Previous year, Accrued (payroll), Used (payroll).
These can be entered manually or imported from an external payroll system.

Note: Unapproved requests are not included in the calculation of balances.