{"id":681,"date":"2026-06-24T19:29:30","date_gmt":"2026-06-24T19:29:30","guid":{"rendered":"https:\/\/www.macalester.edu\/workday-support\/?page_id=681"},"modified":"2026-06-29T17:31:23","modified_gmt":"2026-06-29T17:31:23","slug":"worktag-overview","status":"publish","type":"page","link":"https:\/\/www.macalester.edu\/workday-support\/worktag-overview\/","title":{"rendered":"Worktag Overview"},"content":{"rendered":"
\n
\n \t \t

The Workday Financial Data Model (FDM) serves as the foundational accounting structure, replacing traditional chart of accounts (COA) to a flexible, multi-dimensional model that provides deeper financial insight.<\/p>\n \t <\/div>\n<\/section>\n\n\n

From FOAPALs to Worktags<\/strong><\/h2>\n\n\n\n

Traditional accounting systems often rely on a long, segmented string of code (known as a FOAPAL, account string, or coding block) to classify a single financial transaction. This rigid structure can be difficult to manage and limit reporting capabilities. Workday replaces this with the Foundation Data Model (FDM)<\/a>*.<\/strong> Instead of a single code, the FDM uses a combination of a summarized Ledger Account<\/strong> and multiple descriptive Worktags<\/a><\/strong>**. This approach separates the “what” (the Ledger Account) from the “who, where, and why” (the Worktags), allowing for more robust and flexible data analysis and reporting.<\/p>\n\n\n\n

Translating Worktags<\/strong><\/h2>\n\n\n\n

Transitioning to Workday involves conceptually mapping legacy account codes to the new FDM structure. This is not a one-to-one data transfer. Instead, each segment of your legacy string is deconstructed and mapped to an independent worktag in Workday.<\/p>\n\n\n\n

A single transaction might be coded with a FOAPAL string such as 10-1100-75020-PROJ987-General<\/strong>.<\/p>\n\n\n\n

In Workday, the string is broken into components (worktags) to support multi-dimensional reporting and workflow routing logic:<\/p>\n\n\n\n