Here are the position and pay (remuneration) data fields available for onboarding, and the associated transaction rules.
- If onboarding employee position data without the pay details, remember to set the installation option, onboard employee position data only (opos) to y (yes).
- Only a single position and pay (remuneration) entry per new employee is allowed where the employment number is zero (only a single employment can be onboarded).
- It is possible to onboard multiple split cost centre records.
- The position and pay (remuneration) data fields are subject to transaction rules. Transaction rules depend on the movement types defined in the installation settings:
- define ns (new starter) movement code, operator code (obns) - for onboarding
- define reemploy move, oper code (obre) - for re-employments
- define ns (new starter) movement code, operator code (obns) - for onboarding
Transaction rules
The following table explains how transaction rule settings influence cost code validation.
When the transaction rule called default from previous movement is set to... | and the transaction rule called display only is set to... | EmpowerHR... |
|---|---|---|
n | n | expects a cost code on the take-on table If the cost code is split, the system expects splits on the split table |
y | n | defaults the cost code and splits from the position but overrides it if there is a non-blank code in the take-on table. If the cost code is split, the system expects splits on the split table |
y | y | defaults the cost code and splits from the position and ignores anything on the take-on tables |
n | y | determines this is not a valid combination and no cost take-on occurs |
Position and pay data fields
Employee position & pay (remuneration) data field description | Field length | Req? | EmpowerHR tag PositionAndRemuneration. | Notes |
|---|---|---|---|---|
| Position Number | 10 | y | Position | Must be a valid position number |
| Position Start Date | 9 | y | PositionStartDate | Acceptable formats: ddmmyy, ddMmmyy, ddmmccyy, or ddMmmccyy |
| Date the position was held upto (End date) | 9 | n | PositionEndDate | Acceptable formats: ddmmyy, ddMmmyy, ddmmccyy, or ddMmmccyy |
| Classification | 8 | y | Classification | If entered, this must be a valid code. This field can be left blank and default from the employee’s position. |
Cost Centre | 16 | n | CostCentre | If entered, this must be a valid code. This field can be left blank and default from the employee’s position. |
| Admin Unit (Agency / Location) | 4 | n | AdminUnit | |
| P/A or Job | 16 | n | ProgramActivityOrJobNumber | Must be a valid code |
| Section Code | 4 | n | Section | If entered, this must be a valid code. This field can be left blank and default from the employee’s position. |
| Duty Code | 4 | n | Duties | |
| Location Code | 4 | n | Location | If entered, this must be a valid code. This field can be left blank and default from the employee’s position. |
| Authority | 4 | n | Authority | |
| Employment Type | 4 | n | EmployeeType | If entered, this must be a valid code. This field can be left blank and default from the employee’s position. |
| Employment Condition | 4 | n | EmploymentCondition | If entered, this must be a valid code. This field can be left blank and default from the employee’s position. |
| Probation Period | 12 | n | ProbationPeriod | |
| Work Pattern Code | 6 | y | WorkPattern | Must be a valid code |
| Public Holiday Code | 4 | y | PublicHoliday | Must be a valid code |
| Contact Reason | 4 | n | ContractExpiryReason | If entered, this must be a valid code |
Contract Expiry Date | 9 | n | ContractExpiryDate | Acceptable formats: ddmmyy, ddMmmyy, ddmmccyy, or ddMmmccyy |
Contract Signed | 1 | n | ContractSigned | If entered, must be:
|
| User Field (4) | 8 | n | UserField4 | |
| User Field (5) | 8 | n | UserField5 | |
| Narrative (Job) | 180 | n | Narrative | |
| Class Level | 2 | y | AwardLevel | If employee is paid h (hourly), a valid classification level must be entered, otherwise leave blank |
Pay Basis | 1 | y | PayBasis | Must be one of the following:
|
| Hours Per Period | 10 | y | HoursPerPeriod | Enter the number of hours per pay period (using two decimal places) |
| Hours Per Week | 10 | y | HoursPerWeek | Enter the number of hours per week (using two decimal places) |
| FTE % | 10 | y | FtePercentage | Format = 100.00 |
| Base Salary | 10 | y* | BaseSalary | *Only enter an annual salary (using two decimal places) if pay basis is s (salary), otherwise leave blank |
| Hourly Rate | 12 | Y* | HourlyRate | *Only enter an hourly rate (using six decimal places) if pay basis is s (salary), otherwise leave blank |
| Variation % | 10 | n | VariationPercentage | |
| Variation Amount | 10 | n | VariationAmount | |
| Salary Maintain | 1 | n | SalaryMaintain | |
| Salary Barrier Level | 2 | n | SalaryBarrierLevel | |
| Increment Date | 9 | n | NextIncrementDate | Acceptable formats: ddmmyy, ddMmmyy, ddmmccyy, or ddMmmccyy |
Auto Increment Flag | 1 | y | AutoIncrement | Must be one of the following:
|
Pay By Exception Flag | 1 | y | PayByException | Must be one of the following:
|
Pay Flag | 1 | y | Pay | Must be:
|
| Pay Start Date | 9 | y | PayStartDate | Acceptable formats: ddmmyy, ddMmmyy, ddmmccyy, or ddMmmccyy |
| Narrative (Pay) | 100 | n | RemunerationNarrative |
Employee position and pay (remuneration) split cost code data field description | Field length | Req? | EmpowerHR tag CostCode. | Notes |
| Cost Centre | 16 | y | CostCentre | |
| Percentage | 2 | y | Percentage | Must be numeric and splits must total 100% |
© 2023 Fusion5. All rights reserved.