Study guide
3.3 Cost Centers, Company Hierarchies & Locations
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
3.3 Cost Centers, Company Hierarchies & Locations
Key Takeaways Explain This Topic AI
Create Cost Center organizations to allocate payroll and related expense to a financial cost owner; roll them up through Cost Center Hierarchies for reporting.
Company organizations represent legal entities; Company Hierarchies structure multi-entity reporting without replacing the supervisory staffing tree.
Configure company and cost center hierarchy reporting structures so finance and HCM reports roll numbers to the correct parents.
Locations store physical workplace data; Location Hierarchies group sites for reporting, security filters, and operational views.
Workers typically inherit Cost Center, Company, and Location through position organization assignments—not through personal email or manager preference settings.
Last updated: September 2026
3.3 Cost Centers, Company Hierarchies & Locations
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: Beyond the supervisory tree, HCM Fundamentals requires you to create and hierarchy Cost Centers and Companies for financial and legal reporting, and to create Locations and location hierarchies for physical workplace structure. These organization (and location) structures are assigned primarily through positions and feed payroll cost, legal entity, and site-based reporting.
Supervisory Organizations answer "who manages this person?" Cost Centers, Companies, and Locations answer "who pays for them, which legal entity employs them, and where do they work?" Treat these as distinct configuration topics from the older guide (T5–T7), rather than collapsing them into a single org tree.
Cost Center Organizations
A Cost Center is the organization type designed primarily for financial cost allocation . Payroll expense, accounts payable attributions in integrated designs, and management reporting commonly use Cost Centers as the cost owner dimension.
Creating a Cost Center
When you create a Cost Center organization, you typically define:
Name and reference ID consistent with finance's chart of accounts mapping.
Subtype if the tenant uses cost center subtypes for classification.
Hierarchy placement (parent cost center or hierarchy node) for roll-up reporting.
Roles such as Cost Center Manager or finance partners where the design uses them for approvals or visibility.
Availability / inactive status so obsolete cost centers stop receiving new assignments.
Cost Centers can be hierarchical: individual cost centers roll into Cost Center Hierarchies so finance can see Plant totals, Division totals, or Company-wide labor cost without flattening every leaf node in every report.
- Object Question it answers Example
- Cost Center Which cost owner absorbs this role's cost? CC-4500 Assembly Labor
- Cost Center Hierarchy How do leaf cost centers roll up for reporting? Manufacturing → Plant A → Assembly Labor
- Supervisory Org Who manages the people? Assembly Line 1 team
Exam trap: Region and Location are not substitutes for Cost Center. Region is geographic/territory grouping; Location is physical address. If the question asks which sub-organization type is used primarily for financial cost allocation, the answer is Cost Center .
How workers get a Cost Center
A worker's Cost Center is part of their job/position organization assignments. Defaults may originate from staffing setup. To change the current worker's assignment, use Change Organization Assignments for Worker , an approved mass organization-assignment process, or the applicable staffing event. Edit Position Restrictions changes future-occupant restrictions, not the current worker.
Personal email, "manager preferences," or free-text notes do not drive cost allocation.
Configuration scenario: Finance opens a new R&D lab cost center CC-8800. HCM creates the Cost Center org, places it under the R&D hierarchy node, and updates position organization assignments for the ten lab roles. Next payroll and labor reports charge those workers to CC-8800 without moving them in the supervisory tree—their manager remains the Lab Director under the same Sup Org.
- Company Organizations and Company Hierarchies
- Company as legal entity
A Company organization represents a legal entity —the employer of record, payroll filer, and tax-reporting entity. Multi-company tenants can maintain many Companies in one Workday environment. Workers are typically assigned to a Company through their Position , just as with Cost Center.
- Need Use Company Do not use
- Employer of record / tax entity Yes Cost Center or Region
- Internal cost owner for a team No — use Cost Center Company alone
- Manager hierarchy for hire approvals No — use Supervisory Org Company tree as people manager
- Company hierarchy reporting structures
Company Hierarchies structure how legal entities roll up for consolidated reporting and organizational analytics. Configuring a company hierarchy reporting structure means:
Creating or confirming Company organizations for each legal entity.
Building hierarchy relationships (parent/child or hierarchy membership per tenant design).
Validating that reports and integrations that depend on company roll-up use the hierarchy, not an ad-hoc list.
Keeping hierarchy maintenance in sync with legal entity changes (mergers, new subsidiaries, entity closures).
Company hierarchy does not replace Supervisory Organization for staffing events. A worker can be employed by Company "Northwind Germany GmbH" while reporting managerially through a global supervisory tree that spans multiple legal entities.
Configuration scenario: Northwind operates US Inc., UK Ltd., and Germany GmbH. HCM creates three Company orgs and a Company Hierarchy with "Northwind Group" as the top reporting node. Payroll and tax still run per legal entity; executive headcount by entity uses Company, while executive headcount by management chain uses Supervisory Org.
Cost Center Hierarchy Reporting Structures
Parallel to companies, Cost Center Hierarchies provide the financial roll-up path:
Leaf cost centers hold the assignments used on positions.
Parent nodes aggregate for P&L-style labor views and budget vs actual analyses.
Hierarchy design should match how finance already thinks about cost (by function, by plant, by product line)—not invent a second conflicting map.
Configuration tasks in practice language include configure company and cost center hierarchy reporting structures . Mentally separate:
- Hierarchy Primary consumers Typical root
- Supervisory hierarchy Managers, HR, BP routing Enterprise / segment leadership
- Company hierarchy Legal, payroll ops, entity reporting Group / holding structure
- Cost center hierarchy Finance, controlling, labor cost Function or plant cost structure
When all three are clean, the same worker can appear correctly in management, legal entity, and cost reports without duplicate "shadow" org trees maintained in spreadsheets.
- Locations and Location Hierarchies
- Creating locations
A Location in Workday represents a physical workplace (or logical site) with address and related attributes—not an accounting entity. Locations support:
Position and hiring restrictions (where the role sits).
Local practices, time zones, and operational reporting.
Security and business process conditions that filter by location.
Worker workplace data for compliance and facilities coordination.
When creating locations, capture accurate address components, time zone, and any location usage flags the tenant relies on. Inactive or closed sites should be end-dated or inactivated so they stop appearing as default options.
- Location hierarchies
- Location Hierarchies group individual locations into higher-level nodes—for example: Americas
- ├── United States
- │ ├── New York Metro
- │ │ ├── NYC HQ – Floor 12
- │ │ └── Brooklyn Warehouse
- │ └── Texas
- │ └── Austin Office
- └── Canada
- └── Toronto Office
Uses of location hierarchies include regional headcount, facilities planning, and security or BP filters that apply to "all US sites" without listing every building. Creating the hierarchy is separate from creating each leaf location; both are in-scope configuration skills.
Exam trap: Do not treat Location as the financial cost owner. "Which type allocates cost?" → Cost Center. "Which stores physical address / site?" → Location.
Putting Assignments Together on the Position
A realistic position might carry:
- Assignment Example value Driven process examples
- Supervisory Organization Assembly Line 1 Manager approvals, staffing
- Company Northwind US Inc. Employer, tax, entity rules
- Cost Center CC-4500 Assembly Labor Labor cost reporting
- Region North America Territory analytics
- Location Plant A – Building 2 Workplace, local rules
Changing one dimension should be intentional:
Move to a new manager → supervisory (often Reorganization or Change Job / position move).
Charge cost to a new budget owner → Cost Center on the position.
Transfer to another legal employer → Company (often with broader staffing/legal process).
Relocate desk/site → Location (and possibly related compensation or local rule impacts).
Configuration Quality Checklist
Create Cost Centers with finance-approved IDs before mass position load.
Build Cost Center Hierarchy parents that match controlling's roll-up map.
Create Companies for each legal entity; build Company Hierarchy for group reporting.
Create Locations with complete address/time zone data; build Location Hierarchies for regional views.
Assign these on positions (and validate inheritance to workers).
Never "fix" a missing Cost Center by misusing Supervisory Org or Location.
If you can create these objects, hang them on hierarchies, and explain how workers inherit them through positions, you have covered the core of T5–T7 for HCM Fundamentals Organizations.