Use these prompts in Deployment Agent in an Implementation, Preview, Sandbox, or Customer Central tenant. The agent is not for Production payroll processing. CRAFT, from the sample-prompts topic (updated 2026-11-06), is Context, Role, Action, Format, and Tone. Add in my tenant, or in my [tenant name] tenant in Customer Central, when the answer must match your configuration. Ask has no on-screen indicator.
Published prompts are quoted from Workday. Pattern prompts keep that shape and name an object the same pages already use. Patterns are not extra official samples.
Payroll Agent, on the Workday-Built Agents list, is a separate conversational assistant for Workday Payroll. Self-Service Agent has its own payroll skills. Do not ask Deployment Agent to turn those on. Configure them in Agent Management Hub.
Published prompts
New Financials calculated field
I am an implementer working on Financials. Provide step-by-step instructions on how to create a calculated field that counts Scheduled Weekly Days.
Context is Financials. Role is implementer. Action is the count. Format is step-by-step. There is no “in my tenant,” so treat the answer as how-to guidance. If Scheduled Weekly Days is not a field on the business object in your tenant, say so in a follow-up and name the object Business Object Details shows.
Object Transporter and Payroll
I am getting a SOAP error while using Object Transporter to migrate Payroll data. What are the common causes for this error and how do I fix them?
This published sample does not include the error text. Prefer the SOAP example’s second step and paste the fault. Use this sentence when you truly want common causes for Object Transporter payroll migration, then follow with the exact message.
Submit_Expense_Report parent-element fault
Published, in two turns:
I am an integration consultant working on a Financials implementation. I am calling the Submit_Expense_Report web service and receiving a ‘Validation error occurred’ message regarding a missing field.
The error says: ‘The field Expense_Report_Data is required.’ I have confirmed this field is in my XML. What are the most common hidden missing fields or security issues that cause this specific SOAP fault for this service?
The topic says this generic parent fault sometimes means a missing child element or a security requirement. Optional third turn, also published:
List the specific functional area and security domain permissions my Integration System User (ISU) needs to initiate this specific web service.
Payroll Specialist cannot see a field
I am a Workday security administrator. In my tenant, users assigned to the Payroll Specialist role cannot view the ‘Bonus Plan Override’ field on worker profiles. Please look in my tenant and inspect our security configuration to explain which domain security policy controls access to this field, which security groups currently have View access, and how to update the policy.
The example result names domain Worker Data: Compensation Explicit, says the role-based Payroll Specialist group is missing from View, and tells you to edit the policy and activate pending changes. Check the domain yourself before you activate. Customer Central follow-up, published:
How would activating this security policy change impact downstream security group assignments in our impl2 tenant?
Replace impl2 with the connected tenant you mean.
Supplier invoice line, from the Evaluate Expression topic
This is a configuration grid, not a chat sample. Use it when the agent suggests a payee field and you need the published shape. Business object on the calculation tab is Payee in Workday’s table, field type Single Instance, default Empty Instance. Conditions: Supplier is not empty returns Supplier as Worktag. Contingent worker is not empty returns Contingent Worker. Evaluation stops at the first true row.
Ask for steps that match that grid:
I am a Workday administrator working on Financials. Provide step-by-step Create Calculated Field instructions for an Evaluate Expression on the Payee business object, field type Single Instance, default Empty Instance. If Supplier is not empty, return Supplier as Worktag. If Contingent worker is not empty, return Contingent Worker. Number the steps. State that testing stops at the first true condition.
That wording is a pattern wrapped around a published grid. The grid wins if the reply reorders the rows.
Patterns that stay inside published EIB and payroll skills
Inbound payroll EIB identifiers
Workday’s payroll EIB example uses Import Payroll Input or Import Payroll Off-cycle Payment, Separate Type Column on Deduction, and ID types Deduction_Code and Workday_Deduction_Code. Ask the agent to explain that mapping, not to invent columns:
I am an implementer working on Payroll. Provide step-by-step instructions for an inbound EIB on Import Payroll Input so one spreadsheet can load a company deduction code and a Workday deduction code. Include Template Model, Separate Type Column on Deduction, and where I look up ID types. Number the steps.
Then compare the reply to Integration IDs and keep the file as XML Spreadsheet 2003. If the launch returns a SOAP fault, switch to the published fault prompt and paste the integration event text. Do not stay on the “common causes” sample once you have a message.
Manager payroll input through Self-Service Agent
The MSS - Payroll - Advanced skill calls the existing Request Payroll Inputs business process, uses your payroll and security configuration, creates inputs only for workers on Workday Payroll, blocks the request when the primary position is in an external pay group or the worker has no pay group, and defaults a position-based input to the primary position for a multi-job worker when the manager does not name a position. Deployment Agent does not enable that skill. A safe explanatory prompt:
As a Workday administrator, give me a layman’s terms explanation of what the Self-Service Agent MSS - Payroll - Advanced skill will and will not submit. Provide the answer in bullet points.
Check the bullets against that skill description. If a bullet says the skill creates inputs for an external pay group, the bullet is wrong.
Employee payroll questions are not this agent
ESS - Payroll - Base retrieves compensation, payment, and tax-form information. ESS - Payroll - Advanced covers bank accounts, tax withholdings, and payment elections. Those are Self-Service Agent skills. A Deployment Agent prompt will not configure them. Say which product you are in before you test a worker scenario.
Checks before you trust a financial answer
| Reply claims | You confirm |
|---|---|
| Reply claimsA calculated field function | You confirmThe function exists on Create Calculated Field for that business object. Evaluate Expression: first true wins, then default. |
| Reply claimsA domain and a View group | You confirmThe domain security policy, then Activate Pending Security Policy Changes only after you agree. |
| Reply claimsAn ISU domain list | You confirmThe web service’s security, not a generic integration group. |
| Reply claimsAn EIB column | You confirmTemplate Model and Integration IDs. XML Spreadsheet 2003. |
| Reply claimsA payroll input for any worker | You confirmMSS - Payroll - Advanced blocks external pay groups and workers with no pay group. |
| Reply claims“Do this in Production chat” | You confirmDeployment Agent is not a Production assistant. Payroll Agent and Self-Service Agent are the other catalog rows. |
Thumbs up or thumbs down after you try the steps. For SOAP, the example’s closing line tells you to rate the guidance. Applying a domain change is a separate activation.
Frequently asked questions
Which prompt do I use for a payroll SOAP error?
If you have the message, use the two-turn Submit_Expense_Report pattern and replace the service name and the fault text. If you only know that Object Transporter failed while moving Payroll data, use the published Object Transporter sentence, then paste the fault in the next message.
Can one prompt cover the EIB and the security domains?
Split them. CRAFT samples are one Action. The EIB pattern ends at the template. The ISU question is the published third turn on the SOAP example.
Does this library configure Payroll Agent?
No. Payroll Agent is a Workday-built agent you register from the catalog if your SKU includes it. These prompts are for Deployment Agent in non-production.
What if Customer Central inspects the wrong payroll tenant?
The sample-prompts topic says to name the connected tenant. “In my tenant” is not specific enough there. Use the impl2-style follow-up with the real tenant name.
Sources checked
Frontmatter pages, fetched 2026-11-16.
Sources checked
- Deployment Agent Sample Prompts for Implementation Environments and Customer Central
- Example: Troubleshoot a SOAP Error with the Deployment Agent
- Example: Troubleshoot Security Policy and Access Configuration with the Ask Skill
- Example: Include Workday and Company-Specific Deductions in EIB Spreadsheets
- Self-Service Agent Skills
- Evaluate Expression