6.2 Eligibility Rules & Compensation Defaulting

6.2 Eligibility Rules & Compensation Defaulting

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 exam 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

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:

1. One package per worker population design (employees eligible for only one compensation package).
2. One grade eligibility per design (employees eligible for only one compensation grade).
3. Clear grade profile selection when localized pay ranges are required.
4. 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:

1. Name and describe the rule for admin maintainability (for example, "US Full-Time Salaried Managers").
2. Define condition criteria using the attributes that uniquely identify the population.
3. Attach the rule to the relevant package, grade, grade profile, plan, and/or plan profile.
4. Test with sample workers on Hire or Propose Compensation: confirm the package and plans default (or become correctly available).
5. 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.

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:

1. 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.
2. The worker must be eligible for the package and eligible for a plan in the package for that plan defaulting to occur as expected.
3. 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.
4. For plan profiles, the first plan profile that the employee meets the eligibility rule criteria for will default into the compensation-related transaction.
5. 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

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.