Hi everyone!
I was looking into the vacation settings in Personio. We use Personio across 3 countries where there are different regulations.
As far as accruals are concerned I have set up individual accrual policies so that is not an issue. However, we want to start implementing our policy of limiting the number of carry over days and providing a cut-off date at which - if not used - the carried over days will be removed from the system.
It is currently not possible for me to adapt the carry over regulations per country. Example: In Germany we limit the number of carry over days to 10 and the cut-off is 31.03. In Croatia the limit is also 10, but with a cut-off date 30.06. In the US there is no cut-off date. I would like to open a discussion about how this can be reflected to avoid manual data adjustments. As far as I can see it is currently not possible to limit the number of days carried over but again I may be missing something.
Also: It is currently not possible to apply a specific date by which the change in the vacation regulations becomes live. Example: We currently do not have a cut-off date set. We would like to set that up for 2023, but not apply that to past years. If I set it up the system automatically removes all carry over vacation days that were not used in the past by the set cut-off date. This in turn changes the current vacation data for employees. (I am currently manually adjusting everything manually!). I think that particularly small organisations may not want to have a hard cut when the team is small but as the organisation grows it may become necessary or desirable to use that function so employees are not accruing a large backlog of vacation (and causing the organisation to build up respectively high financial accruals for this). This is why we would like to start using the function but not retrospectively.
I would be interested to hear feedback on this and learn about any development plans that may be in place.
Cheers, and enjoy your day!
Linda