Designing a Scalable Workday Financial Data Model (2026)

The Workday Financial Data Model is the most consequential design decision in any Workday Financials implementation. A well-designed FDM gives finance teams the reporting flexibility they need for the next decade. A poorly designed FDM creates years of cleanup work. This guide covers the core principles for designing an FDM that scales.

---

What Makes an FDM Scalable?

A scalable FDM is one that can accommodate business growth, organizational change, and evolving reporting requirements without requiring a fundamental redesign. Scalability in the FDM context means:

• Adding new legal entities without restructuring the chart of accounts
• Expanding into new geographies without adding new account segments
• Introducing new business lines without creating new Worktag types
• Answering new management reporting questions without building new account codes

The key to scalability is designing the FDM around dimensions (Worktags) rather than accounts. When reporting requirements change, you add new Worktag values — not new accounts. This is far less disruptive than restructuring a chart of accounts.

For background on how the FDM works, see our Workday Financial Data Model Explained guide.

---

Key Concepts

Dimensional Reporting: The core principle of the Workday FDM is that financial data is analyzed across multiple dimensions simultaneously. A single transaction can be analyzed by company, cost center, project, program, and any custom dimension — without pre-configuring every possible combination.

Worktag Cardinality: Cardinality refers to the number of values in a Worktag dimension. High-cardinality Worktags (hundreds of cost centers, thousands of projects) require careful hierarchy design to remain manageable in reports.

Required vs. Optional Worktags: Required Worktags must be entered on every transaction. Optional Worktags can be entered when relevant. The balance between required and optional Worktags determines the data quality and the data entry burden.

Reporting Trees: Workday uses Reporting Trees to aggregate Worktag values into hierarchical structures for reporting. A Cost Center Reporting Tree might roll up individual cost centers into departments, departments into divisions, and divisions into the company.

---

FDM Design Principles

Principle 1 — Separate Statutory from Management Reporting The chart of accounts should be designed for statutory reporting (GAAP, IFRS). Management reporting dimensions should be captured through Worktags. Do not embed management reporting requirements in the chart of accounts.

Principle 2 — Design for the Business You Will Be The FDM should accommodate the business you will be in five years. If you plan to expand internationally, design the Company and Currency structures for multi-entity, multi-currency operations from the start. Adding these structures later is significantly more complex.

Principle 3 — Minimize Required Worktags Every required Worktag adds friction to every transaction. Start with the minimum set of required Worktags needed for statutory compliance and critical management reporting. Add optional Worktags for supplementary analysis.

Principle 4 — Design Hierarchies for Leadership's View Worktag hierarchies should mirror how leadership wants to see the business. If the CEO wants to see results by product line, the Cost Center hierarchy should roll up to product lines. If the CFO wants to see results by geography, the hierarchy should roll up to geographic regions.

Principle 5 — Plan for Workday Marketplace Apps If you plan to use Workday Extend applications or Workday Marketplace apps, ensure your FDM is compatible with their data requirements. Some apps require specific Worktag types or account structures.

---

Common FDM Design Mistakes

Replicating the legacy chart of accounts: The most common FDM design mistake is taking the existing SAP or Oracle chart of accounts and mapping it directly to Workday. Legacy charts of accounts are designed for segment-based reporting and do not translate well to Workday's dimensional model.

Over-engineering Worktags: Creating 20+ Worktag types to capture every possible reporting dimension creates a system that is theoretically powerful but practically unusable. Users cannot remember which Worktags are required, and data quality suffers.

Ignoring future growth: Designing the FDM for the current state of the business without considering future growth leads to painful restructuring projects when the business expands.

Conflating operational and financial dimensions: Not every operational concept needs to be a financial Worktag. If a dimension is only needed for operational reporting (not financial reporting), consider whether it belongs in the FDM or in a Workday Extend application.

---

Best Practices

Run FDM design workshops with finance leadership. The FDM design should be validated by the people who will use it — CFO, Controller, FP&A team. Do not let IT make FDM decisions without finance input.

Prototype the top 20 management reports. Before finalizing the FDM design, prototype the 20 most important management reports using the proposed Worktag structure. If you cannot build these reports with the proposed design, the design needs to change.

Document the design rationale. Document why each Worktag was created, what reporting it supports, and what values it contains. This documentation is essential for future administrators who need to maintain the FDM.

Plan a post-go-live FDM review. Schedule a formal FDM review 6 months after go-live. By this point, users will have identified gaps and improvement opportunities that were not apparent during design.

---

Frequently Asked Questions

How many accounts should a Workday chart of accounts have? Most mid-market organizations need 200–500 accounts. Large enterprises with complex operations may need 500–1,000 accounts. More than 1,000 accounts typically indicates that management reporting dimensions have been embedded in the chart of accounts rather than captured through Worktags.

Can we add Worktag types after go-live? Yes, but adding a new required Worktag type after go-live requires retroactive data entry to tag historical transactions. Adding optional Worktag types is less disruptive. This is why it is better to design the complete Worktag structure before go-live, even if some Worktags start as optional.

How does the FDM affect period close? A well-designed FDM with clear required Worktags and complete hierarchies makes period close faster. Finance teams can run consolidated reports immediately without manual data aggregation. A poorly designed FDM with missing Worktags and incomplete hierarchies makes period close slower.

---

Key Takeaways

• A scalable FDM is designed around Worktag dimensions rather than account codes, allowing reporting requirements to evolve without restructuring the chart of accounts.
• The chart of accounts should be kept lean (200–500 accounts) with analytical depth captured through Worktags.
• Minimize required Worktags to reduce data entry friction while maintaining data quality for critical reporting.
• Design Worktag hierarchies to mirror how leadership views the business.
• Validate the FDM design by prototyping the top 20 management reports before finalizing it.

---

AssistNow designs Workday FDMs for enterprise clients. Our FDM design workshops deliver a validated, scalable design in 3–4 weeks. Contact us to get started.