Skip to content
KiweelyKiweelyKiweely

Approving Workday Expense Reports and Purchase Requisitions in Teams and Slack

Approving Workday Expense Report Event and Requisition Event workflows in Teams or Slack requires more than header totals: managers need itemized spend categories, corporate card flags, receipts, and supplier worktags rendered live under Workday security.

  • By Kiweely
  • 6 min read
On this page

Cost-center managers and finance approvers will not approve a $4,800 Expense Report Event or a $32,000 Requisition Event in Microsoft Teams or Slack if the card shows only a header total and a requester name. To move financial approvals out of email backlogs without weakening internal controls, an embedded Teams or Slack approval view must render itemized lines, Spend Categories / Expense Items, Cost Center and Project worktags, corporate card vs. out-of-pocket splits, and live receipt or quote attachments—all fetched on demand under the approver’s own Workday OAuth session.

Financial approvals fail in generic chat bots for the opposite reason HR notifications fail: too little line-item scrutiny. Under SOX and procurement policy, clicking Approve attests that the approver verified business purpose, accounting worktags, policy exceptions, and supporting documentation. When a chat card hides line splits or attachments, conscientious budget owners ignore the bot, while careless ones create audit exceptions that Expense Partners have to unwind later.

What Approvers Actually Check on Expense Reports vs. Purchase Requisitions

Before wiring Workday APIs to a Teams tab or Slack modal, map the exact header, line, worktag, and attachment fields that turn a blind click into a compliant financial sign-off:

Field Group Expense Report Event (EXP-...) Requisition Event (REQ-...) Workday API / WQL Read Surface
Field GroupHeader Summary Expense Report Event ( EXP-... )Submitter, Reimbursement Currency, Total Amount, Corporate Card Paid vs. Employee Reimbursable, Business Purpose memo. Requisition Event ( REQ-... )Requester, Requesting Entity / Company, Requisition Type, Total Extended Amount, Deliver-To Location. Workday API / WQL Read SurfaceGET /expense/v1/reports/{ID} or WQL expenseReportsForCompany; GET /procurement/v5/requisitions/{ID}
Field GroupLine-Level Detail Expense Report Event ( EXP-... )Expense Date, Expense Item (Airfare, Hotel, Client Meals), Merchant, Per-Unit / Converted Amount, Attendees, Itemizations (hotel room vs. room service). Requisition Event ( REQ-... )Item Description, Spend Category, Supplier / Supplier Contract, Quantity, Unit Cost, Ordering Method. Workday API / WQL Read SurfaceWQL expenseReportLinesAndItemizations; GET /procurement/v5/requisitions/{ID}/requisitionLines
Field GroupAccounting Worktags Expense Report Event ( EXP-... )Cost Center, Company (highlighting intercompany overrides), Project / Billable flag, Custom Worktags. Requisition Event ( REQ-... )Cost Center, Split Allocation percentages across departments, Project, Fund / Grant. Workday API / WQL Read SurfacerequisitionLinesAndLineSplitsForCompany (WQL) & expenseReportLinesAndItemizations
Field GroupRisk & Policy Flags Expense Report Event ( EXP-... )Expense Protect risk alerts, missing receipt flags, policy rate-table overages, duplicate transaction warnings. Requisition Event ( REQ-... )Check Budget (Financial) status, non-catalog manual sourcing flag, questionnaire responses. Workday API / WQL Read SurfacebusinessProcess/v1/events/{ID} + step help text & comments
Field GroupSupporting Files Expense Report Event ( EXP-... )Scanned meal/hotel receipts (JPEG/PDF) per expense line. Requisition Event ( REQ-... )Vendor SOWs, competitive quotes, sole-source justification PDFs. Workday API / WQL Read Surfaceprocurement/v5/.../attachments/{subID}?type=getFileContent & businessProcess/v1/events/{ID}/attachments

A frequent surprise when building external Expense or Procurement approval screens is hitting 403 Forbidden on line-item reads even though the manager can see the task in GET /common/v1/workers/me/inboxTasks.

Why that happens: inboxTasks requires only Core Navigation, whereas reading financial lines via REST or WQL checks functional domain security (domain vs. business process security policies). Notice in Workday’s OpenAPI specification that GET /expense/v1/reports/{ID} is secured by Self-Service: Expense Report (designed for a worker’s own expense reports), whereas managers and cost-center approvers inspect subordinate and org-routed expense lines through organization-scoped domains in the Expenses and Procurement functional areas:

  • Expense Report Manager / Cost Center Approver Domains:
    • View: Organization Expense Report and Reports: Organization Expense Report Line Reporting (subdomains under Reports: Organization Expense Report Reporting) allow organization-based roles to query header, line, and itemization rows via WQL (expenseReportLinesAndItemizations, expenseReportsForCompany).
    • Process: Expense Report - View (under Process: Expense Reports) grants company-based or unconstrained roles (such as Expense Partner or Auditor) view access across the company.
  • Purchase Requisition Approver Domains:
    • GET /procurement/v5/requisitions/{ID} and /requisitionLines explicitly honor View: Organization Requisition, Process: Requisition - View, Process: Requisition - Reporting, and Self-Service: Requisition, alongside the Requisition Event business process security policy.

