Employee salaries include all the pays that employees receive based on their assignment to jobs. Employees can have multiple pays, and pays can be structured with a unique basis– meaning we can handle that some people are paid based on hourly/daily/annual or other mechanisms. The way that this works is that each record has an fte_basis, which represents the number of units of pay that are equivalent to a 1.0 FTE over a school year. To determine the annual pay, Allovue multiplies the fte_basis by amount. The employee pay_type is an open field to define the type of pay. This allows employees to include their stipend and non- regular salary pays.
Employee Salaries Data Elements
|
Element |
Description |
Example |
|---|---|---|
|
Employee Code |
Unique identifier for an employee, typically the employee number. Should be a displayed value. |
1 |
|
Pay Type |
A description of the type of pay. May be “regular salary” or “longevity stipend” or similar. |
Regular Salary |
|
Segment Code |
The object or other dimension that this salary is always charged to.
|
101 |
|
Pay Basis |
A descriptor of how someone receives this pay. Examples include hourly, daily, pay period, or annual basis. This is only used as a description. |
Daily |
|
FTE Basis |
The number of units that represent a 1.0 FTE when receiving this pay.
|
185 |
|
Amount |
This is the rate of pay per basis. For hourly, the hourly rate, for daily, daily, etc. |
300 |
|
Start Date |
The first day this employee made this salary rate. |
2023-02-14 |
|
End Date |
The last day this employee made this salary rate. |
|
Employee Salaries Data Validations
-
employee_code, pay_type, segment_code, pay_basis, fte_basis, amount, andstart_date are not null.
-
employee code, pay type and start_date are unique.
-
start_date less than end_date OR end_date is NULL.
-
employee_code matches an existing employee.
-
Segment code matches an existing segment code for that dimension.