Standard position movement data file format

Here are the fields for the desktop bulk-upload of standard position movements. For the upload procedure, see Crossboard position/temporary movement data. For the web services equivalent, see Standard position movements fields in the web services section.

Position movements file

One row per movement, 47 columns.
  • The fields are subject to validation. 
Column Position movements field description Field length Req? Notes
A Function Code 4 y Acceptable codes are:
  • cond
  • auto
  • ploy
  • prom
  • salc
  • tran
B Movement Code 4 n Must be a valid code.
C Employee Code 10 y Must be a valid code.
D Old position number 10 n* *For an employee with:
  • single employment, if the old position number is not provided, EmpowerHR defaults to Employment
  • multiple employments, if the old position number is not provided, an error occurs
E Employment 3 n* *If employment is not provided, EmpowerHR defaults from old position. Employment is used to refer to the old position employment, not for generating a new employment.
F New movement/change date 9 y Format: ddmmyy, ddMmmyy, ddmmccyy or ddMmmccyy
G New position number 10 n* *If the new position number is not provided, EmpowerHR uses the old position.
H End date 9 n You can enter:
  • the end date for the movement, or
  • 99999999, if the movement does not have an end date (open-ended)
I Classification/Award code 8 y If entered, this must be a valid code.

This field can be left blank and default from the position if set to do so in the transaction rule for the movement code used.

J Cost Code 16 n If entered, this must be a valid code.

This field can be left blank and default from the position if set to do so in the transaction rule for the movement code used.

K Admin unit 4 n  
L Program Activity or Job 16 n  
M Section code 4 n If entered, this must be a valid code.

This field can be left blank and default from the position if set to do so in the transaction rule for the movement code used.

N Duty code 4 n  
O Location code 4 n If entered, this must be a valid code.

This field can be left blank and default from the position if set to do so in the transaction rule for the movement code used.

P Authorising officer 4 n  
Q Employment type 4 n If entered, this must be a valid code.

This field can be left blank and default from the position if set to do so in the transaction rule for the movement code used.

R Employment condition 4 n If entered, this must be a valid code.

This field can be left blank and default from the position if set to do so in the transaction rule for the movement code used.

S Probation period 12 n  
T Work pattern code 6 y Must be a valid code
U Public holiday code 4 y Must be a valid code
V Contract reason 4 n If the transaction rule defol is set to:
  • n and the take-on file has blank data for the column, then EmpowerHR creates a blank Contract Reason for the new movement record, otherwise EmpowerHR populates the field with non-blank data from the take-on file.
  • y and the take-on file has blank data for the column, then EmpowerHR populates the new movement record with the previous movement's Contract Reason data, otherwise EmpowerHR populates the field with non-blank data from the take-on file.
  • y and you still want to make the field blank (that is, not populate it from the previous movement's data), then set the column in the take-on file to 9999.
W Contract expiry date 9 n You can enter the contract expiry date for the movement using the format: ddmmyy, ddMmmyy, ddMmmccyy, ddMmmccyy, or If the transaction rule defol is set to:
  • n and the take-on file has blank data for the column, then EmpowerHR creates a blank Contract Expiry Date (open-ended date) for the new movement record, otherwise EmpowerHR populates the field with non-blank data from the take-on file.
  • y and the take-on file has blank data for the column, then EmpowerHR populates the new movement record with the previous movement's Contract Expiry Date data, otherwise EmpowerHR populates the field with non-blank data from the take-on file.
  • y and you still want to make the field blank (that is, an open-ended date), then set the column in the take-on file to 99999999
X Contract signed 1 n  
Y User field 4 8 n  
Z User field 5 8 n  
AA User narrative 180 n  
AB Award level 2 y* *If hourly paid, then enter level or leave blank
AC Pay basis 1 y Must be one of the following:
  • h (hourly) or
  • s (salary)
AD Hours per period 10 y Two decimal places
AE Hours per week 10 y Two decimal places
AF FTE % 10 y  
AG Base salary 10 n  
AH Hourly rate 12 n  
AI Variation % 10 n  
AJ Variation amount 10 n  
AK Salary Maintain? 1 n  
AL Salary barrier level 2 n  
AM Next Increment date 9 n Format: ddmmyy, ddMmmyy, ddmmccyy or ddMmmccyy
AN Auto increment 1 y Must be one of the following:
  • y
  • n
  • d (school functionality)
AO Pay by exception 1 y Must be one of the following:
  • y
  • n
  • r (school functionality)
AP Pay 1 y Must be:
  • y (yes) or
  • n (no)
AQ Pay start date 9 y Format: ddmmyy, ddMmmyy, ddmmccyy or ddMmmccyy
AR Employee remuneration narrative 100 n  
AS Salary Package? 1 n  
AT Schedule Code 6 n  
AU Deleted Flag 1 n Must be blank


Split cost codes file

Use this file only when your movements have split cost centres, and tick Split Cost Centres Load on the Crossboarding Initiation screen. One row per cost code in the split.

Column

Position movements field description

Field length

Req?

Notes

A
Function Code
 4 y Acceptable codes:
  • cond
  • auto
  • ploy
  • prom
  • salc
  • tran
B
Movement Code  4 n For position movement only
C
Position Number10n

D
Employment Number3n
E
Employee Code10y
F
Cost Code16y
G
Split percentage2yMust be numeric and splits must total 100%



Next topic

Overtime code fields




 

© 2023 Fusion5. All rights reserved.