How to Email Receipts to Sage Expense Management

Sage Expense Management does not publish one universal Magic Mail address for every account. Each user has a unique destination. In the web app, open Settings, choose Preferences, and scroll to Magic Mail. In the mobile app, open Settings and choose Magic Mail. Copy the exact address shown for the person whose expense should be created or updated.

Forward the receipt or invoice email to that address. Sage Expense Management says Magic Mail extracts details such as amount, date of spend, and merchant. When an eligible matching expense exists, it attempts to attach the receipt. When no match is found, the normal result is a new Incomplete expense in Expenses > Unreported, not a completed or approved report.

That distinction prevents a common operating mistake. “The email was sent” means only that the upstream mailbox created an outbound message. “The expense exists” means Magic Mail ingested it. “The receipt matched” means Sage Expense Management associated it with an eligible corporate-card expense. “The expense is ready” means a person completed mandatory fields and reviewed the result. Track those states separately.

The product name can be confusing during setup. Fyle is now Sage Expense Management, but current help pages and app URLs still use the fylehq.com domain, and older articles may refer to Fyle or receipts@fylehq.com. Use the current Sage Expense Management user interface as the destination source of truth rather than copying a generic address from an old blog post.

The cleanest first test comes from the email address the user employs to sign in to Sage Expense Management. Current registered-sender guidance still documents forwarding receipts from that login address, even though Magic Mail is now the more useful user-specific destination. Starting with the known account address removes one variable from the first test.

For receipts that arrive in a personal address, secondary business inbox, or shared mailbox, Sage Expense Management documentation is inconsistent. The current Profile and secondary-inbox article says to add the address under Preferences, send a verification link, and complete verification. A newer Magic Mail article says users can forward from a personal address without repeating that requirement. These statements should not be flattened into a promise that every arbitrary sender works.

Use the conservative procedure: add the exact secondary inbox in Preferences when that control is available, complete any verification request, and then send one receipt from that address. If a shared alias rewrites the From address, verify the address that actually appears on the outbound message rather than the friendly address employees see in their mail client.

Keep user ownership explicit. A company may have several people with different Magic Mail addresses and several inbound receipt mailboxes. Document a mapping of sender, Magic Mail owner, and expected Sage Expense Management user. Sending a receipt to a colleague's Magic Mail address can create a valid-looking expense under the wrong owner, which is harder to diagnose than a rejected message.

If Gmail automatic forwarding is planned, complete the sender test first. The beta Gmail workflow introduces a second setup event: Google sends a forwarding verification message to Magic Mail, and Sage Expense Management says it returns that message to the Gmail inbox so the user can approve it. Do not troubleshoot filter syntax until the destination and sending identity have both succeeded manually.

Sage Expense Management supports several capture paths, and they solve different problems. Magic Mail is the natural route for digital receipts and invoices already present in an inbox. The Gmail and Outlook integrations let a user create an expense from an open email. Mobile capture is designed for paper receipts. Web upload fits files already saved on a computer. Text and Slack can fit employees who work primarily in those channels when the organization has enabled them.

Using every method at once is not a mature workflow. It can create duplicate expenses and make responsibility unclear. Pick a default for each document source, then define exceptions. For example, send recurring SaaS invoices through a reviewed inbox rule, use mobile capture at restaurants, and use web upload for a multi-page PDF that finance already downloaded.

Choose a recent, readable receipt with one merchant, one total, and one transaction context. Avoid a bundled marketplace digest, an encrypted attachment, a portal notification with no receipt evidence, or a thread containing several unrelated documents. A clean test makes it possible to identify whether a problem belongs to delivery, extraction, matching, or required fields.

Forward the original message from the intended mailbox to the copied Magic Mail address. Preserve the attachment and useful message body. Do not change the total, merchant, or date in the forwarded email to make it resemble the card charge. The downstream system should receive the original evidence, and any correction should happen in the expense review record with an audit trail.

Open Expenses > Unreported after processing. If the receipt found an eligible match, inspect that expense and its History. If a new Incomplete expense was created, open it and review the extracted amount, date, merchant, payment mode, category, project, cost center, and other mandatory fields. Fill only information you can support, save it, and then add it to the correct report when ready.

