This page (revision-25) was last changed on 26-Nov-2021 10:22 by jescott

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
25 26-Nov-2021 10:22 12 KB jescott to previous
24 26-Nov-2021 10:22 11 KB JEscott to previous | to last
23 26-Nov-2021 10:22 11 KB JEscott to previous | to last
22 26-Nov-2021 10:22 11 KB JEscott to previous | to last
21 26-Nov-2021 10:22 11 KB JEscott to previous | to last

Page References

Incoming links Outgoing links
FLSA
FLSA

Version management

Difference between version and

At line 22 changed one line
;: Personality then takes the FLSA Regular Earnings Element and divides those earnings by the total of the four hours elements. The FLSA Regular Earnings Element should include ONLY those earnings paid at a regular rate; for example, do not include earnings paid at double time.
;: [{$applicationname}] then takes the FLSA Regular Earnings Element and divides those earnings by the total of the four hours elements. The FLSA Regular Earnings Element should include ONLY those earnings paid at a regular rate; for example, do not include earnings paid at double time.
At line 33 changed one line
*The use of FLSA in Personality requires that all remuneration paid for overtime hours be stored into a separate pay component from regular earnings. This restriction will ensure that overtime premiums already paid in an FLSA period, are taken into consideration when calculating the FLSA premium amount.
*The use of FLSA in [{$applicationname}] requires that all remuneration paid for overtime hours be stored into a separate pay component from regular earnings. This restriction will ensure that overtime premiums already paid in an FLSA period, are taken into consideration when calculating the FLSA premium amount.
At line 35 changed one line
*If an FLSA [User Calc|USERCALC] is used,Personality executes the FLSA logic, executes the FLSA [User Calc|USERCALC], then re-runs the FLSA logic in order to consider the results of the FLSA [User Calc|USERCALC].
*If an FLSA [User Calc|USERCALC] is used,[{$applicationname}] executes the FLSA logic, executes the FLSA [User Calc|USERCALC], then re-runs the FLSA logic in order to consider the results of the FLSA [User Calc|USERCALC].
At line 121 changed one line
This [pay component|PAY COMPONENTS] must be included in the ‘Gross’ element as well as the FLSA gross element.
This pay component must be included in the ‘Gross’ element as well as the FLSA gross element.
At line 123 changed one line
All calculated premiums are recorded into the [pay component|PAY COMPONENTS] assigned to this usage.
All calculated premiums are recorded into the pay component assigned to this usage.
At line 131 changed 4 lines
The [pay component|PAY COMPONENTS] with the usage ‘7001-FLSA Premium Hours’ must NOT be included in any of the FLSA Hours elements since they are not really hours worked. This [pay component|PAY COMPONENTS] will simply hold the number of hours used in the FLSA premium calculation.
The number of excess hours over and above the regular FLSA hours is logged in the Pay if the Usage 7001 is set up. It is recorded ONLY if the FLSA premium is NOT zero. Previously it was recorded even when the FLSA premium was zero.
The pay component with the usage ‘7001-FLSA Premium Hours’ must NOT be included in any of the FLSA Hours elements since they are not really hours worked. This pay component will simply hold the number of hours used in the FLSA premium calculation.
At line 137 changed 7 lines
!!FLSA Case Studies
There are two case studies provided in the [FLSA CASE STUDIES] link which illustrate how FLSA is calculated.
----
![Notes|Edit:Internal.FLSA]
[{InsertPage page='Internal.FLSA' default='Click to create a new notes page'}]
[FLSA CASE STUDIES]
This page (revision-25) was last changed on 26-Nov-2021 10:22 by jescottTop