6.2 Eligibility Rules & Compensation Defaulting

Workday Pro HCM Core Certification Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts & Format 1.2 Eligibility, Learning Path & Access 1.3 Study Strategy & Blueprint Map

2 Navigation & Business Objects

2.1 Navigation Techniques in Workday 2.2 Business Objects & Finding Data

3 Organizations & Hierarchy

3.1 Organization Types & Subtypes 3.2 Supervisory Organizations & Reporting Structure 3.3 Cost Centers, Company Hierarchies & Locations 3.4 Leadership Roles & Worker Organization Assignments

4 Staffing Models

4.1 Position Management Staffing Model 4.2 Job Management Staffing Model 4.3 Hiring Restrictions on Organizations

5 Job Profiles & Job Structure

5.1 Creating & Editing Job Profiles 5.2 Job Profiles, Jobs, Positions & Workers 5.3 Job Families, Family Groups & Job Requisitions

6 Compensation Fundamentals

6.1 Compensation Framework Components 6.2 Eligibility Rules & Compensation Defaulting 6.3 Packages, Grades & Grade Profiles 6.4 Salary Plans, Allowance Plans & Worker Comp Events

7 Jobs, Positions & Staffing Events

7.1 Creating Positions & Position Hiring Restrictions 7.2 Managing Filled, Unfilled, Close & Freeze 7.3 Hire Process End-to-End 7.4 Job Changes & Additional Staffing

8 Termination & Contingent Workers

8.1 Terminate Employees 8.2 Contracting Contingent Workers 8.3 Ending Contingent Worker Contracts

9 Configurable Security

9.1 Functional Areas, Domains & Business Processes 9.2 User-Based, Role-Based & Workday-Assigned Groups 9.3 Domain Security Policies 9.4 BP Security Policies, Org Access & Activation

10 Business Process Framework

10.1 Organizations, Security & BP Relationships 10.2 Default, Org-Specific & Rule-Based Definitions 10.3 Definition, Type, Event & Step

11 Business Process Steps & Approvals

11.1 Actions & Subprocesses 11.2 Approvals & Approval Chains 11.3 Completing Tasks During Business Processes

12 Business Process Configuration

12.1 Condition Rules 12.2 Advanced Routing, Labels & Help Text 12.3 Custom Notifications 12.4 Step Ordering Letters & Validation Conditions

13 BP Management & Security

13.1 Mass and Individual BP Management 13.2 BPs and Configurable Security Interaction

14 Report Writer Fundamentals

14.1 Standard Reports & Copy/Modify 14.2 Building Custom Reports: Index vs Standard 14.3 Sorting, Filtering & Prompts 14.4 Report Security, Sharing & Ownership

15 Advanced Reporting & Calculated Fields

15.1 Scheduling Reports 15.2 Matrix Reports 15.3 Discovery Boards 15.4 Calculated Fields & Report Performance

6.2 Eligibility Rules & Compensation Defaulting

Key Takeaways Explain This Topic AI

Compensation eligibility rules determine which packages, grades, grade profiles, and plans are available for a worker based on job, location, company, worker type, and similar attributes.

Rules must map to packages, grades, grade profiles, plans, and plan profiles so defaulting during transactions is accurate.

Compensation defaulting automatically proposes package, grade, grade profile, and plan values for eligible workers to reduce manual data entry on Hire and Change Job.

Defaulting requires eligibility for the package and for the plan(s) in that package; a plan outside the package may remain selectable but will not default the same way.

Workers should be eligible for one package and one grade; when multiple plan profiles match, the first profile that meets the rule criteria defaults into the transaction.

Last updated: September 2026

6.2 Eligibility Rules & Compensation Defaulting

Study index: T-numbers here refer to this guide’s index of an older Workday topic list. They are not current Workday task IDs or published exam weights.

Quick Summary: Eligibility rules decide which workers can receive which compensation components. Compensation defaulting uses those rules—plus package associations—to automatically propose packages, grades, grade profiles, and plans on Hire, Change Job, and related compensation transactions. Misconfigured rules produce missing defaults, wrong plans, or multiple competing packages.

After you know the framework objects, the next configuration skill is who gets what and how values appear automatically . Tasks T21 (create compensation eligibility rules) and T22 (purpose of compensation defaulting; how defaulting applies on Hire/Change Job) are tightly linked: defaulting only works when eligibility and package associations are designed correctly.

Purpose of Compensation Eligibility Rules

A compensation eligibility rule is criteria-based configuration that automatically associates a group of employees with compensation components such as packages, grades, grade profiles, and plans. Eligibility can also identify populations for a localized profile among multiple grade profiles.

Typical rule criteria

Criterion family Examples
Job structure Job profile, job family, job family group, management level
Organization Company, location, region, cost center (as designed)
Worker attributes Worker type (employee vs contingent), time type (full-time / part-time), exempt status
Other attributes Country, custom fields, calculated criteria used in advanced designs

Eligibility does not set the dollar amount by itself. Amounts come from plan defaults, grade profile guidance, or manual entry during Propose Compensation. Eligibility answers: May this worker receive this component?

Why rules must map cleanly

Rules must map to packages, grades, grade profiles, plans, and plan profiles so defaulting during a transaction is accurate. Practical design goals:

One package per worker population design (employees eligible for only one compensation package).

One grade eligibility per design (employees eligible for only one compensation grade).

