3.2 The Hire Process & Contingent Worker Contracting

Anatomy of the Hire Employee Business Process

The Hire Employee business process (Hire) is one of the most vital workflows in Workday HCM. It orchestrates the transition of a prospective candidate into an active worker, establishing their contractual, organizational, and financial relationship with the enterprise. Because Workday employs a configurable Business Process Framework (BPF), the Hire event does not function as an isolated data-entry screen; rather, it coordinates a sequence of actions, approvals, review steps, and automated sub-processes across human resources, total rewards, payroll, and information technology.

Initiators and Security Context

The roles permitted to initiate the Hire process depend on the organization's domain security policies and business process definitions. Typical initiators include:

• HR Partner: Standard initiator for corporate and administrative hires.
• Recruiter: Initiates the hire when Workday Recruiting is deployed, transitioning candidates directly from the job application stage to "Ready for Hire".
• Manager: Permitted in decentralized operational environments (such as retail stores or manufacturing facilities).

+-----------------------------------------------------------------------------------------+
|                           HIRE EMPLOYEE BUSINESS PROCESS                                |
+-----------------------------------------------------------------------------------------+
| 1. Initiation & Pre-Hire Selection (Duplicate Matching Check)                           |
| 2. Staffing Details Entry (Supervisory Org, Position/Job Profile, Hire Date, Reason)    |
| 3. Job Classification & Details (Employee Type, Time Type, Location, Scheduled Hours)   |
| 4. Propose Compensation Hire (Sub-process: Package, Grade, Base Salary/Hourly, Plans)   |
| 5. Review & Approvals (Manager, HR Partner, Compensation Partner, Cost Center Manager)  |
| 6. Upstream / Downstream Sub-processes:                                                 |
|    - Create Workday Account (System Credentials, Security Groups)                       |
|    - Assign Pay Group (Payroll Integration)                                             |
|    - Assign Costing Allocations (Financial Charging)                                    |
|    - Onboarding & Document Checklists (I-9, Direct Deposit, Benefit Elections)          |
+-----------------------------------------------------------------------------------------+

---

Pre-Hire Lifecycle and Duplicate Prevention Architecture

In Workday's data model, an individual does not begin their lifecycle as a Worker. Instead, they exist first as a Person, which is instantiated in staffing workflows as a Pre-Hire.

Pre-Hire Creation vs Matching

A Pre-Hire is a staging business object that stores personal demographic details, contact information, and national identifiers prior to active employment. A Pre-Hire can enter the Workday tenant through multiple pathways:

• Manual Entry: Using the Create Pre-Hire task directly.
• Workday Recruiting: Automatically created when an applicant applies for a job requisition.
• External ATS Integration: Ingested via Enterprise Interface Builder (EIB) or Web Services API from third-party systems.

Duplicate Detection Engine

Creating duplicate pre-hires is a severe operational hazard that fragments employment history, impairs tax reporting, creates multiple user accounts, and scrambles rehire benefits eligibility. Workday incorporates a robust duplicate detection engine that evaluates new pre-hire submissions against existing records in the database.

The matching algorithm evaluates:

• Government National ID (Social Security Number, National Insurance Number, Tax ID)
• Legal Name (First Name, Last Name, Secondary/Maternal Surnames)
• Date of Birth
• Contact Information (Personal Email Address, Phone Number)

When a potential match is identified during the initiation of a Hire, the system presents the initiator with a Match Resolution Screen displaying existing records alongside matching percentage confidence scores. The initiator must select between two choices:

1. Use Existing Pre-Hire: Re-links the existing Person record to the new staffing transaction. This is the mandatory best practice for rehires, previous contingent workers converting to employees, or candidates who previously applied for other positions.
2. Create New Pre-Hire: Confirms that despite similar biographical data, the candidate is a distinct individual (e.g., individuals sharing identical names without matching national IDs).

---

Step-by-Step Hire Workflow Execution

Once the pre-hire is selected or created, the Hire business process progresses through sequential and parallel steps:

1. Staffing Details and Date Configuration

