---
title: "How Workday Audits Web Service Business Processes — Kiweely"
description: "Where Workday records initiator identity, OAuth API clients, timestamps, comments, and approval steps when business processes start via REST or SOAP."
url: https://kiweely.com/guides/workday-business-process-audit-trail-initiated-via-web-service
---

# How Workday Audits Business Processes Initiated via REST or SOAP Web Services

Workday records every web-service-initiated business process in the Full Process Record and View Audit Trail under the authenticated Workday account. Whether that audit trail shows a real employee or a shared system bot depends on whether the caller used user-delegated OAuth or an ISU.

-   **Checked** against Workday on November 15
-   Applies to **Workday Business Processes & Auditing**
-   6 min read
-   Published November 15
-   By Kiweely

Workday logs every business process initiated through a REST endpoint or SOAP operation inside the event’s **Full Process Record** and the **View Audit Trail** report using nondestructive updates. What appears in the **Initiator** and **By** columns depends entirely on the authentication method: a user-delegated OAuth client (`Register API Client`) logs the individual worker’s Workday account, whereas an integration credential (`Register API Client for Integrations` or WS-Security) logs the shared Integration System User (ISU).

Understanding how Workday separates business process history, system audit trails, and user activity logs allows security administrators and SOX auditors to trace external API writes with zero ambiguity.

## Where Workday Stores Web Service Transaction Evidence

Workday splits transaction evidence across four distinct surfaces, each governed by its own security domain in the `System` functional area.

| Audit Surface | Navigation / Task | Required Security Domain | Key Web Service Fields Captured |
| --- | --- | --- | --- |
|  **Full Process Record** | Related Actions on event -> **Business Process** -> **Full Process Record** | `Business Process Administration` (or contextual access to the event) | `Process` tab steps, `By` (completing account), `For` (reassigned/delegated target), `Event Record Moment`, `Comments`, and `All Actions` sub-events |
|  **Object Audit Trail** | Related Actions on instance -> **Audit** -> **View Audit Trail** (or run `View Audit Trail` task) | `System Auditing` (or `Auditor` security group) | Nondestructive old value, new value, submitting Workday account, transaction timestamp, and originating web service task name |
|  **Account / Task Audit** | `View User or Task or Object Audit Trail` report | `System Auditing` | Filtered history of all changes made by a specific Workday account (such as an ISU or employee), specific web service task, or business object over a date range |
|  **Session & Request Log** | `View User Activity` report or `/activityLogging` REST endpoint | `User Activity Logging` (`Enable User Activity Logging` on `Edit Tenant Setup - System`) | `Request Time`, `System Account`, client `IP Address`, `User Agent`, accessed `Task`, `Target` object, and `Activity Category` (`READ` or `WRITE`) within a rolling 30-day window |

## User-Delegated OAuth vs. Integration System User Attribution

When an external application initiates a Workday business process—for example, `POST /workers/{ID}/requestTimeOff` in the `absenceManagement/v5` REST API, `POST /eventSteps/{ID}/approve` in `businessProcess/v1`, or `Submit_Expense_Report` via SOAP—Workday resolves the caller’s credential to a Workday account before evaluating the Business Process Security Policy.

### 1\. User-Delegated OAuth (`Register API Client`)

When an application authenticates workers via OAuth 2.0 Authorization Code Grant (with PKCE), Workday binds the session to that specific employee’s Workday account:

-   **Initiation Security Check:** Workday checks whether the worker’s own security groups (`Employee As Self`, `Manager`, `HR Partner`) hold `Initiate` permission on the Business Process Security Policy (for example, `Request Time Off` or `Home Contact Change`).
-   **Process Tab Attribution:** On the **Full Process Record** -> **Process** tab, the `Initiation` step shows the employee’s name and Workday account, the exact completion timestamp, and any comment passed in the API payload.
-   **Approval Routing:** Because the process is initiated interactively under a worker’s security context rather than an automated integration batch, Workday evaluates all configured step entry conditions, validation conditions, and `Approval` or `Approval Chain` steps identically to a browser submission.

### 2\. Integration System User (`Register API Client for Integrations` or ISU SOAP)

When middleware authenticates with an Integration System User:

-   **Initiation Security Check:** The ISU’s `Integration System Security Group` (constrained or unconstrained) must be explicitly added to the **Initiating Action** list for the web service operation on the Business Process Security Policy (and hold `Put` access on the underlying integration domain).
-   **Process Tab Attribution:** Every event initiated through that middleware displays the ISU account name (for example, `ISU_Expense_Portal`) as the initiator. If middleware accepts requests from 5,000 employees and submits them through one ISU, Workday’s native `Initiator` field cannot distinguish which human triggered the request unless the middleware writes an unverified text string into the `Comment` element.
-   **Auto-Complete Behavior:** Many SOAP operations expose a `Business_Process_Parameters` block containing `<wd:Auto_Complete>true</wd:Auto_Complete>`. When `Auto_Complete` is set to `true`, Workday automatically skips `Approval` steps and step conditions on approvals—though it still evaluates entry condition rules for `Integration` steps, `Service` steps, and `Action` steps that launch sub-events.

