TimeSimplicity & Other Product Ideas

This was allowed in TW but is not allowed in TWP.  I have 2 reasons why this would be helpful.  There may be more.

1. Accrual Adjustments - Sometimes an employee's accrual balances need to be adjusted retroactively (wrong PTO Code set up on employee, for example).  Calculating the accruals manually can be difficult on complex accruals. If we could unfreeze the employee's punches back to a certain date, the balances would adjust automatically per rules in the script.  After the correction is made, the employee could be "Refinalized".  Currently, client has to calculate each pay period accrual manually and then make the change(s) in the current period.

2. Recording Timesheets in Finalized Periods - Some clients track "NON-PAYROLL" workers in Swipeclock.  These workers are set up with the  "Export Block" field set to "BLOCK", to exclude them from payroll integration.  Certain industries, like health care, are required to report the time using the PBJ reporting set up in SC.  These hours are often submitted to the business monthly or quarterly.  Since the hours must be reported on the day each service was provided, the client has to call us to unfinalize all pay periods back to the date of the hours that have to be entered.  This is a dangerous process for obvious reasons.  Allowing these "NON-PAYROLL" workers to be unfinalized would eliminate this danger.

Perhaps an event log could be written when a period or a single employee is unfinalized.  This might satisfy compliance requirements and help prevent fraud.

Thanks for the consideration!

Frank