peopletechguide.com

Tag: workday cost center

  • Build Workday Organization Hierarchy from Scratch

    Here’s a confession from every Workday implementation:

    • Week 1, someone asks: “How should we structure our organizations?”
    • Week 3, someone says: “Let’s just copy our current org chart.”
    • Week 8, someone realizes: “Wait, this doesn’t work the way we thought.”
    • Week 20, someone admits: “We need to redesign the entire organization structure.”

    I’ve watched this pattern repeat across dozens of Workday implementations. Teams rush to build organization hierarchies without understanding how they actually work in Workday. They treat Supervisory Orgs like departments, Cost Centers like teams, and wonder why security breaks, approvals route incorrectly, and reports pull the wrong data.

    The truth is this: your organization hierarchy is the structural foundation of your entire Workday tenant. Get it right from day one, and Workday runs smoothly. Get it wrong, and you’ll spend months fixing downstream consequences.

    This guide walks you through building Workday organization hierarchies from scratch. We’ll cover Supervisory Organizations, Cost Centers, superior org logic, manager assignments, and the design decisions that separate clean implementations from messy ones.

    Let’s build it right the first time.

    Why Organization Hierarchy Matters in Workday

    Organizations in Workday are not just labels or groupings. They are active system objects that control critical functionality across your entire tenant.

    Your organization hierarchy determines:

    Security and Data Access:

    • Which HR Partners can see which workers
    • Which Payroll Partners can process payroll for which teams
    • Which managers inherit role-based permissions
    • How domain security scopes access by organization

    Business Process Routing:

    • Where hiring approvals go
    • Who approves compensation changes
    • How time off requests route to managers
    • Which stakeholders review terminations

    Reporting and Analytics:

    • How you slice headcount by department, location, or business unit
    • How Finance reports costs by Cost Center
    • How HR tracks diversity metrics by organization
    • How leadership views organizational spans of control

    Financial Postings:

    • Where worker costs land in the General Ledger
    • How budget vs. actuals roll up by Cost Center
    • Which organizations own spend and expenses

    Get your organization hierarchy wrong, and all of these break. Security fails. Approvals route incorrectly. Reports pull bad data. Finance can’t reconcile costs.

    The time to fix organization design is before you load workers, not after.

    Understanding Workday Organization Types

    Before we build anything, let’s clarify what we’re building. Workday provides several organization types, but two are critical for most implementations:

    Supervisory Organizations

    What They Are:
    Supervisory Organizations (Sup Orgs) define your reporting structure. They group workers who report to the same manager and form a hierarchical tree that mirrors your organizational chart.

    What They Control:

    • Worker reporting relationships (who reports to whom)
    • Business process routing (hiring, promotions, terminations, comp changes)
    • Role-based security (HR Partner, Payroll Partner roles are assigned at the Supervisory Org level)
    • Approval chains (time off, expenses, requisitions route through the Supervisory Org hierarchy)
    • Manager self-service access (managers can see and manage their team)

    Key Point:
    If your Supervisory Org tree is wrong, everything downstream breaks. Approvals route to the wrong manager. Security grants access to the wrong workers. Reports show incorrect reporting lines.

    Cost Centers

    What They Are:
    Cost Centers represent financial responsibility. They are the organizational unit that owns the budget, tracks spend, and posts to the General Ledger.

    What They Control:

    • Budgeting and forecasting (Cost Centers are the primary dimension for budget allocation)
    • Spend analytics (requisitions, expenses, journal entries route to Cost Center managers)
    • General Ledger posting (worker costs post to the GL based on Cost Center assignment)
    • Financial reporting (Finance reports actuals vs. budget by Cost Center hierarchy)

    Key Point:
    Cost Centers tell Finance who owns the numbers. Supervisory Orgs show reporting lines. Cost Centers show financial lines. These are often (but not always) the same.

    The Foundation: Superior Organization Logic

    Every organization hierarchy in Workday is built using superior organization relationships. This is the single most important concept to understand before you create a single organization.

    How Superior Org Logic Works

    In Workday, organizations don’t exist in isolation. Every organization (except the top-level organization) has a superior organization above it in the hierarchy.

    Think of it like a family tree:

    • Parent Org (superior)
    • Child Org (subordinate to the parent)
    • Grandchild Org (subordinate to the child, which is subordinate to the parent)

    When you create an organization, you define its superior organization. Workday automatically builds the hierarchy tree based on these relationships.

    Example:

    textCEO Organization (top-level, no superior)
