Brex Receipt Email Addresses: Which One Should You Use?

Brex has more than one receipt email path because manual receipt forwarding and mailbox-rule forwarding are not the same workflow. Current Brex support documentation tells users to forward online expense receipts to receipts@brex.com when they want Brex to match a receipt to an expense. The same receipt article documents receipts+forwarding@brex.com inside the Gmail and Outlook forwarding-rule setup.

That distinction matters because the question is not only "what is the Brex receipt email address?" It is "which sending path am I using?" A one-off receipt that an employee is forwarding from their own inbox is different from a Gmail filter, a Google Workspace add-on, or an Outlook rule forwarding future messages on a condition.

Use receipts@brex.com for the manual workflow Brex documents and receipts+forwarding@brex.com when following its Gmail or Outlook rule instructions. This is an intended-use distinction, not proof that a one-off send to the plus-address will fail. In either workflow, Brex says the sender must be associated with the Brex account or account copilot.

Choose the address by sending workflow. The destination alone does not prove the receipt will match; sender eligibility, receipt quality, transaction age, and Brex account settings still matter.

Use receipts@brex.com when the employee has an online-expense receipt email in hand and wants Brex to match it to an expense. Brex says the receipt can be in the email body or an attachment.

Use receipts+forwarding@brex.com when you are configuring Gmail or Outlook to forward selected receipt emails by rule. Brex documents this address in the Gmail forwarding setup and the Outlook rule setup. This path is about mailbox automation, so the filter or rule conditions matter as much as the destination.

Use Brex's Google Workspace add-on instead of a Gmail forwarding rule when your organization wants its admin-managed Gmail collection path. Brex says admins can install the add-on for Gmail accounts not associated with Brex, but receipts from those accounts will not be delivered.

Do not apply Brex's general upload-format guidance automatically to every email route. The receipt-forwarding instructions for receipts@brex.com say the receipt may be in the email body or an attachment. Brex's separate file-type article covers uploading and storing XML or CFDI files through the dashboard or app and says those files can also be forwarded, but it does not establish that Gmail or Outlook rules using receipts+forwarding@brex.com support the same formats in the same way.

For an ordinary emailed receipt, preserve the receipt in the message body or attach the document the vendor supplied. For XML or CFDI documentation, use the direct expense upload workflow Brex documents or confirm the forwarding route for your account rather than assuming parity with automated mailbox rules.

For normal card receipt forwarding, current Brex documentation says to forward the email receipt to receipts@brex.com so Brex can try to match it to an existing expense.

Brex says the receipt can be part of the email body or an attachment. Preserve a clear receipt rather than a long thread or a bundle of unrelated files so you can diagnose matching problems more easily.

Brex also documents typo aliases for this path: receipt@brex.com, reciepts@brex.com, and reciept@brex.com. Standardize employee instructions on receipts@brex.com rather than an alias.

Brex says only receipts less than two months old match automatically. Separately, when Brex auto-validation is enabled, it considers a receipt validated if at least two of merchant, amount, and purchase date match the expense. Brex says validation is best-effort and can vary with image quality, merchant data, and account settings.

In Brex's current support article, receipts+forwarding@brex.com appears in the Gmail and Outlook forwarding-rule sections. Use it when following those setup instructions.

For Gmail, Brex says to add receipts+forwarding@brex.com as a forwarding address, then import Brex's suggested filters or create a filter from an example email and select Forward it to that address. Brex also says users receive an email confirmation when Brex has confirmed the forwarding request.

For Outlook, Brex says to create a rule, choose the relevant email conditions, and forward matching messages to receipts+forwarding@brex.com. That can help with recurring vendors, but it is also where mistakes become quiet: a broad rule can send order confirmations, shipping updates, cancellations, or portal notices that are not clean receipts.

The automated forwarding address is not a substitute for rule design. A good forwarding rule starts from a known receipt pattern: same sender, consistent subject pattern, and receipt content that Brex can use. A bad rule starts from a broad keyword like "order" or "payment" without checking what else that sender sends.

The sender address is one of the most important details in this workflow. Brex says email receipts must be forwarded from an email address associated with your Brex account or your account copilot. That means the "from" address can matter as much as the "to" address.

