This calculation type uses the same logic as the regular Viking. At the end of the monthly period, Viking will compare the actual performed regular working hours with the Reg. max. set in the pay group.
REMARK: Reg. max. can only contain one value. This implies that every month will be compared with the same value. Example: February has 28 days comparison with 160 hours; January has 31 days ALSO comparison with 160 hours!
Where the target hours are not achieved, Viking will use the overtime hours to fill up to the regular hours. You can specify which OT type to steal from first, second, etc. to fill up the regular hours.
Monthly Viking pay group window in Astrow Web
The counters used should be defined first in Configuration - Counter Operations then linked to a definition Counter Definition. This calculation uses the counters definitions Daily OT A-E.
Daily OT counter operation definition in Astrow Web
In overtime group you need to define the overtime rule and add to regular. You can also check if the overtime needs authorization. Please make sure you won’t link the same counters (A-E) used by Daily OT to overtime group definition, because the calculation will double those:
Overtime group definition in Astrow Web
Set the zones in the day program (zone based overtime). Check the Reg. option. There is no need to check the OT boxes as this will use the daily and weekly counters A-E set in counters definition, unless you want this to populate other counters than the ones defined there.
Overtime definition in day program in Astrow Web
REMARKS:
· No counter definitions are required for quantity based overtime!
· Monthly Viking can only be used with a monthly pay period type!
· You can only use zone based overtime OR quantity based overtime!
Define the Reg. max. Here you should enter the regular monthly working hours (monthly basis).
to add a new definition (see