Contract independent compensations & more compensation improvements (February)

Created by Marcel Poelker, Modified on Fri, 14 Feb at 7:12 AM by Marcel Poelker

With this release we've made working with compensations more flexible.


Contract independent compensations

While contracts still carry the salary, all other compensations are now added in a separate tab on the employee page and they can have a custom date range, so that they are independent from any contract. This specifically makes working with custom compensations simpler, as they were hard to maintain in certain situations like when going through contract changes.


Aggregation pages still match compensations against their corresponding contracts, so that the costs are associated properly. Steady compensations are paid out as long as there is an active contract (started and not ended), while custom compensations are allowed to have payouts outside of any contract as well - another point to give you more flexibility. For compensations matching on-leave contracts payouts are paused.


Additionally we have simplified the UI around compensations as well, so that it's easier to understand where to find what information.



Further compensation related changes

  • We have added a new template "one-time payment" when creating new compensations
  • Compensation type has been renamed to category (base, bonus, other)
  • We removed the distinction between Salary and Fee for simpler usability. Now all employees regardless of their employment type have a base compensation called "Salary". This includes also freelancers. If it's desired to see freelancers separately, it can be done so by adding employment type to the aggregation table.


Other changes:

  • The dashboard considered employees on-leave for their average calculations and for totals it excluded them. Now employees on-leave are excluded in all cases


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article