• Hire Date: The official legal start date of employment. Workday evaluates all organizational rules, compensation defaults, and security assignments as of this effective date.
• Reason: The business justification driving the hire (e.g., Hire Employee > New Position, Hire Employee > Rehire). Reasons belong to Reason Categories, which govern conditional step routing throughout the workflow.
• Supervisory Organization: The organizational unit owning the headcount.
• Position Selection (Position Management): The initiator must select an approved, open position with an Availability Date on or before the Hire Date.
• Job Profile Selection (Job Management): The initiator selects the Job Profile directly from the allowed profiles on the supervisory organization.

2. Job Classifications and Work Attributes

• Employee Type: Distinguishes Regular employees (indefinite tenure) from Temporary employees (fixed-term engagements).
• Time Type: Designates Full-Time or Part-Time status, establishing standard hours.
• Location: The physical work site or remote worker designation, controlling tax jurisdictions and holiday calendars.
• Work Space: Specific facility seating or office assignment.
• Scheduled Weekly Hours & Full-Time Equivalent (FTE): Defines working commitment and automatically calculates the FTE ratio against the organization's standard weekly hours (e.g., 40 scheduled hours / 40 standard hours = 1.0 FTE; 20 hours = 0.5 FTE).

3. Propose Compensation Hire Sub-Process

The Propose Compensation Hire sub-process executes automatically during the hire sequence. Workday's compensation rules engine evaluates the worker's Job Profile, Location, and Management Level to determine eligibility for:

• Compensation Package: The overarching container defining applicable guidelines.
• Compensation Grade & Grade Profile: Establishes minimum, midpoint, and maximum salary/hourly pay ranges, often localized by geographic cost of labor.
• Base Pay Plans: Assigns either a Salary Plan (for exempt/salaried workers) or an Hourly Plan (for non-exempt/hourly workers).
• Allowance Plans: Assigns fixed or calculated allowances (e.g., car allowance, cell phone stipend).
• Merit and Bonus Plans: Assigns bonus targets and short-term incentive plans based on job level.

If the proposed compensation falls outside the minimum or maximum thresholds defined by the Grade Profile, Workday generates configurable warnings or errors, and routes an additional approval step to the Compensation Partner.

4. Downstream Automated Sub-Processes

Upon final approval of the Hire business process, Workday triggers critical sub-processes:

• Create Workday Account: Evaluates tenant account generation rules to create a user name (e.g., first.last or employee ID), sets password generation parameters, and establishes sign-in credentials.
• Assign Security Groups: Based on the worker's organization, job profile, and management level, role-based and job-based security groups are automatically assigned (e.g., Employee as Self, Manager, Department Approver).
• Assign Pay Group: Links the worker to the appropriate payroll cycle (e.g., Bi-weekly Hourly, Semi-monthly Salaried).
• Assign Costing Allocations: Specifies general ledger accounting splits if the worker's salary is charged to accounts other than their default supervisory org cost center.
• Launch Onboarding Checklist: Delivers self-service tasks to the worker's My Tasks inbox (e.g., emergency contacts, direct deposit configuration, Form I-9 verification, benefits open enrollment).

---

Staffing Model Mechanics During Hire

The staffing model configured on the supervisory organization strictly dictates how the hire screen is rendered and validated:

Hire in Position Management

• The user must select an existing open position from a prompt.
• If no position exists, the user cannot proceed with the hire until a Create Position business process is fully approved.
• The position's Availability Date must be on or before the proposed Hire Date. If a position is available starting November 1st, entering an October 15th Hire Date generates a fatal validation error.
• The position's Earliest Hire Date must also be respected.
• Key job attributes (Job Profile, Location, Time Type, Worker Type) automatically default from the Position Restrictions and lock down entry to ensure compliance.

Hire in Job Management

• The user selects the Supervisory Organization and is prompted directly for a Job Profile.
• The system validates that the selected Job Profile is included in the organization's Hiring Restrictions.
• The system checks that the organization has available headcount under its defined Hiring Limits (or is set to Unlimited).
• No position object is referenced or consumed.

---

Contract Contingent Worker Business Process

