How imports create job architecture

When your employee file includes job information, the import can build your structure for you, so you don't have to set everything up by hand first.

What can be created

• Organisation units: from the Organization Unit column, when Create missing org units is on.

• Positions: from Position Title or Position ID, when Create missing positions is on.

• Job families, career paths, job levels and job grades: from the matching columns (Job Family, Career Path / Track, Job Level Code or Name, Job Grade).

A grade column is optional. If you don't need grades, leave the column out and none are created.

How grades are read

• Whole numbers are grades: 6 is grade 6.

• Decimals are sub-grades: 6.1 sits under grade 6. If the file only has 6.1, grade 6 is created as well.

• If your file skips grades, for example 3 and 6, the missing grades in between are filled in so the ladder has no holes.

• If the lowest and highest grades in your file are more than 30 apart, nothing is filled in: only the grades in the file are created, because a stray value such as 90 is more likely an ID than a grade. Grades above 100 are rejected.

Good to know

• You can also import each structure on its own: positions, pay bands, org units, job families, career paths and job grades each have their own import. See Other imports.

• If your organisation uses entities, an import for a single entity can't create job levels or job families, because those belong to the group.

• To set up levels and grades without a file, see Setting up job architecture with the wizard.

Related articles

• Importing employees from a CSV file

• How Evenpay structures jobs

• Managing grades and career paths

• Other imports