How to Email Receipts to Workday Expenses

Workday administrator documentation places the Expense Receipt Email Forwarding Address in the Expenses Hub card configuration. That makes the destination tenant-controlled. Do not copy a public example or another employer's address into a production rule.

The University of Virginia publishes its own address, receipts@expensereport.virginia.edu, as an institutional example. It also says the receipt appears as a Quick Expense in its Workday desktop experience. Your organization may use a different address, label, queue, or configuration.

Before sending a receipt, check the email address that will appear as the sender. The University of Virginia instructs employees to add or verify their work or home email in Workday Contact Information before emailing a receipt. Other tenants can apply their own identity and policy rules, so confirm the local requirement with the administrator.

This matters when Expensent routes a receipt from a connected inbox rather than the employee's normal mailbox. Test with the sender identity Workday expects, then keep the source account and result visible in Expensent history.

Send one known receipt to the tenant address and preserve the original message. The University of Virginia's current instructions say an emailed receipt becomes available in Quick Expenses on Workday desktop. Workday's broader product material describes Email-to-Expense as a way to create expense reports from inboxes and other supported collaboration channels.

Treat delivery, ingestion, and review as separate states. A sent message is not proof that Workday created an expense, attached the correct receipt, or made the item ready for submission.

Email is useful when the source receipt is already in a mailbox. Workday also supports tenant-enabled mobile and browser capture, and its product materials describe receipt scanning, card activity, and Email-to-Expense. The University of Virginia lists mobile capture and computer uploads alongside email.

Choose email when preserving the original message helps the audit trail. Choose direct upload when the file is local or the tenant's sender rule does not fit. Both paths still end with Workday review and policy handling.

Connect the inbox where receipts arrive, confirm the tenant address and sender policy with the Workday administrator, and review one controlled receipt in Expensent. Route that message and verify the resulting Workday queue before creating a rule.

Use separate rules when the same inbox contains receipts for different employees, entities, or expense contexts. Keep messages that need a different sender, a local upload, or manual classification in review.

Review the receipt inside Workday, confirm the employee and expense context, and correct any extracted values before submitting. If the receipt cannot be found, stop before resending and use the diagnostic sequence to separate address, sender, file, and queue problems.

Expensent owns inbox discovery, historical catch-up, review, and the approved email handoff. Workday owns tenant ingestion, expense creation, receipt association, policy checks, approvals, and submission.