How to Email Receipts to ExpensePoint
Send receipts from a verified mailbox to mywallet@expensepoint.com, then review receipt reading, transaction matching, and expense reports.
Read this if…
Use this guide to set up the verified-sender email route and compare capture methods. If the receipt arrived but did not match the expected transaction, use the focused diagnostic.
Related: Troubleshoot an ExpensePoint match
TL;DR
ExpensePoint uses mywallet@expensepoint.com as the Receipt Wallet destination. The sending mailbox must first be linked to the user and marked verified.
The receipt reader supports previews and extraction for PDF, BMP, GIF, JPEG, PNG, TIFF, and email. It reads fields including vendor name, date, and total, then stores the record in the Receipt Wallet.
Corporate card matching can take up to 24 hours after transaction data arrives. A match above the documented threshold still appears for user verification before it becomes an expense in a report.
In This Guide
- 1. Link and verify every sending mailbox
- 2. Prepare receipt evidence for the reader
- 3. Compare email with scanner and direct upload
- 4. Understand reading, matching, and expense creation
- 5. Use Expensent for discovery and a verified-sender handoff
- 6. Finish the expense and report inside ExpensePoint
- 7. Sources checked
- 8. Related reading
- 9. Frequently asked questions
1. Link and verify every sending mailbox
Open the ExpensePoint Receipt Wallet, then Linked Email Addresses. Add the mailbox that will send receipts and complete the confirmation link from the newest verification email. The status in ExpensePoint should show that the address is verified before the first receipt send.
ExpensePoint allows additional sender addresses, but each one follows the same confirmation requirement. An expired link or an older duplicate verification message can fail. Use Resend Verification, open the newest message, and check spam if the confirmation is missing.
The sender is part of delivery
Sending to mywallet@expensepoint.com is not enough. The actual From address must be linked and verified for that ExpensePoint user.
2. Prepare receipt evidence for the reader
ExpensePoint says PDF, BMP, GIF, JPEG, PNG, TIFF, and email support previews and receipt reading, with PDF and JPEG described as the best receipt formats. The reader extracts the vendor name, date, and total amount and can mark an uploaded file as not a receipt.
Expensent currently sends PDF, JPG, and PNG attachments up to 3 MB each. Use the overlap supported by both systems, choose the clearest original evidence, and confirm that vendor, date, total, tax, and currency are readable before sending.
| Receipt input | ExpensePoint treatment | Expensent handoff |
|---|---|---|
| PDF or JPEG/JPG | Preferred ExpensePoint reader formats | Use a clear file up to the current 3 MB attachment limit. |
| PNG | Supported for preview and reading | Use when the complete receipt is legible. |
| BMP, GIF, or TIFF | Supported by ExpensePoint reading | Use another ExpensePoint upload path because Expensent does not currently send these attachment types. |
| Non-receipt file | Can be marked Not a Receipt after reading | Review the source before delivery. |
3. Compare email with scanner and direct upload
Email forwarding fits digital receipts already delivered to a verified mailbox. Direct web upload fits a local file. The mobile receipt scanner fits paper evidence at the time of purchase. All of these methods feed the Receipt Wallet, where the user can create an expense or verify a relationship with transaction data.
Choose the source method that preserves the clearest evidence. Email is not a reason to send decorative images or an entire unrelated thread. Scanner capture is not a reason to discard the original until the reader output and expense report have been checked.
4. Understand reading, matching, and expense creation
Receipt reading happens before transaction matching. ExpensePoint compares available receipt fields such as vendor, date, total, and tax with transactions and other records. Its mobile transaction guide says a result over 80 percent is considered a true match, while also warning that OCR may not read every receipt perfectly.
Corporate card transaction data can arrive later than the receipt. ExpensePoint says match identification can take up to 24 hours. Out-of-pocket receipts do not need to wait for a card feed and can create an expense directly in a chosen report.
Verify Match is a user decision. The screen can show receipt, expense, transaction, and travel booking, and a match needs at least two relevant entities. After confirmation and report assignment, the receipt leaves the unassigned Receipt Wallet list and appears with the expense.
5. Use Expensent for discovery and a verified-sender handoff
Connect the same mailbox that ExpensePoint lists as verified. Expensent can find current and historical receipt emails, show the source and available files, and send selected evidence from that connected mailbox to mywallet@expensepoint.com.
Expensent creates a new message with an Expensent subject and summary body. Selected files are attached, and body-only evidence appears beneath the summary. ExpensePoint controls reading and matching, so test one clear receipt and inspect the exact Receipt Wallet record before approving a recurring rule.
- 1Verify the source mailbox inside ExpensePoint.
- 2Connect that same mailbox to Expensent.
- 3Review and send one clear PDF, JPG, or PNG receipt.
- 4Inspect reader fields, Receipt Wallet state, and any proposed match.
- 5Approve a recurring rule only for the vendor pattern that completed the workflow.
6. Finish the expense and report inside ExpensePoint
Review the receipt image, extracted fields, transaction, expense category, project or GL coding, policy requirements, report, and approver before submission. A receipt stored in the wallet is evidence awaiting a job, not a completed reimbursement or accounting record.
Expensent owns source discovery, review, and approved email delivery. ExpensePoint owns receipt reading, matching, expense creation, report approval, audit trail, and accounting output.
7. Sources checked
These sources were used to verify product behavior, current terminology, and the boundaries between native workflows and Expensent.
9. Frequently asked questions
Can I email receipts to ExpensePoint?
Yes. ExpensePoint documents mywallet@expensepoint.com as the Receipt Wallet destination, but the sending address must be linked and verified first.
What information does ExpensePoint read from a receipt?
ExpensePoint documents vendor name, date, and total amount, and its matching guidance also uses fields such as tax when comparing records.
How long does ExpensePoint card matching take?
ExpensePoint says it can take up to 24 hours to identify matches after the corporate card transaction data is available.
Does emailing a receipt create a finished expense report?
No. The receipt enters the Receipt Wallet. The user still verifies or creates the expense, assigns it to a report, completes required fields, and submits it.
Build a verified ExpensePoint receipt route
Verify the sending mailbox, test one receipt through reading and matching, and approve recurrence only after the complete report path is clear.
Get Started