Skip to main content

Hello Voyagers! 🌍

We’re excited to announce the first step on our journey to revamp Personio’s compensation setup. Managing employees’ compensation is complex – esp. for international teams. We've heard loud and clear that you need more scalable tools. Here’s what’s changing now, why it matters, and what’s next.

Why This Matters

As organizations grow and expand internationally, compensation management gets… tricky. Our old setup for “additional compensation” made it hard for HR teams to keep an overview of the compensation components they offer.

What’s New? 🚀

We’re improving how you manage compensation types in Personio. The new experience allows you to:

  • Sort compensation types by name, type (recurring, one-time) and creation date,
  • Filter compensation types by name, type (recurring, one-time) and creation date, and
  • Search compensation types

Also, different types of compensation – recurring and one-time – are now visually more distinct through colour-coded labels.

What’s In It for You?

Easily keep an overview of all compensation types in your compensation schema.

What’s Next?

The next milestones will make setting up and managing compensation even more efficient:

  • Compensation type assignment: Save time assigning compensation types to groups of employees in bulk. 
  • Compensation overview: Save time reviewing and updating your employees’ compensation in bulk.
  • Eligibility criteria: Confidently assign compensation types to employees – with employee attribute-based eligibility criteria (e.g. ”workplace”, ”job”, “rack”, “level”) that you can flexibly customize to your needs. 

We’d love to hear what you think! Drop your thoughts below or reach out via the in-app feedback tool.

Thanks for helping us shape the future of Personio salary and compensation management—one update at a time! 💡

Tobias

 

 

Exciting stuff!

Tagging some community members for visibility 😊

​@SalC ​@SabbuSchreiber ​@fmason ​@LegoMD ​@HRJoy ​@xtine08 ​@rstambolieva ​@KSO ​@Nadia Chubarova ​@michelap 

Hi ​@Tobias, sounds like an exciting update! I love the new overview and the simplicity of it. 😃 One question, will there be an archive option for compensation types that are not used anymore? 

Thank you for sharing ☀️

Thanks, ​@SabbuSchreiber – great to hear you love the new overview and its simplicity 🙏.

Regarding:

will there be an archive option for compensation types that are not used anymore?  

Not as part of this update. We keep hearing about this need though and are hence considering adding support for archiving moving forward.

What should be the impact from archiving from compensation types from your point of view (in the settings as well as throughout the product)? 

Hi ​@Tobias 

I’m honestly missing an archive option for most of the settings. The issue I often run into is that if I want to delete something (due to change of settings, new type of settings, etc.), the whole history will be deleted or changed (i.e. time off types, work schedules, etc.). I wasn’t sure if that’s also the case if we want to delete a compensation type that’s not used anymore but since there’s no archive option, I assume any past entries with the compensation type in question would then be voided?

There have been some archive options for a few settings coming out and those have been great but I’m still missing them for the more crucial setting options that have bigger impact on the daily ops. 😊

Got you. Thanks again, ​@SabbuSchreiber .

I wasn’t sure if that’s also the case if we want to delete a compensation type that’s not used anymore but since there’s no archive option, I assume any past entries with the compensation type in question would then be voided?

That’s the current product behaviour, yes.

Hence, we believe when we tackle archiving in this area, we would want to preserve the history while hiding the respective compensation types in settings and deactivating them for future assignment. 

Ooh - great redesign! Thanks for flagging this ​@Tobias and ​@Moe 😁

Terms & Conditions of the Personio Voyager CommunityAccessibility statement