Skip to content
KiweelyKiweelyKiweely

How to Trace Who Approves a Leave or Expense Request in a Workday Supervisory Org

To find who approves a worker’s leave or expense request in Workday, inspect the active Business Process Definition for the worker’s Supervisory Organization, evaluate step entry and exit condition rules, and resolve assigned and inherited roles up the management or organization hierarchy.

  • Checked against Workday on
  • Applies to Workday Business Processes
  • 7 min read
  • Published
  • By Kiweely
On this page

To determine exactly who will approve a leave request (Request Leave of Absence / Request Time Off) or expense report (Expense Report Event) in Workday, trace four layers in order: which Business Process Definition governs the worker’s Supervisory Organization, which Entry Condition Rules activate each step, how Approval vs. Approval Chain routing resolves Position versus Organization hierarchies, and which worker holds the assigned or inherited role (plus any active task delegation) as of the event date.

Checking the worker’s direct manager on their profile header is never sufficient on its own: threshold-based approval chains, Cost Center Manager overrides on expense lines, unassigned local roles that inherit upward, and Manage Delegation Settings rules frequently route steps elsewhere.

Step 1: Identify the Governing Business Process Definition

Workday allows administrators to attach rule-based subordinate Business Process Definitions to specific Supervisory Organizations, countries, or company hierarchies alongside the Default Definition.

  1. Open the worker’s profile and note their Supervisory Organization (for example, Warehouse 4).
  2. Search for the business process type—such as Request Time Off, Request Leave of Absence, or Expense Report Event—and select Related Actions -> Business Process -> View Definition (requires Business Process Administration or Manage: Business Process Definitions in the System functional area for full inspection).
  3. If the tenant uses Rule-Based Business Process Definitions, check View Rule-Based Business Process Configuration first. Workday evaluates definition rules in order at initiation; a worker in Germany or in a unionized logistics org may execute a completely different workflow definition than the tenant’s (Default Definition).

Step 2: Distinguish Step Types and Routing Modes

Once you have the active Business Process Definition open on the Business Process Steps tab, inspect the Order, Type, If (Entry Condition), and Group (Security Group) columns. Leave and expense workflows rely on four primary approval patterns:

Step Type & Routing Pattern Common Leave / Expense Use Case How Workday Resolves the Assignee
Step Type & Routing PatternApproval (Single Constrained Role) Common Leave / Expense Use CaseStandard Request Time Off routed to Manager; Request Leave of Absence routed to Absence Partner or HR Partner How Workday Resolves the AssigneeRoutes to the worker(s) holding that role on the target worker’s Supervisory Organization (or inherited from the nearest Superior Organization if locally unassigned).
Step Type & Routing PatternApproval (Worktag / Cost Center Role) Common Leave / Expense Use CaseExpense Report Event routed to Cost Center Manager or Project Manager How Workday Resolves the AssigneeRoutes to the role holder on the Cost Center, Project, or Grant worktag entered on the expense header—or per line when Maintain Line-Level Routing is configured.
Step Type & Routing PatternApproval Chain (Position-Based Routing — Default) Common Leave / Expense Use CaseMulti-level Expense Report Event exceeding a dollar threshold or extended unpaid leave How Workday Resolves the AssigneeFollows the manager of the worker’s position, then the manager of that manager’s position, up the management chain until an Exit Condition returns true.
Step Type & Routing PatternApproval Chain (Organization-Based Routing) Common Leave / Expense Use CaseEnabled via Related Actions -> Business Process -> Maintain Advanced Routing -> Organization-Based Routing How Workday Resolves the AssigneeIgnores cross-hierarchy position reporting and routes strictly to the Manager role of the worker’s Supervisory Org, then the 2nd-level Superior Org, 3rd-level Superior Org, and so on.

Key Edge Case: Position Hierarchy vs. Organization Hierarchy

Suppose James sits in Organization A reporting to Betty (Manager of Organization A), whose own position reports to Logan in Organization BB rather than Tony in Organization AA (the Superior Organization of Organization A):

  • With Position-Based Routing (Workday’s default when Organization-Based Routing is unchecked), an Approval Chain step routes Betty -> Logan -> Steven (Organization BBB).
  • With Organization-Based Routing checked on Maintain Advanced Routing, the step routes Betty -> Tony -> Chris up Organization A -> AA -> AAA.
  • Check Edit Tenant Setup - Business Processes to see whether Enable Enhanced Position-Based Approval Chain Routing is enabled; when active, Workday evaluates all managers consistently at each level when a position reports to multiple managers and exposes predictive report fields such as Workers Possibly Assigned Next.

Step 3: Evaluate Entry, While-Running, and Exit Condition Rules

