A Period Salary Plan in Workday supports paying employees more than 12 times per year (e.g., 13 or 14 payments for regions like Italy or Spain).

This allows payroll to spread annual salary across the correct number of pay periods.

Why not the others?

A. Unit salary plan – Pays based on units (like per credit hour for faculty), not extra months.

B. Hourly plan – Pays by worked hours, not relevant to salaried employees.

D. Salary plan – Standard salary plan assumes 12 months and does not support extra pay periods.

A seniority dynamic calculated plan automatically adjusts based on worker attributes such as length of service.

Workday evaluates dynamic calculations daily , ensuring that once an employee reaches their 3-year, 6-year, or other milestone, the plan amount updates automatically without manual intervention.

Why not the others?

A. Audit report + Request Compensation Change – Unnecessary; dynamic plans do not require manual updates.

B. Schedule Automatic Step Progression – That applies to step progression plans , not dynamic calculated plans.

C. Mass Operation Management – Used for bulk updates, but not required here because Workday auto-updates dynamic plans.

Compensation grades in Workday define pay ranges (minimum, midpoint, maximum) for job profiles.

Their purpose is guidance during compensation transactions (hire, promotion, merit increase, etc.), ensuring pay is competitive and consistent.

They do not enforce payroll mapping or overtime eligibility directly but help managers and HR align salary offers to market ranges.

Why not the others?

B. Connect salary to payroll → That is done by compensation elements , not grades.

C. Overtime eligibility → Determined by work hours & worker type , not grades.

D. Compensation basis for reporting → Controlled by comp basis setup , not grades.

Since the eligibility rule evaluates pay rate type = salaried , you need to ensure every job profile has the correct pay rate type assigned .

This prevents mismatches where employees may not qualify for the salary plan due to missing or inconsistent data.

Why not the others?

A. Modify rule to evaluate all job profiles → Broadens scope incorrectly; doesn’t ensure data integrity.

C. Pay rate type on job requisitions → Impacts recruiting, not existing employee eligibility.

D. Assign salary plan to job profiles → Comes after ensuring the pay rate type is consistently set.

The scenario describes a compensation partner being able to assign any allowance plan , even when the employee is not eligible .

This is controlled by the security domain "Add Compensation Plans: Add Allowance" , which allows users with access to bypass eligibility and directly assign allowance plans.

Why not the others?

A. Worker Data: Compensation Plan Type → Governs visibility to compensation data, not bypassing eligibility.

B. Select Any Compensation Package → Pertains to choosing packages, not adding allowance plans outside eligibility.

C. Worker Data: Compensation for Managers → Grants managers ability to propose comp, but does not override eligibility.

During a Change Job , compensation may be recalculated, and plans with no eligibility criteria may inadvertently be dropped.

The compensation partner must restore the plan after the transfer using Propose Compensation Change .

This ensures the employee retains the allowance assignment without disrupting the change job process.

Why not the others?

A. Roll Out Compensation Plans → Mass rollout, not individual fix.

B. Plan Adjustment → Adjusts targets/amounts, not restores removed plans.

D. Request Compensation Change → Typically for ad hoc changes; restoration during job change is handled via Propose Compensation Change .