Ok back dating new starters is a common occurence on the site I am on, soemtimes more than one month

Recurring payment elements are being handled automatically in the first paid period but non-recurring is being handled by retro pay.

there is a problem with retro pay that it will not capture details/process elements in a period that has not been processed. So if an emp is not processed in their starting month but tries to claim overtime via OTL the overtime is not picked ..ok we can get round that

BUT we now have another problem in that Overtime entered in their first paid period is not being picked up either, anyone had this problem...detailed description below

New Starter Month 1
Put on retrospectively and not processed at all

New Starter Month 2
Normal processing, with recurring payment elements do a catch up for the missing month payments.

New Starter Month 3
Ovetime entered in Month 2 via core
Retro pay run and does not pcik up anything from Month2

Silly question, but I assume the overtime elements are set up for retropay?

Delboy

Is the problem only on new starters?

Delboy

As far as we have identified but we are still digging

This has been proven to be a bug, which affects only secondary assignments...quite important for Councils !!!!

Wonfer how no-one else has come across it ??

The triggers are picking up the change but the Retro Notifications report is ignoring them