Saved-up special rule enabled
If the saved-up special rule is enabled and the user has not enough vacation balance the special rule will kick-in with a message informing that the availability will become negative on a given date:
“Applying this absence would result in availability on [date] to be [- amount] days of [absence type]. Are you sure?”
Depending on what amount is entered on Minimum balance allowed the availability amount shown in the special rule dialog can have two different meanings:
if applying another vacation absence would make the available balance exceed the Minimum balance allowed then that vacation day will result as self-paid
if applying another vacation absence would make the available balance within the Minimum balance allowed then that vacation day will be a paid day and the available balance will have a negative amount
For more information about the Minimum balance allowed refer to this article: http://helpapp.samesystem.com/en/articles/5432513-minimum-balance-setting-in-absence-type
When applying an absence it is important to consider where absence is placed, either before or after already existing vacation absences.
Saved up rule is enabled, minimum balance allowed = 0, and the vacation is applied on a date after already existing vacations
If there is not enough vacation balance at that date the balance will become negative and it will result as unpaid vacation in approved hours salary and salary file.
Example:
Arthur Schopenhauer has already approved vacation in July and its balance on July 26th is zero.
If we apply an absence on July 27th the saved up dialog will show the following dialog:
If the user confirms the action, July27th will result as not saved up in approved hours salary and with the salary code for overused in salary file if you have created one.
Approved hour salary
Remember that under Holiday you see the total of days spent regardless of being paid or unpaid while in Not saved up (Holiday) you can see the unpaid days
Salary File
Remember to create salary codes for the absence type including a salary code for not saved up absence
In the salary file you can see the used vacation days with the relative salary codes
Saved up rule is enabled, minimum balance allowed = 0, the vacation is applied on a date before already existing vacation
If there is not enough vacation availability the balance will become negative on the latest date where there is a vacation and not on the day where the user is currently adding vacation. Thus, in the approved hours salary and salary file the unpaid day is not necessarily the one that "caused" the negative balance but it is the latest in the calendar.
Example:
Arthur Schopenhauer has already approved vacation in July and how we have seen in the salary file and approved hours salary the days from July 19th to July 21st have salary code 3103 for paid days while the day on July 27th has salary code 380, and the day is unpaid because not saved up.
If we add a vacation day on July 15th the saved up rule will show the following message:
The system makes unpaid the latest absence while the one just applied becomes unpaid
Approved hours salary
Salary File
In the salary file you can see that July21st has the salary code for Not saved absence
Saved-up special rule enabled and enforced
When the saved-up special rule is enforced the user will not have the option to use not saved up day. The system suggests the use of partial absence
“Applying this absence would result in availability on 2021-08-09 to be -0.64 days of Ferie. Consider using partial absence instead” - Thus, it’s not possible to add vacation
N.B. the saved up special rule doesn't work correctly in the vacation planner when using a monthly release "period end" and "after period end" is used. The reason is that in vacation planner looks at the available balance at the end. of the holiday period and does not take into consideration the monthly breakdown.