├── Sales Organization (superior: CEO Organization)
│   ├── Sales North America (superior: Sales Organization)
│   └── Sales EMEA (superior: Sales Organization)
├── Engineering Organization (superior: CEO Organization)
│   ├── Engineering Product (superior: Engineering Organization)
│   └── Engineering Platform (superior: Engineering Organization)
└── Finance Organization (superior: CEO Organization)

    Each organization points to its superior. Workday builds the tree automatically.

    Why Superior Org Logic Matters

    Superior org relationships control:

    • Hierarchy roll-ups: Reports can roll up headcount, costs, and data by superior org
    • Security inheritance: Role-based security can inherit down the org tree
    • Approval routing: Some business processes route approvals up the superior org chain
    • Reporting structures: Organizational charts and workforce planning tools use superior org logic

    If you assign the wrong superior org, the hierarchy breaks. Workers appear in the wrong branch of the tree. Reports pull incorrect data. Security grants access to the wrong teams.

    Step-by-Step: Building Your First Supervisory Organization Hierarchy

    Let’s walk through building a Supervisory Organization hierarchy from scratch. We’ll use a realistic example: a mid-sized company with 500 employees across Sales, Engineering, Finance, and HR.

    Step 1: Design the Hierarchy on Paper First

    Before you touch Workday, map out your organization structure on paper (or a spreadsheet). Answer these questions:

    What are your top-level organizations?

    • CEO
    • Sales
    • Engineering
    • Finance
    • HR
    • Operations

    What are the subordinate organizations under each?

    • Sales: Sales North America, Sales EMEA, Sales APAC
    • Engineering: Engineering Product, Engineering Platform, Engineering Data
    • Finance: Finance FP&A, Finance Accounting, Finance Tax
    • HR: HR Business Partners, HR Talent Acquisition, HR Payroll

    Who are the managers for each organization?

    • CEO Org: Jane Smith (CEO)
    • Sales Org: Tom Johnson (VP Sales)
    • Sales North America: Sarah Lee (Director Sales NA)
    • Engineering Org: Mike Chen (VP Engineering)

    How many levels deep is your hierarchy?

    • Level 1: CEO
    • Level 2: VPs (Sales, Engineering, Finance, HR)
    • Level 3: Directors (by function or region)
    • Level 4: Managers
    • Level 5: Individual Contributors (optional: some orgs put ICs in their own leaf orgs)

    Design Principles:

    • Keep hierarchies shallow (3-5 levels maximum, avoid 7+ levels)
    • Align with reporting lines (Supervisory Orgs follow who reports to whom, not budget ownership)
    • Use clear naming conventions (e.g., “Sales – North America” not “NA Sales Team”)
    • Plan for growth (leave room for future orgs without redesigning the entire tree)

    Step 2: Create the Top-Level Organization

    We’ll start by creating the CEO Organization (the top of the tree).

    Navigate to Workday:

    1. Search for Create Supervisory Organization
    2. Click the task to open it

    Fill in Organization Details:

    • Organization Name: CEO Organization
    • Organization Code: ORG-CEO (create a unique code for reference)
    • Organization Type: Supervisory
    • Superior Organization: Leave blank (this is the top-level org, it has no superior)
    • Manager: Jane Smith (search by name or Employee ID)
    • Default Cost Center: (optional, can assign a default Cost Center for workers in this org)
    • Effective Date: Your go-live date or the date the org becomes active

    Click OK to submit.

    Workday creates the organization and assigns Jane Smith as the manager.

    Key Points:

    • The top-level organization has NO superior organization
    • Every other organization in your hierarchy will have a superior
    • The manager you assign becomes the default approver for workers in this org
    • Organization Code is your external reference ID (use it for EIB loads and integrations)

    Step 3: Create Second-Level Organizations (VPs)

    Now we’ll create the VP-level organizations that report to the CEO.

    Create Sales Organization:

    1. Navigate to Create Supervisory Organization
    2. Fill in:
      • Organization Name: Sales Organization
      • Organization Code: ORG-SALES
      • Organization Type: Supervisory
      • Superior Organization: CEO Organization (search and select)
      • Manager: Tom Johnson (VP Sales)
      • Effective Date: Same as CEO org
    3. Click OK

    Repeat for other VP-level orgs:

    • Engineering Organization (superior: CEO Organization, manager: Mike Chen)
    • Finance Organization (superior: CEO Organization, manager: Lisa Brown)
    • HR Organization (superior: CEO Organization, manager: David Kim)

    Your hierarchy now looks like this:

    textCEO Organization (Jane Smith)
