The Future Salary Schedules import file format is .xml, .exml, .csv, .txt, or .unl.
-
The Hourly or Salary Indicator must be H (hourly) or S (salaried).
-
For salaried schedules (Hourly or Salary Indicator = S), Contract Days per Year and Hours Worked per Day must each be greater than 0.
-
Steps must be sequential, starting from 1 with no gaps, and must not exceed 99. If the Step column is omitted from the file, the system assigns step numbers automatically based on row order.
-
If future changes for the same salary schedule code already exist, the import will fail with an error. The existing future-change record must be deleted before re-importing.
-
If the salary schedule code already exists in the current Salary Schedule table, a warning is generated, but the import can proceed. The existing schedule will be replaced when the imported future changes are posted.
The following table shows the data columns, names, descriptions, destination database fields, and whether the field is required in the Future Salary Schedules .csv import file.
|
Column |
Name |
Description |
Destination Database Field (table.field) |
Required or Optional |
|---|---|---|---|---|
|
A |
Control Number |
Unique identifier for the import batch. The limit is eight characters. The value must be the same across all rows. |
ischedule.batch_no |
Required |
|
B |
Contract Days |
The number of contract days worked per year. Must be greater than 0 for salaried schedules. The value must be the same across all rows. The wizard sets this value to 0 by default on the Static Column Value Mapping page. For salaried schedules, override the default with a value greater than 0. |
ischedule.days_worked |
Required |
|
C |
Schedule Title |
The description of the salary schedule. The limit is 20 characters. The value must be the same across all rows. |
ischedule.desc_x |
Required |
|
D |
Effective Date |
The date the salary schedule takes effect. The value must be the same across all rows. |
ischedule.eff_date |
Required |
|
E |
Hours Worked Per Day |
The number of hours worked per day. Must be greater than 0 for salaried schedules. The value must be the same across all rows. The wizard sets this value to 0 by default on the Static Column Value Mapping page. For salaried schedules, override the default with a value greater than 0. |
ischedule.hours_day |
Required |
|
F |
Hourly or Salary Indicator |
Indicates whether the schedule is hourly or salaried. Valid values:
The value must be the same across all rows. |
ischedule.hs_flag |
Required |
|
G - DA |
Range 01 - Range 99 |
Salary amount for each range at the step defined in that row. Include only the ranges needed. Omitted ranges default to 0. The column heading used in the file becomes the range description in the salary schedule; headings longer than eight characters are truncated. |
ischedule.range_01 - ischedule.range_99 |
Optional |
|
DB |
Schedule |
The three-character code that identifies the salary schedule. The value must be the same across all rows. |
ischedule.schedule |
Required |
|
DC |
Step |
The step number for the row. Each row must represent a unique step. Steps must be sequential, starting from 1 with no gaps, up to a maximum of 99. If omitted, the system assigns step numbers automatically based on row order. |
ischedule.step |
Optional |
Example CSV Layout (3 steps, 2 ranges)
Control Number,Effective Date,Schedule,Title,H/S,Days,Hours/Day,Step,Range 01,Range 02
SA001,07/01/2026,TCH,TEACHER SALARY,S,185,7.50,1,42000.00,44000.00
SA001,07/01/2026,TCH,TEACHER SALARY,S,185,7.50,2,43500.00,45500.00
SA001,07/01/2026,TCH,TEACHER SALARY,S,185,7.50,3,45000.00,47000.00
The constant fields (SA001, 07/01/2026, TCH, etc.) can alternatively be omitted from the file entirely and entered once on the Static Column Value Mapping page of the wizard.