A step listed on the Business Process Definition only fires if its conditions pass. Select Related Actions -> Business Process -> Maintain Step Conditions on any step to inspect three distinct condition hooks:

  1. Entry Condition (If column): Evaluated before the step starts. Common examples include:
    • Leave duration > 5 days (Total Days Requested > 5 routes to HR Partner or Absence Partner).
    • Leave type in selection list (FMLA, Parental Leave, or Sabbatical).
    • Expense report total > threshold (Total Reimbursement Amount > 2500 USD triggers Cost Center Manager or Finance Auditor).
    • Processing user security caveat: if a condition rule references a report field whose security logic is embedded in the field itself and the user completing the previous step lacks access to that field, Workday skips the step.
  2. While-Running Condition (Approval Chain / Consolidated Approval Chain only): Acts as a per-level filter. If false at level $N$, Workday skips that level and checks level $N+1$. Watch out for Routing Restrictions (such as Exclude Prior Approvers): Workday evaluates the while-running condition before applying the routing restriction, which can leave a level Unassigned if the sole person at that level already approved an earlier step.
  3. Exit Condition (Approval Chain / Consolidated Approval Chain only): Evaluated starting from the completion of each level. In expense workflows, an Exit Condition typically checks whether the approver who just signed off holds a sufficient Approval Authority limit for the expense report amount. Once true, the chain exits immediately; if never met, it climbs all the way to the top of the management hierarchy.

If you are diagnosing an already initiated event and want to see why a rule returned true or false, open the event’s Related Actions -> Rule Tester (available for customer-created condition rules) to inspect the exact boolean evaluation trace.

Step 4: Resolve Supervisory Org Roles, Inheritance, and Delegations

Once you know which role-based security group a step targets (for example, Manager, Absence Partner, HR Partner, or Cost Center Manager), verify who actually holds that role:

  1. Open the worker’s Supervisory Organization (or the Cost Center worktag on the expense report) and select the Roles tab.
  2. Filter or scan for the Role assigned to the business process step:
    • Assigned directly: The worker(s) listed in Assigned To receive the task in My Tasks.
    • Inherited: If the role is not directly assigned on Warehouse 4, look at the Inherited section or click up to the Superior Organization. Workday inherits supporting roles downward automatically unless overridden locally.
    • Unassigned: If neither the local org nor any Superior Organization holds an active worker in that role—or if the sole assignee is the requester themselves and self-approval is restricted—the step stalls in Unassigned Tasks until a Business Process Administrator reassigns it.
  3. Check Active Delegations: Run Manage Delegation Settings (or inspect the For and Awaiting columns on an active event) for the resolved approver. If the manager delegated My Tasks approvals during their own vacation:
    • When Retain Access to Delegated Tasks within My Tasks is checked, the All Actions tab shows the delegate in Awaiting and both the delegate and delegator in Event.
    • When unchecked, only the delegate appears on the Process tab.

Inspecting Live Remaining Approvers on an Active Event

When a leave or expense request is already In Progress, you do not need to simulate rules manually:

  • In the Workday UI: Open the event -> Related Actions -> Business Process -> View Remaining Process (or open Full Process Record -> Process tab -> click Remaining Process). Workday evaluates the remaining steps and displays up to 5 awaiting names alphabetically in Person (Up to 5) and the total count in All Persons.
  • Via the Workday REST API: Query GET /events/{ID}/inProgressSteps and GET /events/{ID}/remainingSteps in businessProcess/v1:
http
GET /ccx/api/businessProcess/v1/{tenant}/events/8f219c04e112100018a4c9002b110091/remainingSteps?limit=20
Accept: application/json
  • In Custom Reports: Include Awaiting Persons for the active step and Workers Possibly Assigned Next (or Workers Possibly Assigned Next Excluding Delegates) for downstream chain levels.

Questions like “Who is my expense report waiting on right now?” are among the highest-volume internal helpdesk pings. With Kiweely Bridge (coming next), employees and managers can ask Claude, ChatGPT, or Gemini directly under their own Workday OAuth permissions—or approve pending leave and expense cards from Slack, Microsoft Teams, or the phone through Kiweely Leaf (coming next)—while honoring every Business Process Security Policy visibility setting (Hide Comments from Person, Hide Process History from Person) configured in your tenant.

Frequently asked questions

Why did a request route to a superior Supervisory Organization's HR Partner instead of a local one?

When an assignable role such as HR Partner or Absence Partner has no direct assignee on the worker's immediate Supervisory Organization, Workday walks up the Superior Organization chain and assigns the step to the inherited role holder.

What is the difference between position-based routing and organization-based routing on an Approval Chain step?

Position-based routing (the default) follows the manager of the worker's position and each manager's own position hierarchy, even across different org trees. Organization-based routing (enabled in Maintain Advanced Routing) follows the managers of Superior Supervisory Organizations.

How can I see remaining approvers on an already submitted leave or expense event?

Open Related Actions on the event, select Business Process -> View Remaining Process (or open the Full Process Record -> Process tab and click Remaining Process), or call GET /events/{ID}/remainingSteps in the businessProcess/v1 REST API.

Why did an Approval Chain step stop after one manager for one expense report and climb three levels for another?

Approval Chain steps evaluate while-running and exit condition rules at each level—typically comparing the Expense Report Total Amount against each manager's Spend Approval Authority or management level.

Sources checked

Related guides

All guides

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

We’ll email you once to confirm. Unsubscribe in one click from any issue.