Is there a way to force retropay to caclulate for all elements even if the result might be 0?
If I make a change to an element, say Basic Salary after payroll has been run in the previous month, then run retropay by element, in the next month I can see a Basic Salary Retro element. But what if there are other elements that depend on the value of basic salary, shoudn't they be recalculated as well? I ran into this issue with proration earier and I'm very unhappy to see the same nonsense repeat itself with retropay. The last legislation I worked with didn't behave like this to the best of my knowledge (working with Saudi a.t.m) so I'm thinking this might be a setup issue
OK I figured it out. For the current implementation, we are not using the salary administration window. The total salary is made of basic, housing, transport and this is entered manually.
If these elements were calculated from the formula a change in the annual salary would trigger proration or retropay in all.
For a workaround, I am going to create an annual salary element, then try to build a user hook to update this each time a change is made to one of the standard elements.
Just need to figure out how to build user hooks for PAY_ELEMENT_ENTRIES table.