Setup Considerations: Calculations
You can use this topic to help make decisions when planning your configuration and use of calculations in Workday. It explains:
- Why to set them up.
- How they fit into the rest of Workday.
- Downstream impacts and cross-product interactions.
- Security requirements and business process configurations.
- Questions and limitations to consider before implementation.
Refer to detailed task instructions for full configuration details.
What It Is
A calculation in Workday performs a specific operation and delivers a result. The result can be a:
- Date.
- Numeric value.
- Boolean (true/false) response.
Business Benefits
- Workday calculations enable you to use Workday data to make business decisions, reducing the need to refer to other information sources.
- Workday delivers many standard calculations that are available for you to use. You can also create custom calculations to process information based on the unique needs of your business.
- Calculations in Workday are transparent. Calculation administrators can view the calculation conditions and operands to verify the setup.
Use Cases
Use cases for calculations vary, depending on the type of calculation and the Workday products that you use.
Product | Example Use Cases |
|---|---|
Absence |
|
Payroll |
|
Student |
|
Questions to Consider
Question | Considerations |
|---|---|
How many calculations are you creating? How often are you processing them? | Workday recommends that you follow these guidelines to optimize processing time:
|
What kinds of data can you use as inputs in calculations? | You can use Workday-delivered report fields that have an authorized usage of Calculation Engine (Payroll/Absence) or other calculations.
You can use custom fields as operands only in these calculation types:
|
What if you need to modify a calculation? | When calculation parameters or operands change, consider whether you can replace the calculation instead of modifying it. If you must modify an existing calculation, use caution.
Calculations aren't effective dated, except for advanced lookup tables. Modifying existing calculations could have undesirable impacts on calculations that evaluate data in the past, such as retro pay in Payroll and Absence. Components that reference the calculations, such as earnings, deductions, time off plans, and accruals, are effective dated. You can replace the calculations in the components that use them and create a new effective date snapshot for the change. When replacing a calculation, create a new calculation by copying the existing calculation. Name both calculations so that it's clear that one replaces the other. |
Which users will view, modify, and use calculations? | You can create a calculations administrator role, and assign those users security to maintain calculations. Because calculations can impact multiple products, and can use or generate sensitive or confidential data, ensure that any user with access to edit calculations understands the impacts. |
Do you use more than 1 Workday product that uses calculations? | If yes, and different workers manage calculations for different products, consider setting up segmented security for calculations. Segmented security can prevent workers from accessing or using calculations from other product areas |
Recommendations
- Before you create calculations, define a naming convention for them. Make sure that the name reflects what the calculation does, making it easier to select the correct calculation when you search. You can also use theCommentsfield to document the purpose and the logic of the calculation.
- Always search for an existing calculation before you create a new one.
- For best performance and maintainability, avoid creating large nested calculations when possible.
- Don't use a custom calculation in more than 1 product area. Changes that you make for 1 product might not apply to others. Instead, create separate calculations for each product.
- Change the name of inactive calculations so that it's clear that they're no longer in use.
- If you plan to use custom fields in calculations, review the requirements for using custom fields in calculations.Workday only supports custom fields under specific conditions in calculations. See Concept: Requirements for Custom Fields in Calculations.
- For Payroll calculations: When you test custom calculations in a sandbox environment, check them for accuracy in both on-cycle and retro pay calculations.
Requirements
Assign each of your company-specific calculations to 1 or more product-specific categories. Use the category to identify the Workday products that use the calculation. Category can be used to limit access to calculations.
Limitations
- You can't edit, copy, or delete Workday-owned calculations.
- You can't combine AND and OR conditions in the same logic calculation. Instead, you can nest calculations by selecting a logic calculation as an operand of another logic calculation.
Tenant Setup
Access the
Calculation Assistant Opt-In
task to enable the Calculation Assistant, which uses generative AI to provide you with insights into the meaning and structure of calculations.Security
Domain | Considerations |
|---|---|
| Users with security enabled for these domains can create, view, and edit calculations. |
Access Calculation (Segmented) domain in the Core Payroll, Implementation, Payroll Interface, and Time Off and Leave functional areas | Users can configure access to calculations using segment-based security groups. |
Set Up: Student Interim Calculation domain in the Financial Aid functional area. | Users with security enabled for this domain can create, view, and edit interim calculations. |
Calculation: Delete domain in these functional areas:
| Users with security enabled for this domain can delete calculations that aren’t in use. |
Business Processes
No impact.
Reporting
You can use the
All Calculations by Category
report data source to create custom reports on calculations. Reports or Dashboards | Considerations |
|---|---|
All Calculations
| Use to review calculations by category and type. You can view Workday-owned calculations, custom calculations, or both. |
All [calculation type] Calculations
| Use to review calculation details such as operands, conditions, and comments. You can view Workday-owned calculations, custom calculations, or both. |
Calculation Exception Audit
| Use this report to find calculations that:
|
Evaluate Student Calculation
| Use to test and review details for calculations in the Student or Common category. |
Tenant Analyzer
| Use to identify and fix payroll and absence calculations that don't meet Workday recommendations. |
Integrations
Web Services | Considerations |
|---|---|
Get Advanced Lookup Tables
| Retrieves information about advanced lookup tables. |
Put Advanced Lookup Table
| Uploads advanced lookup table data. Can also update or delete data in existing advanced lookup tables. |
Connections and Touchpoints
Features | Considerations |
|---|---|
Absence | Time off plans, accruals, and time offs.
Absence balances. Calculate values over a period of time (Example: Year-to-date) for:
|
Custom fields | When configured, you can use custom fields as inputs to calculations. |
Payroll | Earnings and deductions.
Pay accumulations. Calculate a total by adding or subtracting the values of:
Pay balances. Calculate values over a period of time (Example: Year-to-date) for:
Pay component groups. Calculate a total by adding the values of a set of earnings and deductions in a pay period. To subtract, use a pay accumulation or an arithmetic calculation. |
Financial Aid | Calculate amounts for:
Specify eligibility for:
Calculate the minimum cumulative GPA for satisfactory academic progress. |
Student Financials | Calculate amounts for:
Specify eligibility for:
|
Workday offers a Touchpoints Kit with resources to help you understand configuration relationships in your tenant. Learn more about the Workday Touchpoints Kit on Workday Community.