See the “Services by clients” screen for information. The following figures describe the upper table.
Four employees work for one client. ISAS does not control how worked hours are actually divided between employees (1) if more than one worked on the same day (clime). Therefore, the hours are randomly distributed in the ISAS data file. RSAkit initially suggests the hour distribution as approved in ISAS—see the blue digits (2):
The task is to rearrange the hours following the actual worked hours.
For the employee in the last line, RSAkit placed the correct data. Nothing needs to be entered manually here. The number that is shown in the ‘revised’ cell will be used in the payroll, regardless of who — i.e., RSAkit or you — input it there.
For the employee in the penultimate line, we obviously must enter the value “8”, which is what he actually worked (1). These hours have not yet been approved (“Need Authorization”), but we expect this to happen.
Please note: The new sum in the column “Revised” is highlighted in yellow (2). This means that the sum of “Revised” hours now exceeds the amount in the column “Approved”, but is less than the quantity in the columns “Approved” and “Need Authorization.”
For the employee in the next line, we enter the value “7”, based on the hours actually worked (1).
Please note: The amount in the column is highlighted in red (2). This means that the sum of “Revised” hours now exceeds the amount in the columns “Approved” and “Need Authorization.”
If we know that the first employee had incorrect hours registered in ISAS, and decide to allocate exactly as many hours as approved in ISAS, then we press the “calculator” icon (1).
RSAkit calculates revised hours for the line, where the icon was clicked (1).
However, it does not take into account hours in the “Need Authorization” status. Therefore, we manually adjust the clock for the first employee.
So, you fixed three values and one was correct (shown in blue).