├── Sales Organization (Tom Johnson)
├── Engineering Organization (Mike Chen)
├── Finance Organization (Lisa Brown)
└── HR Organization (David Kim)

    Step 4: Create Third-Level Organizations (Directors)

    Now we’ll create Director-level organizations under each VP org.

    Create Sales North America:

    1. Navigate to Create Supervisory Organization
    2. Fill in:
      • Organization Name: Sales – North America
      • Organization Code: ORG-SALES-NA
      • Organization Type: Supervisory
      • Superior Organization: Sales Organization (NOT CEO Organization)
      • Manager: Sarah Lee (Director Sales NA)
      • Effective Date: Same as parent org
    3. Click OK

    Repeat for other Director orgs:

    • Sales – EMEA (superior: Sales Organization)
    • Sales – APAC (superior: Sales Organization)
    • Engineering – Product (superior: Engineering Organization)
    • Engineering – Platform (superior: Engineering Organization)
    • Finance – FP&A (superior: Finance Organization)
    • Finance – Accounting (superior: Finance Organization)

    Your hierarchy now looks like this:

    textCEO Organization (Jane Smith)
├── Sales Organization (Tom Johnson)
│   ├── Sales - North America (Sarah Lee)
│   ├── Sales - EMEA (John Davis)
│   └── Sales - APAC (Amy Wong)
├── Engineering Organization (Mike Chen)
│   ├── Engineering - Product (Alex Garcia)
│   └── Engineering - Platform (Maria Lopez)
├── Finance Organization (Lisa Brown)
│   ├── Finance - FP&A (Robert Taylor)
│   └── Finance - Accounting (Jennifer White)
└── HR Organization (David Kim)

    Step 5: Create Fourth-Level Organizations (Managers)

    Continue building down the hierarchy for Manager-level orgs.

    Example: Create Sales – NA East:

    1. Navigate to Create Supervisory Organization
    2. Fill in:
      • Organization Name: Sales – NA East
      • Organization Code: ORG-SALES-NA-EAST
      • Organization Type: Supervisory
      • Superior Organization: Sales – North America (NOT Sales Organization)
      • Manager: James Wilson (Sales Manager East)
    3. Click OK

    Continue until your full hierarchy is built.

    Step 6: Validate the Hierarchy Tree

    After creating all organizations, validate that the hierarchy is correct.

    Navigate to:

    1. Search for View Supervisory Organization
    2. Select CEO Organization
    3. Click Organization Chart or View Hierarchy

    Workday displays your full org tree visually.

    Check for:

    • All organizations appear in the correct superior/subordinate relationships
    • No orphaned orgs (orgs that don’t appear anywhere in the tree)
    • Managers are assigned correctly
    • Naming conventions are consistent

    Common Issues:

    • Org appears in the wrong branch: You assigned the wrong superior org. Edit the org and correct the superior.
    • Org doesn’t appear at all: You forgot to assign a superior (unless it’s the top-level org). Edit and add superior.
    • Circular reference error: Org A is superior to Org B, Org B is superior to Org C, Org C is superior to Org A. Fix by breaking the circular reference.

    Step-by-Step: Building Your Cost Center Hierarchy

    Cost Centers work the same way as Supervisory Organizations, but they represent financial responsibility instead of reporting lines.

    Step 1: Design the Cost Center Structure

    Work with Finance to design the Cost Center hierarchy. It should align with:

    • Your Chart of Accounts structure
    • Budget ownership and responsibility
    • How Finance wants to report actuals vs. budget

    Example Cost Center Structure:

    textCorporate Cost Center (top-level)
├── Sales Cost Center
│   ├── Sales NA Cost Center
│   ├── Sales EMEA Cost Center
│   └── Sales APAC Cost Center
├── Engineering Cost Center
│   ├── Engineering Product Cost Center
│   └── Engineering Platform Cost Center
├── Finance Cost Center
└── HR Cost Center

    Key Decision:
    Do Cost Centers mirror Supervisory Orgs exactly? Or do they differ?

    • Same structure: Easier to maintain, simpler for users to understand
    • Different structure: More flexible for Finance reporting, but adds complexity

    Step 2: Create Cost Centers

    The process is identical to creating Supervisory Organizations, but you use Create Cost Center task instead.

    Create Top-Level Cost Center:

    1. Search for Create Cost Center
    2. Fill in:
      • Cost Center Name: Corporate Cost Center
      • Cost Center Code: CC-CORP
      • Organization Type: Cost Center
      • Superior Organization: Leave blank (top-level)
      • Manager: CFO or Finance Director
      • Effective Date: Go-live date
    3. Click OK

    Create Subordinate Cost Centers:
    Repeat for each Cost Center, assigning the correct superior Cost Center.

    Step 3: Assign Cost Centers to Workers

    Once Cost Centers are created, assign them to workers.

    Option 1: Assign Default Cost Center at Supervisory Org Level

    • Navigate to Edit Supervisory Organization
    • Set Default Cost Center for the org
    • All workers in that Supervisory Org inherit the Cost Center automatically

    Option 2: Assign Cost Center Individually

    • Navigate to Change Job for a worker
    • Assign Cost Center on the Job Details page
    • This overrides the default Cost Center from Supervisory Org

    Critical Design Decisions

    Decision 1: Where Does the Manager Sit?

    This is the most common org hierarchy mistake:

    Should the manager sit INSIDE the org they manage, or in the SUPERIOR org?

    The Right Answer:
    Managers should sit in the superior organization of the org they manage, NOT inside it.

    Example:

    CORRECT:

    textSales Organization (Tom Johnson, VP Sales)
