Skip to content
ICEPS conference wordmark International Conference on Education, Psychology and Society 2020 ICEPS · Sapporo, Japan
August 5 to 7, 2020 Sapporo, Hokkaido Email the secretariat

Learning resource

Workday Training Modules Explained for New Learners

A plain guide to how Workday is organised into modules, what each module covers, and the order that helps a new learner build confidence.

Home › Education and Psychology › Workday Modules

Overview

Workday is a single cloud system for people, payroll, finance and planning. Instead of one enormous screen, the system is arranged into modules. Each module focuses on one area of work, such as hiring, payroll or expenses, and each one can be switched on for the people who need it.

For a new learner, that arrangement is helpful. You do not have to understand the whole system at once. You can learn one module, see how it fits the wider flow of data, and then add the next.

Key idea. A module is not a separate product. It is a set of tasks and pages that share the same data, the same security model and the same reporting tools.

Why Workday is modular

Organisations rarely buy every part of the system at once. A company might begin with core human capital management and payroll, then add recruiting, time tracking or financial management later. Modules make that possible without rebuilding the whole system.

Modules also control what people see. A manager in one department may need time approval, while a payroll specialist needs pay calculations and a finance analyst needs journals. Security roles decide which modules and which tasks each person can open.

Core modules

Most learners meet the same core areas first. The table below groups them by the kind of work they support.

Common Workday modules and the teams that use them
ModuleWhat it coversWho uses it
Core HCMWorker records, job changes, organisation structureHR teams and managers
PayrollPay calculation, payslips, deductions and taxPayroll and finance
Time TrackingHours, schedules and approvalsManagers and employees
AbsenceLeave requests, balances and calendarsManagers and HR
BenefitsEnrolment, life events and plan dataHR and employees
RecruitingRequisitions, candidates and offersRecruiters and hiring managers
LearningCourses, assignments and completion recordsLearning teams and employees
Financial ManagementLedgers, journals, expenses and suppliersFinance
ReportingReports, dashboards and calculated fieldsAnalysts and administrators
SecurityRoles, groups and domain policyAdministrators

Core HCM

Core HCM holds the worker record. Everything else depends on it, because payroll, time, benefits and reporting all read from the same worker data. New learners should start here. Learn how a hire becomes a worker record, how a job change is entered, and how the organisation chart is built.

Payroll

Payroll turns time, compensation and deductions into pay results. It is one of the most sensitive modules, and access is tightly controlled. Learners usually begin with pay groups, earning and deduction codes, and the payroll cycle.

Time Tracking and Absence

Time tracking records hours worked and supports approval. Absence handles leave requests and balances. The two are often learned together because both affect pay and both involve manager approval.

Benefits

The benefits module manages enrolment, life events and plan data. Learners meet eligibility rules and open enrolment windows here.

Recruiting

Recruiting follows a candidate from application to offer and then hands the new hire to Core HCM. It is a good module for seeing how one part of the system passes data to another.

Learning

The learning module assigns courses, tracks completion and stores records. It is often the module that new administrators practise in first, because the actions are easy to see and easy to reverse.

Financial Management

Financial management covers the ledger, journals, expenses and suppliers. Learners with a finance background often start here, while HR learners usually meet it later through expenses or supplier data.

Reporting and Security

Reporting is not a single screen but a skill that runs across every module. Calculated fields, report prompts and dashboards let you answer questions that the standard pages do not. Security roles decide who may run those reports and see the results.

How the modules connect

Modules share data, so a change in one place appears in another. A new hire in recruiting becomes a worker in Core HCM, the worker receives a schedule in time tracking, requests leave through absence, and is paid through payroll. A finance analyst then sees the labour cost in the ledger.

Understanding these flows is more useful than memorising menus. When you know where data starts and where it is used, you can trace a problem instead of guessing.

  • Recruiting to Core HCM. An accepted offer creates the worker record.
  • Core HCM to time and absence. The worker record drives schedules and leave eligibility.
  • Time and absence to payroll. Approved hours and leave feed the pay run.
  • Payroll to finance. Pay results become labour cost in the ledger.
  • Everything to reporting. Each module writes data that reports can read.

A learning path for new learners

A steady order beats a random tour of menus. The sequence below keeps each step grounded in the one before it.

  1. Navigation and terminology. Learn the search bar, the worklets, the inbox and the difference between a task and a report.
  2. Security roles. Find out which role you hold and which modules it opens.
  3. Core HCM. Practise worker records, job changes and the organisation chart.
  4. Time and absence. Follow one approval from request to completion.
  5. Reporting. Build a simple report, add a prompt, and save it to a dashboard.
  6. Specialisation. Choose payroll, recruiting, benefits or finance based on your role.

A sandbox or training tenant is the best place to practise. Mistakes there do not touch live pay or worker records.

Delivery formats

Workday learning usually arrives in a few formats. Each one strengthens a different part of your understanding.

  • Instructor led sessions. A trainer walks a group through a module with live examples.
  • Self paced eLearning. Short recorded lessons that you complete on your own schedule.
  • Guided labs. Exercises in a practice tenant where you perform the task yourself.
  • Certification paths. A sequence of courses and an exam for administrators and consultants.

Most learners combine formats. A recorded lesson gives the overview, a lab builds muscle memory, and a live session answers the questions that only appear when you try the task.

Practical tips

  • Start with the worker record. Almost every module depends on it.
  • Learn the search bar first. It finds tasks faster than any menu.
  • Keep a notes file of task names and where they live.
  • Practise in a sandbox, never in production pay runs.
  • Ask which security role you hold before you assume a page is missing.
  • Review one report from prompt to output before building a new one.
  • Revisit the data flows after each module. The connections become clearer with repetition.

Common questions

Do I need to learn every module?

No. Most people learn the modules their role uses and a working knowledge of how the others connect. Administrators and consultants usually go wider.

How long does it take?

The basics of navigation and Core HCM can be covered in a few days. A confident working knowledge of a payroll or finance module usually takes several weeks of practice.

Is a sandbox necessary?

It is strongly recommended. Practising in a sandbox lets you make mistakes safely and repeat a task until it feels routine.

What should I learn after the basics?

Reporting. It applies to every module and it is the skill that turns data into answers.

Where to go next

This article sits alongside the learning material gathered for the conference. You can read more about the wider theme on the education and psychology page, explore the conference tracks, or return to the important dates for the programme.