Study guide

8.1 Terminate Employees

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

8.1 Terminate Employees

Key Takeaways Explain This Topic AI

Terminate is the staffing business process that ends an Employee's primary employment relationship and drives offboarding, benefits, payroll finalization, and seat vacancy effects.

Last Day of Work and Termination Date are related but not always identical fields—know that both can appear on the event and that date choices drive effective dating of downstream processes.

In Position Management, termination vacates the Position seat; the seat is not auto-deleted. In Job Management, occupancy ends without leaving a persistent vacant seat.

Completed Termination events are not casually undone: Cancel applies only while in progress; Rescind reverses completed events and unwinds downstream effects; Correct edits data without full unwind.

Offboarding checklists, To Dos, and subprocesses hang off the Termination BP design—they are part of the event framework, not a separate product module in practice.

Last updated: September 2026

8.1 Terminate Employees

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: Termination ends an Employee's primary employment in Workday. You capture reason, last day of work, termination date, and rehire eligibility; the business process then drives offboarding tasks and downstream effects. In Position Management the seat becomes vacant; completed events require Correct or Rescind—not Cancel—to change after the fact.

Jobs and Positions staffing events (T28–T36) close the hire-to-exit lifecycle. Older-guide topic T34 Terminate employees sits after Hire (T32) and staffing movements (T33). Termination is a useful integrated scenario because it touches staffing models, business processes, security initiation rights, and position vacancy—not because you must memorize every offboarding checklist item in a customer's tenant.

What Terminate Does

Terminate is the business process that ends an Employee worker's primary employment relationship. When the event completes successfully:

The worker's employment status transitions out of active employment (subject to effective dates on the event).

Organization and position occupancy for that primary job end as of the event's effective dating.

Downstream processes configured on the Termination BP can fire: offboarding To Dos/checklists, benefits end, payroll final pay, system-access related tasks, and notifications.

History is preserved . Workday does not "delete the person" as the default model; termination is a lifecycle state change with audit trail.

  • Concept Role on Terminate
  • Worker (Employee subtype) The person whose primary employment is ending
  • Termination BP Configurable workflow: initiate → approvals/To Dos → complete

Termination reason Coded reason (voluntary resignation, involuntary, retirement, etc.) used for reporting and policy

  • Last Day of Work Last calendar day the employee actually works
  • Termination Date Effective date of the employment end as captured on the event
  • Eligible for rehire Flag/decision used later if the person returns
  • Position (if PM) Seat becomes vacant unless separately closed/frozen

Exam trap: Terminate is not the same as deleting a Worker record, not the same as End Additional Job, and not the same as End Contingent Worker Contract (T36). Using the wrong exit event is a classic distractor.

Last Day of Work vs Termination Date

Many exam and real-world scenarios hinge on date nuance :

Field (conceptual) Typical meaning Why it matters

Last Day of Work Final day the person performs work Drives operational offboarding (badge, laptop return, coverage)

Termination Date Effective employment end date on the staffing event Drives effective dating of status, often benefits and payroll cutover

Pay Through / related pay dates How long pay continues (tenant/payroll design) Not identical to "last day in the office" in every design

Practical nuances for T34

They can be the same day. Many resignations set last day of work = termination date.

They can differ. Example: last day of work is Friday after a notice period, but policy or regional practice sets termination effective dating in a specific way for benefits or leave. In practice, recognize both concepts , not invent one universal legal rule for every country.

Effective dating drives visibility. After the event's effective date, the worker should no longer appear as an active employee in the supervisory org for ongoing staffing decisions; history remains queryable under security.

Do not confuse with position availability date. Freezing/closing a position or changing earliest hire date is a position lifecycle task (T30–T31), not a field you invent on Terminate to "delete" capacity.

Configuration scenario: Alex resigns. Last day of work is 15 March. HR initiates Termination with last day of work 15 March, termination date aligned to that exit, reason Voluntary – Resignation, eligible for rehire = Yes. In a Position Management org, Position P-882 becomes vacant after the event completes. Facilities still has a To Do to collect the laptop—because offboarding steps are configured on the Termination BP, not because Terminate auto-invents a separate "Asset Management app" in practice.