xml

```
<!-- SOAP Business_Process_Parameters block: Auto_Complete=false preserves full approval routing -->
<wd:Business_Process_Parameters>
  <wd:Auto_Complete>false</wd:Auto_Complete>
  <wd:Run_Now>true</wd:Run_Now>
  <wd:Comment_Data>
    <wd:Comment>Submitted from external absence portal</wd:Comment>
  </wd:Comment_Data>
</wd:Business_Process_Parameters>
```

## Inspecting the Full Process Record After an API Call

To audit a specific transaction initiated via REST or SOAP, locate the event (using `Find Events`, the worker’s **Worker History**, or `GET /events` in `businessProcess/v1`) and open **Related Actions** -> **Business Process** -> **Full Process Record**:

1.  **Process Tab:** Lists every executed and remaining step. Check the **Status** column (`Initiated`, `Submitted`, `Awaiting Action`, `Approved`, `Step Completed`, `Auto-Completed`) and the **Person (Up to 5)** / **By** columns. If a step was reassigned or completed via `POST /eventSteps/{ID}/reassign`, Workday displays `Reassigned` in **Status**, puts the original assignee in the **For** column, and updates the **Event Record Moment** on the **All Actions** tab once the reassignment completes.
2.  **Comments Tab:** Displays comments submitted in the initial REST/SOAP payload or appended during step actions (`POST /eventSteps/{ID}/approve`, `deny`, or `sendBack`), along with the author’s Workday account and timestamp. Note that if the Business Process Security Policy enables **Hide Comments from Person** or **Hide Process History from Person**, the target worker will not see approval comments, though auditors on `Business Process Administration` still see the complete record.
3.  **All Events & Notifications Grid:** Displays sub-events triggered by the transaction and custom or system notifications delivered across email or SMS channels (`Channel Sent On`).
4.  **All Actions Tab:** Breaks down every underlying service step, approval assignment, and sub-process action, recording the exact **Event Record Moment** timestamp external audit integrations rely on.

## Querying Business Process Events via REST and WQL

Auditors and integration engineers can verify event initiation and step progression programmatically without opening the browser UI.

### Using the `businessProcess/v1` REST API

The `GET /events` endpoint retrieves business process events for a specified worker (the `worker` query parameter is required; omitting it returns an empty collection) and is secured by the `Core Navigation` and `Public Business Processes` domains:

http

```
GET /ccx/api/businessProcess/v1/{tenant}/events?worker=3aa5550b7fe348b98d7b5741afc65534&initiatedOnOrAfter=2026-11-01T00:00:00Z&limit=20
Accept: application/json
```

Once you have the event Workday ID (`ID`), inspect completed and pending workflow steps:

-   `GET /events/{ID}/completedSteps` — returns each finished step, completing worker, and completion timestamp.
-   `GET /events/{ID}/inProgressSteps` — returns steps currently awaiting human or integration action.
-   `GET /events/{ID}/remainingSteps` — projects downstream steps remaining in the workflow.
-   `GET /events/{ID}/comments` — returns audit comments attached to the event.

### Using WQL for Tenant-Wide Process Audits

Administrators secured to the `Business Process Administration` domain can query the indexed `businessProcessTransactionsIndexed` data source via WQL to audit web-service-initiated events across the tenant by initiator and date range:

sql

```
SELECT businessProcessEvent,
       worker,
       initiator,
       status,
       effectiveDate,
       dateAndTimeInitiated,
       dateAndTimeCompleted
FROM businessProcessTransactionsIndexed
WHERE dateAndTimeInitiated >= '2026-11-01T00:00:00.000-08:00'
  AND inProgress = true
```

## Correlating Network Origin in User Activity Logging

While `View Audit Trail` persists permanently for SOX compliance, it focuses on business object mutations rather than HTTP client metadata. When you also need the caller’s source IP address and HTTP `User-Agent`, verify that **Enable User Activity Logging** is checked on **Edit Tenant Setup - System**:

-   Workday flushes activity records to the `View User Activity` report approximately every 2 minutes and retains them for 30 days before purging older rows during the weekly maintenance window.
-   Export records weekly via a scheduled custom report on the `User Activity` data source or the `/activityLogging` REST endpoint (which returns up to 250,000 rows in background mode compared to 50,000 in interactive UI runs).
-   Combine `Maintain IP Ranges` and `Manage Authentication Policies` so Workday rejects OAuth bearer requests originating outside your approved connector infrastructure.

