Automate Receipt Emails to Pleo Without Fetch
Find and route recurring receipt emails from the mailbox linked to the Pleo user, without granting Fetch mailbox access.
By ilios Galil · Founder, Expensent
Published July 18, 2026 · Updated August 3, 2026
Last verified : July 11, 2026
Read this if…
Your team wants recurring receipt emails to reach Pleo without granting Fetch mailbox access.
Pleo email workflow
Preserve user-level ownership: approved receipts should be sent to forward@fetch.pleo.io from the work email linked to that Pleo user.
Keep body-only, portal-only, refund, credit, mixed-thread, and ownership mismatches in a named exception queue.
A sent email is not complete until the user confirms the correct receipt on the intended Pleo expense or records another approved Pleo outcome.
In This Guide
1. Route recurring receipt emails to Pleo
Expensent finds current and historical receipt emails in the mailbox linked to the Pleo user and sends selected documents to forward@pleo.io.
Confirmed sender-and-subject patterns can route new recurring receipts automatically. The sending address must remain linked to the intended Pleo user so Pleo can attribute the document correctly.
Use direct Pleo upload or manual forwarding for occasional receipts that arrive in another mailbox.
2. Treat Pleo as a second control point
An email marked sent is not a completed receipt control. Pleo may associate the evidence with an expense, or the item may require user action in Receipt Inbox. Pleo says Receipt Inbox is private to the user and that finance can see the receipt after the user manually attaches it to an expense.
The Pleo user should compare the intended expense with the receipt evidence and confirm the attachment. Where the result is uncertain, the user should resolve Receipt Inbox or add the receipt directly to the expense. Pleo's current receipt guidance also tells users to review key details when adding a receipt and correct them when needed.
Finance should monitor completion rather than perform invisible matching on the cardholder's behalf. A useful control report shows sent items awaiting Pleo confirmation, Receipt Inbox items awaiting user action, direct uploads completed, and missing-receipt cases still open.
Upstream complete: approved evidence left through the expected linked sender. Pleo complete: the intended expense shows the correct receipt and required details. Exception complete: the user resolved Receipt Inbox, uploaded evidence directly, or followed the missing-receipt process.
3. Sources checked
These sources were used to verify product behavior, current terminology, and the boundaries between native workflows and Expensent.
5. Frequently asked questions
Can a team run a Pleo receipt workflow without Fetch access?
Yes. Expensent can find current and historical receipt emails in the mailbox linked to the Pleo user, send them to forward@pleo.io, and automate future matches from recurring senders. Pleo handles the receipt association after delivery.
Can finance forward every employee's receipts from one mailbox?
Do not assume a shared finance mailbox can stand in for every cardholder. Pleo documents the forwarding sender as the work email linked to the user's Pleo account. Keep a sender-to-user ownership map and route each approved receipt through the corresponding linked work email.
What belongs in the Pleo receipt exception queue?
Queue messages when the sender is not the linked Pleo user, the evidence is body-only or behind a portal, the transaction is unclear, the message is a refund or credit, Pleo did not attach it, or Receipt Inbox still needs the user to choose the expense.
Can I forward a body-only receipt to Pleo?
Pleo documents email-body conversion for Fetch, but the official sources checked for this guide do not separately confirm the same behavior for manual forwarding. Keep body-only messages in review, preserve the original message, and confirm the evidence in Pleo before treating that pattern as approved.
What should happen to a portal-only receipt notice?
Do not forward the notice as if it were the receipt. Assign it to the Pleo user or an approved reviewer to retrieve the actual evidence, then add or forward that evidence through the user-owned Pleo path.
Who is responsible for the final receipt match in Pleo?
The Pleo user owns the final association. Pleo says Receipt Inbox is private to that user until the receipt is manually attached to an expense. Finance can monitor unresolved work, but the operating model must assign the user to confirm the intended expense or follow the company's missing-receipt process.
Send recurring receipt emails to Pleo
Find current and historical receipt emails, route them from the mailbox linked to the Pleo user, and automate future matches from recurring senders.
Get Started