When manually creating a new band set, you must first define which HRIS fields you'll be using to match employees to Bands within Pave and your company’s pay types. Once the band set is configured, Pave will generate a CSV template you can fill out with your bands, and you can then re-upload the completed CSV into the band set.

When manually creating a new band set, you must first define which HRIS fields you'll be using to match employees to Bands within Pave and your company’s pay types. Once the band set is configured, Pave will generate a CSV template you can fill out with your bands, and you can then re-upload the completed CSV into the band set. 

### Steps:


1. Click on the **Market Pricing** button in the left tool bar.
    ![](https://support.pave.com/servlet/rtaImage?eid=ka0TV0000001fKT&feoid=00NUn00000C06g9&refid=0EMTV00000EnF98) 
2. Click **Import existing compensation bands:** ![](https://support.pave.com/servlet/rtaImage?eid=ka0TV0000001fKT&feoid=00NUn00000C06g9&refid=0EMTV00000EnG6n) 
3. Choose the compensation types. You will be able to preview the fields Pave requires for each job and its corresponding band. You can view these required fields here by expanding the table preview:
    ![](https://support.pave.com/servlet/rtaImage?eid=ka0TV0000001fKT&feoid=00NUn00000C06g9&refid=0EMTV00000EnGDF) 

   The following combinations are allowed.
   * Family and Level (e.g. Engineering, P4)
   * Title and Level (e.g. Software Engineer, P5)
   * Title (e.g. Senior Software Engineer)
   * Job Code (e.g. SWE-13A)

   ### Location-Based Pay:

   Admins then need to select whether or not the company uses location-based pay. If a company uses location-based pay practices, Pave will use the `metro` field in the HRIS to match employees to their corresponding job (and its band). Companies may often define `metro` with cities or tiers.

   
   
   Additionally, if a company selects that they use location-based pay, the CSV will be populated with the Payzone column. This payzone column can be filled with the same values as the `metro` field if desired, and can be used to set granular access controls. For example, a recruiter for the SF office may have permissions set to only view Software Engineering bands in Payzone: San Francisco.

   
   
   Once an option is selected, the table preview on the right will populate with values found in the company’s HRIS for that specific field(s). For example, if Title and Level is selected, all unique title and level combinations from your HRIS will be pre-populated in the CSV. This allows the admin to easily fill out the CSV with all the bands for each job and ensure all employees have a matching job (and Band) in Pave.

   If no values are populated for a selected option, either the integration isn’t connected or values do not exist for those fields in the HRIS.

| **Compensation Value** | **Definition** |
|----|----|
| **Base Pay** | Base pay is the guaranteed compensation for an employee. This does not include equity, variable pay or bonuses. |
| **Total Pay** | Total pay is the sum of base and target variable ranges. Some customers may choose to submit total pay rather than separate base and target variable ranges. |
| **Total Equity** | Refers to the value of all the equity grants for an employee. Can also be utilized to track the refresher target for the band. |
| **New Hire Equity** | Refers to the value of the first grant received by an employee at the time that it was received. |
| **Shares and Value (for equity)** | Shares is the number of shares given to employees within this pay range. \n   Customers can also choose to calculate equity by total equity value which would encapsulate number of shares multiplied by share price. \n   Customers can only provide either equity shares or equity values. \n   When used in Comp Planner, Pave will automatically calculate the other column based off of the provided share price. |
| **Variable Pay** | Variable is compensation awarded to employees based on performance in addition to base pay.  |
| **Target Variable Pay Percentage** | Percentage of base pay used to define the target variable amount. This value is used in Compensation Planner. |
4. Name the Band Set and generate the CSV:
    ![](https://support.pave.com/servlet/rtaImage?eid=ka0TV0000001fKT&feoid=00NUn00000C06g9&refid=0EMTV00000EnGBe) 
5. Download your Pave generated CSV template: 
    ![](https://support.pave.com/servlet/rtaImage?eid=ka0TV0000001fKT&feoid=00NUn00000C06g9&refid=0EMTV00000EnGGT) 
   
   The band set configurations can be modified before the CSV is uploaded. This may be the case if an admin realizes they use only base pay min and max rather than base pay min, target and max, for example.
6. Once the CSV Band template has been filled out, re-upload the completed CSV into the band set within Pave:
    ![](https://support.pave.com/servlet/rtaImage?eid=ka0TV0000001fKT&feoid=00NUn00000C06g9&refid=0EMTV00000EnGI5) 
   
   Only Band Admins will be able to view the HRIS matchers in the Band Manager once the CSV is successfully uploaded. Users with the Band Viewer permission will only be able to view the required job identifier fields and relevant pay ranges on the band.

   ### Job Identifiers

   For each row in the uploaded CSV, the combination of `Function`- `Ladder` - `Ladder Rank` - `Payzone` (payzone only if using location-based pay) must be unique as each job should have its own unique set of identifiers:

    ![](https://support.pave.com/servlet/rtaImage?eid=ka0TV0000001fKT&feoid=00NUn00000C06g9&refid=0EMTV00000EnGLJ)

 ![](https://support.pave.com/servlet/rtaImage?eid=ka0TV0000001fKT&feoid=00NUn00000C06g9&refid=0EMTV00000EnGOX) 7. Fix any errors that you may encounter. Please contact our Support team at [support@pave.com](mailto:support@pave.com) if you have any questions!




Manually Create New Band Sets

Pay Types: Calculated TDC, Annual Equity, and Refresh Equity

Band Sets

Employee Distribution in Bands

Editing Bands

View changes

Upload/Download Bands

Unmatched Employees

Calculated Columns

Managing & Reordering Calculated Columns

How to duplicate band sets

Survey aging

Edit and apply benchmarks

Set weights and logic

Map data sources to jobs

Supported survey providers

Manage Pave data sources

Manage survey data sources

Benchmarks overview

Step 2: Benchmarking

Bands Set Audit Log

Job Architecture 101

Pay Zone Manager

Grades

Setting up Company Job Architecture

Company Job Architecture

Step 1: Build Foundation

Generate Bands from Market Data

Bulk & Manually Associate Market Data to Bands

Step 3: Update Ranges

Generate Bands for New Jobs in Your Job Architecture

Compare Bands

Relative Permissions

Advanced Filters

Ongoing Management & Analysis

Market Pricing

Market Data Connections Set up

Market Data Connections Overview

Integrations 101

Integrations

Adding Columns

Team View Overview

Team View Column Configuration

Team View Customizations

Re-ordering Columns

Deleting Columns

Team View Settings

Team View

Comp Planner Configurations Overview

Compensation Planner 101

Getting Started - Compensation Planner

Compensation Planner FAQs

Cycle Specific Permissions

Employee Eligibility

Step 1: Initial Cycle Setup

First-Class Columns

Using Handlebars Formula for Calculated Columns

Columns

Step 2: Column Configuration

OTE Planning Configuration Guide

What is OTE Planning?

Step 3: OTE Planning

Am I able to update or change approval chains during a cycle?

Updating Approval Chains

Compensation Cycle Data Upload

Step 4: Data Management

How can I configure market adjustment recommendations for employees?

How can I configure variable raise recommendations for employees?

Recommendation Logic

What are Recommendations?

Step 5: Recommendation Logic

Budgets

Budget Dashboard

Top Down Budgets: In-app Configurations

Step 6: Budget Confirmation

Planning Windows Setup Guide

Planning Windows Overview

Monthly & Hourly Pay

Employee Compensation History Popout

UI Toggles

Filtering & Sorting

Approval Statuses

Step 7: Planner Experience

Smart Flags

Compensation Outliers

Manager Compression Flag

Vesting Drop Flag

Step 8: Controls & Governance

Peers Overview

Cycle Outcomes

Value Rounding in Compensation Planning

In App Reward Letter Editor

Reward Letters

Peers Configuration Guide

Cycle Progress Dashboard Overview

Other Cycle Actions

 Compensation Planner

Logging In

Custom Role Creation Guide

Creating an Account

How to add a colleague to Pave’s Market Data Platform

Market Data Role Management

Why does it matter to get levels and role families right?

SSO Configuration Guide

Account Setup

Contact Us

How much does Pave Market Data access cost?

How does Pave Work?

Intro to Pave

Pave 101

Compensation Philosophy

Total Compensation

Compensation 101

The Stock Option Lifecycle

ISO Tax Implications

The Basics of Stock Options

The Confusing AMT (Alternative Minimum Tax)

ISO Strategies

An Overview of How Stock Options Work

Equity 101

Account Creation Troubleshooting and FAQs

How to Benchmark Executive Compensation

Login Troubleshooting and FAQ

How does company size affect which department, job family and job level I should choose?

How does Pave determine a role level and role family?

What are Job Levels, Departments and Job Families? Why are they important?

Troubleshooting Rippling Zero Records Error

What Market Data Connections does Pave currently support?

FAQs

Getting Started

Option Driver Deprecation FAQs

Option Driver

Option Impact Deprecation FAQs

Option Impact

Option Impact & Option Driver

Executive Reporting Dashboard

Cycle Monitoring and Reporting

Building Market-Based Compensation Bands

Employee Groups

Cycle Configuration

How does Recommendation Logic work?

Am I able to change another user’s permissions or login credentials while impersonating?