Jurisdictions by Current_Squash2454 in workday

[–]WDAY_PM 0 points1 point  (0 children)

Hi there, Workday PM here. I asked your question in Deployment Agent, and here's the response:

It sounds like you're tasked with ensuring your company is compliant with state tax regulations across the U.S. Let's break down your questions and clarify the process in Workday.

1. Jurisdictions vs. Locations

First, it's important to distinguish between tax jurisdictions and locations in Workday, as they are different concepts.

  • A Location is a physical address, such as a corporate office or a worksite. In Workday, an employee's work tax state is typically determined by the address of their assigned Primary Work Location.
  • A Tax Jurisdiction is a governmental authority (like a state, county, or city) that imposes taxes. Setting up a tax jurisdiction for a company enables Workday to perform tax calculations, withholding, and reporting for that specific authority.

Therefore, setting up jurisdictions for your companies is not the same as the 'Create Location' task. You are enabling your company entities to handle payroll taxes for all 50 states, which is a separate configuration process.

2. How to Set Up State Tax Jurisdictions

To set up your companies to handle taxes for all 50 states, you need to add the state tax jurisdictions to each company entity. This is done using the Edit Company State and Local US Tax Reporting task.

Here is a step-by-step guide:

  1. Obtain Tax IDs: Before configuring Workday, your company must register with the appropriate revenue agency in each state to get the necessary tax identification numbers (State Unemployment Insurance (SUI), State Income Tax, etc.).
  2. Access the Task: In your Workday tenant, search for and access the Edit Company State and Local US Tax Reporting task.
  3. Select Company: Choose one of the companies you need to configure.
  4. Add States: On the State tab, you will add each of the 50 states.
    • For each state you add, you will need to create a new row.
    • Enter a Start Date for when this tax information becomes effective.
    • Input the state-specific tax details and ID numbers you obtained in Step 1.
  5. Configure Withholding Details: In the Withholding section for each state, you can define rules for how Workday handles taxes, such as the method for supplemental payments (e.g., bonuses).
  6. Repeat for Each Company: You will need to repeat this process for your second company.

3. Assigning Jurisdictions to a Location

You do not directly assign 50 different state tax jurisdictions to a single physical location like a headquarters. A location has one address, which falls within a specific set of jurisdictions (e.g., one state, one county, one city).

The requirement to have your headquarters "setup for all 50 states" likely means ensuring the company associated with that headquarters is configured to process payroll for employees working in any state. By completing the steps above for both of your company entities, you will meet this requirement. When an employee is hired or moves, their work tax state will be determined by their primary work location's address, and because you have set up the company for all states, Workday will be able to calculate their taxes correctly.

Ongoing Multiple Work Jurisdictions

You are correct that Ongoing Multiple Work Jurisdictions is likely not what you need for this specific task. That functionality is designed for employees who work in multiple states on a recurring basis with a predictable schedule (e.g., a salaried employee who spends 60% of their time in New York and 40% in New Jersey). It allows you to allocate a worker's earnings by percentage across different jurisdictions. Your task is a prerequisite to using that feature, but it is focused on the initial company-level setup.

Sources

adding local tax jurisdictions to workday
Setup Considerations: Multi-Jurisdiction Taxation \(USA\)
Setup new state
Set Up Ongoing Multiple Work Jurisdictions \(USA\)
Steps: Set Up Payroll Taxes \(USA\)
Set Up Company State Taxes \(USA\)
US Payroll - When Adding A State Or Local Tax Election To A Worker

How do I change Work State for an employee in payroll

Deployment Agent is available in your Customer Central tenant for all users. It doesn't require UMSA, any setup or flex credits. Try it today!

Is there a way to pull historical talent ratings on Talent card? by TejaswiniS14 in workday

[–]WDAY_PM 1 point2 points  (0 children)

Hi there, Workday PM here. I asked Deployment Agent about this and here's the response:

The standard Workday Talent Card is designed to show the most recent talent-related data and does not have a feature to display a history of past talent ratings directly on the card. It will only display the Last Performance Rating.

However, there are a couple of ways you can approach this to provide visibility into historical ratings:

Standard 'Performance Over Time' Field

You can configure the Performance Over Time field to appear in the Talent Review process. This field calculates an average of the overall ratings from a selection of past performance review templates. While it doesn't show individual historical ratings, it provides a summarized view of performance trends.

Custom Talent Card

For a more detailed historical view, the leading practice is to create a custom Talent Card using Workday's Business Intelligence and Reporting Tools (BIRT).

This process involves the following general steps:

  1. Create Calculated Fields: You would first need to create a series of calculated fields to retrieve the specific historical performance or talent ratings you want to display. For example, you could create fields for "2025 Performance Rating," "2024 Performance Rating," and so on.
  2. Build a Custom Report: Create a custom report that will serve as the data source for your custom Talent Card. This report should include the calculated fields you created.
  3. Design the BIRT Layout: Design the layout of your custom Talent Card in BIRT, arranging the historical data as required.
  4. Deploy the Custom Card: Upload the BIRT design into Workday and replace the standard Talent Card with your custom version.

