Workday Emailed Receipt Not in Quick Expenses? Check the Intake Path
Trace the tenant address, sender identity, attachment, ingestion state, and Workday queue before sending the receipt again.
Read this if…
Use this guide when a receipt was sent to Workday but is not visible in the expected queue. Workday community discussions about multi-address email ingestion and forwarding loops make the intake path worth checking before OCR or policy diagnosis.
Related: Open the Workday setup guide
TL;DR
Confirm the current tenant-specific address first. A public or employer-specific example cannot prove the destination for your Workday environment.
Check the sender against Workday Contact Information or the local policy, then retest with one clear PDF, JPEG, JPG, or PNG if those formats are supported.
Compare the sent message with Quick Expenses or the tenant queue. Do not resend repeatedly when the message may be waiting for ingestion or associated with another employee context.
In This Guide
1. Confirm the exact tenant destination
Workday administrator documentation puts the Expense Receipt Email Forwarding Address in tenant Expenses Hub settings. Compare the sent message with the address currently shown for your organization. Do not assume that an address from an employer guide, search result, or another Workday tenant still applies.
The University of Virginia's receipts@expensereport.virginia.edu address is a useful example of institution-specific setup, not a general Workday destination.
2. Check sender identity and forwarding behavior
Verify the From address and compare it with the employee's Workday Contact Information or your organization's documented sender rule. A connected inbox can preserve the original message while changing the sender that Workday evaluates, so confirm what the delivered message actually contains.
A recent Workday community discussion describes difficulty ingesting email from multiple addresses and warns about forwarding loops. That discussion concerns Workday email ingestion broadly, not a universal receipt defect, but it supports checking aliases, rules, and loops before resending a receipt.
| Observed result | What it suggests | Next action |
|---|---|---|
| No sent message | The source rule or Expensent handoff did not run. | Check the source history and destination before checking Workday. |
| Sent to an old address | The tenant destination changed or the saved rule is stale. | Copy the current address and run one controlled test. |
| Sent from an unrecognized address | Workday may not associate the receipt with the intended employee. | Verify Contact Information or the local sender policy. |
| Receipt in another queue | The tenant's routing or employee context differs from the expected view. | Ask the Workday administrator to trace the ingestion record. |
3. Retest with one supported attachment
Use one clear receipt and preserve the original message. The University of Virginia lists PDF, JPEG, JPG, and PNG for computer uploads and says emailed receipts become Quick Expenses in its tenant. Other organizations can apply different limits, so treat those formats as a controlled test rather than a guarantee for every Workday customer.
If direct upload works but email does not, the file and employee context are useful comparison points. Focus next on the address, sender, forwarding rule, and tenant ingestion status.
- Confirm the message was sent and record its timestamp.
- Compare the recipient with the current tenant address.
- Compare the From address with Workday Contact Information.
- Test one legible file and avoid multiple resends.
- Check Quick Expenses and any tenant-specific receipt queue.
4. Distinguish arrival from downstream visibility
If the tenant has a processing delay or a separate ingestion queue, a sent message may not be visible in Quick Expenses immediately. Ask the administrator which queue and status represent an accepted receipt in your environment. Do not treat a missing screen item as proof that the email was rejected.
If the receipt appears but the merchant or employee is wrong, stop treating the issue as delivery failure. Correct the Workday expense context and investigate sender association or extraction separately.
5. Run one clean recovery and preserve the trace
After correcting the destination, sender, or file, run one controlled test and record the resulting Workday queue or expense ID. Remove overlapping forwarding rules that can create loops or duplicate submissions.
Give the administrator the original message, From and To addresses, attachment details, timestamp, source rule history, and the queue you checked. This is more useful than sending the same receipt repeatedly.
6. Sources checked
These sources were used to verify product behavior, current terminology, and the boundaries between native workflows and Expensent.
8. Frequently asked questions
Why is my Workday receipt not in Quick Expenses?
Check the current tenant address, sender identity, attachment, forwarding rule, processing queue, and tenant-specific screen. Quick Expenses is the documented view for the University of Virginia example, but your organization can use a different queue.
Can I use the Workday receipt address from another organization?
No. Workday receipt addresses are tenant or organization specific. Ask your administrator for the current address.
What sender should I use?
Use the sender identity recognized by your Workday tenant. The University of Virginia requires the address to be listed in Workday Contact Information; confirm your organization's rule.
Should I resend the receipt several times?
No. Preserve the original trace, check the queue and process state, correct the root cause, and run one controlled recovery test.
Can Expensent fix a Workday ingestion problem?
Expensent can show source history and control the approved handoff. Workday remains responsible for tenant ingestion, employee association, expense creation, and queue visibility.
Trace the Workday intake once
Keep the tenant address, sender, source message, and Workday queue visible so one controlled recovery explains what happened.
Get Started