Keep the original source email until the test is fully reviewed. A successful outbound send is not proof that the document attached to the correct expense. The source message is needed if OCR extracted a wrong total, the sender mapping placed it under the wrong user, or several similar card charges caused an ambiguous result.

Record the result in a small operating note: sender address, Magic Mail owner, receipt merchant, sent time, whether an expense was created, whether it matched, and what a person changed. That note becomes the evidence for deciding whether a recurring rule is safe. One success proves the specific pattern, not every message from the vendor.

Sage Expense Management currently documents Gmail automatic forwarding to Magic Mail as a beta workflow. Google sends a forwarding verification email to the Magic Mail destination, Sage Expense Management returns it to the Gmail inbox, and the user follows the confirmation link. After verification, Gmail filters can forward matching future messages.

Use narrowly defined filters. Sage Expense Management warns that forwarding without filters can send every email to Magic Mail and create spammy expenses. A keyword such as “payment” or “order confirmation” is not sufficient proof that a message contains a usable receipt. Combine a stable sender with a specific subject or attachment condition, then inspect early results.

Native Gmail forwarding is a strong option for a small set of predictable vendors and a user who needs only future mail. It does not provide historical catch-up, and it can be harder to review borderline messages before delivery. Outlook users need a different route, and a shared finance team may need more visibility into what was discovered versus what was actually sent.

Expensent uses a connected Gmail or Outlook mailbox to surface likely receipts and invoices for review. Users can route selected messages, scan older mail, and create rules from a reviewed sender plus subject pattern. This is an upstream workflow, not an improvement to Magic Mail extraction or matching. The connected sending mailbox must still map safely to the intended Sage Expense Management user.

Choose the smallest automation that satisfies the job. Use manual Magic Mail forwarding for low volume, a Gmail filter for a stable future-only pattern, and Expensent when review, Outlook coverage, historical catch-up, or a consolidated exception view matters. Keep portal-only notices and ambiguous order emails out of automatic routes regardless of the tool.

The web app supports manual expense creation and receipt upload. Sage Expense Management currently documents JPG, PNG, and PDF as common web-upload formats, with the ability to add multiple receipts to one expense and rotate images. Treat that as web-app guidance. It does not prove that every email channel accepts the same file set, size, encryption, or multiple-document behavior.

The mobile app fits paper receipts captured at the point of purchase. The user can photograph the receipt, let the product extract available details, correct orientation, add mandatory fields, and save. This path avoids emailing a photograph to yourself first. It also makes ownership explicit because the employee is already signed in.

Text-message capture is useful when the organization has enabled it and employees receive card-spend prompts. Users can send a receipt image and reply to prompts for coding fields. It is a different workflow from Magic Mail: the channel and user identity are already tied to text settings, while Magic Mail relies on email routing and the destination owner.

The Gmail and Outlook integrations are suited to one-off inbox submissions where the user is already reading the receipt email. They create an expense from the open message without requiring a separate forward. They may be preferable to Magic Mail for employees who do not want a saved destination contact or for messages that deserve manual confirmation.

Slack can create expenses and accept receipt attachments when the organization has connected it. Use it for teams already governed in Slack, not as a reason to duplicate an email submission. A receipt should have one intentional entry route. If employees sometimes use Slack and sometimes Magic Mail for the same vendor, add a review step for potential duplicates before reports are submitted.

Magic Mail can also be entered directly as the receipt email for supported merchant flows, such as the currently documented Uber Business Profile example and the beta point-of-sale use case. Direct delivery reduces inbox handling, but it also removes the chance to review the source message first. Limit it to business profiles or merchants where ownership and expense purpose are reliably known.

Receipt delivery and receipt matching are separate. Sage Expense Management documents email or text matching against corporate-card expenses. It does not apply that receipt-matching path to reimbursable, mileage, or per-diem expenses. If the document belongs to one of those workflows, create or complete it through the appropriate method instead of waiting for a card match that cannot occur.

For a receipt to attach automatically, the candidate corporate-card expense must be in Incomplete or Complete state. The documented criteria use amount, date, merchant similarity, and the number of possible matches. Amounts must match exactly, except Sage Expense Management allows a difference within 20 percent for food, lodging, or taxi categories. Dates must fall within one day, and merchant text must reach at least 40 percent similarity.