On your user-delegated Register API Client registration, include the Expenses, Procurement, and Tenant Non-Configurable (plus Workday Query Language if running WQL line queries) Functional Areas. Because every call uses the signed-in approver’s own OAuth token, an engineering cost-center manager can inspect lines routed to CC-410 Cloud Infrastructure while remaining completely blocked from reading executive travel or unrelated marketing requisitions.

Streaming Receipt Images and Vendor Quotes Without Storing Files

Financial receipts and supplier Statements of Work contain sensitive commercial pricing, home addresses on telecom bills, and travel itineraries. Caching those PDFs in an Amazon S3 bucket or chat attachment CDN creates unnecessary data-retention risk.

Instead, stream attachments on demand over TLS when the approver taps a receipt thumbnail inside the embedded Teams or Slack drawer:

http
GET /ccx/api/procurement/v5/{tenant}/requisitions/a3f5b554007d20e98360015c5e6daf6/attachments/9bc1048277d1100018a20015c5e6daf6?type=getFileContent HTTP/1.1
Authorization: Bearer <approver_delegated_access_token>
  1. Metadata First: Render file names, MIME types, and byte sizes alongside the line items so the chat drawer opens in under a second without downloading 15 MB of PDFs upfront.
  2. Ephemeral Byte Pass-Through: When the approver clicks Vendor_Quote_Q4.pdf or Hotel_Folio.jpg, fetch the binary stream using their Workday bearer token and render it directly in an in-memory viewer—writing zero bytes to server disk or chat channel history.

Handling Approve, Send Back, and Step-Type Nuances

Not every financial step in My Tasks is a simple Approval step—and treating Deny and Send Back as interchangeable frustrates employees:

  • Prefer Send Back Over Deny for Fixable Errors: If an employee coded a $220 client dinner to Office Supplies instead of Business Meals or forgot an itemized hotel folio, clicking Deny (POST /businessProcess/v1/eventSteps/{ID}/deny) kills the entire Expense Report Event. Surfacing a prominent Send Back action (POST /businessProcess/v1/eventSteps/{ID}/sendBack) with a required reason returns the report to the initiator with corporate card transactions still attached. (Note: if a step uses Workday’s specialized Send Back Expense Lines action or Review step where an Expense Partner edits worktags directly, check stepType on GET /businessProcess/v1/eventSteps/{ID}—Approval steps go to /approve, while Review or Action steps that require line-level edits such as buyer sourcing on manually sourced goods requisitions should deep-link cleanly to the specific task when buyer fields like Supplier or Fulfillment Source are mandatory.)
  • Intercompany Subprocesses: When an expense line crosses legal entities, Workday spawns Initiate Expense Report Intercompany Event. Remember Workday’s built-in rule: if an intercompany approver denies their subprocess step, Workday denies the entire parent expense report. Displaying a clear badge (“Intercompany Line Approval — Denying rejects the full report; use Send Back to request a Cost Center/Company correction”) prevents accidental full-report rejections.

See approving, denying, and sending back Workday business process steps via REST and SOAP APIs for exact request payloads and validation error codes.

How Kiweely Leaf and Kiweely Bridge Support Finance & Procurement Teams

  • Kiweely Leaf (coming next) lets HRIS and Financials admins build rich, line-item approval views for Expense Report Event and Requisition Event inside Microsoft Teams, Slack, DingTalk, Feishu, and Lark, in the browser, or in the Kiweely Leaf mobile app—complete with itemized worktags, split allocations, and live receipt previews, running 100% pass-through on each approver’s Workday OAuth token with zero financial data stored at rest and no Workday Extend license.
  • Kiweely Bridge (coming next) connects Claude, ChatGPT, and Gemini directly to Workday REST, WQL, SOAP reads, and RaaS reports under user-delegated OAuth so budget owners can ask ad-hoc spend and requisition questions in plain English, while holding every enabled write behind an out-of-band browser approval card.

Frequently asked questions

Why can a manager see an Expense Report approval step in My Tasks via API but get 403 Forbidden when fetching line items?

Workday separates Business Process step routing from domain read access. Ensure the API client includes the Expenses or Procurement Functional Area and the manager's security group holds View permissions on domains such as View: Organization Expense Report, Reports: Organization Expense Report Line Reporting, or View: Organization Requisition.

Can approvers inspect receipt images and supplier quote PDFs inside an embedded Teams or Slack approval view?

Yes. Stream attachment bytes on demand from Workday's procurement v5 (/requisitions/{ID}/attachments/{subresourceID}?type=getFileContent), businessProcess v1 (/events/{ID}/attachments), or expense line attachment endpoints using the approver's OAuth token without caching files on an external server.

How does intercompany or split cost-center routing affect chat approvals?

Workday's Expense Report Event and Requisition Event workflows support line-level routing modifiers, split worktag allocations, and Initiate Expense Report Intercompany Event subprocesses. Querying awaiting Event Record steps per approver guarantees each cost-center manager sees and approves the exact step Workday routed to them.

What is the difference between Deny and Send Back on an Expense Report or Requisition?

Deny permanently terminates the Expense Report Event or Requisition Event (forcing the requester to build a new submission or cancel), whereas Send Back returns the transaction to the initiator or a prior review step so the employee can fix a missing receipt or wrong Spend Category and resubmit.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

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