How to Email Receipts to Airwallex Expenses

Airwallex currently documents receipts@expenses.airwallex.com for a person manually forwarding a digital receipt. It documents receipts+forwarding@expenses.airwallex.com inside the Google Workspace and Microsoft 365 administrator rule workflows. Expensent sends selected messages from the connected mailbox, so the manual destination is the appropriate starting point for an approved individual handoff.

Sender identity is part of the match. Airwallex says the email should come from the registered user who owns the relevant card expense, a contact on the company card, or an applicable delegated identity. A finance alias that is not attached to the card can deliver evidence without producing the intended automatic match.

Email fits receipts that already arrive in a registered inbox. Bulk upload is useful for a folder of existing documents. Direct web or mobile attachment fits a known card expense, while reimbursement upload handles out-of-pocket purchases. Each path reaches Airwallex with a different user identity and context.

The administrator-managed Gmail and Outlook rules are broad organization controls. They use keyword conditions and an exclusion for Airwallex system mail to avoid a forwarding loop. Expensent provides a separate reviewed route for selected current or historical messages and does not replace those administrator settings.

Airwallex currently accepts up to ten files on a card expense, with a maximum of 10 MB per file, across common image, PDF, spreadsheet, and Word formats. Expensent has a narrower current attachment route: PDF, JPG, and PNG files up to 3 MB per attachment. Use the overlap supported by both systems for an Expensent handoff.

Prefer the original readable PDF or image. Check that the merchant, date, amount, currency, and tax evidence are visible. Keep the source message until Airwallex has attached the correct receipt and the expense has passed the organization's required review.

Airwallex identifies the uploader from the sender or logged-in user, limits the search to eligible expenses for that identity, and compares signals that include transaction date and amount. A delegate can search within the delegator's eligible scope, and a company-card contact can work with that card's expenses.

When confidence is not high enough, the receipt remains in the receipt inbox. The user can attach it to a card expense manually or use it in a reimbursement report. Users who belong to several Airwallex organizations should also check the default organization selected under Receipt forwarding because unmatched documents are stored there.

Connect the registered mailbox where vendor receipts arrive. Expensent can find current and historical receipt emails, surface the source and available files, and send selected evidence from the connected mailbox to the manual Airwallex receipt destination.

Expensent creates a new message with an Expensent subject and summary body. Selected attachments are added to that message, and body-only evidence appears beneath the summary. It does not preserve the original message unchanged. Test the exact envelope with one receipt because Airwallex owns document reading and matching.

Receipt delivery does not complete the expense. Open the Airwallex record and review merchant, date, amount, currency, tax, category, tracking fields, receipt, policy flags, and any required explanation. Then submit it through the organization's approval workflow.

Keep discovery, matching, and accounting sync as separate checkpoints. Expensent owns inbox discovery and the approved email handoff. Airwallex owns the expense record, policy, approval, reimbursement, and accounting destination.