Skip to main content

Hi community,

At the moment all employees at my company (based in Spain) have the same Absence Type for holidays and different accrual policies.
For 2023 we want to change this, and assign each employee to a corresponding Absence Type for their subsidiary (different labor laws/carryover rules in each country).
I have 2 questions:

#1: because there is unlimited carryover on some of these new types, if we assign the new absence type + accrual policy, people will have the prorated amount since hire date. How can I avoid this?

Possible solution: On 01.01.2023 do a manual bulk upload of employees with each absence type, manually assigning the # of days just for the year 2023.

#2: Once they are unassigned the current accrual policy, they will lose any carryover they had
What is the best way to add this carry over to their new accrual policy?
Manually, by downloading a point in time report of their absence balance and then bulk uploading a new adjustment?

Thanks for any and all help on the matter. 

Hello @samara20 !

Thank you for your reaching us, I’ll be happy to help you with your questions.

#1: because there is unlimited carryover on some of these new types, if we assign the new absence type + accrual policy, people will have the prorated amount since hire date. How can I avoid this?

I’d recommend to create an accrual policy with 0 Days to assign from the hire date on the new absence and the accrual policy you will use in the future assign it from the beginning of the next entitlement period. This way you will have a fresh start for 2023 and there is no need for a manual adjustment. 

#2: Once they are unassigned the current accrual policy, they will lose any carryover they had

Once the policy is unassigned the carryover will not be accounted so before you do that, follow the steps on this help center article and then do an import of absence balance in bulk on then new absence applied on the 31st December so they will pass to the next year as carryover. 

Best,

Jorge

 


Thank you Jorge!


Your reply