Enterprises frequently leverage non-employee labor, including independent contractors, agency temps, and professional services consultants. Workday handles these individuals through the Contract Contingent Worker business process (Contract Contingent Worker).

+-----------------------------------------------------------------------------------------+
|                        EMPLOYEE vs CONTINGENT WORKER COMPARISON                         |
+--------------------------------+--------------------------------------------------------+
| DIMENSION                      | EMPLOYEE               | CONTINGENT WORKER             |
+--------------------------------+------------------------+-------------------------------+
| Primary Staffing Workflow      | Hire Employee          | Contract Contingent Worker    |
| Contract Start & End Dates     | Hire Date (End optional)| Mandatory Contract End Date   |
| Workday Payroll Processing     | Yes (Gross-to-net pay) | No (Accounts Payable/Vendor)  |
| Vendor / Staffing Agency Req.  | No                     | Yes (Mandatory Vendor link)   |
| Compensation Sub-process       | Propose Compensation   | Disallowed / Not Applicable   |
| Benefits Plan Eligibility      | Eligible (Health, 401k)| Ineligible (FLSA / ERISA)     |
| Primary Security Group         | All Employees          | All Contingent Workers        |
| Conversion to Employee         | N/A (Already Employee) | Convert to Employee workflow  |
+--------------------------------+------------------------+-------------------------------+

Unique Contingent Worker Configuration Requirements

When contracting a contingent worker, several mandatory fields distinguish the event from an employee hire:

1. Contingent Worker Type: A required configurable category defining the classification of labor (e.g., Agency Temp, Independent Contractor, Consultant, Outsourced Services).
2. Vendor: The supplier or staffing agency providing the contractor. The vendor must exist as a recognized business object in the tenant.
3. Contract Start Date & Contract End Date: While regular employees have an open-ended hire date, contingent workers must have a specified Contract End Date. This date enforces compliance, triggers contract extension notifications, and automates de-provisioning upon project conclusion.
4. No Compensation Plans: Workday HCM does not execute compensation proposals for contingent workers. Contingent workers are not paid through Workday Payroll; their compensation is remitted through vendor accounts payable invoices. Attempting to assign base salary or merit plans to a contingent worker violates core system architecture.

Converting Contingent Workers to Employees

When an enterprise hires an existing contractor as a permanent employee, administrators must never terminate the contingent worker and create a separate new employee record. Doing so breaks employment continuity and creates duplicate identities.

Instead, Workday provides a dedicated business process: Convert Contingent Worker to Employee (Convert to Employee). This workflow:

• Retains the exact same Person record, historical Pre-Hire ID, and Workday Account credentials.
• Ends the contingent worker engagement contract.
• Instantiates an active Employee record tied to the new position or job profile.
• Initiates the Propose Compensation Hire sub-process to establish employee salary, bonus, and benefits eligibility.

---

Exam Traps & Common Misconceptions

• Exam Trap 1: Proposing Compensation for Contractors. Exam scenarios frequently describe contracting a consultant and ask which base pay plan to assign. Fact: Contingent workers cannot be assigned Workday compensation plans; their financial remuneration occurs through vendor billing outside HCM.
• Exam Trap 2: Pre-Hire Creation for Former Employees. A question may ask what steps to take when hiring an applicant who worked for the company three years ago. Fact: The initiator must use the existing Pre-Hire record via duplicate matching. Creating a new pre-hire generates a fragmented duplicate record.
• Exam Trap 3: Position Availability Date Violations. A scenario will present a position with an Availability Date of October 1st and ask if an employee can begin on September 25th. Fact: Workday throws a fatal error if the Hire Date precedes the Availability Date. The position availability date must be adjusted first.
• Exam Trap 4: Employee Type vs Worker Type. Candidates often confuse Employee Type with Worker Type. Fact: Worker Type is a macro classification (Employee vs Contingent Worker). Employee Type is a sub-classification applied only to employees (Regular vs Temporary).
• Exam Trap 5: Automatic Account Generation. Questions often test whether a separate IT ticket is mandatory to create user accounts. Fact: Workday's Business Process Framework can automatically invoke the Create Workday Account sub-process as part of the Hire workflow, instantly generating user accounts and security groups.