In 2019, Cornerstone will remove the option to load Compensation data via the Data Load Wizard (DLW). The exact timing of this is yet to be determined but will be announced in advance to give clients time to plan.
- To load Compensation data, clients will need to use the new Edge Import Employee Salary Load tool which was made available in the August '18 Release to clients with Compensation or Cornerstone HR and Data Load Wizard (DLW).
If you are uploading new data to the system, first select a template by clicking the Template link in the lower-left corner. This ensures the proper data is included and that it is in the proper format. In the template, columns that are red are required. See Load Data - Select Data Load Template.
To upload a file of data
- Click the button and locate the file.
- You can only upload the following file types: .xls, .xlsx, .csv, .txt.
- Once the file is selected, click the button. An Upload File pop-up appears with different options depending on the type of file that is uploaded.
- Excel File (.xls, .xlsx). Select Worksheet (Excel files only) - Only one worksheet can be uploaded at a time, so if the Excel file has multiple worksheets, you must select the worksheet that you are uploading.
- Text, Comma, or Pipe Separated File (.txt, .csv). Select Delimiter (Tab, Comma, or Pipe Separated files only) - Select what delimiter (e.g., tab, comma, pipe) is used to separate records within the file. This enables the system to properly extract the data from the file.
-
- Select Template - If you used a template to create the file, select the appropriate template. If no template is used, select the "No template used" option. If you have used the Data Load Wizard in the past and saved a template for this file type, that template is available here.
- My File has titles/headers - Data files should have titles or headers for each column of data. If the file you uploaded does not have titles or headers, deselect this option. Deselecting this option modifies the next step in the review process.
- After selecting the appropriate options, click . The file is uploaded and listed on the page.
If this is the wrong file or the wrong worksheet within the file, you can delete it by clicking the Remove icon 
to the left of the file title and upload another file. Alternatively, you can browse and upload a new file. When the correct file is uploaded, click to proceed to the Review step. See Load Compensation Data - Step 4 - Review.
Employee Salary Data Use Cases
Use Case 1: User loads records or updates existing records
Data before Data Load
| User ID | Wage Type | Labor Hours | Current Salary | Effective Date | Currency ID |
|---|---|---|---|---|---|
| 333 | Annual | 2000 | 80000 | 05/01/2013 | EUR |
| 444 | Annual | 2080 | 100000 | 03/01/2013 | USD |
Data Load
| User ID | Wage Type | Labor Hours | Current Salary | Effective Date | Currency ID |
|---|---|---|---|---|---|
| 111 | Annual | <blank> | 50000 | 07/01/2013 | USD |
| 222 | Hourly | 1080 | 80000 | 06/10/2013 | USD |
| 333 | Annual | 2000 | 100000 | 05/01/2013 | EUR |
| 444 | Annual | 2500 | 150000 | 04/01/2013 | EUR |
Data after Data Load
| User ID | Wage Type | Labor Hours | Current Salary | Effective Date | Currency ID |
|---|---|---|---|---|---|
| 111 | Annual | <blank> | 50000 | 07/01/2013 | USD |
| 222 | Hourly | 1080 | 80000 | 06/10/2013 | USD |
| 333 | Annual | 2000 | 100000 | 05/01/2013 | EUR |
| 444 | Annual | 2080 | 100000 | 03/01/2013 | USD |
| 444 | Annual | 2500 | 150000 | 04/01/2013 | EUR |
In this example, the following occurred:
- User ID 111 and 222 were added as new records.
- User ID 333 was updated because a matching combination of User ID and Effective Date existed in the system.
- A second record was added for User ID 444 because the existing Effective Date for User ID 444 did not match the Effective Date that was loaded.
Use Case 2: Labor Hours is blank for an Hourly Wage Type
Data Load
| User ID | Wage Type | Labor Hours | Current Salary | Effective Date | Currency ID |
|---|---|---|---|---|---|
| 123 | Hourly | <blank> | 20000 | 07/01/2013 | USD |
Data after Data Load
| User ID | Wage Type | Labor Hours | Current Salary | Effective Date | Currency ID |
|---|---|---|---|---|---|
| 123 | Hourly | 2080 | 20000 | 07/01/2013 | USD |
In this example, the following occurred:
- User ID 123 was added as a new record. Because the Labor Hours value was left blank and the Wage Type was set to Hourly, the Labor Hours value was set to 2080, which is the default value.
Use Case 3: User updates existing record, and Labor Hours is blank for an Hourly Wage Type
Data before Data Load
| User ID | Wage Type | Labor Hours | Current Salary | Effective Date | Currency ID |
|---|---|---|---|---|---|
| 345 | Hourly | 1040 | 40000 | 07/01/2013 | USD |
Data Load
| User ID | Wage Type | Labor Hours | Current Salary | Effective Date | Currency ID |
|---|---|---|---|---|---|
| 345 | Hourly | <blank> | 50000 | 07/01/2013 | USD |
Data after Data Load
| User ID | Wage Type | Labor Hours | Current Salary | Effective Date | Currency ID |
|---|---|---|---|---|---|
| 345 | Hourly | 2080 | 50000 | 07/01/2013 | USD |
In this example, the following occurred:
- User ID 345 was updated because a matching combination of User ID and Effective Date existed in the system. Because the Labor Hours value was left blank and the Wage Type was set to Hourly, the Labor Hours value was set to 2080, which is the default value.
Use Case 4: User updates existing record and Labor Hours is unmapped
Data before Data Load
| User ID | Wage Type | Labor Hours | Current Salary | Effective Date | Currency ID |
|---|---|---|---|---|---|
| 798 | Hourly | 1040 | 75000 | 07/01/2013 | USD |
Data Load
| User ID | Wage Type | Current Salary | Effective Date | Currency ID |
|---|---|---|---|---|
| 798 | Hourly | 100000 | 07/01/2013 | USD |
Data after Data Load
| User ID | Wage Type | Labor Hours | Current Salary | Effective Date | Currency ID |
|---|---|---|---|---|---|
| 798 | Hourly | 1040 | 100000 | 07/01/2013 | USD |
In this example, the following occurred:
- User ID 798 was updated because a matching combination of User ID and Effective Date existed in the system. Because the Labor Hours value was unmapped in the data load, the Labor Hours value was unaffected by the data load.
Individual Targets Data Use Cases
Use Case 1: User loads records or updates existing records
Data before Data Load
| User ID | Target Type | Target Name | Fixed or Percentage | Amount | Target Date |
|---|---|---|---|---|---|
| 123 | Bonus | Holiday | Percentage | 25 | 12/25/2013 |
| 567 | Bonus | Quarterly | Fixed | 7000 | 06/25/2013 |
| 567 | Equity | LTI | Fixed | 1500 | 08/10/2013 |
Data Load
| User ID | Target Type | Target Name | Fixed or Percentage | Amount | Target Date |
|---|---|---|---|---|---|
| 123 | Bonus | Quarterly | Fixed | 5000 | 06/25/2013 |
| 123 | Equity | RSA | Percentage | 20 | 07/10/2013 |
| 123 | Bonus | Holiday | Fixed | 1500 | 12/25/2013 |
| 567 | Bonus | Quarterly | Fixed | 5000 | 06/25/2013 |
| 567 | Equity | NQO | Percentage | 30 | 07/10/2013 |
Data after Data Load
| User ID | Target Type | Target Name | Fixed or Percentage | Amount | Target Date |
|---|---|---|---|---|---|
| 123 | Bonus | Quarterly | Fixed | 5000 | 06/25/2013 |
| 123 | Equity | RSA | Percentage | 20 | 07/10/2013 |
| 123 | Bonus | Holiday | Fixed | 1500 | 12/25/2013 |
| 567 | Bonus | Quarterly | Fixed | 5000 | 06/25/2013 |
| 567 | Equity | NQO | Percentage | 30 | 07/10/2013 |
| 567 | Equity | LTI | Fixed | 1500 | 08/10/2013 |
In this example, the following occurred:
- For User ID 123, the Bonus target named Holiday was updated because a matching combination of User ID, Target Type, Target Name, and Target Date existed in the system.
- For User ID 567, the Bonus target named Quarterly was updated because a matching combination of User ID, Target Type, Target Name, and Target Date existed in the system.
- For User ID 567, the Equity target named LTI was unchanged.
- A second and third record was added for User ID 123 because the existing Target Type, Target Name, and Target Date for User ID 123 did not match the Target Type, Target Name, and Target Date that was loaded.
- A third record was added for User ID 567 because the existing Target Type, Target Name, and Target Date for User ID 567 did not match the Target Type, Target Name, and Target Date that was loaded.
Salary Structure Data Use Cases
Use Case 1: User loads records or updates existing records
Data before Data Load
Data Load
| Primary OU | Secondary OU | Wage Type | Minimum Value | Maximum Value | Market Value | Annualized Range |
|---|---|---|---|---|---|---|
| 111 | 999 | Annual | 10000 | 50000 | 45000 | <blank> |
| 222 | 888 | Hourly | 30000 | 70000 | 65000 | TRUE |
| 333 | 777 | Annual | 40000 | 60000 | 50000 | <blank> |
| 444 | 666 | Hourly | 50 | 70 | 65 | FALSE |
| 444 | 555 | Annual | 100000 | 200000 | 150000 | <blank> |
Data after Data Load
| Primary OU | Secondary OU | Wage Type | Minimum Value | Maximum Value | Market Value | Annualized Range |
|---|---|---|---|---|---|---|
| 111 | 999 | Annual | 10000 | 50000 | 45000 | <blank> |
| 111 | 999 | Hourly | 20000 | 40000 | 40000 | FALSE |
| 222 | 888 | Hourly | 30000 | 70000 | 65000 | TRUE |
| 333 | 777 | Annual | 40000 | 60000 | 50000 | FALSE |
| 444 | <blank> | Hourly | 45 | 80 | 60 | TRUE |
| 444 | 666 | Hourly | 50 | 70 | 65 | FALSE |
| 444 | 555 | Annual | 100000 | 200000 | 150000 | FALSE |
In this example, the following occurred:
- Primary OU 222 was added as a new record.
- Primary OU 333 was updated because a matching combination of Primary OU, Secondary OU, and Wage Type existed in the system.
- A second record was added for Primary OU 111 because the existing Wage Type for Primary OU 111 did not match the Wage Type that was loaded.
- A second and third record was added for Primary OU 444 because the existing Secondary OU and Wage Type for Primary OU 444 did not match the Wage Type that was loaded.