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.
Today every expense report waits in the manager's inbox for the same click, and the finance team checks receipts by sampling weeks after payment. Policy exceptions are found in the audit, and the traveller has moved on to the next trip.
The app reads each submitted expense report from Workday with its lines, receipts, cost center and policy flags. A report within policy and under 1,000 is approved by rule within seconds and goes straight to payment. A report with a policy exception, a missing receipt or a total above the band goes to the manager with the exception highlighted and the traveller's last 6 months of reports beside it, and then to the expense auditor for the receipts; totals above 5,000 also go to the finance manager. Every decision returns to the Workday business process step, so the report shows the same status in both places.
| Lane | Does |
|---|---|
| Traveller | submits the report in Workday; answers questions and adds receipts on the mobile screen |
| Manager | approves or returns reports with exceptions; sees the cost center's travel budget |
| Expense auditor | checks receipts and policy on the exceptions; approves or returns |
| Finance manager | approves totals above 5,000 and repeated exceptions |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Reports to review | grid of reports waiting with traveller, total, exceptions and days waiting; filter by cost center; open button |
| S02 Report review | lines with amount, item, policy flag and receipt image; the traveller's reports for 6 months; cost center budget used to date; approve, return with a question |
| S03 Traveller mobile | mobile screen: the question asked, add a receipt photo, reply; status of each report |
| S04 Auditor check | exceptions only, with the receipt beside the line; accept or reject per line; note |
| S05 Expense board | reports approved by rule, by manager and by finance; exceptions by type and cost center; days to payment |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Expense report | the report, its lines, status, cost center and policy flags | Workday |
| Employee | the traveller's manager and cost center | Workday |
| Cost center | the owner who sees the travel spend | Workday |
| Budget line | the travel budget line of the cost center | Workday |
| Object | What changes |
|---|---|
| Expense report | approval, return or rejection written to the Workday business process step with the note; the report moves to payment or back to the traveller |
Start: An expense report submitted in Workday whose lines carry a policy flag, or whose total is above 1,000.
# start criterion, in canonical fields; each system page shows it in that system's fields
{expense.status} = 'submitted' and ({expense.policy} = 'exception' or {expense.amount} > 1000)| Step | Moves when |
|---|---|
| Report read | lines, receipts and policy flags read; reports within policy and under 1,000 approved by rule |
| Manager review | exception shown with the receipt; manager approves, returns or asks the traveller |
| Auditor check | receipts and policy confirmed per line; rejected lines returned with the reason |
| Finance approval | totals above 5,000 or a third exception in 6 months approved by the finance manager |
| Returned to Workday | decision written to the business process step; report paid or back with the traveller |
| Component | Trigger → action → outcome |
|---|---|
| rul_auto_approve | on report read → check every line against policy and the 1,000 band → approve in Workday and record the rule that applied |
| btn_ask_traveller | on click → send the question to S03 → pause the clock until the reply or the receipt arrives |
| btn_approve | on click → call the Workday approval operation for the business process step → store the Workday ID, refresh S01 |
| grd_exceptions | on load → read the traveller's reports for 6 months → show a repeat flag when the same exception appears 3 times |
| Step | Time limit and escalation |
|---|---|
| Manager review | 2 working days, then the manager is reminded and the report is shown to the manager's manager |
| Traveller reply | 5 working days, then the report is returned |
| Auditor check | 2 working days, then the finance manager is copied |
Names, places and figures are illustrative; the pattern is the catalogue's.
On a Monday morning the app read 640 reports submitted over the weekend across the European sales teams, approved 512 of them by rule before 08:00, and put 128 in front of 41 managers with the exceptions marked. Ravi, a manager in Zurich, saw a 1,900 hotel line over the city cap with a conference flag, asked for the conference agenda at 08:20, got the photo from the traveller's phone at 08:45 and approved by 09:00. The auditor cleared the receipts by 11:00, Workday showed the report approved a few seconds later, and payment ran on Wednesday.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Other systems connect through the same handlers; see how SmartApps connect.
About 30 minutes to a first running screen on your live rows, and 3 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.
Any of Workday, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.
Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
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.