peopletechguide.com

Tag: workday companies

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

  • Your Workday Accounting Backbone

    Your Workday Accounting Backbone

    Workday Accounting

    If Workday is the brain of your finance system, the accounting backbone is its spine: Companies, Ledgers, Worktags and Posting Rules. When these four are designed well, every supplier invoice, customer invoice, expense report and journal flows cleanly into the General Ledger, and your reports match how the business actually thinks. When they are not, you get mispostings, reconciliation headaches and a long queue of “please fix my coding” tickets.​

    This guide walks through how to think about and explain that backbone in Workday language, but in a way that finance and accounting teams immediately recognize.

    Companies: the legal and reporting anchors

    In Workday Financials, Companies (sometimes called Company / Entity) represent the legal or accounting units where you keep books and produce financial statements.​​

    From a finance perspective, a Company is:

    • A legal entity that needs its own statutory accounts.
    • The core object Workday uses for balance sheets, P&Ls and trial balances.
    • The anchor for settings like functional currency, year-end close rules and consolidation.​

    Key design decisions:

    • Define one Company per legal entity that reports separately (for example, “US Corp”, “India Pvt Ltd”, “UK Ltd”).
    • Use Company Hierarchies to group companies for management reporting and consolidation (e.g., “EMEA Region”, “Global Consolidation”).​
    • Make sure every operational process (Procurement, Expenses, Customer Invoicing, Projects) is configured to capture the right Company on each transaction.​​

    Once Companies are set correctly, finance users can filter reports by entity and trust that every transaction belongs to the right legal book.

    Ledgers: where the accounting happens

    If Companies answer “who,” Ledgers answer “which book.” In Workday, ledgers hold accounting entries for a Company.​

    Typical patterns:

    • A Primary Ledger per Company, which holds your main accounting entries.
    • Optional additional ledgers for adjustments, local GAAP vs. group GAAP, or management-only entries.​

    In daily work you see ledgers in:

    • Journals – you pick the ledger (often implicit via Company) and accounting date/period.
    • Financial reports – you can specify which ledger(s) to include for a given statement.​

    For most non-technical users:

    • You do not configure ledgers yourself, but knowing which ledger a report uses (Primary vs. Adjustment) explains why numbers may differ from other tools.
    • You can be confident that all subledger activity (AP, AR, Expenses, Projects, Payroll) ultimately posts into the ledger defined for that Company.​​

    Think of the ledger as the “book” your external auditors care about; everything else is just detail feeding into it.

    Worktags: replacing account strings with smart labels

    The real Workday magic for accounting is Worktags. Instead of long account strings (Company–Department–Account–Project…), Workday uses Worktags as flexible labels on each line.​

    Worktags:

    • Classify transactions for financial, operational and external reporting.
    • Can be assigned to any line that generates a financial update: requisitions, invoices, expenses, time, journals, payroll, etc.​​

    Common Worktags in many tenants include:

    • Cost Center – the department or unit owning the cost.
    • Fund / Program / Grant / Project / Gift – funding or project dimensions, often called Driver Worktags.​
    • Spend Category – what you are buying (e.g., Office Supplies, Travel – Airfare), analogous to an expense account.
    • Revenue Category – what income you’re recognizing (e.g., Product Revenue, Service Fees).​
    • Location, Assignee, Custom Worktags – extra slices for where and who.​

    Important concepts:

    • Driver Worktags: the main Worktags users pick (for example, Project or Cost Center). These trigger Related Worktags to auto-populate, making entry easier and more consistent.​
    • Related Worktags: automatically filled-in tags tied to the Driver (for example, choose Project → default Cost Center and Program appear).

    For the AP team, expense users or journal preparers, this means:

    • You focus on choosing the right Worktags instead of trying to remember a long string of codes.
    • Changing one Worktag (e.g., Project) can automatically adjust related tags, keeping combinations valid and reportable.​

    Posting Rules: the engine translating worktags into accounts

    Behind the scenes, Workday’s Account Posting Rules (often described as the “accounting rules engine”) take those Worktags and decide which Ledger Accounts to use.​

    Key idea:

    • Users pick Worktags like Company, Cost Center, Spend Category, Project.
    • Posting Rules map those combinations to ledger accounts and build the debit/credit lines for the journal.​

    Examples:

    • Entity: US Corp + Spend Category: “Office Supplies” → Debit 640000 (Office Supplies Expense), Credit 200000 (AP).
    • Entity: India Pvt Ltd + Spend Category: “Travel – Airfare” → Debit 642100 (Travel Expense), Credit 200000 (AP).​

    Benefits:

    • End users no longer select ledger accounts directly; they select the business-friendly Worktags, and the system applies consistent accounting.​
    • Finance can centrally manage accounting logic without retraining every user when accounts or rules change.

    From a design perspective:

    • Account Posting Rule Sets should mirror your chart of accounts and key Worktag dimensions.
    • Changes to accounting (for example, moving certain spend to a new account) are made in rules, not transaction screens.​

    How it all comes together in a transaction

    Let’s walk a basic supplier invoice through the backbone:

    1. Company / Entity
      • AP selects Company “US Corp” on the supplier invoice. This determines which books and ledger are used.​​
    2. Worktags on the invoice line
      • Cost Center: “Sales – East”
      • Spend Category: “Travel – Airfare”
      • Project: “Project X” (as a Driver Worktag, auto-filling Cost Center and maybe Program)​
    3. Posting Rules
      • Workday’s Account Posting Rule Set sees Company + Spend Category (and possibly Project/Fund) and maps to the correct expense and AP accounts.​
    4. Ledger
      • The system posts the resulting journal to the Primary Ledger for US Corp in the appropriate period.​

    The AP user only needed to know: the correct Company and Worktags. The complex accounting logic happened automatically and consistently.

    Design tips for a strong accounting backbone

    When setting up or improving your backbone, a few principles help:

    • Start with your Foundation Data Model (FDM)
      • Align Companies, Cost Centers, Programs, Projects and other Worktags to how the business actually manages and reports.​
      • Treat FDM design workshops like building the foundation of a house: get them right before everything else.
    • Keep Worktag usage clear and controlled
      • Decide which Worktags are required on which business events (for example, Cost Center and Spend Category always required on journals).​​
      • Document which Worktag combinations are valid; misuse of Worktags is a major cause of messy reporting.
    • Centralize Posting Rules ownership
      • Assign accounting or finance system owners to manage Account Posting Rule Sets.
      • Test new rules with sample transactions before moving them to production to avoid mispostings at scale.​
    • Train users on Worktags, not on GL codes
      • Provide quick reference guides showing which Worktags to use for common scenarios instead of giving them the chart of accounts.​
      • Show how Worktags appear in reports so users understand why accurate tagging matters.

    When the backbone is clear and users know their part, finance can shift from fixing coding errors to analyzing the business.

    A well-designed accounting backbone in Workday – with clean Companies, structured Ledgers, thoughtful Worktags and robust Posting Rules – turns Workday into a reliable single source of truth for finance. Transactions flow from operations to the GL with minimal manual intervention, and your reports finally reflect the real story of the business without endless offline rework.