A compensation review cycle is far easier to run well in the weeks before it opens than in the weeks after. Once managers are working in their worksheets, every configuration problem becomes a live ticket, and every fix risks changing numbers someone has already seen. 

This checklist walks through the seven areas we review most often ahead of a Workday compensation cycle: process dates, eligibility, matrix and guidelines, pools and budgets, multicurrency, security and statements. It is written for HR, Finance and Enterprise Applications leaders who want to know what to check, in what order, and why each item matters. 

Why Review Before the Cycle Opens 

Most of the compensation configuration in a Workday tenant was built once, at go-live, for the organisation as it looked then. Reorganisations, new entities, new worker types and new currencies change the inputs, but nothing forces the configuration to be revisited. The result is rarely an error message. It is a manager who cannot see a worksheet, a pool that does not reconcile, or a statement that disagrees with a conversation. 

A short, structured review before the cycle opens catches most of these while they are still cheap to fix. Where you can, run it in a sandbox or preview tenant with realistic data, so that nothing you change touches live numbers. 

1. Process Dates: Snapshot, Effective and Visibility 

A compensation review process carries several dates, and each one controls something different. The compensation snapshot date is the date Workday uses to determine which employees are eligible for inclusion, and Workday can include employees in eligibility waiting periods as of that date, depending on plan setup. The organisation snapshot date sets the hierarchy and which organisations are assigned a planner. It does not determine security role assignments, and organisations inactivated after it are removed from the hierarchy. The effective date also drives eligibility for proposed target changes, and the employee visibility date, where used, hides pay-related data from employees until it passes. 

Check that each date reflects how the business actually works this year, rather than being copied forward from the last cycle. Then test a handful of recent movers. Anyone who changed role, organisation or location close to a snapshot date is where date problems show up first. 

2. Eligibility Rules and Plan Profiles 

Eligibility is evaluated for each compensation component, using rules built from fields such as organisation, job profile, location and position. Three behaviours catch teams out. 

First, when a worker qualifies for more than one plan profile, the first qualifying profile is the one that defaults into the transaction, so the order of profiles matters. Second, a compensation grade linked directly on a job profile takes precedence over the compensation rule. Third, rules written for last year’s organisation can quietly include or exclude the wrong people. 

Run the test eligibility rule task against a sample of workers across every entity and worker type, and use the rule assignment report to see which components rely on each rule. 

3. Compensation Matrix and Guidelines 

Workday supports a classic compensation matrix, which typically maps inputs such as performance rating and compa-ratio band to a minimum and maximum merit percentage, and a total value compensation matrix, which uses a custom calculation that can draw on skills, performance or other worker attributes. 

Whichever you use, guidelines are only as current as the ranges and ratings underneath them. Compa-ratio compares pay with the midpoint of the pay range, so out-of-date midpoints shift every guideline built on them. Check that rating scales match this year’s performance process, that compa-ratio bands still reflect your grade structure, and that a default factor exists for workers who have no review rating. 

4. Pools and Budgets 

Workday builds pools from the bottom up. Contributions are stored at employee level and rolled up by organisation, and pools are calculated once when the process is initiated. Values can still move afterwards if parallel events change an employee’s contribution. Holdbacks are what remains once the distributed amount is subtracted from the total pool, and Workday can create positive or negative organisation adjustments to keep the top-level pool intact. 

For Finance, that points to two checks before launch. Confirm that the inputs behind the pools are final, and agree how mid-cycle events will be handled, so approved budgets and actual awards can be reconciled when the cycle closes. 

5. Multicurrency: Agree the Approach Early 

Organisations paying in more than one currency need to settle the currency approach before the cycle opens. The review process asks you to choose a currency rate type and a reference currency, while compensation values for employees paid in another currency still display in their own currency. If the date you are converting on is in the future, Workday’s guidance is to choose a rate type whose rate will not change before that date, so that pool and award calculations use one consistent exchange rate. 

The decision is as much a Finance policy as a configuration setting. Which rate type, which date, and who signs it off? Write it down before the cycle opens, so managers in different countries are not debating exchange rates halfway through. 

6. Security and Approvals 

Setting up and running a review depends on dedicated security domains, including one for compensation management events and one for compensation review process reviewers. Check that the right people hold them, and that approval chains still match current reporting lines. 

Remember that the organisation snapshot date does not assign security roles, so a reorganisation can leave visibility out of step with the hierarchy. Test with a manager, an HR partner and a reviewer, not only an administrator. 

7. Review Statements 

Review statements can be released before, on or after the effective date, and a statement only becomes visible once its PDF has been generated. If you use an employee visibility date, pay-related data stays hidden until that date passes. 

Test the layout, the release timing, and the numbers against what managers will actually say in their conversations. A statement that contradicts the conversation undermines the decision behind it. 

The Pre-Season Checklist 

Use this list to close out your pre-season review. 

  • Process dates reviewed: compensation snapshot, organisation snapshot, effective and employee visibility 
  • Eligibility rules tested for recent movers across every entity and worker type 
  • Plan profile order and job profile grade links checked 
  • Matrix, rating scales, compa-ratio bands and default factors confirmed 
  • Pool inputs final, with a plan for mid-cycle events 
  • Currency rate type, reference currency and sign-off documented 
  • Security domains and approval chains checked against current reporting lines 
  • Statements tested for layout, release timing and accuracy 

Get a Second Set of Eyes 

If you would like a second set of eyes, this October we are opening ten free deep technical diagnoses of Workday Compensation setups for organisations six to thirty-six months post go-live. Our specialists review your plans, eligibility rules, approvals and statements, and hand back a clear, prioritised list of what to fix before your next cycle opens. 

First ten organisations only. Closes 20 October. 

Book your Paid Workday Compensation Diagnosis to identify opportunities for improvement. For deeper insights, read The Complete Guide to Workday Advanced Compensation.