peopletechguide.com

Tag: workday tenant design

  • 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.

  • From Configurator to Workday Architect

    Most Workday tenants do not fail because of one bad business process or one broken report. They fail slowly—through years of ad‑hoc configuration, one‑off exceptions and “just this once” changes that accumulate into technical and functional debt. Workday’s own guidance, partner methodologies and tenant health assessments all emphasize the same shift: from configurator thinking (“how do I make this work?”) to architect thinking (“how does this design impact everything else over three years?”).​

    Here are 12 configuration principles that help you build clean, scalable tenants instead of fragile ones.

    1. Start with a strong Foundation Data Model (FDM)

    The FDM—companies, ledgers, Worktags (Cost Center, Program, Project, etc.)—is the backbone of both HCM and Financials.​

    Architect mindset:

    • Design FDM once with input from HR, Finance, and key business units; avoid letting each module invent its own structures.​
    • Keep Worktag structures simple, with clear rules for how they are used in HR and Finance; add complexity only where it enables reporting or control.​

    If the FDM is clean, downstream configuration (security, reports, integrations) becomes dramatically easier to scale.

    2. Configure for the 80%, not every edge case

    Workday is flexible enough to encode every exception, but that does not mean you should.​

    Architect mindset:

    • Design business processes and rules to handle the standard 80–90% of cases elegantly.
    • For the remaining 10–20%, use manual workarounds or clearly documented exception paths rather than embedding them in configuration.​

    This keeps business processes understandable and maintainable over time.

    3. Prefer configuration patterns over one-off rules

    Configurations tend to multiply. An architect looks for patterns that can be reused across countries, business units and modules.​

    Examples:

    • Standard approval chains for similar processes (for example, all hire‑like processes share a pattern).
    • Reusable Condition Rules and Eligibility Rules instead of copy‑pasted logic.​

    Document patterns and intentionally reuse them instead of letting new teams create their own local variants.

    4. Keep business processes lean but controlled

    Workday business processes can quickly become bloated if every stakeholder demands a new step.​

    Architect mindset:

    • Limit each process to meaningful steps: initiations, key approvals, critical notifications.
    • Use conditions to add steps only where needed (by Company, Country, Threshold) instead of building multiple similar processes.​
    • Avoid serial approval chains where parallel approvals will do; keep cycle time in mind.

    Lean processes are easier to test, explain, and adjust when organizations change.​

    5. Treat security as design, not an afterthought

    Security is not just a technical concern; it shapes HR and Finance’s day-to-day experience.​

    Principles:

    • Design role-based security groups aligned to real job functions (HR Partner, Payroll Admin, AP Specialist, HRIS Analyst) rather than individuals.​
    • Use domain security and business process security consistently across modules; avoid granting “god access” to fix short-term issues.​
    • Build in Segregation of Duties (SoD) from the start, especially for financial processes.​

    Clean security models are critical for audit, compliance, and user trust.

    6. Design for change and Workday releases

    Workday has a fast release cadence, and your tenant needs to evolve safely.​

    Architect mindset:

    • Use sandbox tenants, refresh strategies and clear promotion paths (Prototype → Test → Production) for configuration changes.​
    • Treat release notes and Workday’s Release Best Practices as part of your configuration lifecycle—plan, test and adopt, not “flip everything on in prod.”​
    • Avoid hard‑coding assumptions that break when Workday adds new fields, features or locales.

    This is how you avoid regressions every six months.

    7. Make calculated fields and reports a shared asset

    Calculated fields and custom reports often become the “shadow logic” of a tenant.​

    Architect mindset:

    • Maintain a catalog of calculated fields: purpose, owner, usage, and deprecation status.​
    • Reuse key patterns (tenure, headcount flags, manager chain, normalized demographics) instead of recreating them per report.
    • Keep “heavy” calculated fields out of operational lists where they hurt performance; use them where they matter for analytics.​

    Treat reporting and calculated fields like a product, not a dumping ground.

    8. Integrations: choose standard patterns before custom

    Workday’s Integration Cloud and Cloud Connect offerings exist to prevent over-customization.​

    Principles:

    • Use Cloud Connect and standard connectors for payroll, banks, tax, and major partners where available.​
    • Standardize on a small set of integration patterns—event-based vs snapshot, EIB vs Core Connector vs API—based on use case.​
    • Keep integration mappings aligned with FDM and avoid embedding business logic in external tools when it belongs in Workday configuration.

    This reduces long-term integration debt and fragility.

    9. Document configuration decisions, not just settings

    Tenants age, teams change, and without context, configuration becomes opaque.​

    Architect mindset:

    • Maintain decision logs: why certain designs were chosen, what alternatives were rejected, and what assumptions were made.​
    • Link decision records to actual configuration (business processes, security policies, Worktags) so future teams can understand impact.
    • Treat configuration workbooks and architectural diagrams as living artifacts, not project relics.​

    This is crucial for troubleshooting, audits, and future transformations.

    10. Test across end-to-end scenarios, not just unit steps

    Configuration rarely breaks in isolation; it breaks across process boundaries: hire to payroll, requisition to payment, project to revenue.​

    Principles:

    • Design end‑to‑end test scenarios that cross modules (HCM ↔ Payroll ↔ Time, or Procurement ↔ Projects ↔ Assets ↔ GL).​
    • Involve business users in testing so real-life exceptions and policies are surfaced.​
    • Retain a core regression suite for future releases and major changes.​

    End‑to‑end testing is where “architect thinking” reveals cross‑module impacts that configurators miss.

    11. Measure tenant health and refactor regularly

    Even with good practices, configuration drifts. A tenant health check surfaces where refactoring is needed.​

    Architect mindset:

    • Use Workday and partner health assessments to analyze configuration complexity, performance, and unused objects.​
    • Periodically retire obsolete business processes, calculated fields, reports, Worktags and security groups.
    • Watch performance metrics—report load times, integration runtimes—and adjust designs that cause inefficiencies.​

    Think of this as refactoring in software engineering: keeping the codebase clean as requirements evolve.

    12. Govern configuration like code

    Finally, treat Workday configuration with the same respect as application code.​

    Principles:

    • Implement change management: requests, impact analysis, approvals, and tracked deployments for configuration changes.​
    • Separate duties: builders, reviewers, and approvers for high‑risk changes (security, FDM, payroll, tax, critical BPs).​
    • Align with IT and risk functions so Workday is part of the organization’s broader control and architecture landscape.​

    This mindset shift—from configurator to architect—is what keeps Workday tenants clean, scalable and ready for whatever HR and Finance need next. When these 12 principles guide your decisions, Workday becomes an asset that gets better every year instead of a system that “worked fine at go‑live” and slowly decays.​