# Send reward letters to Workday

Reward letter writebacks let you send finalized reward letters from a Compensation Planning merit cycle directly to Workday. Each letter is delivered as a PDF to the employee's Worker Documents in Workday, giving you a centralized place to store and manage compensation communications alongside other employee records.

This feature requires a Workday integration connected to Pave and separate writeback credentials. Setup involves configuration in both Workday and Pave.

## Before you begin

Before you can send reward letters to Workday, you need to complete setup in your Workday tenant and have a finalized merit cycle with released reward letters in Pave.

### Workday requirements

Complete these steps in Workday before configuring the writeback in Pave:


1. **Create an Integration System User (ISU).** Create a dedicated ISU for the Pave writeback. This is separate from any ISU used for your main Workday data sync to Pave.
2. **Create an Integration System Security Group (ISSG).** Create an unconstrained ISSG and assign the ISU you created. The ISSG must have Put access under the following domain security policies:


3. **Choose a document category.** Decide which document category the reward letters should be filed under in Workday. You can use a Workday-delivered category or a custom (client-defined) category. Note the category name for use during Pave setup.
4. **Get the Staffing endpoint URL.** Locate the endpoint URL for the Staffing web service in your Workday tenant. The URL must end with a version number (for example, `https://services1.myworkday.com/ccx/service/YourTenantID/Staffing/v44.0`). Collect URLs for each environment you plan to use (sandbox, production).

### Pave requirements