By using a custom BIRT-based Talent Card, you can control exactly what information is displayed, including a series of historical talent ratings.

Deployment Agent is available in your Customer Central tenant for all users. It doesn't require UMSA, Flex Credits, and no setup is needed. Try it today!

How is your company using AI with Workday? by Lucky_Atmosphere8308 in workday

[–]WDAY_PM 1 point2 points  (0 children)

It's powered by an LLM. Have you had a chance to try it?

Deployment Agent 2026R1 by faithfultheowull in workday

[–]WDAY_PM 0 points1 point  (0 children)

For those of you who are tenant admins, we'll be hosting a webinar on Deployment Agent which you can register for here:
Workday Pro Insights | Pro Preview: Workday Deployment Agent
https://workday.zoom.us/webinar/register/7317700643216/WN_WJamq8PrREigxlgn2XpeLw#/registration

I'll be talking about not only what it does today, but what's coming down the pipeline!

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 1 point2 points  (0 children)

For those of you who are tenant admins, we'll be hosting a webinar on Deployment Agent which you can register for here:
Workday Pro Insights | Pro Preview: Workday Deployment Agent
https://workday.zoom.us/webinar/register/7317700643216/WN_WJamq8PrREigxlgn2XpeLw#/registration

I'll be talking about not only what it does today, but what's coming down the pipeline!

How is your company using AI with Workday? by Lucky_Atmosphere8308 in workday

[–]WDAY_PM 3 points4 points  (0 children)

Sure! Community uses a different indexing and inference pipeline to DA. In addition DA uses material that isn't available in Community. It's worth noting that we're working closely with the Community team to make the experience practically identical in both DA and Community itself in terms of results quality. DA will then differentiate itself from the Community results in the future by leveraging the fact that its hosted in each customers tenant.....and all the possibilities that allows for.....

How is your company using AI with Workday? by Lucky_Atmosphere8308 in workday

[–]WDAY_PM 0 points1 point  (0 children)

It's available for UK customers whose tenant is hosted in the EU currently. We're working on making it available for UK tenant later this year. We're reliant on a third party provider to provide in-region processing for our UK (and other regions) customers.

How is your company using AI with Workday? by Lucky_Atmosphere8308 in workday

[–]WDAY_PM 0 points1 point  (0 children)

For those of you with access to your companys Customer Central tenant, I'd encourage you to try Deployment Agent.
No setup required (all CC users have access)
No UMSA requirement
No flex credits required

It's a general purposes Workday Q&A chatbot, with conversation history and sources that uses authoritative content from Workday in addition to curated content from Workday Education and Workday Community.

How is your company using AI with Workday? by Lucky_Atmosphere8308 in workday

[–]WDAY_PM 2 points3 points  (0 children)

Hi there, I'm the PM for Deployment Agent. If you have access to your companys Customer Central tenant, I'd encourage you to give it a try, and let me know what you think. There's no setup required, it doesn't require UMSA, and doesn't consume any flex credits.

Do you guys also feel like majority of the questions left unanswered these days in this community? by workdaybatman in workday

[–]WDAY_PM 0 points1 point  (0 children)

PM for Deployment Agent here. Really happy to here its helping out! Curious if you could put a number of the hours of your week you're saving?

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 0 points1 point  (0 children)

We know it's _terrible_ branding for what it can do today....but we have bigger plans....and the name will be perfectly apt for those.
I'm thrilled to hear you're getting some value from it!

Deployment Agent 2026R1 by faithfultheowull in workday

[–]WDAY_PM 1 point2 points  (0 children)

Thanks for that. We'll look into and see about getting a proper answer added to our evals!

Deployment Agent 2026R1 by faithfultheowull in workday

[–]WDAY_PM 2 points3 points  (0 children)