Downstream Effects You Must Expect

Termination is a staffing event with a long tail . High-level effects:

Staffing / organization

Primary job ends; worker leaves the active roster of the Supervisory Organization.

Position Management: Position remains and is typically vacant (available to fill) unless HR closes or freezes it.

Job Management: No persistent vacant seat object; headcount/occupancy simply decreases.

Business process framework

Approvals may be required (manager, HR Partner) per BP definition.

To Dos , checklists , and subprocesses implement offboarding: return equipment, exit interview, revoke access, knowledge transfer.

Notifications can alert security, IT, or payroll partners.

Cross-functional systems (conceptual)

  • Area Typical effect of completed Termination
  • Benefits Coverage end rules apply from configured dates
  • Payroll Final pay / stop ongoing payments per integration design
  • Security Role assignments and access tied to active worker/org membership lose effect as designed
  • Reporting Active headcount drops; historical employment remains reportable

Exam trap: Termination does not reverse the worker's entire historical hire, compensation history, or financial journals as a blanket rule. Unwinding a completed bad termination is a Rescind problem (or Correct for limited data fixes), not "run Terminate again."

Terminate vs Related Exit / Job Events

  • Event What it ends What it preserves
  • Terminate Primary employee employment Worker history; person can be rehired later
  • End Additional Job One secondary job only Primary employment continues
  • End Contingent Worker Contract Contingent contract relationship Contingent path (T36)—not employee Terminate
  • Change Job / Transfer Job context, not full employment end Worker remains employed

If a worker has multiple jobs, ending only a secondary assignment is not Terminate. If the stem says "contractor engagement ends," do not answer with employee Terminate.

Cancel, Correct, and Rescind on Termination Events

Because Termination has heavy downstream effects, practice scenarios should include event correction choices after mistakes:

  • Operation When it applies Effect
  • Cancel BP still in progress (not successfully completed) Stops the incomplete event; no completed termination

Correct In progress or completed, where supported by BP type and security Edits supported event data without fully unwinding the event

Rescind BP completed Reverses the completed event and unwinds downstream effects—powerful and destructive; use sparingly

Awareness for T34 (not a full BP chapter): If HR entered the wrong termination date and the event already completed with benefits and access tasks fired, Cancel is no longer available . Choose Correct when a limited data fix is appropriate, or Rescind when the termination should never have completed and downstream work must reverse. Permission to Cancel/Rescind/Correct is governed by Business Process Security Policy , not by "whoever initiated."

Scenario: An HR Partner completes Termination for the wrong employee. The event is complete. The fix is not Cancel. Security-permitted Rescind (with careful coordination) is the path to reverse a completed false termination; then process the correct worker if needed.

Offboarding at Study Depth

Offboarding is not a separate blueprint chapter title in T34, but it is how Termination BPs deliver consistent exit operations:

Configured as To Dos , checklists , and subprocesses on the Termination definition.

Ensures every exit triggers the same operational handoffs (IT, facilities, manager knowledge transfer).

Does not replace the need for a proper Termination reason, dates, and staffing model awareness.

Keep offboarding high level : know it hangs off the Termination BP; do not invent proprietary step names as universal exam truth.

  • Position Lifecycle After Employee Termination Employee active in Position (PM)
  • │
  • └── Terminate (complete)
  • │
  • ├── Worker no longer active employee
  • └── Position → Vacant (unless Close / Freeze)
  • │
  • ├── Backfill Hire into same Position
  • ├── Freeze (block hire temporarily)
  • └── Close (retire seat capacity)

Exam link to T11/T30–T31: Termination does not auto-close the position, does not auto-switch the supervisory org to Job Management, and does not delete Job Profiles.

Practical Mental Checklist (T34)

Is the person an Employee with primary employment ending? → Terminate.

Capture reason , last day of work , termination date , rehire eligibility .

Predict seat outcome from staffing model (vacant seat vs no seat).

Expect offboarding steps from BP design.

If the event is wrong after completion → Correct or Rescind , never Cancel.

Master Terminate as the controlled employee exit event: dates and reason first, model-aware seat effects second, BP lifecycle operations third—then you are ready for contingent contract entry and exit (T35–T36).