Skip to content
KiweelyKiweelyKiweely

Expense Report Create-and-Submit Screens Outside Workday Menus

Workday Expense v1 covers quick expenses, expense items, report lines, and report submit. Submit is the Expense Report Event. A screen outside Workday menus should validate first, then submit as the worker, and treat a saved draft as unfinished.

  • Checked against Workday on
  • Applies to Workday Extend
  • 4 min read
  • Published
  • By Kiweely
On this page

Workday’s Expense v1 REST service is the documented surface for quick expenses and expense reports. The explorer page describes reports you can create, modify, or submit, and it secures GET /reports with Self-Service: Expense Report and POST /reports/{ID}/submit with the Expense Report Event business process. A create-and-submit screen outside Workday’s menus has to follow that split: collect lines, then submit the event as the signed-in worker.

Kiweely Leaf (coming next) can host that screen in the browser, in Teams, or on the phone. It runs each call as that worker and stores the layout, not the receipts or the amounts.

The operations this session verified

Expense v1, base https://api.us.wcp.workday.com/expense/v1 on the explorer page:

Operation What Workday documents
OperationGET and POST /entries What Workday documentsQuick expenses. Create uses a minimal field set.
OperationGET, PUT, PATCH, DELETE /entries/{ID} What Workday documentsOne quick expense. POST /entries/{ID}/attachments adds files to an existing entry.
OperationGET /expenseItems and GET /expenseItems/{ID} What Workday documentsItems allowed on report lines.
OperationGET /reports What Workday documentsThe worker’s reports. Domain: Self-Service: Expense Report.
OperationGET /reports/{ID} What Workday documentsOne report.
OperationPOST /reports/{ID}/lines What Workday documentsAdds lines to a report.
OperationPOST /reports/{ID}/submit What Workday documentsSubmits that report. Business process: Expense Report Event.
OperationGET /values/bespokePrompt/... What Workday documentsPrompt values for currency, expense group, and expense item.

REST fundamentals also document the tenant path https://{tenantHostname}/api/{serviceName}/{version}/{tenant} for integrations. Use the host your API client is registered against. This guide does not paste a sample tenant host.

The explorer listing verified here does not print a separate create-report REST method next to GET /reports. The Graph API documents a createExpenseReport mutation whose input type is Expense_ReportPostServiceRepresentation_CreateInput, and a createQuickExpense mutation that can carry attachments. Confirm the create path in REST API Explorer on your tenant before you wire a button. If the tenant only exposes Graph for create, call that, then continue with the report id Workday returns.

Validate, then submit

Validate-only mode applies to REST POST, PUT, PATCH, and DELETE when you send x-validate-only: 1. Workday checks operation security, display options, field-level security, prompts, currency, and required fields, and it does not persist. A passing call returns 200. Persist by sending the same request with the header absent or set to 0. The documented sample is a PUT to /expense/v1/entries/{id} that fails validation because date is missing while amount is present.

Graph uses the same header. The header guide shows createExpenseReport rejected for an invalid creationDate when validate-only is on. Use that pass before the worker sees a success state.

Submit is a different step from save. POST /reports/{ID}/submit is what starts the Expense Report Event. A screen that stops after creating lines has left a draft. Say “Saved, not submitted” until that call succeeds, then show the business process status Workday returns.

Attachments on createQuickExpense use the Graph multipart form and a File field named in the schema (attachmentContent in Workday’s example). The receipt bytes belong in that request. Leaf’s published design stores no employee HR data at rest, so the screen should not keep a copy of the receipt after Workday accepts it.

A screen that matches the menu it replaces

  1. On open, GET /reports as the worker and list drafts separately from submitted reports.
  2. Load items from GET /expenseItems and currencies from the prompt resource. Do not ship a hardcoded category list.
  3. Create the quick expense or the report with the operation your tenant actually exposes. Run validate-only on the way in.
  4. Add lines with POST /reports/{ID}/lines.
  5. On the submit control, call POST /reports/{ID}/submit and leave the approval chain on the Expense Report Event. The screen does not approve itself.

Prompt values and expense items are tenant data. A warehouse and a corporate card program will not share the same item list. Read them live.

Leaf (coming next) is the place to describe this screen if you want it hosted. Approval of the submitted report still follows the Expense Report Event you already configured.

Questions

Can the screen submit as a shared integration user so workers skip sign-in?

Workday secures GET /reports with a self-service domain. A shared user returns that user’s reports, or an empty set, and the Expense Report Event records the wrong initiator. Leaf calls run as the signed-in employee.

What if validate-only passes and submit fails?

The draft can exist while the business process rejects it. Show Workday’s error and leave the report in the draft list. Do not show a confirmation that names a report id you have not submitted.

Sources checked

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.