The vacation allowance payment can occur in different occasions, therefore the system allows you to configure the situations that must trigger the payment, depending on the employee grouping.

According to the law, the vacation allowance must be paid before the leave period. Since it is possible to have more than one leave period per employee, you must indicate (configure) the period before which the payment is made.

Currently, the system supports the following payment-triggering methods:

• Fixed date – the allowance is paid entirely on a fixed date, independently of the number of leave periods
• Longest leave period – the allowance is paid entirely before the longest leave period
• First leave period – the allowance is paid entirely before the longest leave period (if there is more than one leave period)
• Cumulated leave days – the allowance is paid entirely before the leave period that is taken when the number of leave days (since the beginning of the year) adds up a previously stipulated number. For example, the company pays vacation allowance when the employee leave days exceed 12. If he takes 5 days in March, 5 days in April and 5 days in June, the payment is made in May, that is, before the period in which the leave days exceed 12 (in June the employee’s cumulated leave days add up to 15).
• In every leave period – the allowance is paid before each leave period, proportionally to the number of days taken, and provided that the period is longer than X days.
• Every period – the allowance is paid every month (1/12 each time), regardless of the number of leave periods.
• In case you wish to use a different method for calculating the payment, configure the user-exit EXIT_RPCALCP0 as described in the IMG.

 If you wish, you can define the earliest (date before which no payment is made) and the latest (date after which no payment is made) payment date. Per default, these dates are set, respectively, as the first and last day of the leave entitlement year to avoid that payments regarding one leave entitlement year is shifted to the previous or to the following year.

Activities

Evaluating payment triggering