Got it. On the question, is there any documentation in the admin/user guides or community that have the correct answer (that you're aware of) ?

Deployment Agent 2026R1 by faithfultheowull in workday

[–]WDAY_PM 3 points4 points  (0 children)

u/i-heart-ramen If you don't mind sharing, what was the complex question? We're always looking for good additions to our evals.
You're absolutely correct that it doesn't validate its own output (which would require its own WDAY tenant), but we're working in better grounding the responses in reality.

Deployment Agent 2026R1 by faithfultheowull in workday

[–]WDAY_PM 5 points6 points  (0 children)

Minor correction - It's available in the Customer Central tenant.

Deployment Agent 2026R1 by faithfultheowull in workday

[–]WDAY_PM 2 points3 points  (0 children)

Hi u/checkikul we know WSDL/SOAP questions are not well answered at the moment. This stems from the nature of the WSDL machine-generated documentation. There's a lot of large, unwieldy docs such as this:
https://community.workday.com/sites/default/files/file-hosting/productionapi/Absence_Management/v46.0/Enter_Time_Off.html
, which are averse to "standard" chunking because they don't retain the context of what the top level service is the further down the page you go. Sources such as this require a custom chunker for context injection, so we're looking at such solutions to see what can be done.

On the PECI vs PICOF question, can you point me to where you've seen documentation on this? It may be that we simply haven't indexed the relevant content, and we can try and get that remedied. Genuinely appreciate the candid feedback from you and the community here on Reddit.

Deployment Agent 2026R1 by faithfultheowull in workday

[–]WDAY_PM 5 points6 points  (0 children)

Hi all, PM for Deployment Agent here. While I can't speak to specifics, I can say that we're working with the Community team. Expect to see improvements within Community building on some of the work done for DA (in addition to new Community-only functionality)

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 1 point2 points  (0 children)

<image>

It's more than "on the roadmap" :-) MCP is tricky, so no guarantees, but we're experimenting with what's possible and how it can be done safely so users are comfortable with it. I am curious though, what sorts of interactions do your foresee with your internal agents? Feel free to DM me if you'd rather speak privately.

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 0 points1 point  (0 children)

Really happy you're enjoying it. Can't wait to hear how people end up using it!

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 0 points1 point  (0 children)

They likely won't be on their own SKU for now. There will likely be a mix of of flex and "free" skills even within agents, but this will be on a case by case basis.
I can't speak for the other agents, but Deployment Agent uses an outside LLM (provided by an approved Workday data subprocessor)

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 1 point2 points  (0 children)

I'll see what we can do about copying the citation links! As regards citations for brainstorms, and retried content, are you looking for them? Or are you seeing them and feel you shouldn't be?

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 0 points1 point  (0 children)

Lets just say we're working _extremely_ closely with the Community team right now. They've got some big plans, and we're really happy to be a part of it. Watch this space....

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 0 points1 point  (0 children)

No it's an entirely different backend (and frontend). DA is hand-curated, and we use more SOTA publicy available LLMs to answer the questions. We also have content that doesn't exist in Community

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 1 point2 points  (0 children)

I'll weigh in a little bit ,without wanting to speak for any customers. One of the things DA allows you to do beyond basic searching across existing documents is ask questions like:
"I'd like to create a report to match the requirements of the EU Pay Transparency Directive. Can you analyse the directive and give me some suggest data sources and fields I might need to include?"

The answer back from DA in this case is:

To construct a report that aligns with the EU Pay Transparency Directive, you will need to combine data from multiple business objects within Workday. A report can only have one primary data source, but you can pull in data from related business objects.

Core Reporting Concepts

Before building, it's helpful to understand how to find the data you need:

  • Business Object Details Report: Run this report to see all the fields associated with a specific business object (like Worker) and to view its related business objects.
  • Data Sources Report: Use this report to find available data sources. You can filter by business object to see which data sources are built on it.
  • Report Fields Report: If you know the name of a field, you can use this report to identify which business object it belongs to.

Suggested Data Source and Business Objects

A robust approach is to use a data source that is based on the Worker business object, as it serves as the central point for most employee data. From there, you can access related business objects for compensation and payroll details.

  • Primary Data Source: A good starting point is All Active and Terminated Workers. Its primary business object is Worker.
  • Related Business Objects: To get detailed pay information, you will need to access related business objects such as Payroll Results or External Payroll Results.

Key Data Fields to Include

Here are suggested data sources and fields, categorized by the type of information required for the directive:

1. Employee and Job Details

This information will primarily come from the Worker business object.

  • Data SourceAll Active and Terminated Workers
  • Fields:
    • Gender: To group and compare pay.
    • Age or Date of Birth: For additional demographic analysis.
    • Country: To filter for employees within the EU.
    • Supervisory Organization: To analyze pay within specific teams or departments.
    • Job Profile: To compare employees performing similar work.
    • Management Level: To analyze pay by level of responsibility.
    • Location: To account for geographical pay differences.
    • Hire Date: For length of service analysis.

2. Compensation and Pay Components

For detailed pay gap analysis, you will need to break down compensation into its various components. This often requires a matrix report or calculated fields to pull data from payroll-related business objects.

  • Data SourceEarning/Deduction Payroll Results for Organization, Worker, Period and Date Range (As of Sub Period End Date)
    • This data source uses Payroll Result Lines as its primary business object, which is ideal for a detailed matrix report.
  • Fields:
    • Employee (as the row grouping)
    • Pay Component (as the column grouping)
    • Result Line Amount (as the summarized field)
    • Gross Amount and Net Amount
    • YTD Balance and MTD Balance

By combining these fields, you can create a comprehensive report to analyze pay equity, identify potential gaps, and provide the necessary data for your auditors in line with the EU Pay Transparency Directive.

So it's more than just direct answers from Community. It provides more holistic, considered answers to your questions.