Clear grade profile selection when localized pay ranges are required.

Plan eligibility that matches the package contents so defaults can land.

Exam trap: Eligibility rules are not merit cycle calendars, not payroll pay group schedules, and not the substitute for domain security. They control compensation component availability and defaulting populations .

Creating Eligibility Rules (Conceptual Task Flow)

When the exam or a lab says "create a compensation eligibility rule," think in this sequence:

Name and describe the rule for admin maintainability (for example, "US Full-Time Salaried Managers").

Define condition criteria using the attributes that uniquely identify the population.

Attach the rule to the relevant package, grade, grade profile, plan, and/or plan profile .

Test with sample workers on Hire or Propose Compensation: confirm the package and plans default (or become correctly available).

Avoid overlap with other packages/grades that could also evaluate true for the same worker.

Configuration scenario: Northstar Health wants only full-time US employees in Job Family "Nursing" to receive the Clinical Professional package and its RN salary plan. The implementer creates an eligibility rule: Company = US Operating Co, Time Type = Full Time, Job Family = Nursing. That rule is assigned to the Clinical Professional package, the clinical grade, the appropriate grade profile, and the RN salary and clinical allowance plans. A part-time nurse fails the rule and does not default into the full-time clinical package.

Purpose of Compensation Defaulting

Compensation defaulting eases data entry by automatically defaulting compensation components —packages, grades, grade profiles, and plans—onto worker compensation for employees who meet the rule's eligibility requirements. The business purpose is speed, consistency, and fewer user errors on high-volume staffing events.

Without defaulting, every Hire would require an expert to hand-select package, grade, profile, and every plan. With defaulting, the system proposes the designed set; the user reviews, adjusts amounts within policy, and submits.

Without defaulting With defaulting
Manual search of all plans Package and eligible plans pre-populated
High risk of wrong package Population-driven correct package
Slow Hire / Change Job Faster Propose Compensation step
Inconsistent grade usage Default grade / grade profile applied
How Defaulting Applies on Hire and Change Job

Staffing events are the primary places HCM Core tests defaulting awareness.

Hire

On Hire , after job, organization, and related details are established, the process commonly includes Propose Compensation Hire (as a subprocess or related step). Defaulting evaluates the candidate/worker attributes against eligibility rules and, when design is correct:

Defaults the compensation package .

Defaults the compensation grade and, if configured, the matching grade profile .

Defaults eligible plans associated with that package (for example salary plan and amount-based allowance plan).

The hiring partner or compensation partner then confirms or adjusts amounts (for example setting the salary plan amount within grade guidance).

Change Job

On Change Job (promotion, transfer, lateral move, and similar reasons), worker attributes often change—new job profile, new location, new company, new management level. Propose Compensation Change re-evaluates eligibility:

The worker may become eligible for a new package or grade .

Plans may add, remove, or replace based on new eligibility.

Amounts may need update (promotion increase) while grade midpoints change with the new profile.

Defaulting on Change Job prevents a promoted manager from remaining on an individual-contributor-only package simply because nobody remembered to swap plans. Hire / Change Job

│
▼
Worker + job + org attributes established
│
▼
Eligibility rules evaluated
│
▼
Package / grade / grade profile / plans defaulted
│
▼
Propose Compensation reviewed → submit
Critical Defaulting Rules (Exam Favorites)

Memorize these operational truths:

Assign the eligibility rule to a compensation package and associate the default grade, grade profile, and one or more plans with that package for package-driven defaulting to work as designed.

The worker must be eligible for the package and eligible for a plan in the package for that plan defaulting to occur as expected.

Being eligible for a plan that is not in the package may leave the plan available to select without producing the same defaulting behavior as package-associated plans.

For plan profiles, the first plan profile that the employee meets the eligibility rule criteria for will default into the compensation-related transaction.

Target profiles can support grades, grade profiles, and many plan types (including period salary, one-time payment, merit, bonus, stock, allowance, and commission concepts in broader compensation design).

Exam trap: Defaulting is not "payroll automatically pays the invoice." It is HCM compensation component proposal during compensation transactions inside staffing and related events.

Failure Modes and How to Diagnose Them

Symptom on Hire / Change Job Likely cause
No package defaults Missing or false eligibility on package; worker attributes do not match rule
Wrong package defaults Overlapping package eligibility; worker matches multiple rules
Grade missing Grade not associated / eligibility not mapped to grade or package defaults
Plan missing from defaults Plan not in package, plan eligibility fails, or plan profile order issue
Plan selectable but not defaulted Eligible for plan outside package association pattern
Profile wrong city range Grade profile eligibility not distinguishing locations

Realistic exam scenario: "An HR Partner hires a worker and no compensation package defaults. What should you check first?" Prefer answers about eligibility rule criteria vs worker attributes and rule assignment to the package , not "delete the supervisory organization" or "disable security activation."

Design Checklist for T21–T22

Write eligibility rules that produce mutually exclusive package populations where possible.

Map rules to package + grade + grade profile + plans .

Validate Hire defaulting with at least one worker per major population.

Validate Change Job defaulting when job family, location, or management level changes.

Document that defaulting reduces entry effort but does not remove the need to review amounts and policy exceptions.

Master eligibility and defaulting together: rules without package association are incomplete; packages without rules will not auto-select the right populations on staffing events.