The Workday Financial Data Model (FDM) Explained (2026)

The Workday Financial Data Model is the architectural foundation of every Workday Financials deployment. It determines how transactions are recorded, how costs are allocated, and how reports are structured. Organizations that design their FDM well gain decades of reporting flexibility. Organizations that rush it spend years trying to fix it.

---

What Is the Workday Financial Data Model?

The Workday Financial Data Model (FDM) is a multidimensional framework that defines how financial transactions are categorized and stored in Workday. Unlike traditional ERP systems that use a single, flat chart of accounts with long account strings (e.g., 1000-200-300-400), Workday uses a dimensional model where each transaction is tagged with multiple independent attributes called Worktags.

This dimensional approach means you can slice financial data by any combination of dimensions — by company, cost center, project, program, fund, or any custom dimension — without needing a separate account code for each combination. It is a fundamentally more flexible architecture than what SAP, Oracle, or legacy systems provide.

---

Key Concepts

Chart of Accounts: In Workday, the chart of accounts is simplified. It contains only the core account types (revenue, expense, asset, liability, equity) without the additional segments used in legacy systems. The analytical detail that was previously embedded in account strings is now captured through Worktags.

Worktags: Worktags are the dimensional attributes attached to every financial transaction. They are the core innovation of the Workday FDM. Common Worktags include:

• Company — the legal entity
• Cost Center — the organizational unit responsible for the cost
• Project — the project or initiative being charged
• Fund — used primarily in higher education and government
• Program — a grouping of related activities
• Custom Worktags — any additional dimensions specific to your organization

Worktag Hierarchies: Each Worktag type can be organized into a hierarchy. Cost Centers can roll up to Departments, which roll up to Divisions, which roll up to the Company. These hierarchies drive consolidated reporting and budget roll-ups.

Ledger Account: The ledger account is the basic account type (e.g., Salaries Expense, Office Supplies). In Workday, ledger accounts are kept simple and combined with Worktags to produce detailed reporting.

---

FDM Architecture

The FDM architecture in Workday consists of three layers:

Layer 1 — The Chart of Accounts: This is the foundational account structure. It should be kept as simple as possible — typically 200–500 accounts for a mid-market company. The temptation to replicate a legacy chart of accounts with thousands of accounts should be resisted.

Layer 2 — Worktag Dimensions: This is where the analytical depth lives. Each Worktag dimension is independent, meaning you can report on any combination without pre-configuring it. A company with 50 cost centers, 100 projects, and 10 programs has 50,000 potential reporting combinations without needing 50,000 accounts.

Layer 3 — Reporting Structures: Workday uses Summary Ledger Accounts and Custom Reporting Trees to aggregate data across the chart of accounts and Worktag hierarchies. These structures power dashboards, financial statements, and management reports.

For a complete guide to designing this structure, see our article on Designing a Scalable Workday Financial Data Model.

---

Best Practices

Keep the chart of accounts lean. The most common FDM design mistake is replicating a legacy chart of accounts with hundreds of segments. In Workday, a lean chart of accounts (under 500 accounts) combined with well-designed Worktags is far more powerful and maintainable.

Define required versus optional Worktags carefully. Required Worktags must be entered on every transaction. Every required Worktag adds friction to data entry. Only make a Worktag required if it is genuinely needed for statutory reporting or critical management reporting.

Design Worktag hierarchies for reporting, not just operations. Worktag hierarchies should mirror how leadership wants to see the business. If the CFO wants to see results by geography, then the Cost Center hierarchy should roll up to geographic regions.

Plan for future growth. The FDM should accommodate the business you will be in five years, not just the business you are today. If you plan to expand internationally, design the Company and Currency structures accordingly from the start.

Validate with finance, not just IT. FDM design sessions should be led by finance leadership. The people who run the month-end close and produce management reports are the ones who will live with these decisions.

---

Frequently Asked Questions

How many Worktags should a typical organization have? Most mid-market organizations use 5–8 Worktag types. Large enterprises may use 10–15. More than 15 Worktag types typically indicates over-engineering that will create data entry friction and user adoption problems.

Can the FDM be changed after go-live? Yes, but with significant effort. Adding new Worktag types post-go-live requires retroactive data entry or journal entries to tag historical transactions. Changing the chart of accounts requires remapping all historical data. This is why getting the FDM right before go-live is so important.

What is the difference between a Worktag and a segment in SAP or Oracle? In SAP and Oracle, segments are embedded in the account string and must be pre-defined. In Workday, Worktags are independent dimensions that can be combined freely. This makes Workday far more flexible for reporting but requires a different design mindset.

How does the FDM affect Workday reporting? Every Workday report can filter, group, and aggregate by any Worktag. A well-designed FDM means you can answer any financial question without building a new report. A poorly designed FDM means you are constantly building workarounds.

Does the FDM affect integrations? Yes. External systems that send financial data to Workday (payroll, procurement, billing) must map their data to the Workday FDM. This mapping work is a significant part of integration development.

---

Key Takeaways

• The Workday FDM replaces legacy account strings with a multidimensional model using Worktags.
• A lean chart of accounts combined with well-designed Worktags is more powerful than a complex chart of accounts.
• Worktag hierarchies drive consolidated reporting and should be designed to match how leadership views the business.
• FDM design decisions are difficult to reverse after go-live. Invest the time to get them right before configuration begins.
• The FDM affects every aspect of Workday Financials — reporting, integrations, business processes, and user experience.

---

For help designing a Workday FDM that scales with your business, contact AssistNow. Our Workday Advisory team has designed FDMs for organizations ranging from 500 to 50,000 employees.