6.4 Salary Plans, Allowance Plans & Worker Comp Events

6.4 Salary Plans, Allowance Plans & Worker Comp Events

Quick Summary: Salary plans carry base salaried pay; amount-based allowance plans carry fixed extra pay amounts. Workers receive and change those plans through compensation events, especially Propose Compensation inside Hire and Change Job. Configure plans, attach eligibility, place them in packages, then maintain pay via events—not ad hoc silent edits (tasks T25–T27).

With packages and grades in place, HCM Core still expects you to configure plans and maintain worker compensation. Plans are where amounts live; events are how amounts change with auditability.

Configuring a Compensation Salary Plan

A salary plan is the primary vehicle for base pay for salaried workers. Configuration concepts you should be able to explain:

Conceptual create flow

1. Create the Salary Plan object with business naming standards.
2. Set plan attributes required by your tenant (frequency, currency handling, rounding behaviors as designed).
3. Attach eligibility so only intended populations can receive it.
4. Add the plan to the relevant compensation package(s).
5. Coordinate with grade design so Propose Compensation guidance makes sense.
6. Test: eligible hire defaults the salary plan; ineligible hire does not.

Configuration scenario: Contoso configures "US Exempt Salary Plan" for full-time exempt employees. Eligibility: US company, exempt, full-time. The plan sits on the US Salaried package next to Grade bands P1–P6. On Hire, Propose Compensation defaults the salary plan; the HR Partner enters 105,000, which sits between the profile minimum and maximum for the worker's grade profile.

Salary plan vs hourly plan (awareness)

HCM Core vocabulary also includes hourly plans for non-exempt or hourly populations. Do not put hourly retail associates on a salaried plan "because the package was convenient." Package and eligibility design should route hourly workers to hourly plans and salaried workers to salary plans.

Configuring an Amount-Based Allowance Plan

An allowance plan pays additional compensation beyond base salary or hourly pay—housing, transportation, meal, location premium, on-call stipend, and similar. Task T26 focuses on an amount-based allowance plan: the allowance is defined as a monetary amount (as opposed to purely unit-based allowance designs that count units × rate).

Amount-based allowance characteristics

Conceptual create flow

1. Create Allowance Plan configured as amount-based.
2. Define amount entry expectations (default amount if any, editability rules per design).
3. Attach eligibility (for example Job Family = Sales AND Location Country = US).
4. Add the allowance plan to the appropriate package if it should default with that program.
5. Test Hire/Change Job: eligible workers see the allowance plan default or available; amounts can be set or confirmed.

Configuration scenario: Field sales directors receive a 750 monthly auto allowance. The implementer creates amount-based allowance plan "US Sales Auto Allowance," eligibility for Sales management levels, package membership on US Salaried Sales. Base salary remains on the salary plan; the allowance is a second plan line on the worker's compensation.

Exam trap: An allowance plan is not a compensation grade and not a bonus plan. Bonus plans target variable performance pay; allowance plans typically represent structured additional pay components. Grades remain the range guidelines for base pay decisions.

Maintaining Worker Compensation Events

Task T27 centers on maintaining worker compensation—the ongoing lifecycle after initial hire setup.

Why events matter

Workday HCM is event- and effective-date driven. Changing someone's pay should create a compensation event with reason, effective date, and audit history—not an invisible overwrite. Common event contexts include:

What you maintain on the worker

• Active plans and amounts (salary, allowance, and others).
• Package and grade / grade profile context guiding the assignment.
• Effective dating of changes for history and payroll handoff design.
• Alignment after job attribute changes that alter eligibility.

Realistic exam scenario: A worker transfers from Austin to New York. Change Job updates location; Propose Compensation re-evaluates eligibility; grade profile switches to High Cost; salary plan amount may be adjusted; amount-based location allowance might be added. Maintaining compensation through the event keeps package, grade, and plans consistent with the new job.

Propose Compensation in the Staffing Context

HCM Core strongly associates compensation with staffing business processes:

Hire

1. Initiate Hire; complete worker, job, organization, and related steps.
2. Propose Compensation (often a subprocess) opens.
3. Defaulted package, grade, grade profile, salary plan, allowance plans appear when eligibility and package design are correct.
4. User confirms or edits amounts; submits into approvals per BP definition.

Change Job and related staffing movements

1. Initiate Change Job with an appropriate reason (promotion, transfer, and so on).
2. Update job profile, org assignments, location, or other drivers of eligibility.
3. Propose Compensation runs in context so pay program stays aligned to the new role.
4. Completing staffing without reviewing compensation is a common operational failure—exam questions may test that compensation is part of the staffing flow, not an unrelated afterthought.

Staffing BP (Hire / Change Job)
        │
        ├── Job & org details
        │
        └── Propose Compensation (subprocess / step)
                 ├── Package / grade / profile
                 ├── Salary plan amount
                 └── Allowance plan amount(s)

Security and BP awareness (light touch)

Who can propose or approve compensation depends on business process security and domain permissions (Compensation-related functional areas). HCM Core security chapters cover the model in depth; for this section, know that Propose Compensation is a secured step in staffing, not a public edit for every employee.

End-to-End Design Checklist (T25–T27)

1. Salary plan created with correct population eligibility.
2. Amount-based allowance plan created for the extra-pay use case.
3. Both plans added to the right package(s) where they should default.
4. Grades / profiles guide base pay; allowances sit as separate plan lines.
5. Hire test: defaults + amount entry + approval path.
6. Change Job test: eligibility change updates plans/profiles appropriately.
7. Ad hoc compensation change path known for off-cycle maintenance.
8. Historical events remain queryable for audit and reporting.

Common Confusions

Exam Scenarios

Scenario A — Configure salary plan. Correct answers mention plan setup, eligibility, package association, and use on Propose Compensation—not "create a custom organization named Salary."

Scenario B — Amount-based allowance. Stem describes a fixed 300 monthly remote-work stipend. Best object: amount-based allowance plan, not a second compensation grade and not a stock plan.

Scenario C — Maintain worker comp. Stem: manager needs an off-cycle increase next Monday. Prefer initiating the appropriate compensation event with effective date, not editing a report output or changing Supervisory Organization roles.

Scenario D — Staffing context. "Where does Propose Compensation commonly appear?" In Hire and Change Job (staffing) flows as the step that applies package defaults and plan amounts to the worker.

If you can configure a salary plan and an amount-based allowance plan, place them in packages with eligibility, and maintain worker pay through Propose Compensation and other compensation events, you have completed the HCM Fundamentals compensation task cluster (T20–T27) at exam depth for Workday Pro HCM Core's 50-question, 80% pass, 100-minute format.