Workday-Pro-Compensation WorkdayProCompensationExam Questions and Answers

Employees requesting one-time payments for self may see sensitive options like Gross Up or Send to Payroll .

To prevent them from updating these fields, configure Optional Fields for Request One-Time Payment for Self and hide the checkboxes.

This limits their visibility and update access without affecting manager/HR workflows.

Why not the others?

A. Optional Fields for Request One-Time Payment → Applies to manager/HR use, not self-service.

C. Remove Employee as Self from self-service comp domain → Would block employees from initiating requests entirely.

D. Payroll security domain → Payroll security doesn’t control compensation request UI fields.

Default compensation for requisition compensation ensures that all hires from a requisition default to the same plan amounts/rates , supporting consistency in offers.

This prevents discrepancies between candidates applying for the same role and requisition.

Why not the others?

A. Guidelines on a position → Position compensation is separate from requisition compensation.

C. Every employee in position receives same compensation → Controlled by position defaults, not requisition.

D. Eligible plans view → That’s determined by compensation package setup , not requisition defaults.

progression but haven’t yet been moved to the next step.

The corrective action is to run Schedule Automatic Step Progression , which processes all eligible employees and updates their step automatically.

Why not the others?

B. Maintain Compensation Steps + progression rule → Only needed if rules are missing. If employees appear, rules already exist.

C. Change Job → Not required; step progression is automated.

D. Set Up Grade Job Profile Adjustment → Used for grade changes, not step progression.

When multiple compensation bases apply to an employee, Workday selects the primary basis based on ranking (lowest number = highest priority) .

Rankings here:

Management = 1

International = 2

Sales = 3

Therefore, Management Compensation is the primary basis.

Why not the others?

B. Sales Compensation → Ranked lowest (3).

C. International Compensation → Ranked 2, lower than Management.

D. Total Base Pay → Not listed among eligible ranked bases here.

In Workday, when you set an Actual End Date on a compensation plan, the plan remains active through that date .

Workday automatically removes the plan the day after the entered actual end date.

Example: If Actual End Date = March 31, the plan is removed effective April 1 .

Why not the others?

B. Last day of the month +1 → Too restrictive; not always tied to month-end.

C. On the actual end date → Wrong; the plan is valid through the end date.

D. Last day of the pay period +1 → Not relevant; tied to end date, not pay periods.

If the eligibility rule for Sales / Australia profile is changed to remove “Sales,” then all Australian employees (regardless of job family) become eligible.

As a result:

Any Australian employee moving roles will be assigned the allowance.

Sales employees will no longer qualify , so their allowances are automatically removed during compensation/job changes.

Why not the others?

A. Sales removed immediately → Removal only happens at a transaction/job change evaluation.

C. All Australians automatically enrolled → Not automatic, triggered during job/comp events.

D. System error → Not how Workday handles eligibility changes.

To retire or replace an existing bonus plan , you need to mass-remove it from all employees currently assigned.

The standard Workday task for this is Remove Compensation Plans from Employees , which allows you to:

Select the compensation plan to remove.

Apply an eligibility rule to identify affected employees.

This is efficient and ensures employees no longer carry the outdated plan.

Why not the others?

A. Mark plan inactive → Prevents new assignments but doesn’t remove existing employee assignments.

C. Request Bonus Payment web service → Used for issuing payments, not removing plans.

D. Change Job → Not appropriate for mass plan removal.

Some countries (e.g., Italy, Spain) legally require employees to be paid 13 or 14 times per year .

Workday supports this by using a Period Salary Plan with a multiplier , which allows additional months, weeks, or days of pay.

In this case, to meet the legislation for an extra month, configure the period salary plan with a 1-month multiplier .

Why not the others?

A. Amount-based allowance plan → Allowances are supplemental, not designed for legislated base salary multipliers.

B. Percent-based merit plan → Merit is performance-based, not a legislative requirement.

C. One-time payment plan → One-time payments are ad hoc, not recurring annual extra months.

Assigning a compensation grade to a job profile links that job to a defined pay range (min, midpoint, max).

This ensures that whenever employees are hired or promoted into the job profile, Workday defaults the pay range guidance automatically.

Managers and HR can then use this information to propose fair and competitive pay.

Why not the others?

B. Target compensation amount → Target comp is usually set at the employee or plan level, not the grade.

C. Eligibility for bonus plans → Controlled via eligibility rules , not compensation grades.

D. Compensation frequency → Determined by plan setup (annual, monthly, hourly) , not by grades.

Effective Date (March 1) = When the pay increase is valid for payroll.

Employee Visibility Date (March 21) = When employees can actually see the change in Workday.

This allows managers to communicate the increase by March 20, and employees only see it from March 21 onward, while payroll processes it correctly on March 31.

Why not the others?

A. Expected End Date March 31 → Used to close plans, not to control visibility.

B. Actual End Date March 1 → Would end the plan immediately.

D. Effective Date March 5 → Wrong; payroll needs it effective March 1.

In eligibility rule setup, the Source External Field or Condition Rule column shows both fields and condition rules.

To restrict your entry to fields only , Workday requires the prefix field: .

Example: entering field:Worker Type ensures only fields appear, excluding other condition rules.

Why not the others?

B. Brackets → Not a recognized syntax.

C. All caps → Doesn’t change filtering behavior.

D. Asterisk → Used for wildcard searches, not filtering.

In Workday, one-time payments (like signing bonuses ) must flow from Offer → Hire to remain consistent.

If the signing bonus added during Offer doesn’t carry into Hire , it means the Hire business process is missing the Request One-Time Payment subprocess .

Adding it ensures that any one-time payments from the offer are automatically included in the hire event.

Why not the others?

A. Include in package → Package inclusion allows proposal but doesn’t ensure carry-forward into Hire.

B. Add approval step → Workflow step won’t fix missing subprocess link.

D. Update security policy → Security won’t solve missing subprocess configuration.

For Total Cost (India) , the requirement is that only 50% of total comp should be allocated toward salary plans .

This is achieved by using the Manage Basis Total option , where you can set maximum percentages for specific plan types (e.g., Salary = 50%).

This ensures salary stays capped at half of total, regardless of other components.

Why not the others?

A. Fixed compensation basis → Doesn’t handle percentage capping.

B. Remove retirement plans → Irrelevant; retirement can stay, the key is controlling salary %.

D. Change ranking to 50 → Ranking only determines basis priority, not limits.