Salary structures

Salary structures identify ranges of pay for jobs or a family of jobs. You assign these ranges to jobs, positions, or work assignments.

Work assignments and positions that use salary structures always use the version in effect when the salary structure is invoked. A salary structure version remains in effect until a later version is created. You can update salary structures without changing their version date, or to have a record of rate changes, you can create a new version to update the rates for a salary structure. When you create a new version, you can copy the active iteration of the last version as is and then apply changes to the rates as needed, or you can copy the last version and concurrently apply an automatic percent or flat amount increase to each rate in the active iterations.

You can add a grade to an existing salary structure, but it must be added to the end of the salary structure. You cannot insert a grade in between grades.

Salary structures let you complete these tasks:

  • See where a resource’s salary lies within the range for their job

  • Create "what if" modeling scenarios for your organization's budgeting and planning processes

Traditional salary structures include three zones for storing salary range amounts for a given job; for example, Minimum, Midpoint and Maximum. Non-traditional salary structures can contain one, two, four, five, or more zones for storing salary range amounts.

Note: 

To accommodate geographical differentials in pay ranges work assignments, you can display up to five zones. If more than five zones exist, only the minimum, maximum, and compa zones are shown.

To accommodate modeling, use a status field that indicates whether the structure is active. You can create multiple iterations of the same salary structure for the same effective date and geographic differential.

You can use different salary structures to accommodate geographical differentials in pay.