Skip to main content

Hi,

I have a question regarding one of our colleagues who is finishing their Ausbildung. According to our setup, they are entitled to 24 vacation days per year, and as of now, they still have 12 days remaining.

We would now like to transition them to a full-time employee in Personio. My question is:

  1. Can Personio correctly calculate the vacation balance during and after the status change (taking into account remaining days from the internship period)?

  2. What is the recommended way to switch the profile from "intern/trainee" to "full-time employee"? Should I just update the existing data (e.g., position, status, contract), or is there a better approach?

  3. Will all development history remain visible after this change, or is there anything I should watch out for when doing the transition?

Thanks in advance for your support!
Anna

Hi there! Just tagging ​@jwilliams79, ​@rstambolieva, ​@berat can, and ​@Laure.vanpelt for some potential help! 


Hi ​@AnnaCzarnik,

Here some insights that might help 😊

  1. The vacation balance is not calculated based on the employee’s status but on the accrual policy you assign. If the yearly entitlement changes, you’d have to update the accrual policy but as far as I’m aware this change can only be implemented “from hire date” or “from current entitlement period”. So if your entitlement period goes from January to December, it would update it retrospectively. The easiest would be to adjust the entitlement manually for this year and then assign the new accrual policy as of the next entitlement period.
    At least that’s how I see it. Maybe someone has more insights and knowledge about this. 😊
  2. Yes, I’d just update the existing profile and schedule the changes to the respective date when the change happens
  3. I would have said yes as it’s tied to the profile but can’t say for sure as we don’t use the P&D section at our company.

I hope that helps? 😊


Hi you all,

Thank you for your already given input! ​@SabbuSchreibers points cover the most important elements already. :)

@AnnaCzarnik I’d like to add some notes. We (somewhat) recently released the first iterations of a re-hiring functionality, that make the re-hiring approach for employees way easier. We plan on expanding here as well. You can find some more information here. As ​@SabbuSchreiber already mentioned, you can easily schedule the respective data changes. For that however, we urgently advise that the attribute >hire date< is not touched for the new employment! Changing the hire date has the potential to distort the employee data history.

So basically, if you feel like you want to start a kind of new employment that will have it’s own start date and requires an own hire date, independently from the former employment, using the re-hiring functionality and creating a new profile might be the better approach. If you won’t touch the hire date, Sabbus comment is the way to go. :)

 

All the best

Michael


Your reply