A receipt may be sent to the documented Brex address from a shared finance inbox, vendor alias, forwarding service, or accounting-firm mailbox that Brex does not associate with the employee or account copilot. In that case, sender eligibility is the problem to investigate.

If you plan to use a shared inbox, prove the path with one clean receipt before you document it for the team. Confirm the sender that Brex sees, the destination used, the employee expense you expected it to match, and whether the receipt appears attached to that expense. If you cannot prove the sender association, use an employee-associated mailbox or manual dashboard attachment instead.

Brex memo behavior is a separate issue from receipt delivery, but it often comes up in the same search. Current Brex memo documentation says that if you are already attaching a receipt to an expense by email, you can include a memo in the same email by typing memo: somewhere in the email body, then typing the memo text.

The safe way to use this is narrowly: add memo text when you are sending a receipt email that should attach to an expense. Do not treat memo: as a general command language for Brex email. Brex also supports memos in the dashboard, app, push notifications, SMS notifications, auto-memo rules, and memo suggestions, depending on setup and capability.

If memos duplicate across expenses, Brex documents a specific edge case: multiple expenses with the same vendor can inherit uploaded receipts or memos when the merchant reuses a single authorization code. That is another reason to test before forwarding a batch of similar transactions from the same vendor.

When a Brex receipt does not show up, do not start by changing addresses randomly. Start by classifying the failure. Did the email bounce? Did Brex confirm a forwarding request? Did the receipt fail to appear on the expected transaction, or did it attach and then fail validation? Those are different problems. Brex says emailed receipts are visible only after a successful match, so do not expect a separate unmatched-email queue.

Do not infer failure from the plus-address alone. Brex documents receipts+forwarding@brex.com for Gmail and Outlook rules but does not say that a one-off message to it will fail. For future sends, use the destination Brex documents for your workflow. For a message already sent, check whether it matched before sending a duplicate.

Check sender association next, then receipt age and whether the receipt appears on the expected expense. Automatic matching is limited to receipts less than two months old. If Brex matched the receipt but auto-validation failed, review the merchant, amount, purchase date, and image quality. Brex says validation is best-effort and account settings can affect it.

Finally, inspect the email rule itself. If the rule captures order updates, refund notices, travel itinerary changes, or portal alerts, Brex may receive messages that are not clean receipts. Narrow the conditions or move those messages into a review workflow before forwarding.

Brex can process receipts after they arrive; Expensent helps make sure the right inbox receipts get there. That is the useful boundary. Expensent does not replace Brex Expense, Brex Assistant, policy rules, approvals, receipt validation, accounting exports, or card administration.

The gap is upstream of Brex. Receipts land in employee inboxes, shared inboxes, forwarded aliases, and old email history. Gmail and Outlook rules work for some recurring patterns, but they are future-facing and rule-driven. They do not give a finance user much review context before messages leave the inbox.

Expensent helps review and route the right inbox receipts before Brex processes them. Users can surface likely receipt emails, review ambiguous cases, forward selected items to the Brex destination they configure, and create sender-and-subject rules from examples they have already checked. That is strongest for email-heavy receipt workflows and historical catch-up.

Use Brex for the downstream expense workflow. Use Expensent when the recurring pain is the handoff: employees forget to forward, old receipts are still in email, a broad filter forwards noisy messages, or the team needs more visibility before receipt emails are sent to Brex.

Before you publish internal instructions, test the workflow with the exact mailbox and destination you want employees to use. Use one recent receipt that clearly matches a Brex card transaction. Send it from the real sender address. Then check whether it attaches to the expected transaction and, where enabled, whether Brex validates it. If it fails to appear, use the manual attachment fallback instead of looking for a separate unmatched emailed receipt.

For Gmail or Outlook rules, test one vendor first. Pick a vendor that sends consistent receipt emails and few non-receipt messages from the same sender. Do not start with travel platforms, marketplaces, or vendors that send shipping updates, cancellation notices, credits, and receipts from the same address.

For historical cleanup, do not rely on future-only rules. Review old inbox receipts, sort out portal notices and non-receipt messages, and forward selected items that are still useful. Remember that current Brex docs say receipts less than two months old match automatically; older items may require manual attachment.