Primary / official references
Primary / official referencesWorkday Glossary — Company / Company HierarchyWorkday Organizations and Worktags
Integration playbook
Workday legal entity structure: separate the financial Company model from the legal entity master
Workday Financial Management uses Company as a primary financial organization and recommends that legal entities generally be represented as companies where possible, while also allowing company structures that are not one-to-one with legal entities.
Practical outcome
Keep legal identity governed even when Workday's Company hierarchy is optimized for financial reporting and operations.
This is an architecture playbook, not a claim that a prebuilt Workday connector is currently available.
How Workday describes Company
Workday documentation describes Company as the primary organization for Financial Management and the level at which a balanced set of books is held. Workday guidance says companies should reflect legal entities where possible, while also noting that a company does not always have to be a legal entity.
Why the legal entity master should remain distinct
The legal record needs registered identity, jurisdiction, ownership, directors/officers, corporate evidence and obligations. Workday's Company model is designed around finance, reporting, security and operational organization. Those models can align closely without being identical.
| Field | Legal-entity concern | Workday concern |
|---|---|---|
| Company / entity name | Approved legal name and effective date | Financial organization naming and reporting |
| Tax ID | Governed identifier + evidence | Used in company/tax processing and relationships |
| Parent / ownership | Legal/economic ownership relationship | Company hierarchy and consolidation configuration |
| Status | Active/dormant/dissolved legal state | Operational finance lifecycle |
| Directors / officers | Governance relationship | Usually outside the core Company master |
Tax IDs and single legal entity relationships
Workday documentation describes Single Legal Entity relationships in which one managing company can relate to other companies for financial and managerial reporting, and notes the importance of Tax ID alignment in that structure. This makes field ownership and synchronization discipline important where the legal entity and operational Company model diverge.
Manage changes as coordinated events
When a legal entity is renamed, reorganized, merged or dissolved, define which Workday Company or hierarchy changes follow. Keep the legal-effective date separate from the system-update timestamp so the audit trail remains understandable.
- Cross-system entity/company identifiers.
- Defined field-level master ownership.
- Source-backed Tax ID and legal-name changes.
- Reconciliation of legal entities versus Workday Companies.
- Approval before downstream synchronization of consequential changes.
- Error queues and audit timestamps for integration events.
Questions
Is a Workday Company always a legal entity?
No. Workday documentation says companies should reflect legal entities where possible but can also represent nonlegal operational structures.
Why keep EntityOS if Workday already has Companies?
EntityOS focuses on the governed legal-entity record, ownership, governance, evidence and obligations, while Workday Company supports financial and organizational processes.
How are Tax IDs relevant?
Workday uses Tax IDs in company and tax configuration, including certain Single Legal Entity relationships, so synchronization should be controlled.
Is there a native EntityOS Workday connector?
Do not assume one. This page describes a data-exchange architecture; current connector availability should be confirmed separately.
How should reorganizations be synchronized?
Treat the approved legal change as the source event and map the corresponding Workday Company/hierarchy updates with effective dates and audit history.
This resource is general operational information, not legal, tax, accounting or regulatory advice. Requirements vary by jurisdiction and facts. Use qualified advisers for jurisdiction-specific decisions.