├── Sales - North America (Sarah Lee, Director Sales NA)
│   ├── James Wilson (Sales Manager, reports to Sarah)
│   ├── Emily Davis (Sales Rep, reports to James)
│   └── Mark Thompson (Sales Rep, reports to James)

    Tom Johnson sits in CEO Organization (superior to Sales Organization).
    Sarah Lee sits in Sales Organization (superior to Sales – North America).
    James Wilson sits in Sales – North America (manages reps in his own org).

    INCORRECT:

    textSales Organization (Tom Johnson sits HERE, manages Sales Org)
├── Sales - North America (Sarah Lee sits HERE, manages Sales NA)

    Why This Matters:

    • Security inheritance works correctly when managers sit in superior orgs
    • Approval routing flows up the chain properly
    • Role-based access grants managers permission to see subordinate orgs
    • Prevents weird permission overlaps and conflicts

    Decision 2: How Deep Should the Hierarchy Go?

    Recommended Depth:
    3-5 levels maximum

    Why:

    • Deep hierarchies (7+ levels) slow approvals
    • Every approval step adds delay and complexity
    • Reporting becomes harder to navigate
    • Security configuration gets messy

    If You Have More Than 5 Levels:

    • Flatten the hierarchy by combining levels
    • Use Custom Organizations for matrix relationships instead of adding Supervisory Org levels
    • Consider whether every level truly represents a distinct manager with approval authority

    Decision 3: Should Individual Contributors Have Their Own Orgs?

    Option 1: ICs Report Directly to Manager’s Org

    • Manager’s org contains both the manager and their direct reports
    • Simpler structure, fewer orgs to maintain
    • Works well for small teams (manager + 3-10 ICs)

    Option 2: ICs Have Their Own Subordinate Org

    • Manager sits in superior org, ICs sit in subordinate org
    • More granular reporting and security scoping
    • Works well for large teams (manager + 20+ ICs) or when you need to segment by sub-team

    Most Common Approach:
    Option 1 for small teams, Option 2 for large teams.

    Decision 4: Naming Conventions

    Use clear, consistent naming conventions for all organizations:

    Good Examples:

    • Sales – North America
    • Engineering – Product
    • Finance – Accounting
    • HR – Talent Acquisition

    Bad Examples:

    • NA Sales Team (inconsistent format)
    • Eng Prod (abbreviations aren’t clear)
    • Accounting Dept (mixing “Finance” and “Dept”)

    Best Practices:

    • Start with function or department name
    • Add geography, sub-function, or team type after a separator (dash or comma)
    • Avoid abbreviations unless universally understood
    • Keep names concise (under 50 characters)
    • Use title case for readability

    Assigning Workers to Organizations

    Once your org hierarchy is built, you need to assign workers to organizations.

    For New Hires

    When you hire a new worker, you assign their Supervisory Organization and Cost Center on the Hire Employee task:

    1. Navigate to Hire Employee
    2. Fill in worker details
    3. In Job Details section:
      • Supervisory Organization: Select the org the worker reports to
      • Cost Center: Select the Cost Center for financial tracking
      • Manager: Workday assigns the manager automatically based on Supervisory Org
    4. Submit and approve

    For Existing Workers

    When you need to move a worker to a new organization, use Change Job:

    1. Navigate to Change Job
    2. Select the worker
    3. In Organizations section:
      • Update Supervisory Organization (if reporting line changes)
      • Update Cost Center (if financial responsibility changes)
    4. Set Effective Date
    5. Submit for approval

    Common Mistakes and How to Avoid Them

    Mistake 1: Building Orgs Based on Locations or Departments Instead of Reporting Lines

    The Problem:
    Teams create Supervisory Orgs for “Seattle Office” or “Marketing Department” without thinking about who reports to whom.

    What Happens:
    Workers in the same office report to different managers, but they’re all in the same Supervisory Org. Approvals route incorrectly. Security breaks.

    The Fix:
    Supervisory Orgs follow reporting relationships. If workers in Seattle report to different managers, they should be in different Supervisory Orgs. Use Locations for geography and Custom Orgs for departments that cross reporting lines.

    Mistake 2: Creating Organizations After Loading Workers

    The Problem:
    Team loads 500 workers into Workday, then realizes they need to create organizations. Now they have to mass-update 500 worker records to assign orgs.

    What Happens:
    Mass updates through Change Job trigger 500 approval workflows. Data quality suffers. Rework takes weeks.

    The Fix:
    Build your organization hierarchy before you load workers. Orgs should exist in Workday before the first worker is hired or migrated.

    Mistake 3: Not Planning for Future Growth

    The Problem:
    You build a hierarchy for today’s 500 employees. Company grows to 2,000 employees. Hierarchy doesn’t scale. You need to restructure.

    What Happens:
    Mass org reassignments. Business process disruptions. Reports break. Security needs reconfiguration.

    The Fix:
    Design your hierarchy for scale. Leave room for new regions, new departments, new functions. Build flexibility into the structure from day one.

    Mistake 4: Inconsistent Superior Org Assignments

    The Problem:
    Sales – North America reports to Sales Organization. Sales – EMEA accidentally reports to CEO Organization (skipping Sales Organization).

    What Happens:
    Hierarchy tree looks broken. Roll-up reports are incorrect. Tom Johnson (VP Sales) can’t see EMEA team data because they don’t roll up to his org.

    The Fix:
    Validate superior org assignments carefully. Use View Supervisory Organization Hierarchy to visually check the tree structure before go-live.

    Workday Tasks for Organization Management

    Create Organizations:

    • Create Supervisory Organization (build Supervisory Org hierarchy)
    • Create Cost Center (build Cost Center hierarchy)
    • Create Region (build geographic groupings)
    • Create Custom Organization (build matrix or project-based orgs)

    Edit Organizations:

    • Edit Supervisory Organization (change superior, manager, or org details)
    • Edit Cost Center (change superior, manager, or cost center details)
    • Inactivate Organization (deprecate old orgs without deleting them)

    View and Validate:

    • View Supervisory Organization (see org details and hierarchy)
    • View Organization Chart (visualize reporting structure)
    • View Cost Center Hierarchy (see Cost Center roll-ups)

    Assign Organizations to Workers:

    • Hire Employee (assign orgs for new hires)
    • Change Job (update orgs for existing workers)
    • Change Organization Assignments (bulk update org assignments)

    Final Thoughts

    Building a Workday organization hierarchy from scratch isn’t complicated. It just requires thoughtful planning and disciplined execution.

    Start with these steps:

    1. Design the hierarchy on paper first (align with stakeholders)
    2. Use superior org logic correctly (every org points to its superior)
    3. Keep hierarchies shallow (3-5 levels maximum)
    4. Follow clear naming conventions (consistent, readable, scalable)
    5. Build orgs BEFORE loading workers (avoid mass updates later)
    6. Validate the hierarchy tree before go-live (check superior relationships)

    Get your organization hierarchy right from day one, and everything else in Workday works smoothly. Security flows correctly. Approvals route properly. Reports pull accurate data. Finance can reconcile costs.

    Get it wrong, and you’ll spend months untangling org assignments, fixing security, and rebuilding hierarchies.

    Start simple. Plan for scale. Document everything.

  • Understanding Workday Organization Types Right

    Every Workday implementation team faces the same question in Week 1: “How should we structure our organizations?”

    And almost every time, someone says: “They’re all basically the same, right? Just different names for groups of people.”

    Wrong.

    Choosing the wrong organization type is one of the fastest ways to create security gaps, break approval workflows, and turn reporting into a nightmare. Workday organizations are not interchangeable. Each type serves a specific functional purpose, drives distinct system behaviors, and impacts everything from business processes to financial postings.​

    If you design your organization structure incorrectly from day one, you will spend months—or years—fixing the downstream consequences.

    This guide explains exactly what each Workday organization type does, when to use it, and how to avoid the most common mistakes that break Workday designs.

    Why Organization Design Matters in Workday

    Organizations in Workday are not just labels. They are the structural foundation of your entire tenant.​

    Organizations control:

    • Security domains – Who can see and edit which worker data
    • Business process routing – Where approvals go and who signs off
    • Reporting hierarchies – How you analyze workforce data
    • Financial postings – Where costs land in the General Ledger
    • Role-based access – Which managers inherit permissions down the hierarchy​

    Get your organization design right early, and Workday runs smoothly. Get it wrong, and you will face:

    • Broken approval chains that route to the wrong manager
    • Security domains that expose sensitive data or lock out HR
    • Reports that pull incorrect headcount or cost data
    • GL postings that land in the wrong cost center or company
    • Rework that requires mass updates, org redesigns, and business process changes​

    The time to fix organization design is before go-live, not after.

    The Core Workday Organization Types

    Workday delivers several organization types out of the box. Each one has a distinct purpose, distinct configuration tasks, and distinct domain security.​

    Let’s break down the big three—and why they are not interchangeable.

    1. Supervisory Organizations: The Backbone of Your Workday Experience

    What They Are:
    Supervisory Organizations (Sup Orgs) define your reporting structure. They group workers who report to the same manager and form a hierarchical tree that mirrors your organizational chart.​

    What They Control:
    Supervisory Orgs are the most powerful organization type in Workday HCM because they drive:

    • Worker reporting relationships – Who reports to whom
    • Business process routing – Hiring, promotions, terminations, job changes, and compensation all route through the Supervisory Org hierarchy​
    • Role-based security – Roles like “HR Partner” or “Manager” are assigned at the Supervisory Org level and inherit down the tree by default​
    • Approval chains – Time off, expenses, and other transactions route to the manager of the worker’s Supervisory Org​
    • Advanced Compensation workflows – Comp planning, merit increases, and bonus allocation follow the Supervisory Org structure

    Why This Matters:
    If your Supervisory Org tree is wrong, everything downstream breaks.​

    Example: A worker sits in the wrong Supervisory Org. Their time-off request routes to a manager in another department. That manager has no context, delays approval, and the worker misses their flight.

    That is not a process problem. That is an organization design problem.

    Key Design Rules:

    • Managers should sit in the superior organization of the org they manage, not inside it​
    • Every Supervisory Org must have one assigned manager​
    • Use Supervisory Org subtypes (e.g., “Corporate,” “Field,” “Shared Services”) to segment different parts of the business without creating separate trees​
    • Default Cost Center can be assigned at the Supervisory Org level to streamline financial defaults​

    Common Mistakes:

    • Creating too many levels (7+ layers) that slow approvals and complicate security
    • Assigning managers to positions inside the org they manage, which creates inheritance conflicts
    • Using Supervisory Orgs to track project teams or matrix relationships (use Custom Orgs instead)

    2. Cost Centers: Your Financial Source of Truth

    What They Are:
    Cost Centers represent financial responsibility. They are the organizational unit that owns the budget, tracks spend, and posts to the General Ledger.​

    What They Control:

    • Budgeting and forecasting – Cost Centers are the primary dimension for budget allocation in Workday
    • Spend analytics – Purchase requisitions, expense reports, and journal entries route to Cost Center managers for financial approval​
    • General Ledger posting – Worker costs (salary, benefits, taxes) post to the GL based on the worker’s Cost Center assignment
    • Financial reporting – Finance teams report actuals vs. budget by Cost Center hierarchy

    Why This Matters:
    Cost Centers tell Finance who owns the numbers.​

    Supervisory Orgs show the reporting line. Cost Centers show the financial line.

    These are often—but not always—the same.

    Example: A worker reports to a manager in the Sales Supervisory Org but is funded by the Marketing budget. Their Supervisory Org is Sales. Their Cost Center is Marketing. Workday tracks both, and reports accordingly.

    Key Design Rules:

    • Assign one primary Cost Center per worker (Workday supports split costing, but keep it simple at first)
    • Cost Center hierarchy should mirror your chart of accounts structure
    • Cost Center managers approve financial transactions (requisitions, expenses, journals) while Supervisory Org managers approve HR transactions (time off, job changes)​
    • Use Cost Center View security to control which Finance users can see which cost data​

    Common Mistakes:

    • Conflating Supervisory Orgs and Cost Centers (“They’re the same thing, right?”)
    • Not assigning a Cost Center manager, which breaks expense and requisition approvals​
    • Creating Cost Centers at too granular a level, which clutters GL reporting

    3. Companies: Legal Entities That Drive Financial Structures

    What They Are:
    Companies represent your legal entities. In Workday, a Company is the top-level organization for Financials, Payroll, and Benefits.​

    What They Control:

    • Legal entity assignment – Every worker must be assigned to a Company
    • Payroll processing – Payroll runs by Company
    • Benefits eligibility – Benefit plans are configured by Company
    • Chart of Accounts – The General Ledger is structured by Company, and Company is the first dimension in every GL posting​
    • Tax and compliance – Legal reporting (W-2s, statutory filings, labor law compliance) is Company-specific

    Why This Matters:
    If you operate in multiple countries or have multiple legal entities (e.g., a holding company with subsidiaries), you must configure each as a separate Company in Workday.

    Key Design Rules:

    • One Company per legal entity
    • Company hierarchy can roll up to a parent for consolidated reporting
    • Do not create “fake” Companies for reporting convenience—use Custom Orgs or Regions instead
    • Ensure workers are assigned to the correct Company for tax and payroll purposes

    Common Mistakes:

    • Using “Company” as a proxy for “division” or “business unit” (use Supervisory Orgs or Custom Orgs instead)
    • Not aligning Company structure with your legal entity structure, which breaks tax and statutory compliance

    4. Regions: Geographic Groupings

    What They Are:
    Regions group workers, locations, and organizations by geography.​

    What They Control:

    • Geographic reporting – Headcount, costs, and workforce analytics by region
    • Regional compliance – Policies, business processes, and benefits that vary by geography
    • Location-based security – Regional HR partners can be granted access to workers in their assigned region
    • Regional management layers – Some organizations use Region hierarchies to create geographic leadership structures (e.g., EMEA Director, APAC VP)

    Why This Matters:
    If you operate globally, Regions help you segment workers, track regional performance, and assign region-specific HR support without creating duplicate Supervisory Org trees.​

    Example: A global company has one Supervisory Org hierarchy for reporting lines but uses Regions to group workers into North America, EMEA, APAC, and LATAM for regional HR team assignments and compliance tracking.

    Key Design Rules:

    • Use Regions for geography, not for business units or functions
    • Region assignment can inherit from Location, or be assigned manually
    • Keep Region hierarchies simple (2-3 levels maximum)
    • Use Regions in security policies to grant HR partners access to workers in their geography​

    Common Mistakes:

    • Creating Regions for non-geographic groupings (e.g., “Remote Workers” as a Region)
    • Overcomplicating Region hierarchies with too many sub-levels
    • Not using Regions at all, then manually maintaining geographic access lists

    5. Custom Organizations: Flexibility for Everything Else

    What They Are:
    Custom Organizations are user-defined organizations that capture any business dimension not covered by Supervisory Orgs, Cost Centers, Companies, or Regions.​

    What They Control:
    Custom Orgs are the Swiss Army knife of Workday organizations. Use them to track:

    • Matrix reporting relationships – A worker reports to one manager (Supervisory Org) but also works for a project manager (Custom Org: Project Team)​
    • Product lines, business units, or divisions – Groupings that cross Supervisory Org boundaries
    • Project teams – Temporary or permanent project assignments that need their own hierarchy
    • Centers of Excellence, shared services, or practice groups – Functional groupings that span multiple Supervisory Orgs
    • Gigs or flex work – Track workers assigned to short-term initiatives or temporary teams​
    • Work Councils or employee representative bodies – Labor governance structures required in certain countries​

    Why This Matters:
    Most businesses are not purely hierarchical. You have matrix relationships, cross-functional teams, project-based work, and shared resources.​

    Custom Orgs let you track all of that without polluting your Supervisory Org tree.

    Example: A product manager reports to the VP of Product (Supervisory Org) but is assigned to the “Mobile App Relaunch” project team (Custom Org). Workday tracks both relationships. The project lead can run reports on their team, but approvals and security still flow through the Supervisory Org.

    Key Design Rules:

    • Use Custom Orgs for reporting and analysis, not for routing or security (unless absolutely necessary)​
    • Create Custom Org Types (e.g., “Project Team,” “Practice Group,” “Business Unit”) to keep them organized​
    • Custom Orgs can be single-level or hierarchical—use hierarchies when you need roll-up reporting
    • Workers can belong to multiple Custom Orgs simultaneously​
    • Avoid using Custom Orgs to fix broken Supervisory Org designs—fix the Supervisory Org instead

    Common Mistakes:

    • Using Custom Orgs for approval routing (this gets complicated fast)
    • Creating too many Custom Org Types, which clutters reporting
    • Assigning workers to Custom Orgs without a clear business use case or reporting need​

    Other Organization Types You Should Know

    Work Councils

    Represent employee representative bodies, works councils, or labor governance structures required in certain countries (especially in Europe). Use Work Councils when you need to track which workers are represented by which council for compliance, reporting, or business process routing.​

    Matrix Organizations

    A legacy organization type used to track dual reporting relationships. In modern Workday implementations, Custom Organizations are preferred because they offer more flexibility and cleaner reporting.​

    Pay Groups

    Not technically an organization, but often confused with one. Pay Groups define payroll frequency (weekly, biweekly, monthly) and are assigned to workers to control payroll processing schedules.

    Project Organizations

    Used in Workday Projects (part of Financials). If you track billable projects, Project Orgs define the project hierarchy for time tracking, billing, and project reporting.

    How to Choose the Right Organization Type

    Here is the simple decision tree most Workday practitioners use:

    If you need to track…Use this organization type
    Reporting lines and manager hierarchySupervisory Organization
    Financial responsibility and budget ownershipCost Center
    Legal entities for payroll, tax, and benefitsCompany
    Geographic groupings (countries, regions)Region
    Matrix teams, projects, business units, or flex workCustom Organization
    Labor councils or employee representative bodiesWork Council

    Golden Rule:
    Use the right org for the right purpose. Do not force one organization type to do the job of another.​

    Why Most Workday Designs Fail at Organization Structure

    Here are the three most common failures I see in Workday organization design:

    1. Conflating Supervisory Orgs and Cost Centers

    Teams assume these are the same thing. They are not.​

    Supervisory Orgs define reporting relationships. Cost Centers define financial responsibility.

    Sometimes they align. Often they do not.

    Example: A sales operations analyst reports to the Head of Sales Operations (Supervisory Org) but is funded by the Marketing budget (Cost Center). If you force Supervisory Orgs and Cost Centers to be identical, you lose the ability to track this split.​

    Fix: Design Supervisory Orgs for reporting lines. Design Cost Centers for financial ownership. Let Workday track both.​

    2. Designing Organizations After Go-Live

    Organizations are not configuration. They are foundational data.​

    You cannot “add them later” without mass updates, org reassignments, and business process changes.

    Fix: Lock down organization design in Week 1 of your implementation. Test it against your business processes, security model, and reporting requirements before you load workers.​

    3. Using Custom Orgs as a Bandaid for Broken Supervisory Org Design

    If your Supervisory Org tree does not reflect reality, the answer is not to create a Custom Org to “fix” it.​

    The answer is to fix the Supervisory Org.

    Fix: Use Custom Orgs for matrix relationships, project teams, and cross-functional groupings—not as workarounds for bad Supervisory Org design.

    Workday Organization Design Best Practices

    1. Design for Scale, Not for Today

    Your organization structure will change. Plan for growth, mergers, acquisitions, and reorganizations from day one.​

    2. Keep Supervisory Org Hierarchies Shallow

    Avoid 7+ levels of management. Deep hierarchies slow approvals, complicate security, and frustrate managers.​

    3. Align Cost Centers with Your Chart of Accounts

    Finance should own Cost Center design. Cost Centers must map cleanly to your GL structure.​

    4. Use Custom Orgs Sparingly

    Every Custom Org Type you create adds complexity to reporting and maintenance. Only create them when you have a clear business use case.​

    5. Test Organization Design Against Security and Business Processes

    Before go-live, validate:

    • Does security inheritance work the way you expect?
    • Do approvals route to the right managers?
    • Can Finance run budget vs. actuals by Cost Center?
    • Can HR pull headcount reports by Supervisory Org?​

    6. Document Your Organization Strategy

    Write down the purpose of each organization type, who owns updates, and how workers get assigned. This becomes your operating manual for post-go-live org maintenance.​

    Real-World Example: Designing Organizations for a Global Company

    Let’s walk through a realistic scenario.

    Company: GlobalTech, a 5,000-employee software company with offices in the US, UK, Germany, India, and Australia.

    Business Requirements:

    • Workers report to functional managers (Engineering, Sales, Marketing, Finance)
    • Costs are tracked by department and region
    • The company has three legal entities (US Inc., UK Ltd., Australia Pty)
    • Product teams are cross-functional and span multiple departments
    • Regional HR teams need access to workers in their geography

    Organization Design:

    Org TypeDesign Decision
    CompanyThree Companies: GlobalTech US Inc., GlobalTech UK Ltd., GlobalTech AU Pty (one per legal entity)
    Supervisory OrgFunctional hierarchy: CEO → VPs (Eng, Sales, Marketing, Finance) → Directors → Managers → ICs
    Cost CenterDepartment-based Cost Centers (aligned with GL): Engineering, Sales EMEA, Sales APAC, Marketing, Finance, IT
    RegionFour Regions: Americas, EMEA, APAC, ANZ (for geographic reporting and HR access)
    Custom OrgProduct Teams (Custom Org Type) with one Custom Org per product line (Mobile, Cloud, Enterprise, Data) for cross-functional project tracking

    Why This Works:

    • Supervisory Orgs define clear reporting lines and drive approvals​
    • Cost Centers align with Finance’s budget structure​
    • Companies align with legal entities for payroll and tax
    • Regions enable geographic reporting and HR access​
    • Custom Orgs track product team assignments without disrupting the Supervisory Org tree​

    Final Thoughts: Get Organizations Right the First Time

    Organizations are the foundation of your Workday tenant.​

    Get them right, and Workday runs smoothly. Security works. Approvals route correctly. Reports pull accurate data. Finance trusts the numbers.

    Get them wrong, and you spend months fixing broken processes, reassigning workers, and redesigning hierarchies.​

    The time to design organizations is before go-live, not after.

    Use Supervisory Orgs for reporting lines and workflow routing. Use Cost Centers for financial ownership. Use Companies for legal entities. Use Regions for geography. Use Custom Orgs for everything else.​

    And never, ever assume that all organizations are “basically the same.”

    They are not.