Why doesn’t Celery switch off the ZV premium automatically?
Employees who earn more than the SVB/SZV Wage Limit are usually not insured under the ZV (the health insurance). So you might expect Celery to switch off the ZV premium for them. But there is an exception.
It depends on the wage in November
What counts is the employee’s SVB/SZV wage in November of the year before. This is called the reference date. That November wage decides if the employee is insured under the ZV for the whole next year. Their actual salary in that year does not matter.
An example
- In November 2018, an employee earns an SVB/SZV wage of 5,500.
- This is below the limit. So the employee is insured under the ZV for all of 2019, from January to December.
- In January 2019, the employee gets a raise to 10,000 gross per month.
- The employee still has to pay ZV premium for all of 2019.
- The premium is calculated over the SVB/SZV Wage Limit per month, not over the full 10,000.
So a pay slip of 10,000 gross per month can still include ZV premium. If Celery switched it off automatically, the salary calculation would be wrong.
Why Celery can’t check this for you
Celery can’t always see the full SVB/SZV wage on the reference date. Not every employer adds all wage parts to the payroll every month. For example, some employers don’t build up (accrue) vacation pay monthly. In that case, Celery doesn’t count the vacation pay in the SVB/SZV wage.
What you need to do
To keep salary calculations correct, you decide per employee whether the ZV premium applies. Check or uncheck the ZV premium setting for each employee yourself.