When edits are made to timesheet entries in EWS, overtime entries needs to recalculate accordingly. This includes changes to the number of hours for a prior timesheet entry, deletes, or adds
My clients are having a hard time accepting that the system will simply delete all subsequent time entry records when a previous time entry record is updated to recalculate OT. I've provided the technical response of, "The system must delete and redo all time entries to properly calculate OT records..." but none of them are truly accepting of this response and are forced to suffer in silence afterward.
An ideal enhancement for my use case is to retain the previously entered information but offer the user a preview of what their new time entry records will be after another OT recalculation is performed on their existing and edited timesheet. The old data is used to generate the new records and it can then be written to the software once the user accepts the changes.
YES! We're on a biweekly pay period and I can't trust staff to enter everything in chronological order (as much as you'd think that would be obvious, for a lot of staff it's not) so I have to manually check all 140 timesheets to make sure I don't miss paying any OT!
YES! Or when someone forgets to enter time for a day earlier in the week but adds it before they submit and the system doesn't calculate any OT. SO FRUSTRATING!
I have a real hard issue with the OT calculation in EWS. We had an employee who forgot to clock out for lunch, that threw her over 40 hours. I fixed it before she submitted her time but it left the OT calculation in the system. Why does a TIMEKEEPING system not recalculate OT when there is a change? Why should managers have to manually add up the hours to see if OT is real or not?
You won't be notified about changes to this idea.