When several expenses could match, Sage Expense Management says it does not attach the receipt to any of them. Instead, it creates a new expense. That behavior is protective: choosing among ambiguous charges would risk attaching evidence to the wrong transaction. The new item should be treated as an exception that needs human ownership, not as proof that Magic Mail failed.

A separate auto-merge flow exists for manual expenses and card transactions. It uses different criteria, including exact amount and a date within five days, and it has state and history restrictions. Do not combine the five-day merge window with the one-day receipt-matching window in a team procedure. They answer different questions.

OCR is also not an accounting decision. A forwarded receipt may produce extracted values that look plausible but are wrong because of tips, taxes, foreign currency, long itemized receipts, image quality, or merchant branding. Current community discussion after the Fyle-to-Sage transition includes complaints about glitchy receipt scanning, but that anecdote does not establish a universal outage. Review the actual record and documented criteria before escalating.

Sage Expense Management remains responsible for required fields, payment mode, policies, reports, approvals, reimbursement, and accounting export. Expensent can preserve and route usable inbox evidence, but it cannot change a card transaction, select a candidate match, approve an expense, or guarantee the downstream result.

For recurring SaaS invoices, begin with one current invoice and confirm that the source message contains an attached or body-based document Sage Expense Management can use. Route it to the correct user's Magic Mail address, review the Incomplete or matched result, and then save a narrow sender-plus-subject rule. Keep renewal notices, failed-payment alerts, and usage summaries out of the rule unless they contain the actual invoice or receipt.

For travel bookings, distinguish a reservation confirmation from a final receipt. Airlines, hotels, and ground transportation can send several messages with different amounts as plans change. Route the final evidence and compare it with the posted card charge. The documented one-day receipt-matching window and merchant similarity can be affected by settlement dates and processor names, so unmatched travel receipts deserve review rather than repeated forwarding.

For employee personal spending, use the reimbursement workflow rather than expecting Magic Mail receipt matching to attach to a corporate-card expense. The receipt can still help create an expense, but the employee must choose the correct payment mode, complete required fields, add it to a report, and follow the organization's approval and reimbursement process.

For shared finance inboxes, map every outbound sender or alias to the intended Sage Expense Management user before routing. If the organization wants expenses to belong to individual cardholders, one shared Magic Mail destination is not a substitute for that ownership model. Use explicit routing rules, preserve the source sender, and keep exceptions visible to finance.

For historical catch-up, search and review in smaller batches. Old messages may refer to refunded orders, canceled subscriptions, or transactions already documented another way. Send one vendor pattern at a time, check for new Incomplete expenses and duplicates, and retain a batch note until finance confirms the result.

For direct merchant delivery to Magic Mail, use a business profile whenever the merchant supports one. Do not replace a personal receipt email with Magic Mail if that would mix private and business purchases. Direct delivery is efficient only when the merchant context, user ownership, and business purpose are already controlled.

Start by asking whether an expense or receipt record appeared in Sage Expense Management. If nothing appeared, check the exact Magic Mail address, owner, sending address, secondary-inbox setup, forwarded evidence, and processing time. Do not investigate amount or merchant matching until intake exists.

If a new Incomplete expense appeared, Magic Mail intake worked but no eligible unique match was found. Confirm whether the intended target is a corporate-card expense in Incomplete or Complete state. Then compare amount, one-day date window, merchant similarity, and competing candidates. Complete required fields only after deciding whether the new item should remain separate.

If the receipt attached to the wrong expense, open History and preserve the source email before changing anything. Compare the competing transactions, user ownership, amount, date, merchant, and payment mode. Use Sage Expense Management's current unlink, merge, or support workflow rather than sending the same receipt again.

If the expense exists and the fields are wrong, correct them from the original evidence. Note whether the issue was image clarity, a tip or tax line, foreign currency, merchant text, or a bundled document. Repeated forwarding usually creates more records without improving the underlying evidence.

If the matching criteria are satisfied and the behavior still differs from current help, collect the expense URL or identifier, user, sender, Magic Mail destination owner, sent time, source document, candidate card transaction, History events, and screenshots. That evidence lets Sage Expense Management support distinguish account configuration, ingestion, extraction, and matching issues.