3.3 Cost Centers, Company Hierarchies & Locations

3.3 Cost Centers, Company Hierarchies & Locations

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?" The exam treats these as distinct configuration tasks (T5–T7) that you must not collapse 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.

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

Workers are typically associated with a Cost Center through their Position's Cost Center assignment (organization assignments / position restrictions). The worker inherits the cost center by filling the position. Common ways to change it:

• Edit Position Restrictions / organization assignment updates on the position.
• Reorganization or bulk assignment programs in larger redesigns.
• Staffing events that move the worker into a position already carrying the new cost center.

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.

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:

1. Creating or confirming Company organizations for each legal entity.
2. Building hierarchy relationships (parent/child or hierarchy membership per tenant design).
3. Validating that reports and integrations that depend on company roll-up use the hierarchy, not an ad-hoc list.
4. 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 on the exam language include configure company and cost center hierarchy reporting structures. Mentally separate:

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:

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

1. Create Cost Centers with finance-approved IDs before mass position load.
2. Build Cost Center Hierarchy parents that match controlling's roll-up map.
3. Create Companies for each legal entity; build Company Hierarchy for group reporting.
4. Create Locations with complete address/time zone data; build Location Hierarchies for regional views.
5. Assign these on positions (and validate inheritance to workers).
6. 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.