peopletechguide.com

Tag: composite reports

  • Why Your Workday Numbers Look “Wrong”

    When Stakeholders Don’t Trust Your Workday Reports

    If you spend time in Workday reporting, you’ve probably heard some version of:

    • “This doesn’t match our spreadsheet.”
    • “Finance is showing a different total.”
    • “Can you just export it? We’ll fix it in Excel.”

    It’s easy to blame Workday when numbers don’t line up. But across different tenants, the same issues appear again and again—and they’re almost always about report design, not platform capability.​

    If your HR and Finance stakeholders regularly say the numbers “look wrong,” chances are you’re hitting one or more of these traps.

    1. You Picked the Wrong Data Source

    If the data source is wrong, everything built on top of it will be wrong too.

    Common patterns:

    • Using a data source that only includes active employees when you actually need to see all workers, including terminated or contingent workers.
    • Mixing HR and Finance data sources with different grain (for example, worker-level vs transaction-level) and then trying to reconcile totals between them.
    • Starting from a niche data source when a broader, delivered one would have been safer.​

    No amount of filters or calculated fields can fix a fundamentally mismatched source. Before building anything complex, confirm:

    • Does this source include the population you care about?
    • At what level does it store data (worker, position, event, line item)?
    • Is this the same lineage you’re comparing against elsewhere?

    If the answer is no, start over with the right source rather than patching around the wrong one.

    2. Your Filters and Prompts Are Fighting You

    Even with the right data source, filters and prompts can quietly sabotage your results.

    Typical issues:

    • Filters are applied on the wrong object; for example, filtering at a related level instead of on the primary business object.
    • Date or Effective Date isn’t prompted, so different users unknowingly compare different time windows.
    • Hidden or default filters (“Do Not Prompt at Runtime”) override what users think they’ve selected.​

    That one checkbox—whether something is prompted or not—can completely change what appears on the report.

    To debug:

    • Temporarily expose all key filters as prompts and run tests with very broad settings.
    • Check whether any underlying default filters are still restricting data, even when prompts seem open.
    • Verify that org, date, and status filters are applied where you actually expect them.

    Until filters and prompts are aligned with the intended question, stakeholders will keep seeing inconsistent results.

    3. Your Calculated Fields Are Double-Counting

    Calculated fields are powerful, but they’re also an easy way to inflate or distort totals.

    Common traps:

    • Aggregating at the wrong level when workers have multiple rows (for example, multiple positions, events, or dependents).
    • Building complex calculated fields, then reusing them everywhere without validating the logic in isolation.
    • Summing values in a matrix or pivot that already reflect aggregated or overlapping data.​

    If your math is built on noisy grain, your totals will always look suspicious.

    Safer patterns:

    • Start with a small debug report using just the fields and groups relevant to the calculation.
    • Confirm row-level behaviour: are you counting workers, events, assignments, or something else?
    • Only then roll the calculated field into your “official” reports and dashboards.

    Once you understand the grain, your numbers become much easier to defend.

    4. You’re Misusing Composite Reports

    Composite Reports have a reputation as “advanced mode,” so many teams reach for them too early.

    In reality, Composite is a specialised tool for:

    • Combining multiple report results or data sets into one “one-stop” output.
    • Handling multi-source, multi-period or multi-view scenarios that truly cannot be expressed in a single advanced report.​

    When you use Composite as your default for anything complex, you usually add:

    • More joins and relationships than you really need.
    • More prompts and filters to coordinate.
    • More performance issues and more places where numbers can drift.​

    If a single Advanced report (possibly surfaced on a dashboard) can answer the question, start there. Treat Composite as the last resort for genuinely complex needs—not as a badge of seniority.

    5. Security Is Silently Hiding Rows

    One of the most underestimated causes of “wrong” totals is security.

    Scenario:

    • An admin runs a report and sees 1,254 workers.
    • A manager runs the same report, with seemingly identical prompts, and sees 1,037.
    • Both assume the other view is wrong.

    In fact, both views might be correct—for their security.

    Because Workday enforces security at the data level, reports will naturally show different populations based on:

    • Supervisory org visibility.
    • Role-based access and domain security.
    • Field-level security and constrained data sources.​

    If you only test reports as an admin, you will miss how they behave for real users.

    Always:

    • Test key reports as different roles (HR Partner, HRBP, Manager, Finance, etc.).
    • Clearly communicate which roles a report is designed for.
    • Document whether a report is meant to be tenant-wide, region-specific, or org-specific.

    If you don’t account for security, you’ll spend hours chasing “wrong” numbers that are actually right for that user.

    A Simple Playbook to Fix “Wrong” Numbers

    When stakeholders don’t trust your reports, you don’t need a brand-new reporting strategy. You need a disciplined way to design and debug.

    Here’s a practical playbook.

    Start with the question, not the tool

    • Ask, “What decision will this report support?” before building anything.
    • Choose the simplest data source and an Advanced report that can answer that specific decision-making need.​

    Strip the report back to basics

    • Remove non-essential filters, columns, and calculated fields.
    • Run the report with broad prompts (wide date ranges, minimal org restrictions).
    • Prove that the base data set is correct first; only then add complexity.

    Test your prompts deliberately

    • Check that prompts are bound to the right underlying fields.
    • Make sure critical prompts—dates, orgs, populations—are present and, where appropriate, mandatory.
    • Look for “hidden” filters or defaults that override the user’s choices at runtime.​

    Debug calculated fields in isolation

    • Build a tiny “debug” report that exists solely to test calculated fields and groupings.
    • Compare its totals against a trusted reference (manual count, legacy report, or a smaller population).
    • Only plug complex calcs into production reports when they match reality in isolation.

    Apply this playbook consistently and two things will happen:

    1. Stakeholders will stop opening every report conversation with “These numbers look wrong.”
    2. You will become the person leaders rely on when they need numbers they can make decisions with.

    And in Workday reporting, that trust is the most valuable metric you can own.

  • Stop Overusing Workday Composite Reports

    Stop Overusing Workday Composite Reports

    Composite Reports Everywhere: A Hidden Workday Problem

    If you’ve spent time in a mature Workday tenant, you have probably seen it: a library full of Composite Reports that are slow to run, hard to edit, and understood by only one or two people. Any time someone asks for a new slice of data, the default response seems to be, “Let’s build a Composite.”

    This pattern is common, especially in environments where reporting was treated as a “technical” activity instead of a core part of how HR and Finance work. Composite Reports absolutely have their place. But overusing them creates complexity, performance issues, and a real dependency on a small group of “report wizards.”

    The real skill in Workday reporting is not knowing how to build the most complex report. It is knowing which report type is the simplest, most sustainable way to answer a business question.

    A Quick Reminder: Workday Report Types in Plain Language

    Workday provides several report types, each suited to different needs.​

    • Simple reports
      Great for straightforward lists with basic filters. Think of them as quick views or ad-hoc extracts.​
    • Advanced reports
      Flexible, support calculated fields, joins, and richer filtering. Most custom reporting needs can be handled here.​
    • Matrix reports
      Excellent when you want cross-tab views—rows and columns—for comparisons such as headcount by location and time.​
    • Composite reports
      Designed for complex scenarios: combining multiple report results, multiple time periods, or different business objects into a single output.​

    Composite Reports are not “better” than other types; they are just more specialized. Treating them as the default option is like using a chainsaw to cut paper.

    Why Teams Overuse Composite Reports

    There are several reasons why Composite Reports become overused in Workday tenants:

    • Misunderstanding of report types.
      Many admins and analysts learn Composite Reports early and assume they are the “advanced” or “professional” choice for all complex needs.​
    • Copy-paste reporting culture.
      Instead of improving existing advanced or matrix reports, teams clone an old Composite and keep adding logic.​
    • Pressure to deliver quickly.
      When deadlines are tight, it can feel faster to “just throw everything into one Composite” rather than step back and design a simpler solution.
    • Lack of reporting strategy.
      Without clear guidelines on which report type to use when, every new request becomes a one-off decision.

    Over time, this leads to a reporting landscape that is powerful, but fragile: if the one person who understands all the Composite Reports leaves, the organization feels stuck.

    When a Composite Report Is the Right Choice

    Composite Reports are valuable when:

    • You truly need to combine multiple report results or data sources that are not easy to join in a single advanced report.
    • You must compare data across multiple time periods in one output.
    • You need more control over layout, formatting, or multi-section outputs than other report types provide.​

    Examples include:

    • Year-end audit reports that combine time, time off, and leave data into one view.
    • Complex financial statements that compare plan vs actual across multiple structures.
    • Executive-ready outputs where you want multiple sections, subreports, and formatted layouts.​

    In these cases, a Composite Report can save time and reduce manual work in Excel by bringing everything into one place.

    When Composite Reports Are Overkill

    However, many real-world reporting needs do not require a Composite. For example:

    • A monthly headcount trend by location or cost center.
    • A list of employees with a specific status and a few key attributes.
    • A time-off summary by department for a given period.​

    In these cases, an advanced report, sometimes combined with a calculated field or a matrix view, is usually enough. Overusing Composite Reports here can cause:

    • Performance issues.
      Composite Reports often run slower, especially when they reference multiple subreports and large datasets.​
    • Maintenance headaches.
      Debugging a problem inside a Composite with multiple subreports is much harder than fixing a single advanced report.
    • Lower adoption.
      If reports are slow, brittle, or confusingly named, HR and Finance users will avoid them and export data to spreadsheets instead.​

    A good rule of thumb: if an advanced or matrix report can answer the question, use that first.

    A Simple Decision Framework for Report Types

    To reduce Composite Report overuse, introduce a simple decision framework for your reporting team:

    1. Start with the question.
      What business question are we trying to answer? Who is the audience—HR, Finance, leadership?
    2. Try standard reports first.
      Check whether Workday already delivers a standard report that can be slightly filtered or adjusted.​
    3. Use advanced reports for most custom needs.
      If standard reports are not enough, design an advanced report with clear prompts, calculated fields, and security alignment.​
    4. Use matrix reports for comparisons.
      When the main value is comparing categories (e.g., departments vs months), consider a matrix report.​
    5. Reserve Composite for true multi-source or multi-period complexity.
      Only move to Composite when you genuinely need to combine multiple reports or time slices in ways other report types cannot handle.​

    This framework alone will prevent many unnecessary Composite Reports from being built.

    Designing Reports HR and Finance Will Actually Use

    Regardless of report type, the way your reports are designed determines whether HR and Finance teams will trust and use them:

    • Use prompts instead of hard-coded filters.
      Allow users to change date ranges, organizations, and other parameters without editing the report definition.​
    • Name reports clearly and consistently.
      Avoid names like “Composite_Report_3_Final_v2”. Use patterns such as “Headcount – Monthly Trend” or “Time Off Summary – By Department”.​
    • Align security early.
      Ensure the right people can run the report without raising access tickets every time.​
    • Document the logic.
      For any complex report, especially Composites, keep a brief design note describing inputs, filters, and key calculations.

    These practices make your reporting layer simpler and more resilient, even as your tenant grows in complexity.

    Cleaning Up an Existing Composite-Heavy Environment

    If your Workday tenant already has “Composite everywhere syndrome,” you can still improve things gradually:

    • Inventory existing reports.
      Identify Composite Reports in use and understand which ones are truly needed.​
    • Find candidates for simplification.
      Look for Composites that could be replaced by one or two advanced or matrix reports.
    • Refactor slowly, starting with high-impact reports.
      Focus first on the slowest, most frequently used reports; redesign them using simpler types where possible.
    • Educate your reporting community.
      Share your report type guidelines and run short sessions for HR, Finance, and admins on “choosing the right report type.”

    Over time, this reduces technical debt and makes it easier for new team members to manage Workday reporting.

    Composite Reports as Part of a Balanced Reporting Strategy

    Composite Reports are not the villain. They are a powerful tool in the Workday reporting toolbox. The problem is when they are treated as the only tool, or as a shortcut for every complex question.

    The goal is a balanced reporting strategy where:

    • Standard, simple, and advanced reports handle most day-to-day needs.
    • Matrix reports provide clear comparisons for HR and Finance leaders.
    • Composite Reports are reserved for genuinely complex, multi-source, or formatted outputs.

    When your team chooses report types intentionally, Workday reporting becomes faster, more maintainable, and more trusted. That’s a key step in simplifying Workday for HR and Finance.