External portals and AI assistants should preserve this native per-worker auditability rather than funneling actions through an ISU. Both [Kiweely Bridge](https://kiweely.com/bridge) and [Kiweely Leaf](https://kiweely.com/leaf) (both coming next) authenticate exclusively through user-delegated `Register API Client` OAuth grants and pause enabled writes for out-of-band browser confirmation, ensuring every transaction in Workday’s `Full Process Record` and `View Audit Trail` reflects the real employee who approved it.

## Frequently asked questions

### Does a REST or SOAP call bypass Workday's nondestructive audit trail?

No. Every transaction submitted through Workday REST APIs or SOAP web services runs through the same Object Management System business services as browser UI actions, recording old values, new values, the submitting Workday account, and exact timestamps.

### Why do some web service transactions skip Approval steps automatically?

When a SOAP web service request or EIB sets Auto\_Complete to true (and the caller holds Put permission on the integration domain), Workday skips Approval steps while still evaluating entry conditions on Integration, Service, and sub-event Action steps.

### How can auditors tell if an action came from an API client rather than a browser session?

Run View Audit Trail on the business process event alongside View User Activity (when Enable User Activity Logging is active on Edit Tenant Setup - System) to inspect the System Account, IP Address, User Agent, and REST or SOAP task entry.

### Who appears as the initiator when an API client uses Authorization Code Grant?

Workday records the signed-in worker's own Workday account in the By and Initiator columns of the Process History and Audit Trail, preserving individual accountability for SOX and internal compliance reviews.

## Sources checked

-   [Workday Concept: Auditing](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/auditing/dan1370797846272.html)
-   [Workday Reference: Auditing-Related Reports](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/auditing/wln1467042699742.html)
-   [Workday Concept: View Business Process Details](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-process-framework-concepts/dan1370797847910.html)
-   [Workday Concept: User Activity Logging](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/user-activity-logging/unv1636547598141.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### How to Authenticate Workday Studio and External Tools Using an OAuth API Client with PKCE (When SSO Blocks Passwords) When SSO leaves consultants without a Workday password, register an API Client with Authorization Code Grant and Support Proof Key for Code Exchange enabled, then use that client ID with Studio or Vine OAuth sign-in instead of username and password auth.](https://kiweely.com/guides/workday-api-client-pkce-sso-without-workday-password)
-   [### How to Audit Over-Permissive Workday Security Groups Before Turning On AI Agents Delegate AI agents inherit the union of an invoking user’s security groups, while ambient agents act through dedicated Ambient Agent Security Groups. Before activating any agent, audit unconstrained User-Based groups, stale role assignments, and View Security for Agent Skill pathways.](https://kiweely.com/guides/workday-security-audit-before-enabling-ai-agents)
-   [### How do I set up an integration system user and API client in Workday so an external app can authenticate? Create the ISU, put it in an Integration System Security Group, grant domain permissions and activate them, register the client for integrations, then generate its refresh token and pick the ISU as the Workday account.](https://kiweely.com/guides/workday-integration-system-user-api-client)

### More guides on Integrations and APIs

[All 89 guides](https://kiweely.com/guides#integrations)

-   [Approving, Denying, and Sending Back Workday Business Process Steps via REST and SOAP APIs](https://kiweely.com/guides/workday-business-process-approve-deny-rest-soap-api)
-   [How Workday Studio PutIntegrationMessage Severity Levels Control Completed-with-Warnings vs. Aborted Runs](https://kiweely.com/guides/workday-studio-error-severity-critical-warning-abort)
-   [How to Fix Workday Studio SDKProfile Not Current and Unsigned Software Startup Errors on Mac and Windows](https://kiweely.com/guides/workday-studio-sdkprofile-not-current-unsigned-macos-errors)
-   [Workday PECI vs. PICOF Payroll Connectors: How Effective-Dated Stack and Retro Changes Export](https://kiweely.com/guides/workday-peci-picof-payroll-connector-change-detection)
-   [Why does my Workday Accounting Journal EIB fail? Balancing, worktag and period errors](https://kiweely.com/guides/workday-financials-accounting-journal-eib-validation-errors)
-   [How to Find Every Domain and Web Service Permission an ISU Needs in Workday (Without Guesswork)](https://kiweely.com/guides/workday-isu-permissions-activate-pending-security-policy-changes)
-   [How to Fix The Load Contains a Duplicate Key and Invalid Reference ID Errors in Workday EIB](https://kiweely.com/guides/workday-eib-duplicate-key-reference-id-errors)
-   [How to Troubleshoot Workday Cloud Connect for Benefits (CCB) and Missing Dependents on 834 Feeds](https://kiweely.com/guides/workday-cloud-connect-for-benefits-834-errors)

### From the blog on Integrations and APIs

[All posts](https://kiweely.com/blog)

-   [What Is an AI-Built Workday Integration Platform Outside the Tenant?](https://kiweely.com/blog/what-is-ai-built-workday-integration-platform)
-   [Nothing Kept After a Run: Zero-Retention Workday Integrations](https://kiweely.com/blog/nothing-kept-after-a-run-zero-retention-integrations)
-   [Retire Workday Studio and EIB Debt with External Integrations](https://kiweely.com/blog/retire-workday-studio-eib-debt-with-external-integrations)

## Let Workday check the work.

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

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

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