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 1 added 2 lines
[{TableOfContents }]
At line 20 changed one line
;: [{$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.
;: 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.
At line 31 changed one line
*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.
*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.
At line 33 changed one line
*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].
*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].
At line 35 changed one line
!!GROUPS
!!Groups
At line 38 changed 2 lines
!Maintain Group ([IDGR]) - Work Rules
;FLSA Hours
!Work Rules tab
;[FLSA Hours|FLSA_HOURS]
At line 44 changed one line
;FLSA Factor
;[FLSA Factor|FLSA_FACTOR]
At line 47 changed one line
;FLSA User Calc
;[FLSA User Calc|USER_CALC_CODE]
At line 63 changed one line
;FLSA Calendar
;[FLSA Calendar|CALENDAR_CODE]
At line 67 changed one line
!Maintain Group ([IDGR]) - Elements
!Elements tab
At line 87 changed one line
!!WORK RULES
!!Work Rules
At line 89 changed 2 lines
!FLSA Method
;Actual Hours Worked(normally used)
;[FLSA Method|FLSA_METHOD]: This field is an optional field tied to the [X_FLSA_CALC_METHOD] lexicon. The user may select any of the following methods:
;:__Actual Hours Worked(normally used)__
At line 92 changed one line
;IDGR FLSA Hours
;:__IDGR FLSA Hours__
At line 94 changed one line
;Use Reg Hrs, etc.
;:__Use Reg Hrs, etc.__
At line 96 changed one line
;Do Not Calculate
;:__Do Not Calculate__
At line 99 changed one line
!!BUSINESS CALENDAR
!!Business Calendar
At line 108 changed one line
!!PAY POINT
!!Pay Points
At line 116 changed one line
!!PAY COMPONENT
!!Pay Components
At line 119 changed one line
This pay component must be included in the ‘Gross’ element as well as the FLSA gross element.
This [pay component|PAY COMPONENTS] must be included in the ‘Gross’ element as well as the FLSA gross element.
At line 121 changed one line
All calculated premiums are recorded into the pay component assigned to this usage.
All calculated premiums are recorded into the [pay component|PAY COMPONENTS] assigned to this usage.
At line 125 changed one line
If an invoked UserCalc needs to adjust the premium, the UserCalc simply stores an amount into the FLSA premium pay component. On return from the UserCalc, FLSA assessment will be made with this money taken into consideration.
If an invoked User Calc needs to adjust the premium, the User Calc simply stores an amount into the FLSA premium pay component. On return from the User Calc, FLSA assessment will be made with this money taken into consideration.
At line 129 changed one line
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.
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.
At line 132 changed one line
[FLSA CASE STUDIES]
!!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'}]
This page (revision-25) was last changed on 26-Nov-2021 10:22 by jescottTop