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.

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.

Best for: an employee manually forwarding a card receipt email. Works with: receipt content in the email body or supported receipt attachments, based on current Brex docs. Watch for: sender eligibility, receipt age, and whether the receipt appears on the expected expense.

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.

Best for: future Gmail or Outlook receipt emails that follow a narrow, repeatable pattern. Risk: broad rules can forward messages that are not usable receipt proof. Safer rollout: test one vendor pattern, check the first few results in Brex, then expand.

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.

Expensent finds current and historical receipt emails and sends selected documents from an eligible mailbox to the Brex destination that matches the sending method.

Confirmed sender-and-subject patterns can route new recurring receipts automatically. Brex then handles attachment, matching, verification, and policy.