People and compliance on Workday

Travel and expense approval on Workday

Approves expense reports within policy by rule and routes the exceptions to the manager and then finance, with the decision returned to Workday within seconds.

SCREENSDATA HANDLERSWORKDAY · READ IN PLACES01 Reports to reviewS02 Report reviewS03 Traveller mobileS04 Auditor checkS05 Expense boarddh_expense_reportExpense reportResource_Management: Get_Expense_Reportsdh_employeeEmployeeHuman_Resources: Get_Workers · RaaSworker reportdh_cost_centerCost centerFinancial_Management: Get_Cost_Centers ·Get_Organizationsdh_budget_lineBudget lineFinancial_Management: Get_Budgets ·Get_Budget_AmendmentsWRITE BACK TO WORKDAYExpense report → Submit_Expense_Report · Approve_Business_Processrows stay in Workday · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the Workday object it reads in place. Writes below the line go through released interfaces with an acknowledgement.
4
objects read in place from Workday
catalogue
5
screens on those rows
catalogue
3 days
to production-grade
estimate
1
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The Workday objects behind each handler

Workers, organisations, positions, time off and expense reports are read in place through Workday's SOAP and REST web services and through Reports-as-a-Service for lists. The rows stay in Workday.

ObjectRead fromFields the app usesFreshness
Expense reportResource_Management: Get_Expense_ReportsExpense_Report.Status (status) · Expense_Report_Line.Expense_Item (policy) · Expense_Report.Total_Amount (amount) · Expense_Report.ID (number)live through the API
EmployeeHuman_Resources: Get_Workers · RaaS worker reportWorker.Employee_ID (id) · Worker.Legal_Name (name) · Worker.Supervisory_Organization (org unit) · Worker.Position_ID (position)live through the API
Cost centerFinancial_Management: Get_Cost_Centers · Get_OrganizationsCost_Center.ID (id) · Cost_Center.Name (name) · Organization.Manager (owner) · Company.ID (company)live through the API
Budget lineFinancial_Management: Get_Budgets · Get_Budget_AmendmentsBudget.Budget_Structure (object) · Budget_Line.Amount (amount) · Budget.Fiscal_Year (year) · Budget.Budget_Name (version)live through the API
The trigger

The start criterion in Workday's own fields

In plain words: An expense report submitted in Workday whose lines carry a policy flag, or whose total is above 1,000.

The criterion runs in Workday through the data handler, so only the matching rows return. The editor shows the rows it selects, and their count, as it is written.

# start criterion in Workday fields
Expense_Report.Status = 'submitted' and (Expense_Report_Line.Expense_Item = 'exception' or Expense_Report.Total_Amount > 1000)

# the same criterion in canonical fields
{expense.status} = 'submitted' and ({expense.policy} = 'exception' or {expense.amount} > 1000)
What the app writes back

Through released interfaces

Writes go through the released web-service operations (for example Submit_Expense_Report, Request_Time_Off, Hire_Employee) under an integration system user with the security groups the operation needs. Each call returns the Workday ID, and the app records it beside the decision.

ObjectWhat changesInterface
Expense reportapproval, return or rejection written to the Workday business process step with the note; the report moves to payment or back to the travellerSubmit_Expense_Report · Approve_Business_Process
Acknowledged and logged

Each write stores the identifier Workday returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.

Access and prerequisites

What is in place before the first build

Security groups are mapped to Lima access policies once. A manager sees their own team in the app, exactly as in Workday.

  • An integration system user with domain security for the objects the app reads and writes
  • A Reports-as-a-Service report for each list the app needs at scale
  • Tenant URL and allowed IP set up
  • Business-process definitions in Workday agreed so approvals raised from the app land in the right step
Register the handlers4 objects from the catalog; each shows its rows at once.
Nearby

This app on other systems, and other apps on Workday

Travel and expense approval on

Other apps on Workday

Terms on this page

Policy flagThe mark Workday puts on an expense line that passes a limit or is still waiting for its receipt.
Business process stepThe approval step in Workday's expense business process that the app completes on the approver's behalf.
Read in placeThe rows stay in Workday; the handler sends the filter and the columns and Workday returns the matching rows.
Questions

Does this app copy data out of Workday?

The screens read through handlers that leave the rows in Workday. History the app needs at scale is landed in the lake by the Backbone, which is the exception by design.

What does Workday need to allow?

The prerequisites above: an integration identity with read rights on the objects listed and write rights on the interfaces named, connectivity, and the scopes agreed with the process owner.

Can I run it on another system as well?

Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, and the app's other system pages show them.

See this app on your data

Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.