* A [Workday integration connected to Pave](https://support.pave.com/en-us/articles/connect-workday-znJMNo0we6)
* A finalized merit cycle with reward letters released. For details on creating and managing reward letters, see [Reward letters](https://support.pave.com/en-us/articles/reward-letters-4KRA17kBVn)
* Integrations admin permissions in Pave

## Set up writeback credentials

The writeback uses its own credentials, separate from your main Workday connection. You configure these in the Workday integration settings in Pave.


1. Go to **Settings > Connections** and open your Workday integration.
2. Go to **Advanced Settings > Reward Letters**.
3. Enter the following:
   * **ISU Username with Workday Tenant**: Your ISU username in the format `ISU_Username@Workday_Tenant_ID`. For example, if your ISU username is "ISU_Pave" and your tenant ID is "Acme", enter `ISU_Pave@Acme`.
   * **ISU Password**: The password for the ISU you created in Workday.
   * **JSON URL**: The Staffing endpoint URL from your Workday tenant, ending with a version number (for example, `v44.0`).
4. Click **Submit**.

A confirmation message directs you back to the cycle configuration page to complete setup.

If credentials fail validation, Pave shows which field has an issue. The username must follow the `ISU_Username@Workday_Tenant_ID` format, and the URL must be a Staffing endpoint ending in a version number.

## Configure and send letters to Workday

After credentials are set up and your cycle is finalized, you can configure how letters are delivered and send them.


1. Go to **Compensation Planning** and open the finalized cycle.
2. Go to **Configurations > Reward Letters**.
3. Under **Send Letters to Workday**, click **Set up**.

If the **Set up** button is disabled, writeback credentials have not been submitted. The tooltip directs you to **Settings > Connections > Advanced Settings > Reward Letters** on your Workday integration.

### Customize the PDF file name

Choose which fields to include in the PDF file name for each employee's letter. Available fields:

* Employee ID
* Full Name
* First Name
* Last Name
* Merit Cycle Name

Select at least one field. Drag fields to reorder them, and click **Add custom text** to insert additional text between fields. A preview at the top of the section shows an example file name based on your selections (for example, `EEID001_JaneDoe.pdf`).

### Set the document category and details

* **Category** (required): Enter the Workday document category where letters should be filed. This must match the category you configured in Workday.
* **Default Workday category**: Turn this on if you are using a Workday-delivered (Workday-owned) document category rather than a custom one. Uploads fail if this toggle does not match your category type.
* **Comment** (optional): Add a comment that appears alongside the letters in each employee's Worker Documents in Workday.

### Review skipped employees

Before sending, the modal shows a warning if any employees will be skipped. Employees are skipped when they:

* Are missing a Workday Employee ID in their profile
* Could not be matched to a Workday employee record

The warning shows a count and breakdown of skip reasons, along with how many letters will be sent (for example, "5 employees will be skipped: 2 missing a Workday Employee ID, 3 couldn't be matched to a Workday employee. 245 of 250 letters will be sent.").

### Send letters

Click **Send to Workday** to begin the upload. A confirmation dialog warns that this action sends letters to all employees with enabled and visible letters and cannot be undone.

Letters are sent in batches. The upload may take several minutes depending on the number of employees.

## Monitor upload status

After sending, the cycle configuration page shows the upload status under **Send Letters to Workday**:

If the upload takes longer than expected, a message appears prompting you to contact the support team.

## Resending letters

If you update reward letters after the initial send (for example, correcting a template error), you can resend them. The **Set up** button on the cycle configuration page changes to **Resend** after the first upload.

When you resend, the updated letter replaces the previous version in Workday. The old file is overwritten, not duplicated.

After the first upload, the PDF file name structure and document category are locked to prevent duplicate uploads under different names. If you need to change these settings, click **Reset config** in the setup modal to unlock them.

## Things to know

* **Only released letters from finalized cycles are sent.** Reward letter visibility must be set to "released" for letters to be included. Letters that have not been released are not sent to Workday.
* **Letters are sent for the entire cycle, not individual employees.** You cannot select specific employees to include. All eligible employees with released letters are included in the upload.
* **Employees without a Workday Employee ID are skipped.** If an employee cannot be matched to a Workday record, their letter is not sent. The setup modal shows which employees will be skipped before you confirm.
* **Resending replaces the previous letter.** The old file in Workday is overwritten by the new version. Letters are not duplicated.
* **Configuration locks after the first send.** The PDF file name structure and document category cannot be changed after the first upload without resetting the configuration.
* **Writeback credentials are separate from your main Workday connection.** Even if you already have Workday connected to Pave for data sync, you need to set up additional ISU credentials specifically for the writeback feature.

Send reward letters to Workday

Connect ADP

Connect BambooHR

Connect Dayforce

Connect Deel

Connect Gusto

Connect HiBob

Connect Workday

Connect Namely

Connect Paylocity

Connect Personio

Connect Rippling

Connect UKG Pro

Connect CharlieHR

Connect Humaans

Connect Justworks

Connect Sapling

Connect SAP SuccessFactors

Connect TriNet

Connect Zenefits

HRIS Integrations

Connect Carta

Connect ComputerShare

Connect Shareworks

Connect E*Trade

Connect Fidelity

Connect Global Shares

Connect Pulley

Connect Schwab

Connect Ledgy

EMS integrations

Connect Culture Amp

Connect Workday Performance

Performance integrations

Connect Ashby

Connect Greenhouse

Connect Lever

Connect Workday ATS

ATS integrations

Manage your connections

Upload custom reports (historical pay, benefits, and original grant value)

Pave API

Integrations

Configure Team View

Team View

Configurations overview

Cycle access permissions

Overview

Employee eligibility

Approval chains

Planning windows

Budgets

Recommendation logic

Adding non-integration data to your cycle

Reward letters

Snapshot cycle data

Cycle Setup

Columns

OTE planning

Writing formulas with Handlebars

Hourly and monthly pay

Columns and Formulas

Using the planner worksheet

Using the employee detail view

Cycle Progress dashboard

Budgets dashboard

Cycle Outcomes dashboard

Approval Statuses 

Worksheet Experience

Overview of smart features in compensation planning

Peer Comparison

Smart Flags

Priority Sort

Compensation Outliers

Manager Compression Flag

Vesting Drop Flag

Flags and Insights

Compensation Planning

Grades

Setting up Company Job Architecture

Company Job Architecture

Job Architecture 101

Pay Zone Manager

Step 1: Build Foundation

Generate Bands from Market Data

Editing Bands

Calculated Columns

Bands Set Audit Log

Bulk & Manually Associate Market Data to Bands

Employee Distribution in Bands

How to duplicate band sets

Managing & Reordering Calculated Columns

Unmatched Employees

View changes

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

Manually Create New Band Sets

Band Sets

Upload/Download Bands

Step 3: Update Ranges

Advanced Filters

Compare Bands

Generate Bands for New Jobs in Your Job Architecture

Relative Permissions

Ongoing Management & Analysis

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

Survey aging

Step 2: Benchmarking

Market Pricing

Create an account and log in

Set up single sign-on (SSO)

Account setup

Configure role permissions

Create and manage roles

Roles and permissions

Impersonate a user

Manage notifications

Complete your company profile

Manage company settings

Platform settings

Account & Permissions

June 2026 data release

Create and manage Peer Groups in Market Data

Create and manage Market Data reports

Equity data benchmarking

Explore data composition

Explore the Pave job catalog

Filter Market Data benchmarks

Get started with Market Data

Share Market Data externally

Market Data Benchmarks (Features & Workflows)

Understand Calculated Benchmarks

Understand Consistency Labels

Understand job matching

Understand Market Data methodology

Understand Job Levels

Market Data Methodology 

Explore Global Location Insights

Explore Equity Practices

Other Pave Market Data Products 

Market Data FAQ

FAQ's

Upgrade to Market Data Pro

Upgrades & Pricing 

Market Data

Customize branding in Total Rewards and Visual Offer Letter

Branding and customization

Configure benefits

Configure equity settings

Customize compensation display

Equity slider and valuation options

Compensation configuration

Future modeling overview

Configure future grant modeling

Configure compensation simulator

Future modeling

Set up Learning Hub content

Learning Hub

Total Rewards & Visual Offer Letter

Security at Pave

Security General Information

 Do you provide encrypted data storage of at least 256 AES?

Does Pave provide activity logs if requested? 

Will Pave connect a customer's data to any other systems?

Does Pave have a data retention policy? How long will the customer's data be kept in Pave's system?

What is Pave's threat detection strategy?

How do customers receive security alerts and/or security advisories?

Is Pave GDPR compliant?

What specific data is shared with Pave?

Can I please have your SOC 2 report?

Can people see our company name if we complete our integrations or is that also de-identified?

Can we complete the integration without sharing PII like employee name and email? 

How can I access Pave's DPA?

Are your data transmissions encrypted with at least TLS 1.2?

Security FAQs

Security

Guide

Pave

<p>Search for answers or submit a support ticket, right from the search bar.</p>