peopletechguide.com

Tag: workday worktags

  • Workday Financials for Non-Tech Finance

    Opening Workday Financials for the first time can feel like stepping into a new language. You see Company, Entity, Ledger, Worktag, Cost Center and wonder how it all ties back to your familiar trial balance and P&L. The good news: once you understand a few core concepts – entities, ledgers and worktags – Workday becomes a very friendly system for non-technical finance users.​

    This tour explains those building blocks using plain finance language, so you can confidently review journals, approvals and reports without needing to be a Workday expert.

    Entities: who’s doing the accounting?

    In Workday, an Entity (often surfaced as Company or Company/Entity) represents the legal or accounting unit where transactions post and financial statements are produced.​

    As a finance user, think of entities as:

    • The companies or legal entities you already know from your statutory books.
    • The units you produce balance sheets, P&Ls and trial balances for.
    • The basis for intercompany relationships and consolidation.

    Key points:

    • Every financial transaction in Workday – supplier invoice, customer invoice, expense report, journal – belongs to an Entity.​
    • Entities drive things like functional currency, fiscal calendar and consolidation rules.
    • When you see questions like “Which company is this invoice for?” in Workday, that maps to entity selection.

    If you understand which entities exist in your group today, you are already halfway to understanding the Workday structure.

    Ledgers: where transactions land

    The Ledger is the place where accounting entries are recorded and balanced. In Workday, you may see Primary Ledger, Adjustment Ledgers, and specific ledger scenarios for local or management reporting.​

    For non-technical users:

    • The Primary Ledger holds your main accounting entries for each entity.
    • Additional ledgers can be used for adjustments, local GAAP vs group GAAP, or other management views.​

    Day to day, you will see ledgers in:

    • Journals – each journal posts to a specific ledger and period.
    • Reports – you can filter or run P&Ls and balance sheets by ledger if you have multiple.

    You do not need to configure ledgers, but knowing which ledger a report uses helps you interpret if numbers are statutory, management, or adjustment-inclusive.​

    Worktags: Workday’s replacement for long account strings

    The biggest conceptual shift in Workday Financials is Worktags. Instead of long account strings (Company-Department-Account-Project…), Workday attaches multiple Worktags as labels to each transaction.​

    Worktags are:

    • Short labels that describe the “who, what, where, why” of a transaction.
    • Used for routing approvals, posting entries and reporting.​

    Common Worktags include:

    • Cost Center – which department or unit owns the cost.
    • Fund / Program / Grant / Project / Gift – funding or project dimensions (often called Driver Worktags).​
    • Spend Category / Revenue Category – what you are buying or what income you are recognizing (similar to account/object codes).​
    • Location – where the cost or revenue occurs (office, store, plant).
    • Assignee – who the cost is related to (for example, an employee for chargebacks).​

    In practice:

    • Every requisition, invoice, expense report and journal uses Worktags instead of a single long code.​
    • One Driver Worktag (like Project or Cost Center) often auto-populates other Related Worktags, making entry easier and more consistent.​

    As a non-technical finance user, your job is usually to:

    • Check that the Cost Center and Spend/Revenue Category are correct.
    • Confirm the Project/Grant/Program if relevant.
    • Make sure the Worktags match how you want to see the spend in reports.​

    How entities, ledgers and worktags meet in a transaction

    Consider a simple supplier invoice in Workday:

    • You select the Company/Entity – this determines which legal entity is booking the expense.
    • The invoice lines use Worktags such as Cost Center, Spend Category, Project and Location.
    • When the invoice is posted, Workday uses its accounting rules to create ledger entries in the correct Ledger with the right accounts and dimensions.​​

    Behind the scenes:

    • Accounting Rules map Worktag combinations (for example, Entity + Spend Category) to ledger accounts.
    • Worktags determine routing (who approves), reporting (which department sees the cost) and analytics.​

    From your perspective, you can review an invoice and quickly answer:

    • “Is this hitting the right company?” (Entity)
    • “Is it going to the right department or project?” (Cost Center / Project Worktags)
    • “Is the type of spend coded correctly?” (Spend Category)

    Once you are comfortable “reading” a Workday transaction like this, reviews and approvals become much easier.​​

    Worktags in reports: how finance actually uses them

    Worktags are not just data entry fields; they are the backbone of Workday financial reporting.​

    Typical reports you will use:

    • Trial balance and P&L by Worktag – for example, P&L by Cost Center, by Program, by Project.
    • Spend by Worktag – spend by Supplier and Spend Category, or by Project and Cost Center.
    • Budget vs actual – combining Worktags used in budgets and actuals to show variances.​

    Benefits for non-technical users:

    • You can easily slice data without needing custom cubes or extra tools.
    • Approvers can drill from a summary P&L down to individual transactions and see all Worktags on each line.​​
    • Audit and compliance checks are easier because every transaction carries clear labels.​

    If reports do not look right, it is often a Worktag issue (wrong Cost Center or Spend Category) rather than a ledger problem.

    Tips for non-technical finance users to get comfortable fast

    To become fluent in Workday Financials without becoming technical:

    • Learn your standard Worktag sets
      • For example, which Cost Centers you support, common Spend Categories, and key Projects or Grants.
      • Keep a simple cheat sheet for your area.​
    • Practice reading journals and invoices
      • Open a few recent transactions and inspect the Worktags and ledger entries.
      • Verify that they align with how you would have coded them in your old system.​​
    • Use Workday reports and drill-downs
      • Start with delivered or standard reports for trial balance, P&L and spend reports.​​
      • Use drill-down to go from high-level numbers to underlying Worktag detail.
    • Ask where Worktags are auto-populated
      • Many Worktags default from the worker, cost center or project. Understanding these defaults reduces manual corrections.​​

    You do not need to know every configuration detail; you just need to know how Entities, Ledgers and Worktags show up in your day-to-day screens and reports.

    Once those three pieces click, Workday stops feeling like a complex system and starts feeling like a flexible, label-based accounting tool that supports the way finance actually thinks about the business.

  • Project Accounting in Workday, Step by Step

    Project Accounting

    Project accounting in Workday is not just a “Finance feature.” It is the thread that connects Projects, Worktags, Time Tracking, Expenses, Procurement and Billing into a single picture of project cost, margin and progress. When you design it intentionally, you can see exactly what each project costs, what to invoice, and how profitable it is—without extracting everything to spreadsheets.​​

    This guide walks step by step from project setup to employee expenses, using Workday terminology throughout.

    Step 1: Design your project Worktag model

    In Workday, Project itself is a Worktag, usually a Driver Worktag. When added to a transaction line, it can auto-populate related Worktags such as Cost Center, Program, or Grant via Related Worktags.​​

    Decisions to make up front:

    • What types of projects will you track?
      • Customer / billable projects (client work, external funding).
      • Internal / administrative projects (internal initiatives, overhead).
      • Capital projects (fixed asset construction, IT implementations).​
    • Which Worktags should be tied to Project?
      • Cost Center, Program, Fund/Grant, Region, maybe a Custom Worktag for Portfolio or Product Line.​​

    Design patterns:

    • Use a clear naming convention for Projects: prefix by project type or business line (e.g., “CUST‑1001 – Client A ERP”, “CAP‑2003 – HQ Renovation”).​
    • Configure Project Allowed Worktags so only valid Worktag combinations can be used with each Project (for example, only certain Cost Centers or Funds).​
    • Build project hierarchies where you need rollups (programs or portfolios) using Project Hierarchies and related structures.​

    A good Worktag design means you do not have to teach users every rule; Workday enforces a lot of it for you.

    Step 2: Create projects with the right attributes

    The Create Project process in Workday captures core data and determines how the project behaves in financials, expenses and billing.​​

    Key fields and decisions:

    • Project Type – Administrative, Customer, Capital, etc. This drives downstream behavior, including capitalization and billing options.​
    • Owning Company / Entity – which legal entity owns the project and will recognize revenue/cost.​​
    • Worktags – Cost Center, Program, Customer (for customer projects), Location, and any Custom Worktags.​​
    • Billable vs Non‑billable – indicates whether costs should be available for billing and margin analysis.​​
    • Project Plan / Tasks – optional but powerful: break the project into tasks or work packages to track cost and progress at a more detailed level.​​

    Best practices:

    • Use template projects for common patterns (for example, standard professional services engagements) to default Worktags, billing settings and tasks.​​
    • Capture Customer and Contract/Billing references at project setup for billable projects to avoid reconciling later.​
    • For capital projects, confirm how costs will later link to Assets and Capitalization processes.​

    Once created, the Project becomes the central Worktag used across time, expenses, procurement and journals.

    Step 3: Capture time and expenses against projects

    To see true project cost, you must push Time Tracking and Expenses through the project lens. Workday Projects ties into both modules.​​

    Time:

    • Configure Time Entry Templates and Time Entry Codes so workers can select a Project (and optionally Task) on their time entries.​​
    • Use Work Type Rules to classify time (e.g., billable vs non‑billable, standard vs overtime) for project cost and revenue.​​
    • Make sure time approvals align with project responsibility—line managers or project managers, depending on your operating model.​​

    Expenses:

    • Enable Project as a Worktag on Expense Reports so employees can charge travel, materials and other charges directly to projects.​
    • Configure Expense Item defaults to automatically set Spend Categories and some Worktags, leaving employees to choose only Project (and maybe a Task).​​
    • Set up expense approval hierarchies that route project‑coded expenses to the right project or cost center owner.​

    By getting time and expenses to consistently carry the Project Worktag, you build a clean cost view without manual allocation journals later.

    Step 4: Capture procurement and AP costs to projects

    Project costs often come through procurement: purchase orders, supplier invoices and sometimes journals. Workday enables project tagging across these flows.​

    Patterns:

    • On Purchase Requisitions and Purchase Orders, include Project and related Worktags on lines that are project-specific.​
    • For Supplier Invoices, either inherit the Project from the PO or allow AP to add Project Worktags directly on invoice lines where appropriate.​
    • Use Project Allowed Worktags rules to prevent invalid combinations (e.g., wrong Cost Center or Fund for that project).​

    Capital projects:

    • Ensure procurement and AP spend for capital projects are coded to the capital project and appropriate Spend Categories (e.g., Capitalizable construction or equipment categories).​
    • Later, Workday can help create Project Assets and move costs from Construction-in-Progress (CIP) to fixed assets.​

    This approach keeps all project-related spend, not just internal time and expenses, visible at project level.

    Step 5: Budgeting and tracking against plan

    Project accounting becomes truly useful when you compare actuals to budget or plan.​

    Options:

    • Use Project Budgets:
      • Create project-level budgets with the Project Worktag plus other dimensions like Cost Center and Spend Category.​
      • Submit for approval and tie them into your broader financial planning process.
    • Use Resource / Project Plans:
      • For services projects, build resource plans to estimate effort and cost by role or worker.​​

    Reporting:

    • Build reports and dashboards showing Budget vs Actual by Project, by Task, and by Worktag (e.g., by Spend Category, Cost Center, Customer).​
    • Include both labor (time, payroll allocations) and non‑labor (supplier, expenses) costs for a full project cost picture.​

    Good practice is to define who owns the project budget (Project Manager, PMO, Finance) and how often you review project financials—monthly is common for active projects.

    Step 6: Billing and revenue for customer projects

    For customer projects, project accounting feeds directly into Workday Project Billing and revenue.​​

    Key elements:

    • Billing Plans: define how and when you bill (time & materials, fixed fee, milestones, retainers).​
    • Billing Events and Invoice Generation: Workday converts billable project transactions into customer invoices according to your billing plan and rules.​​
    • Revenue Recognition: revenue schedules and rules determine when revenue is recognized for project work, potentially decoupled from billing.​

    Make sure:

    • Only appropriately tagged billable time and expenses hit billing, based on Work Types or billable flags.​​
    • Contracts, Projects and Customers are linked correctly so invoices automatically reflect the right project, PO, and tax settings.​

    This ensures your project accounting supports both cost control and the top line.

    Step 7: Governance and “project hygiene”

    Project accounting can decay over time if governance is missing. Keep it healthy with:

    • Project lifecycle rules
      • Clear criteria for moving projects from Open → Active → Closed.
      • Regular reviews to close dormant or completed projects to prevent miscoding.​
    • Worktag hygiene
      • Regular checks for transactions posted to “wrong” or generic projects requiring reclass.
      • Use reports to identify expenses and invoices without Projects where they should have one.​
    • Training and quick references
      • Provide Project and Worktag cheat sheets per business area (which Projects to use, which are closed, etc.).​
      • Train project managers to use Workday reports and dashboards, not offline trackers, for financial views.​

    Treat project accounting as a shared responsibility between Finance, PMO and delivery teams.

    When you design project accounting in Workday as an integrated process—from Project setup to Time & Expense capture, Procurement, Budgeting and Billing. You end up with a living, accurate view of project performance. Finance gets clean numbers, project managers get real insight, and leadership can see where work is truly profitable.

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